juan/autotest
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

cambios profundos con grok

Browse Source
This commit is contained in:
juan
2026-05-26 00:42:42 +02:00
parent ee8cfa03ea
commit 19ea13dadd
99 changed files with 1447 additions and 2597 deletions
Download Patch File Download Diff File Expand all files Collapse all files
testcases/core/features/core-features-check-backward_compatibility_of_new_features.yaml
+51
View File
@@ -0,0 +1,51 @@
# Updated via Autotest Editor - 2026-05-25T21:52:11.908Z
# Source of truth: this YAML file
id: core-features-check-backward_compatibility_of_new_features
module: core
group: core-features
title: >-
Verify new features are backward-compatible with existing configurations and older endpoint
firmware
description: >-
Verify new features are backward-compatible with existing configurations and older endpoint
firmware
priority: Medium
tags: []
references: []
dependencies:
- label: Admin Portal
value: https://pbx.local:4443 (configure via $BASE_URL)
- label: Repository URL
value: ${BASE_URL}/downloads or $REPO_URL
- label: Protocol
value: HTTPS (admin portal) + optional SSH/CLI
- label: Credentials
value: Admin user with sufficient privileges (portal + SSH where needed)
- label: Test Data
value: Clean test tenant or lab PBX instance (recommended isolated environment)
preconditions: []
postconditions: []
steps:
- action: Open admin portal or repository URL in browser context
expected: ''
- action: Execute the main verification or configuration action described in the test
expected: ''
- action: Capture evidence (screenshot, log, API response)
expected: ''
- action: Assert expected outcome
expected: ''
automation_status: partial
file: tests/core/features.spec.ts
custom_fields:
original_action: check
partialNotes: >-
Configuration import checks automated; functional compatibility with older endpoints requires
manual testing
automatable:
- Portal UI configuration and verification steps (already partially automated)
- Data extraction and reporting of current settings
notYet:
- >-
Configuration import checks automated; functional compatibility with older endpoints requires
manual testing
testcases/core/features/core-features-check-provisioning_changes_for_new_features.yaml
+41
View File
@@ -0,0 +1,41 @@
# Updated via Autotest Editor - 2026-05-25T21:52:11.922Z
# Source of truth: this YAML file
id: core-features-check-provisioning_changes_for_new_features
module: core
group: core-features
title: Verify provisioning settings for new features are accessible in the admin portal
description: Verify provisioning settings for new features are accessible in the admin portal
priority: Medium
tags: []
references: []
dependencies:
- label: Admin Portal
value: https://pbx.local:4443 (configure via $BASE_URL)
- label: Repository URL
value: ${BASE_URL}/downloads or $REPO_URL
- label: Protocol
value: HTTPS (admin portal) + optional SSH/CLI
- label: Credentials
value: Admin user with sufficient privileges (portal + SSH where needed)
- label: Test Data
value: Clean test tenant or lab PBX instance (recommended isolated environment)
preconditions: []
postconditions: []
steps:
- action: Open admin portal or repository URL in browser context
expected: ''
- action: Execute the main verification or configuration action described in the test
expected: ''
- action: Capture evidence (screenshot, log, API response)
expected: ''
- action: Assert expected outcome
expected: ''
automation_status: automated
file: tests/core/features.spec.ts
custom_fields:
original_action: check
automatable:
- Full end-to-end execution via Playwright against the admin portal UI
- Navigation, form interaction, and assertions are scriptable
notYet: []
testcases/core/features/core-features-write-analysis_of_new_security_risks.yaml
+42
View File
@@ -0,0 +1,42 @@
# Updated via Autotest Editor - 2026-05-25T21:52:11.924Z
# Source of truth: this YAML file
id: core-features-write-analysis_of_new_security_risks
module: core
group: core-features
title: Identify, analyse, and document new security risks introduced by features in this release
description: Identify, analyse, and document new security risks introduced by features in this release
priority: Medium
tags: []
references: []
dependencies:
- label: Admin Portal
value: https://pbx.local:4443 (configure via $BASE_URL)
- label: Repository URL
value: ${BASE_URL}/downloads or $REPO_URL
- label: Protocol
value: HTTPS (admin portal) + optional SSH/CLI
- label: Credentials
value: Admin user with sufficient privileges (portal + SSH where needed)
- label: Test Data
value: Clean test tenant or lab PBX instance (recommended isolated environment)
preconditions: []
postconditions: []
steps:
- action: Open admin portal or repository URL in browser context
expected: ''
- action: Execute the main verification or configuration action described in the test
expected: ''
- action: Capture evidence (screenshot, log, API response)
expected: ''
- action: Assert expected outcome
expected: ''
automation_status: manual
file: tests/core/features.spec.ts
custom_fields:
original_action: write
manualReason: Security risk analysis requires expert threat modelling, source code review, and human judgment
automatable:
- Most UI-driven configuration and verification steps via Playwright
notYet:
- Security risk analysis requires expert threat modelling, source code review, and human judgment
testcases/core/features/core-features-write-summary_of_each_new_feature_per_release.yaml
+41
View File
@@ -0,0 +1,41 @@
# Updated via Autotest Editor - 2026-05-25T21:52:11.927Z
# Source of truth: this YAML file
id: core-features-write-summary_of_each_new_feature_per_release
module: core
group: core-features
title: Extract and record a summary of each new feature included in this release
description: Extract and record a summary of each new feature included in this release
priority: Medium
tags: []
references: []
dependencies:
- label: Admin Portal
value: https://pbx.local:4443 (configure via $BASE_URL)
- label: Repository URL
value: ${BASE_URL}/downloads or $REPO_URL
- label: Protocol
value: HTTPS (admin portal) + optional SSH/CLI
- label: Credentials
value: Admin user with sufficient privileges (portal + SSH where needed)
- label: Test Data
value: Clean test tenant or lab PBX instance (recommended isolated environment)
preconditions: []
postconditions: []
steps:
- action: Open admin portal or repository URL in browser context
expected: ''
- action: Execute the main verification or configuration action described in the test
expected: ''
- action: Capture evidence (screenshot, log, API response)
expected: ''
- action: Assert expected outcome
expected: ''
automation_status: automated
file: tests/core/features.spec.ts
custom_fields:
original_action: write
automatable:
- Full end-to-end execution via Playwright against the admin portal UI
- Navigation, form interaction, and assertions are scriptable
notYet: []
testcases/core/features/core-features-write-ui_ux_and_admin_portal_changes_validation.yaml
+41
View File
@@ -0,0 +1,41 @@
# Updated via Autotest Editor - 2026-05-25T21:52:11.930Z
# Source of truth: this YAML file
id: core-features-write-ui_ux_and_admin_portal_changes_validation
module: core
group: core-features
title: Capture and record all UI/UX changes in the admin portal for this release
description: Capture and record all UI/UX changes in the admin portal for this release
priority: Medium
tags: []
references: []
dependencies:
- label: Admin Portal
value: https://pbx.local:4443 (configure via $BASE_URL)
- label: Repository URL
value: ${BASE_URL}/downloads or $REPO_URL
- label: Protocol
value: HTTPS (admin portal) + optional SSH/CLI
- label: Credentials
value: Admin user with sufficient privileges (portal + SSH where needed)
- label: Test Data
value: Clean test tenant or lab PBX instance (recommended isolated environment)
preconditions: []
postconditions: []
steps:
- action: Open admin portal or repository URL in browser context
expected: ''
- action: Execute the main verification or configuration action described in the test
expected: ''
- action: Capture evidence (screenshot, log, API response)
expected: ''
- action: Assert expected outcome
expected: ''
automation_status: automated
file: tests/core/features.spec.ts
custom_fields:
original_action: write
automatable:
- Full end-to-end execution via Playwright against the admin portal UI
- Navigation, form interaction, and assertions are scriptable
notYet: []