diff --git a/server/lib/load-testcases.js b/server/lib/load-testcases.js index cf34f69..a701af5 100644 --- a/server/lib/load-testcases.js +++ b/server/lib/load-testcases.js @@ -48,10 +48,18 @@ function yamlToLegacy(yamlTest) { description: yamlTest.description || yamlTest.title || '', status: yamlTest.automation_status || 'manual', file: yamlTest.file || '', - steps: (yamlTest.steps || []).map(s => s.action || s), - automatable: cf.original_automatable || [], - notYet: cf.original_notYet || [], - dependencies: cf.original_dependencies || [], + steps: (yamlTest.steps || []).map(s => { + if (typeof s === 'string') { + return { action: s, expected: '' }; + } + return { + action: s.action || s, + expected: s.expected || '' + }; + }), + automatable: yamlTest.automatable || cf.original_automatable || [], + notYet: yamlTest.notYet || cf.original_notYet || [], + dependencies: yamlTest.dependencies || cf.original_dependencies || [], }; // Preserve extra fields that the old data sometimes had diff --git a/server/scripts/populate-expected-results.js b/server/scripts/populate-expected-results.js new file mode 100644 index 0000000..8ec156a --- /dev/null +++ b/server/scripts/populate-expected-results.js @@ -0,0 +1,169 @@ +#!/usr/bin/env node +/** + * One-time script to populate reasonable 'expected' results + * for all test case steps that currently have empty expected values. + * + * Run with: node server/scripts/populate-expected-results.js + */ + +const fs = require('fs'); +const path = require('path'); +const yaml = require('js-yaml'); + +const TESTCASES_ROOT = path.join(__dirname, '..', '..', 'testcases'); + +// Heuristics for expected results based on action text +function getExpectedForAction(action) { + const a = action.toLowerCase(); + + if (a.includes('open admin portal') || a.includes('repository url in browser')) { + return 'The admin portal or repository page loads successfully without errors, security warnings, or redirects.'; + } + + if (a.includes('navigate to the download') || a.includes('documentation portal')) { + return 'The documentation or downloads section is displayed correctly and the relevant content area is accessible.'; + } + + if (a.includes('search or locate the relevant file')) { + return 'The target file or link matching the filename pattern is found and listed correctly.'; + } + + if (a.includes('assert presence and visibility of the expected document')) { + return 'The document is visible, has the correct title, and its content is accessible for verification.'; + } + + if (a.includes('log in to the admin portal')) { + return 'Authentication succeeds using the provided credentials and the user is taken to the main dashboard.'; + } + + if (a.includes('navigate to the relevant settings section')) { + return 'The correct configuration page or section for the feature is displayed.'; + } + + if (a.includes('read current configuration values')) { + return 'Current configuration values are successfully retrieved via the UI or API and match the known baseline.'; + } + + if (a.includes('execute the main verification or configuration action')) { + return 'The primary action described in the test completes successfully and produces the expected state or output.'; + } + + if (a.includes('capture evidence')) { + return 'Relevant evidence (screenshot, log, or API response) is successfully captured and can be reviewed.'; + } + + if (a.includes('assert expected outcome')) { + return 'All verification assertions pass and the system is confirmed to be in the expected final state.'; + } + + // PBX / Telephony specific + if (a.includes('ensure sip endpoints') || a.includes('softphones are registered')) { + return 'All required SIP endpoints show as registered with the correct status in the PBX.'; + } + + if (a.includes('initiate or receive call using the required scenario')) { + return 'The call is successfully established between the endpoints with ringing and connection confirmed.'; + } + + if (a.includes('verify audio path, signaling, and media parameters')) { + return 'Two-way audio is clear and bidirectional. Signaling (SIP) is correct and media parameters (codec, RTP/RTCP) match expectations.'; + } + + if (a.includes('prepare clean or previous-version vm')) { + return 'A clean or appropriately versioned VM/image is powered on and ready for the test procedure.'; + } + + if (a.includes('perform installation or upgrade procedure')) { + return 'The installation or upgrade procedure completes without errors and the expected new version is active.'; + } + + if (a.includes('post-install verification via portal')) { + return 'Core services are running, the admin portal is reachable, and basic post-install checks pass.'; + } + + // Generic fallback + return 'The action completes successfully and the system reaches the expected state described in the test.'; +} + +function processSteps(steps) { + if (!Array.isArray(steps)) return { steps, changed: false }; + + let changed = false; + + const newSteps = steps.map(step => { + if (typeof step === 'string') { + // Legacy string step - convert to object with estimated expected + changed = true; + return { + action: step, + expected: getExpectedForAction(step) + }; + } + + if (step && typeof step === 'object') { + if (!step.expected || step.expected.trim() === '') { + changed = true; + return { + ...step, + expected: getExpectedForAction(step.action || '') + }; + } + } + + return step; + }); + + return { steps: newSteps, changed }; +} + +function findYamlFiles(dir) { + const results = []; + const entries = fs.readdirSync(dir, { withFileTypes: true }); + + for (const entry of entries) { + const fullPath = path.join(dir, entry.name); + if (entry.isDirectory()) { + results.push(...findYamlFiles(fullPath)); + } else if (entry.name.endsWith('.yaml') && !entry.name.startsWith('SCHEMA')) { + results.push(fullPath); + } + } + return results; +} + +function main() { + console.log('Populating estimated "expected" results for test case steps...\n'); + + const yamlFiles = findYamlFiles(TESTCASES_ROOT); + let updatedCount = 0; + + for (const filePath of yamlFiles) { + try { + const content = fs.readFileSync(filePath, 'utf8'); + const doc = yaml.load(content); + + if (!doc || !doc.steps || !Array.isArray(doc.steps)) { + continue; + } + + const { steps: newSteps, changed } = processSteps(doc.steps); + + if (changed) { + doc.steps = newSteps; + + const header = `# Updated via Autotest Editor - ${new Date().toISOString()}\n# Source of truth: this YAML file\n# Note: Expected results estimated based on step actions\n\n`; + const newContent = header + yaml.dump(doc, { lineWidth: 100, noRefs: true }); + + fs.writeFileSync(filePath, newContent, 'utf8'); + console.log(`✓ Updated: ${path.relative(TESTCASES_ROOT, filePath)}`); + updatedCount++; + } + } catch (err) { + console.error(`✗ Error processing ${filePath}: ${err.message}`); + } + } + + console.log(`\nDone. Updated ${updatedCount} test case file(s).`); +} + +main(); \ No newline at end of file diff --git a/testcases/core/documentation/core-documentation-check-accuracy_installation_and_configuration_guide.yaml b/testcases/core/documentation/core-documentation-check-accuracy_installation_and_configuration_guide.yaml index 6781489..098141b 100644 --- a/testcases/core/documentation/core-documentation-check-accuracy_installation_and_configuration_guide.yaml +++ b/testcases/core/documentation/core-documentation-check-accuracy_installation_and_configuration_guide.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.876Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.816Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-documentation-check-accuracy_installation_and_configuration_guide module: core @@ -24,13 +25,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Navigate to the download / documentation portal - expected: '' + expected: >- + The documentation or downloads section is displayed correctly and the relevant content area is + accessible. - action: Search or locate the relevant file/link by filename pattern - expected: '' + expected: The target file or link matching the filename pattern is found and listed correctly. - action: Assert presence and visibility of the expected document - expected: '' + expected: >- + The document is visible, has the correct title, and its content is accessible for + verification. automation_status: manual file: tests/core/documentation.spec.ts custom_fields: diff --git a/testcases/core/documentation/core-documentation-check-accuracy_trouble_shooting_guide.yaml b/testcases/core/documentation/core-documentation-check-accuracy_trouble_shooting_guide.yaml index ea6474c..b587d5a 100644 --- a/testcases/core/documentation/core-documentation-check-accuracy_trouble_shooting_guide.yaml +++ b/testcases/core/documentation/core-documentation-check-accuracy_trouble_shooting_guide.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.881Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.830Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-documentation-check-accuracy_trouble_shooting_guide module: core @@ -24,13 +25,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Navigate to the download / documentation portal - expected: '' + expected: >- + The documentation or downloads section is displayed correctly and the relevant content area is + accessible. - action: Search or locate the relevant file/link by filename pattern - expected: '' + expected: The target file or link matching the filename pattern is found and listed correctly. - action: Assert presence and visibility of the expected document - expected: '' + expected: >- + The document is visible, has the correct title, and its content is accessible for + verification. automation_status: manual file: tests/core/documentation.spec.ts custom_fields: diff --git a/testcases/core/documentation/core-documentation-write-changed_cli_configuration_commands.yaml b/testcases/core/documentation/core-documentation-write-changed_cli_configuration_commands.yaml index a342278..1ef645e 100644 --- a/testcases/core/documentation/core-documentation-write-changed_cli_configuration_commands.yaml +++ b/testcases/core/documentation/core-documentation-write-changed_cli_configuration_commands.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.886Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.832Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-documentation-write-changed_cli_configuration_commands module: core @@ -24,13 +25,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Navigate to the download / documentation portal - expected: '' + expected: >- + The documentation or downloads section is displayed correctly and the relevant content area is + accessible. - action: Search or locate the relevant file/link by filename pattern - expected: '' + expected: The target file or link matching the filename pattern is found and listed correctly. - action: Assert presence and visibility of the expected document - expected: '' + expected: >- + The document is visible, has the correct title, and its content is accessible for + verification. automation_status: automated file: tests/core/documentation.spec.ts custom_fields: diff --git a/testcases/core/documentation/core-documentation-write-release_notes_feature_changes_and_known_issues.yaml b/testcases/core/documentation/core-documentation-write-release_notes_feature_changes_and_known_issues.yaml index c9e0f73..52f4158 100644 --- a/testcases/core/documentation/core-documentation-write-release_notes_feature_changes_and_known_issues.yaml +++ b/testcases/core/documentation/core-documentation-write-release_notes_feature_changes_and_known_issues.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.893Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.833Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-documentation-write-release_notes_feature_changes_and_known_issues module: core @@ -24,13 +25,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Navigate to the download / documentation portal - expected: '' + expected: >- + The documentation or downloads section is displayed correctly and the relevant content area is + accessible. - action: Search or locate the relevant file/link by filename pattern - expected: '' + expected: The target file or link matching the filename pattern is found and listed correctly. - action: Assert presence and visibility of the expected document - expected: '' + expected: >- + The document is visible, has the correct title, and its content is accessible for + verification. automation_status: automated file: tests/core/documentation.spec.ts custom_fields: diff --git a/testcases/core/features/core-features-check-backward_compatibility_of_new_features.yaml b/testcases/core/features/core-features-check-backward_compatibility_of_new_features.yaml index 7236732..29dcf0f 100644 --- a/testcases/core/features/core-features-check-backward_compatibility_of_new_features.yaml +++ b/testcases/core/features/core-features-check-backward_compatibility_of_new_features.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.908Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.834Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-features-check-backward_compatibility_of_new_features module: core @@ -28,13 +29,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: partial file: tests/core/features.spec.ts custom_fields: diff --git a/testcases/core/features/core-features-check-provisioning_changes_for_new_features.yaml b/testcases/core/features/core-features-check-provisioning_changes_for_new_features.yaml index bf9e7bb..a3b8294 100644 --- a/testcases/core/features/core-features-check-provisioning_changes_for_new_features.yaml +++ b/testcases/core/features/core-features-check-provisioning_changes_for_new_features.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.922Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.836Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-features-check-provisioning_changes_for_new_features module: core @@ -24,13 +25,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: automated file: tests/core/features.spec.ts custom_fields: diff --git a/testcases/core/features/core-features-write-analysis_of_new_security_risks.yaml b/testcases/core/features/core-features-write-analysis_of_new_security_risks.yaml index 5110b11..6468a20 100644 --- a/testcases/core/features/core-features-write-analysis_of_new_security_risks.yaml +++ b/testcases/core/features/core-features-write-analysis_of_new_security_risks.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.924Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.837Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-features-write-analysis_of_new_security_risks module: core @@ -24,13 +25,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: manual file: tests/core/features.spec.ts custom_fields: diff --git a/testcases/core/features/core-features-write-summary_of_each_new_feature_per_release.yaml b/testcases/core/features/core-features-write-summary_of_each_new_feature_per_release.yaml index bebc0cc..ad746e2 100644 --- a/testcases/core/features/core-features-write-summary_of_each_new_feature_per_release.yaml +++ b/testcases/core/features/core-features-write-summary_of_each_new_feature_per_release.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.927Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.838Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-features-write-summary_of_each_new_feature_per_release module: core @@ -24,13 +25,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: automated file: tests/core/features.spec.ts custom_fields: diff --git a/testcases/core/features/core-features-write-ui_ux_and_admin_portal_changes_validation.yaml b/testcases/core/features/core-features-write-ui_ux_and_admin_portal_changes_validation.yaml index 40abb7b..cf33030 100644 --- a/testcases/core/features/core-features-write-ui_ux_and_admin_portal_changes_validation.yaml +++ b/testcases/core/features/core-features-write-ui_ux_and_admin_portal_changes_validation.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.930Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.840Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-features-write-ui_ux_and_admin_portal_changes_validation module: core @@ -24,13 +25,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: automated file: tests/core/features.spec.ts custom_fields: diff --git a/testcases/core/installation/core-installation-check-fresh_installation.yaml b/testcases/core/installation/core-installation-check-fresh_installation.yaml index 4612eae..9fb4d40 100644 --- a/testcases/core/installation/core-installation-check-fresh_installation.yaml +++ b/testcases/core/installation/core-installation-check-fresh_installation.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.933Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.840Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-installation-check-fresh_installation module: core @@ -24,13 +25,17 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Prepare clean or previous-version VM/image - expected: '' + expected: A clean or appropriately versioned VM/image is powered on and ready for the test procedure. - action: Perform installation or upgrade procedure - expected: '' + expected: >- + The installation or upgrade procedure completes without errors and the expected new version is + active. - action: Post-install verification via portal + external tools - expected: '' + expected: Core services are running, the admin portal is reachable, and basic post-install checks pass. automation_status: manual file: tests/core/installation.spec.ts custom_fields: diff --git a/testcases/core/installation/core-installation-check-initial_configuration.yaml b/testcases/core/installation/core-installation-check-initial_configuration.yaml index 7948fb7..948e05c 100644 --- a/testcases/core/installation/core-installation-check-initial_configuration.yaml +++ b/testcases/core/installation/core-installation-check-initial_configuration.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.935Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.841Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-installation-check-initial_configuration module: core @@ -24,13 +25,17 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Prepare clean or previous-version VM/image - expected: '' + expected: A clean or appropriately versioned VM/image is powered on and ready for the test procedure. - action: Perform installation or upgrade procedure - expected: '' + expected: >- + The installation or upgrade procedure completes without errors and the expected new version is + active. - action: Post-install verification via portal + external tools - expected: '' + expected: Core services are running, the admin portal is reachable, and basic post-install checks pass. automation_status: automated file: tests/core/installation.spec.ts custom_fields: diff --git a/testcases/core/installation/core-installation-check-license_activation.yaml b/testcases/core/installation/core-installation-check-license_activation.yaml index cfb0a75..3140d3a 100644 --- a/testcases/core/installation/core-installation-check-license_activation.yaml +++ b/testcases/core/installation/core-installation-check-license_activation.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.938Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.842Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-installation-check-license_activation module: core @@ -24,13 +25,17 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Prepare clean or previous-version VM/image - expected: '' + expected: A clean or appropriately versioned VM/image is powered on and ready for the test procedure. - action: Perform installation or upgrade procedure - expected: '' + expected: >- + The installation or upgrade procedure completes without errors and the expected new version is + active. - action: Post-install verification via portal + external tools - expected: '' + expected: Core services are running, the admin portal is reachable, and basic post-install checks pass. automation_status: automated file: tests/core/installation.spec.ts custom_fields: diff --git a/testcases/core/installation/core-installation-check-post_install_service_status_and_port_verification.yaml b/testcases/core/installation/core-installation-check-post_install_service_status_and_port_verification.yaml index 8b4c6dc..a42d742 100644 --- a/testcases/core/installation/core-installation-check-post_install_service_status_and_port_verification.yaml +++ b/testcases/core/installation/core-installation-check-post_install_service_status_and_port_verification.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.943Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.844Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-installation-check-post_install_service_status_and_port_verification module: core @@ -24,13 +25,17 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Prepare clean or previous-version VM/image - expected: '' + expected: A clean or appropriately versioned VM/image is powered on and ready for the test procedure. - action: Perform installation or upgrade procedure - expected: '' + expected: >- + The installation or upgrade procedure completes without errors and the expected new version is + active. - action: Post-install verification via portal + external tools - expected: '' + expected: Core services are running, the admin portal is reachable, and basic post-install checks pass. automation_status: partial file: tests/core/installation.spec.ts custom_fields: diff --git a/testcases/core/interoperability/core-interoperability-check-addm.yaml b/testcases/core/interoperability/core-interoperability-check-addm.yaml index bd181d1..9050760 100644 --- a/testcases/core/interoperability/core-interoperability-check-addm.yaml +++ b/testcases/core/interoperability/core-interoperability-check-addm.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.947Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.845Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-interoperability-check-addm module: core @@ -26,13 +27,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: automated file: tests/core/interoperability.spec.ts custom_fields: diff --git a/testcases/core/interoperability/core-interoperability-check-siem.yaml b/testcases/core/interoperability/core-interoperability-check-siem.yaml index 7d7626f..b8aa850 100644 --- a/testcases/core/interoperability/core-interoperability-check-siem.yaml +++ b/testcases/core/interoperability/core-interoperability-check-siem.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.952Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.847Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-interoperability-check-siem module: core @@ -26,13 +27,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: automated file: tests/core/interoperability.spec.ts custom_fields: diff --git a/testcases/core/repository/core-repository-check-presence_of_all_mandatory_core-documentation_files.yaml b/testcases/core/repository/core-repository-check-presence_of_all_mandatory_core-documentation_files.yaml index f1a1731..6968374 100644 --- a/testcases/core/repository/core-repository-check-presence_of_all_mandatory_core-documentation_files.yaml +++ b/testcases/core/repository/core-repository-check-presence_of_all_mandatory_core-documentation_files.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.957Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.848Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-repository-check-presence_of_all_mandatory_core-documentation_files module: core @@ -24,13 +25,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Navigate to the download / documentation portal - expected: '' + expected: >- + The documentation or downloads section is displayed correctly and the relevant content area is + accessible. - action: Search or locate the relevant file/link by filename pattern - expected: '' + expected: The target file or link matching the filename pattern is found and listed correctly. - action: Assert presence and visibility of the expected document - expected: '' + expected: >- + The document is visible, has the correct title, and its content is accessible for + verification. automation_status: automated file: tests/core/repository.spec.ts custom_fields: diff --git a/testcases/core/repository/core-repository-check-presence_of_companion_tools_and_supporting_scripts.yaml b/testcases/core/repository/core-repository-check-presence_of_companion_tools_and_supporting_scripts.yaml index e63bb17..6e6c471 100644 --- a/testcases/core/repository/core-repository-check-presence_of_companion_tools_and_supporting_scripts.yaml +++ b/testcases/core/repository/core-repository-check-presence_of_companion_tools_and_supporting_scripts.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.960Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.849Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-repository-check-presence_of_companion_tools_and_supporting_scripts module: core @@ -24,13 +25,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Navigate to the download / documentation portal - expected: '' + expected: >- + The documentation or downloads section is displayed correctly and the relevant content area is + accessible. - action: Search or locate the relevant file/link by filename pattern - expected: '' + expected: The target file or link matching the filename pattern is found and listed correctly. - action: Assert presence and visibility of the expected document - expected: '' + expected: >- + The document is visible, has the correct title, and its content is accessible for + verification. automation_status: automated file: tests/core/repository.spec.ts custom_fields: diff --git a/testcases/core/repository/core-repository-check-presence_of_main_software_version_all_hypervisors.yaml b/testcases/core/repository/core-repository-check-presence_of_main_software_version_all_hypervisors.yaml index 19f06e9..553b2ce 100644 --- a/testcases/core/repository/core-repository-check-presence_of_main_software_version_all_hypervisors.yaml +++ b/testcases/core/repository/core-repository-check-presence_of_main_software_version_all_hypervisors.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.961Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.850Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-repository-check-presence_of_main_software_version_all_hypervisors module: core @@ -24,13 +25,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Navigate to the download / documentation portal - expected: '' + expected: >- + The documentation or downloads section is displayed correctly and the relevant content area is + accessible. - action: Search or locate the relevant file/link by filename pattern - expected: '' + expected: The target file or link matching the filename pattern is found and listed correctly. - action: Assert presence and visibility of the expected document - expected: '' + expected: >- + The document is visible, has the correct title, and its content is accessible for + verification. automation_status: automated file: tests/core/repository.spec.ts custom_fields: diff --git a/testcases/core/repository/core-repository-check-presence_of_patch_version_and_its_compatibility.yaml b/testcases/core/repository/core-repository-check-presence_of_patch_version_and_its_compatibility.yaml index ce8526b..2d38c9e 100644 --- a/testcases/core/repository/core-repository-check-presence_of_patch_version_and_its_compatibility.yaml +++ b/testcases/core/repository/core-repository-check-presence_of_patch_version_and_its_compatibility.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.964Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.851Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-repository-check-presence_of_patch_version_and_its_compatibility module: core @@ -24,13 +25,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Navigate to the download / documentation portal - expected: '' + expected: >- + The documentation or downloads section is displayed correctly and the relevant content area is + accessible. - action: Search or locate the relevant file/link by filename pattern - expected: '' + expected: The target file or link matching the filename pattern is found and listed correctly. - action: Assert presence and visibility of the expected document - expected: '' + expected: >- + The document is visible, has the correct title, and its content is accessible for + verification. automation_status: automated file: tests/core/repository.spec.ts custom_fields: diff --git a/testcases/core/repository/core-repository-check-presence_of_release_notes_and_changelog.yaml b/testcases/core/repository/core-repository-check-presence_of_release_notes_and_changelog.yaml index 2b4edeb..8b96c0c 100644 --- a/testcases/core/repository/core-repository-check-presence_of_release_notes_and_changelog.yaml +++ b/testcases/core/repository/core-repository-check-presence_of_release_notes_and_changelog.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.967Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.852Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-repository-check-presence_of_release_notes_and_changelog module: core @@ -24,13 +25,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Navigate to the download / documentation portal - expected: '' + expected: >- + The documentation or downloads section is displayed correctly and the relevant content area is + accessible. - action: Search or locate the relevant file/link by filename pattern - expected: '' + expected: The target file or link matching the filename pattern is found and listed correctly. - action: Assert presence and visibility of the expected document - expected: '' + expected: >- + The document is visible, has the correct title, and its content is accessible for + verification. automation_status: automated file: tests/core/repository.spec.ts custom_fields: diff --git a/testcases/core/repository/core-repository-check-presence_of_trouble_shooting_guide.yaml b/testcases/core/repository/core-repository-check-presence_of_trouble_shooting_guide.yaml index ca0dd5d..6985cf6 100644 --- a/testcases/core/repository/core-repository-check-presence_of_trouble_shooting_guide.yaml +++ b/testcases/core/repository/core-repository-check-presence_of_trouble_shooting_guide.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.969Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.853Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-repository-check-presence_of_trouble_shooting_guide module: core @@ -24,13 +25,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Navigate to the download / documentation portal - expected: '' + expected: >- + The documentation or downloads section is displayed correctly and the relevant content area is + accessible. - action: Search or locate the relevant file/link by filename pattern - expected: '' + expected: The target file or link matching the filename pattern is found and listed correctly. - action: Assert presence and visibility of the expected document - expected: '' + expected: >- + The document is visible, has the correct title, and its content is accessible for + verification. automation_status: automated file: tests/core/repository.spec.ts custom_fields: diff --git a/testcases/core/security/core-security-check-auto_enrollment_certificate_management_process.yaml b/testcases/core/security/core-security-check-auto_enrollment_certificate_management_process.yaml index e5af264..c3a6370 100644 --- a/testcases/core/security/core-security-check-auto_enrollment_certificate_management_process.yaml +++ b/testcases/core/security/core-security-check-auto_enrollment_certificate_management_process.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.972Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.854Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-security-check-auto_enrollment_certificate_management_process module: core @@ -24,13 +25,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Log in to the admin portal (if required) - expected: '' + expected: >- + Authentication succeeds using the provided credentials and the user is taken to the main + dashboard. - action: Navigate to the relevant settings section - expected: '' + expected: The correct configuration page or section for the feature is displayed. - action: Read current configuration values via UI or API - expected: '' + expected: >- + Current configuration values are successfully retrieved via the UI or API and match the known + baseline. automation_status: automated file: tests/core/security.spec.ts custom_fields: diff --git a/testcases/core/security/core-security-check-encryption_of_sensitive_data_at_rest_and_in_transit.yaml b/testcases/core/security/core-security-check-encryption_of_sensitive_data_at_rest_and_in_transit.yaml index 6d19dcf..9439914 100644 --- a/testcases/core/security/core-security-check-encryption_of_sensitive_data_at_rest_and_in_transit.yaml +++ b/testcases/core/security/core-security-check-encryption_of_sensitive_data_at_rest_and_in_transit.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.974Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.855Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-security-check-encryption_of_sensitive_data_at_rest_and_in_transit module: core @@ -24,13 +25,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Log in to the admin portal (if required) - expected: '' + expected: >- + Authentication succeeds using the provided credentials and the user is taken to the main + dashboard. - action: Navigate to the relevant settings section - expected: '' + expected: The correct configuration page or section for the feature is displayed. - action: Read current configuration values via UI or API - expected: '' + expected: >- + Current configuration values are successfully retrieved via the UI or API and match the known + baseline. automation_status: partial file: tests/core/security.spec.ts custom_fields: diff --git a/testcases/core/security/core-security-check-ip_access_control_lists.yaml b/testcases/core/security/core-security-check-ip_access_control_lists.yaml index beedf09..f55deca 100644 --- a/testcases/core/security/core-security-check-ip_access_control_lists.yaml +++ b/testcases/core/security/core-security-check-ip_access_control_lists.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.978Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.856Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-security-check-ip_access_control_lists module: core @@ -24,13 +25,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Log in to the admin portal (if required) - expected: '' + expected: >- + Authentication succeeds using the provided credentials and the user is taken to the main + dashboard. - action: Navigate to the relevant settings section - expected: '' + expected: The correct configuration page or section for the feature is displayed. - action: Read current configuration values via UI or API - expected: '' + expected: >- + Current configuration values are successfully retrieved via the UI or API and match the known + baseline. automation_status: automated file: tests/core/security.spec.ts custom_fields: diff --git a/testcases/core/security/core-security-check-known_vulnerable_dependencies_in_release_artifacts.yaml b/testcases/core/security/core-security-check-known_vulnerable_dependencies_in_release_artifacts.yaml index cd4fb1a..6fdd55e 100644 --- a/testcases/core/security/core-security-check-known_vulnerable_dependencies_in_release_artifacts.yaml +++ b/testcases/core/security/core-security-check-known_vulnerable_dependencies_in_release_artifacts.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.980Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.857Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-security-check-known_vulnerable_dependencies_in_release_artifacts module: core @@ -24,13 +25,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Log in to the admin portal (if required) - expected: '' + expected: >- + Authentication succeeds using the provided credentials and the user is taken to the main + dashboard. - action: Navigate to the relevant settings section - expected: '' + expected: The correct configuration page or section for the feature is displayed. - action: Read current configuration values via UI or API - expected: '' + expected: >- + Current configuration values are successfully retrieved via the UI or API and match the known + baseline. automation_status: partial file: tests/core/security.spec.ts custom_fields: diff --git a/testcases/core/security/core-security-check-obtain_formal_security_team_sign_off_for_the_new_version.yaml b/testcases/core/security/core-security-check-obtain_formal_security_team_sign_off_for_the_new_version.yaml index 7d40d06..449bf67 100644 --- a/testcases/core/security/core-security-check-obtain_formal_security_team_sign_off_for_the_new_version.yaml +++ b/testcases/core/security/core-security-check-obtain_formal_security_team_sign_off_for_the_new_version.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.982Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.858Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-security-check-obtain_formal_security_team_sign_off_for_the_new_version module: core @@ -24,13 +25,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Log in to the admin portal (if required) - expected: '' + expected: >- + Authentication succeeds using the provided credentials and the user is taken to the main + dashboard. - action: Navigate to the relevant settings section - expected: '' + expected: The correct configuration page or section for the feature is displayed. - action: Read current configuration values via UI or API - expected: '' + expected: >- + Current configuration values are successfully retrieved via the UI or API and match the known + baseline. automation_status: manual file: tests/core/security.spec.ts custom_fields: diff --git a/testcases/core/security/core-security-check-previous_security_findings_have_been_remediated_before_release.yaml b/testcases/core/security/core-security-check-previous_security_findings_have_been_remediated_before_release.yaml index a91a72e..8376990 100644 --- a/testcases/core/security/core-security-check-previous_security_findings_have_been_remediated_before_release.yaml +++ b/testcases/core/security/core-security-check-previous_security_findings_have_been_remediated_before_release.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.984Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.859Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-security-check-previous_security_findings_have_been_remediated_before_release module: core @@ -24,13 +25,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Log in to the admin portal (if required) - expected: '' + expected: >- + Authentication succeeds using the provided credentials and the user is taken to the main + dashboard. - action: Navigate to the relevant settings section - expected: '' + expected: The correct configuration page or section for the feature is displayed. - action: Read current configuration values via UI or API - expected: '' + expected: >- + Current configuration values are successfully retrieved via the UI or API and match the known + baseline. automation_status: manual file: tests/core/security.spec.ts custom_fields: diff --git a/testcases/core/security/core-security-check-security_event_logging_and_audit_trail_is_active.yaml b/testcases/core/security/core-security-check-security_event_logging_and_audit_trail_is_active.yaml index 9bd614e..0818bf0 100644 --- a/testcases/core/security/core-security-check-security_event_logging_and_audit_trail_is_active.yaml +++ b/testcases/core/security/core-security-check-security_event_logging_and_audit_trail_is_active.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.985Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.860Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-security-check-security_event_logging_and_audit_trail_is_active module: core @@ -24,13 +25,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Log in to the admin portal (if required) - expected: '' + expected: >- + Authentication succeeds using the provided credentials and the user is taken to the main + dashboard. - action: Navigate to the relevant settings section - expected: '' + expected: The correct configuration page or section for the feature is displayed. - action: Read current configuration values via UI or API - expected: '' + expected: >- + Current configuration values are successfully retrieved via the UI or API and match the known + baseline. automation_status: automated file: tests/core/security.spec.ts custom_fields: diff --git a/testcases/core/security/core-security-check-unnecessary_services_and_ports_are_disabled.yaml b/testcases/core/security/core-security-check-unnecessary_services_and_ports_are_disabled.yaml index 8408c16..2997523 100644 --- a/testcases/core/security/core-security-check-unnecessary_services_and_ports_are_disabled.yaml +++ b/testcases/core/security/core-security-check-unnecessary_services_and_ports_are_disabled.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.992Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.861Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-security-check-unnecessary_services_and_ports_are_disabled module: core @@ -24,13 +25,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Log in to the admin portal (if required) - expected: '' + expected: >- + Authentication succeeds using the provided credentials and the user is taken to the main + dashboard. - action: Navigate to the relevant settings section - expected: '' + expected: The correct configuration page or section for the feature is displayed. - action: Read current configuration values via UI or API - expected: '' + expected: >- + Current configuration values are successfully retrieved via the UI or API and match the known + baseline. automation_status: partial file: tests/core/security.spec.ts custom_fields: diff --git a/testcases/core/security/core-security-check-verify_role_based_access_control_and_least_privilege_principle.yaml b/testcases/core/security/core-security-check-verify_role_based_access_control_and_least_privilege_principle.yaml index ef29737..d0ad254 100644 --- a/testcases/core/security/core-security-check-verify_role_based_access_control_and_least_privilege_principle.yaml +++ b/testcases/core/security/core-security-check-verify_role_based_access_control_and_least_privilege_principle.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.993Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.863Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-security-check-verify_role_based_access_control_and_least_privilege_principle module: core @@ -24,13 +25,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Log in to the admin portal (if required) - expected: '' + expected: >- + Authentication succeeds using the provided credentials and the user is taken to the main + dashboard. - action: Navigate to the relevant settings section - expected: '' + expected: The correct configuration page or section for the feature is displayed. - action: Read current configuration values via UI or API - expected: '' + expected: >- + Current configuration values are successfully retrieved via the UI or API and match the known + baseline. automation_status: automated file: tests/core/security.spec.ts custom_fields: diff --git a/testcases/core/security/core-security-write-strong_password_policy.yaml b/testcases/core/security/core-security-write-strong_password_policy.yaml index 51d3a27..6fecf50 100644 --- a/testcases/core/security/core-security-write-strong_password_policy.yaml +++ b/testcases/core/security/core-security-write-strong_password_policy.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.995Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.864Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-security-write-strong_password_policy module: core @@ -24,13 +25,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Log in to the admin portal (if required) - expected: '' + expected: >- + Authentication succeeds using the provided credentials and the user is taken to the main + dashboard. - action: Navigate to the relevant settings section - expected: '' + expected: The correct configuration page or section for the feature is displayed. - action: Read current configuration values via UI or API - expected: '' + expected: >- + Current configuration values are successfully retrieved via the UI or API and match the known + baseline. automation_status: automated file: tests/core/security.spec.ts custom_fields: diff --git a/testcases/core/upgrade/core-upgrade-check-configuration_and_database_migration_validation.yaml b/testcases/core/upgrade/core-upgrade-check-configuration_and_database_migration_validation.yaml index bd9ee71..b661b09 100644 --- a/testcases/core/upgrade/core-upgrade-check-configuration_and_database_migration_validation.yaml +++ b/testcases/core/upgrade/core-upgrade-check-configuration_and_database_migration_validation.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.999Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.865Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-upgrade-check-configuration_and_database_migration_validation module: core @@ -24,13 +25,17 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Prepare clean or previous-version VM/image - expected: '' + expected: A clean or appropriately versioned VM/image is powered on and ready for the test procedure. - action: Perform installation or upgrade procedure - expected: '' + expected: >- + The installation or upgrade procedure completes without errors and the expected new version is + active. - action: Post-install verification via portal + external tools - expected: '' + expected: Core services are running, the admin portal is reachable, and basic post-install checks pass. automation_status: partial file: tests/core/upgrade.spec.ts custom_fields: diff --git a/testcases/core/upgrade/core-upgrade-check-in_place_upgrade_from_previous_major_version.yaml b/testcases/core/upgrade/core-upgrade-check-in_place_upgrade_from_previous_major_version.yaml index 625f1d6..729c01f 100644 --- a/testcases/core/upgrade/core-upgrade-check-in_place_upgrade_from_previous_major_version.yaml +++ b/testcases/core/upgrade/core-upgrade-check-in_place_upgrade_from_previous_major_version.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.001Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.866Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-upgrade-check-in_place_upgrade_from_previous_major_version module: core @@ -24,13 +25,17 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Prepare clean or previous-version VM/image - expected: '' + expected: A clean or appropriately versioned VM/image is powered on and ready for the test procedure. - action: Perform installation or upgrade procedure - expected: '' + expected: >- + The installation or upgrade procedure completes without errors and the expected new version is + active. - action: Post-install verification via portal + external tools - expected: '' + expected: Core services are running, the admin portal is reachable, and basic post-install checks pass. automation_status: manual file: tests/core/upgrade.spec.ts custom_fields: diff --git a/testcases/core/upgrade/core-upgrade-check-post_upgrade_regression_of_core_features.yaml b/testcases/core/upgrade/core-upgrade-check-post_upgrade_regression_of_core_features.yaml index 54ee50e..2911531 100644 --- a/testcases/core/upgrade/core-upgrade-check-post_upgrade_regression_of_core_features.yaml +++ b/testcases/core/upgrade/core-upgrade-check-post_upgrade_regression_of_core_features.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.002Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.867Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-upgrade-check-post_upgrade_regression_of_core_features module: core @@ -24,13 +25,17 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Prepare clean or previous-version VM/image - expected: '' + expected: A clean or appropriately versioned VM/image is powered on and ready for the test procedure. - action: Perform installation or upgrade procedure - expected: '' + expected: >- + The installation or upgrade procedure completes without errors and the expected new version is + active. - action: Post-install verification via portal + external tools - expected: '' + expected: Core services are running, the admin portal is reachable, and basic post-install checks pass. automation_status: automated file: tests/core/upgrade.spec.ts custom_fields: diff --git a/testcases/core/upgrade/core-upgrade-check-rollback_procedure_execution_and_verification.yaml b/testcases/core/upgrade/core-upgrade-check-rollback_procedure_execution_and_verification.yaml index 69cb15a..89877d3 100644 --- a/testcases/core/upgrade/core-upgrade-check-rollback_procedure_execution_and_verification.yaml +++ b/testcases/core/upgrade/core-upgrade-check-rollback_procedure_execution_and_verification.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.005Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.868Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-upgrade-check-rollback_procedure_execution_and_verification module: core @@ -24,13 +25,17 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Prepare clean or previous-version VM/image - expected: '' + expected: A clean or appropriately versioned VM/image is powered on and ready for the test procedure. - action: Perform installation or upgrade procedure - expected: '' + expected: >- + The installation or upgrade procedure completes without errors and the expected new version is + active. - action: Post-install verification via portal + external tools - expected: '' + expected: Core services are running, the admin portal is reachable, and basic post-install checks pass. automation_status: manual file: tests/core/upgrade.spec.ts custom_fields: diff --git a/testcases/core/upgrade/core-upgrade-check-schema_upgrade_and_data_integrity_check.yaml b/testcases/core/upgrade/core-upgrade-check-schema_upgrade_and_data_integrity_check.yaml index 5174cb4..591d699 100644 --- a/testcases/core/upgrade/core-upgrade-check-schema_upgrade_and_data_integrity_check.yaml +++ b/testcases/core/upgrade/core-upgrade-check-schema_upgrade_and_data_integrity_check.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.006Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.870Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-upgrade-check-schema_upgrade_and_data_integrity_check module: core @@ -24,13 +25,17 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Prepare clean or previous-version VM/image - expected: '' + expected: A clean or appropriately versioned VM/image is powered on and ready for the test procedure. - action: Perform installation or upgrade procedure - expected: '' + expected: >- + The installation or upgrade procedure completes without errors and the expected new version is + active. - action: Post-install verification via portal + external tools - expected: '' + expected: Core services are running, the admin portal is reachable, and basic post-install checks pass. automation_status: manual file: tests/core/upgrade.spec.ts custom_fields: diff --git a/testcases/core/upgrade/core-upgrade-check-zero_downtime_upgrade_where_supported.yaml b/testcases/core/upgrade/core-upgrade-check-zero_downtime_upgrade_where_supported.yaml index 24122bd..b95cb0a 100644 --- a/testcases/core/upgrade/core-upgrade-check-zero_downtime_upgrade_where_supported.yaml +++ b/testcases/core/upgrade/core-upgrade-check-zero_downtime_upgrade_where_supported.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.007Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.871Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-upgrade-check-zero_downtime_upgrade_where_supported module: core @@ -24,13 +25,17 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Prepare clean or previous-version VM/image - expected: '' + expected: A clean or appropriately versioned VM/image is powered on and ready for the test procedure. - action: Perform installation or upgrade procedure - expected: '' + expected: >- + The installation or upgrade procedure completes without errors and the expected new version is + active. - action: Post-install verification via portal + external tools - expected: '' + expected: Core services are running, the admin portal is reachable, and basic post-install checks pass. automation_status: manual file: tests/core/upgrade.spec.ts custom_fields: diff --git a/testcases/core/virtualization/core-virtualization-check-snapshot_backup_restore_and_consistency.yaml b/testcases/core/virtualization/core-virtualization-check-snapshot_backup_restore_and_consistency.yaml index 0189fca..c38d5ab 100644 --- a/testcases/core/virtualization/core-virtualization-check-snapshot_backup_restore_and_consistency.yaml +++ b/testcases/core/virtualization/core-virtualization-check-snapshot_backup_restore_and_consistency.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.010Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.872Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-virtualization-check-snapshot_backup_restore_and_consistency module: core @@ -26,13 +27,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: partial file: tests/core/virtualization.spec.ts custom_fields: diff --git a/testcases/core/virtualization/core-virtualization-write-guest_agent_integration.yaml b/testcases/core/virtualization/core-virtualization-write-guest_agent_integration.yaml index 7001e4c..738bf5f 100644 --- a/testcases/core/virtualization/core-virtualization-write-guest_agent_integration.yaml +++ b/testcases/core/virtualization/core-virtualization-write-guest_agent_integration.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.011Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.873Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-virtualization-write-guest_agent_integration module: core @@ -26,13 +27,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: manual file: tests/core/virtualization.spec.ts custom_fields: diff --git a/testcases/core/virtualization/core-virtualization-write-resource_allocation_vcpu_vram_vdisk.yaml b/testcases/core/virtualization/core-virtualization-write-resource_allocation_vcpu_vram_vdisk.yaml index b4f456b..797494e 100644 --- a/testcases/core/virtualization/core-virtualization-write-resource_allocation_vcpu_vram_vdisk.yaml +++ b/testcases/core/virtualization/core-virtualization-write-resource_allocation_vcpu_vram_vdisk.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.012Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.874Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-virtualization-write-resource_allocation_vcpu_vram_vdisk module: core @@ -26,13 +27,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: manual file: tests/core/virtualization.spec.ts custom_fields: diff --git a/testcases/core/virtualization/core-virtualization-write-storage_thin_vs_thick_provisioning.yaml b/testcases/core/virtualization/core-virtualization-write-storage_thin_vs_thick_provisioning.yaml index 5e3dbc8..02c1e74 100644 --- a/testcases/core/virtualization/core-virtualization-write-storage_thin_vs_thick_provisioning.yaml +++ b/testcases/core/virtualization/core-virtualization-write-storage_thin_vs_thick_provisioning.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.013Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.875Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-virtualization-write-storage_thin_vs_thick_provisioning module: core @@ -26,13 +27,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: manual file: tests/core/virtualization.spec.ts custom_fields: diff --git a/testcases/core/virtualization/core-virtualization-write-supported_hypervisors_deployment.yaml b/testcases/core/virtualization/core-virtualization-write-supported_hypervisors_deployment.yaml index 1609d57..b21f769 100644 --- a/testcases/core/virtualization/core-virtualization-write-supported_hypervisors_deployment.yaml +++ b/testcases/core/virtualization/core-virtualization-write-supported_hypervisors_deployment.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.014Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.876Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-virtualization-write-supported_hypervisors_deployment module: core @@ -26,13 +27,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: automated file: tests/core/virtualization.spec.ts custom_fields: diff --git a/testcases/core/virtualization/core-virtualization-write-virtual_networking_configuration.yaml b/testcases/core/virtualization/core-virtualization-write-virtual_networking_configuration.yaml index e73d226..1ba6550 100644 --- a/testcases/core/virtualization/core-virtualization-write-virtual_networking_configuration.yaml +++ b/testcases/core/virtualization/core-virtualization-write-virtual_networking_configuration.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.015Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.877Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: core-virtualization-write-virtual_networking_configuration module: core @@ -26,13 +27,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: manual file: tests/core/virtualization.spec.ts custom_fields: diff --git a/testcases/pbx/availability/pbx-availability-check-active_passive_or_active_active_failover.yaml b/testcases/pbx/availability/pbx-availability-check-active_passive_or_active_active_failover.yaml index 85e9b46..dd4986f 100644 --- a/testcases/pbx/availability/pbx-availability-check-active_passive_or_active_active_failover.yaml +++ b/testcases/pbx/availability/pbx-availability-check-active_passive_or_active_active_failover.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.016Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.878Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-availability-check-active_passive_or_active_active_failover module: pbx @@ -26,13 +27,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: manual file: tests/pbx/availability.spec.ts custom_fields: diff --git a/testcases/pbx/availability/pbx-availability-check-automatic_failover_and_call_preservation.yaml b/testcases/pbx/availability/pbx-availability-check-automatic_failover_and_call_preservation.yaml index 0bf170b..17d1d96 100644 --- a/testcases/pbx/availability/pbx-availability-check-automatic_failover_and_call_preservation.yaml +++ b/testcases/pbx/availability/pbx-availability-check-automatic_failover_and_call_preservation.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.017Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.879Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-availability-check-automatic_failover_and_call_preservation module: pbx @@ -26,13 +27,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: manual file: tests/pbx/availability.spec.ts custom_fields: diff --git a/testcases/pbx/availability/pbx-availability-check-database_replication_and_sync_integrity.yaml b/testcases/pbx/availability/pbx-availability-check-database_replication_and_sync_integrity.yaml index dae7a26..979b694 100644 --- a/testcases/pbx/availability/pbx-availability-check-database_replication_and_sync_integrity.yaml +++ b/testcases/pbx/availability/pbx-availability-check-database_replication_and_sync_integrity.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.018Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.880Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-availability-check-database_replication_and_sync_integrity module: pbx @@ -26,13 +27,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: manual file: tests/pbx/availability.spec.ts custom_fields: diff --git a/testcases/pbx/availability/pbx-availability-check-geographic_redundancy_and_geo_distribution.yaml b/testcases/pbx/availability/pbx-availability-check-geographic_redundancy_and_geo_distribution.yaml index 0bdc9dc..738da4a 100644 --- a/testcases/pbx/availability/pbx-availability-check-geographic_redundancy_and_geo_distribution.yaml +++ b/testcases/pbx/availability/pbx-availability-check-geographic_redundancy_and_geo_distribution.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.019Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.881Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-availability-check-geographic_redundancy_and_geo_distribution module: pbx @@ -26,13 +27,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: manual file: tests/pbx/availability.spec.ts custom_fields: diff --git a/testcases/pbx/calls-security/pbx-calls-security-check-acl_ip_whitelisting_and_rate_limiting.yaml b/testcases/pbx/calls-security/pbx-calls-security-check-acl_ip_whitelisting_and_rate_limiting.yaml index a4cb0d3..3a08cdb 100644 --- a/testcases/pbx/calls-security/pbx-calls-security-check-acl_ip_whitelisting_and_rate_limiting.yaml +++ b/testcases/pbx/calls-security/pbx-calls-security-check-acl_ip_whitelisting_and_rate_limiting.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.031Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.888Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-calls-security-check-acl_ip_whitelisting_and_rate_limiting module: pbx @@ -28,13 +29,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Log in to the admin portal (if required) - expected: '' + expected: >- + Authentication succeeds using the provided credentials and the user is taken to the main + dashboard. - action: Navigate to the relevant settings section - expected: '' + expected: The correct configuration page or section for the feature is displayed. - action: Read current configuration values via UI or API - expected: '' + expected: >- + Current configuration values are successfully retrieved via the UI or API and match the known + baseline. automation_status: partial file: tests/pbx/calls-security.spec.ts custom_fields: diff --git a/testcases/pbx/calls-security/pbx-calls-security-check-srtp_sdes_or_dtls_media_encryption.yaml b/testcases/pbx/calls-security/pbx-calls-security-check-srtp_sdes_or_dtls_media_encryption.yaml index f283009..0cac666 100644 --- a/testcases/pbx/calls-security/pbx-calls-security-check-srtp_sdes_or_dtls_media_encryption.yaml +++ b/testcases/pbx/calls-security/pbx-calls-security-check-srtp_sdes_or_dtls_media_encryption.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.032Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.889Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-calls-security-check-srtp_sdes_or_dtls_media_encryption module: pbx @@ -28,13 +29,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Log in to the admin portal (if required) - expected: '' + expected: >- + Authentication succeeds using the provided credentials and the user is taken to the main + dashboard. - action: Navigate to the relevant settings section - expected: '' + expected: The correct configuration page or section for the feature is displayed. - action: Read current configuration values via UI or API - expected: '' + expected: >- + Current configuration values are successfully retrieved via the UI or API and match the known + baseline. automation_status: partial file: tests/pbx/calls-security.spec.ts custom_fields: diff --git a/testcases/pbx/calls-security/pbx-calls-security-check-toll_fraud_prevention_rules_and_alerting.yaml b/testcases/pbx/calls-security/pbx-calls-security-check-toll_fraud_prevention_rules_and_alerting.yaml index bfa90ca..99c2fac 100644 --- a/testcases/pbx/calls-security/pbx-calls-security-check-toll_fraud_prevention_rules_and_alerting.yaml +++ b/testcases/pbx/calls-security/pbx-calls-security-check-toll_fraud_prevention_rules_and_alerting.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.033Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.889Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-calls-security-check-toll_fraud_prevention_rules_and_alerting module: pbx @@ -28,13 +29,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Log in to the admin portal (if required) - expected: '' + expected: >- + Authentication succeeds using the provided credentials and the user is taken to the main + dashboard. - action: Navigate to the relevant settings section - expected: '' + expected: The correct configuration page or section for the feature is displayed. - action: Read current configuration values via UI or API - expected: '' + expected: >- + Current configuration values are successfully retrieved via the UI or API and match the known + baseline. automation_status: automated file: tests/pbx/calls-security.spec.ts custom_fields: diff --git a/testcases/pbx/calls/pbx-calls-check-call_hold_resume_and_music_on_hold.yaml b/testcases/pbx/calls/pbx-calls-check-call_hold_resume_and_music_on_hold.yaml index 0a2cf07..33f426c 100644 --- a/testcases/pbx/calls/pbx-calls-check-call_hold_resume_and_music_on_hold.yaml +++ b/testcases/pbx/calls/pbx-calls-check-call_hold_resume_and_music_on_hold.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.022Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.882Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-calls-check-call_hold_resume_and_music_on_hold module: pbx @@ -28,13 +29,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Ensure SIP endpoints / softphones are registered - expected: '' + expected: All required SIP endpoints show as registered with the correct status in the PBX. - action: Initiate or receive call using the required scenario - expected: '' + expected: >- + The call is successfully established between the endpoints with ringing and connection + confirmed. - action: Verify audio path, signaling, and media parameters - expected: '' + expected: >- + Two-way audio is clear and bidirectional. Signaling (SIP) is correct and media parameters + (codec, RTP/RTCP) match expectations. automation_status: manual file: tests/pbx/calls.spec.ts custom_fields: diff --git a/testcases/pbx/calls/pbx-calls-check-call_waiting_notification_and_switching.yaml b/testcases/pbx/calls/pbx-calls-check-call_waiting_notification_and_switching.yaml index e1d1e7e..cd514d8 100644 --- a/testcases/pbx/calls/pbx-calls-check-call_waiting_notification_and_switching.yaml +++ b/testcases/pbx/calls/pbx-calls-check-call_waiting_notification_and_switching.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.025Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.884Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-calls-check-call_waiting_notification_and_switching module: pbx @@ -28,13 +29,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Ensure SIP endpoints / softphones are registered - expected: '' + expected: All required SIP endpoints show as registered with the correct status in the PBX. - action: Initiate or receive call using the required scenario - expected: '' + expected: >- + The call is successfully established between the endpoints with ringing and connection + confirmed. - action: Verify audio path, signaling, and media parameters - expected: '' + expected: >- + Two-way audio is clear and bidirectional. Signaling (SIP) is correct and media parameters + (codec, RTP/RTCP) match expectations. automation_status: manual file: tests/pbx/calls.spec.ts custom_fields: diff --git a/testcases/pbx/calls/pbx-calls-check-caller_id_presentation_restriction_and_pai.yaml b/testcases/pbx/calls/pbx-calls-check-caller_id_presentation_restriction_and_pai.yaml index 61efec6..2834767 100644 --- a/testcases/pbx/calls/pbx-calls-check-caller_id_presentation_restriction_and_pai.yaml +++ b/testcases/pbx/calls/pbx-calls-check-caller_id_presentation_restriction_and_pai.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.026Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.885Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-calls-check-caller_id_presentation_restriction_and_pai module: pbx @@ -28,13 +29,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Ensure SIP endpoints / softphones are registered - expected: '' + expected: All required SIP endpoints show as registered with the correct status in the PBX. - action: Initiate or receive call using the required scenario - expected: '' + expected: >- + The call is successfully established between the endpoints with ringing and connection + confirmed. - action: Verify audio path, signaling, and media parameters - expected: '' + expected: >- + Two-way audio is clear and bidirectional. Signaling (SIP) is correct and media parameters + (codec, RTP/RTCP) match expectations. automation_status: manual file: tests/pbx/calls.spec.ts custom_fields: diff --git a/testcases/pbx/calls/pbx-calls-check-inbound_call_from_sip_trunk_pstn.yaml b/testcases/pbx/calls/pbx-calls-check-inbound_call_from_sip_trunk_pstn.yaml index e51be44..eb9137b 100644 --- a/testcases/pbx/calls/pbx-calls-check-inbound_call_from_sip_trunk_pstn.yaml +++ b/testcases/pbx/calls/pbx-calls-check-inbound_call_from_sip_trunk_pstn.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.027Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.886Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-calls-check-inbound_call_from_sip_trunk_pstn module: pbx @@ -28,13 +29,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Ensure SIP endpoints / softphones are registered - expected: '' + expected: All required SIP endpoints show as registered with the correct status in the PBX. - action: Initiate or receive call using the required scenario - expected: '' + expected: >- + The call is successfully established between the endpoints with ringing and connection + confirmed. - action: Verify audio path, signaling, and media parameters - expected: '' + expected: >- + Two-way audio is clear and bidirectional. Signaling (SIP) is correct and media parameters + (codec, RTP/RTCP) match expectations. automation_status: manual file: tests/pbx/calls.spec.ts custom_fields: diff --git a/testcases/pbx/calls/pbx-calls-check-internal_extension_to_extension_audio_call.yaml b/testcases/pbx/calls/pbx-calls-check-internal_extension_to_extension_audio_call.yaml index d164f16..5f26d53 100644 --- a/testcases/pbx/calls/pbx-calls-check-internal_extension_to_extension_audio_call.yaml +++ b/testcases/pbx/calls/pbx-calls-check-internal_extension_to_extension_audio_call.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.028Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.886Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-calls-check-internal_extension_to_extension_audio_call module: pbx @@ -28,13 +29,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Ensure SIP endpoints / softphones are registered - expected: '' + expected: All required SIP endpoints show as registered with the correct status in the PBX. - action: Initiate or receive call using the required scenario - expected: '' + expected: >- + The call is successfully established between the endpoints with ringing and connection + confirmed. - action: Verify audio path, signaling, and media parameters - expected: '' + expected: >- + Two-way audio is clear and bidirectional. Signaling (SIP) is correct and media parameters + (codec, RTP/RTCP) match expectations. automation_status: manual file: tests/pbx/calls.spec.ts custom_fields: diff --git a/testcases/pbx/calls/pbx-calls-check-outbound_call_to_sip_trunk_pstn_with_caller_id.yaml b/testcases/pbx/calls/pbx-calls-check-outbound_call_to_sip_trunk_pstn_with_caller_id.yaml index 6e0e5ac..9b7ee94 100644 --- a/testcases/pbx/calls/pbx-calls-check-outbound_call_to_sip_trunk_pstn_with_caller_id.yaml +++ b/testcases/pbx/calls/pbx-calls-check-outbound_call_to_sip_trunk_pstn_with_caller_id.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.029Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.887Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-calls-check-outbound_call_to_sip_trunk_pstn_with_caller_id module: pbx @@ -28,13 +29,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Ensure SIP endpoints / softphones are registered - expected: '' + expected: All required SIP endpoints show as registered with the correct status in the PBX. - action: Initiate or receive call using the required scenario - expected: '' + expected: >- + The call is successfully established between the endpoints with ringing and connection + confirmed. - action: Verify audio path, signaling, and media parameters - expected: '' + expected: >- + Two-way audio is clear and bidirectional. Signaling (SIP) is correct and media parameters + (codec, RTP/RTCP) match expectations. automation_status: manual file: tests/pbx/calls.spec.ts custom_fields: diff --git a/testcases/pbx/calls/pbx-calls-check-three_way_conference_and_multi_party_bridge.yaml b/testcases/pbx/calls/pbx-calls-check-three_way_conference_and_multi_party_bridge.yaml index d6baeca..874e88c 100644 --- a/testcases/pbx/calls/pbx-calls-check-three_way_conference_and_multi_party_bridge.yaml +++ b/testcases/pbx/calls/pbx-calls-check-three_way_conference_and_multi_party_bridge.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.030Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.887Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-calls-check-three_way_conference_and_multi_party_bridge module: pbx @@ -28,13 +29,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Ensure SIP endpoints / softphones are registered - expected: '' + expected: All required SIP endpoints show as registered with the correct status in the PBX. - action: Initiate or receive call using the required scenario - expected: '' + expected: >- + The call is successfully established between the endpoints with ringing and connection + confirmed. - action: Verify audio path, signaling, and media parameters - expected: '' + expected: >- + Two-way audio is clear and bidirectional. Signaling (SIP) is correct and media parameters + (codec, RTP/RTCP) match expectations. automation_status: manual file: tests/pbx/calls.spec.ts custom_fields: diff --git a/testcases/pbx/codecs/pbx-codecs-check-codec_negotiation_g711_g729_opus_g722.yaml b/testcases/pbx/codecs/pbx-codecs-check-codec_negotiation_g711_g729_opus_g722.yaml index f8e3b2f..f0ce3c4 100644 --- a/testcases/pbx/codecs/pbx-codecs-check-codec_negotiation_g711_g729_opus_g722.yaml +++ b/testcases/pbx/codecs/pbx-codecs-check-codec_negotiation_g711_g729_opus_g722.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.035Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.890Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-codecs-check-codec_negotiation_g711_g729_opus_g722 module: pbx @@ -28,13 +29,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Ensure SIP endpoints / softphones are registered - expected: '' + expected: All required SIP endpoints show as registered with the correct status in the PBX. - action: Initiate or receive call using the required scenario - expected: '' + expected: >- + The call is successfully established between the endpoints with ringing and connection + confirmed. - action: Verify audio path, signaling, and media parameters - expected: '' + expected: >- + Two-way audio is clear and bidirectional. Signaling (SIP) is correct and media parameters + (codec, RTP/RTCP) match expectations. automation_status: manual file: tests/pbx/codecs.spec.ts custom_fields: diff --git a/testcases/pbx/codecs/pbx-codecs-check-dtmf_transmission_rfc2833_inband_sip_info.yaml b/testcases/pbx/codecs/pbx-codecs-check-dtmf_transmission_rfc2833_inband_sip_info.yaml index 16adf98..2f3fb74 100644 --- a/testcases/pbx/codecs/pbx-codecs-check-dtmf_transmission_rfc2833_inband_sip_info.yaml +++ b/testcases/pbx/codecs/pbx-codecs-check-dtmf_transmission_rfc2833_inband_sip_info.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.036Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.890Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-codecs-check-dtmf_transmission_rfc2833_inband_sip_info module: pbx @@ -28,13 +29,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Ensure SIP endpoints / softphones are registered - expected: '' + expected: All required SIP endpoints show as registered with the correct status in the PBX. - action: Initiate or receive call using the required scenario - expected: '' + expected: >- + The call is successfully established between the endpoints with ringing and connection + confirmed. - action: Verify audio path, signaling, and media parameters - expected: '' + expected: >- + Two-way audio is clear and bidirectional. Signaling (SIP) is correct and media parameters + (codec, RTP/RTCP) match expectations. automation_status: manual file: tests/pbx/codecs.spec.ts custom_fields: diff --git a/testcases/pbx/codecs/pbx-codecs-check-t38_fax_passthrough_and_error_correction.yaml b/testcases/pbx/codecs/pbx-codecs-check-t38_fax_passthrough_and_error_correction.yaml index 00c7c02..1018c75 100644 --- a/testcases/pbx/codecs/pbx-codecs-check-t38_fax_passthrough_and_error_correction.yaml +++ b/testcases/pbx/codecs/pbx-codecs-check-t38_fax_passthrough_and_error_correction.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.037Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.891Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-codecs-check-t38_fax_passthrough_and_error_correction module: pbx @@ -28,13 +29,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Ensure SIP endpoints / softphones are registered - expected: '' + expected: All required SIP endpoints show as registered with the correct status in the PBX. - action: Initiate or receive call using the required scenario - expected: '' + expected: >- + The call is successfully established between the endpoints with ringing and connection + confirmed. - action: Verify audio path, signaling, and media parameters - expected: '' + expected: >- + Two-way audio is clear and bidirectional. Signaling (SIP) is correct and media parameters + (codec, RTP/RTCP) match expectations. automation_status: manual file: tests/pbx/codecs.spec.ts custom_fields: diff --git a/testcases/pbx/configuration/pbx-configuration-check-backup_restore_full_system_configuration.yaml b/testcases/pbx/configuration/pbx-configuration-check-backup_restore_full_system_configuration.yaml index f834759..f1f5c65 100644 --- a/testcases/pbx/configuration/pbx-configuration-check-backup_restore_full_system_configuration.yaml +++ b/testcases/pbx/configuration/pbx-configuration-check-backup_restore_full_system_configuration.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.039Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.891Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-configuration-check-backup_restore_full_system_configuration module: pbx @@ -24,13 +25,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Log in to the admin portal (if required) - expected: '' + expected: >- + Authentication succeeds using the provided credentials and the user is taken to the main + dashboard. - action: Navigate to the relevant settings section - expected: '' + expected: The correct configuration page or section for the feature is displayed. - action: Read current configuration values via UI or API - expected: '' + expected: >- + Current configuration values are successfully retrieved via the UI or API and match the known + baseline. automation_status: automated file: tests/pbx/configuration.spec.ts custom_fields: diff --git a/testcases/pbx/configuration/pbx-configuration-check-bulk_csv_import_export_of_settings.yaml b/testcases/pbx/configuration/pbx-configuration-check-bulk_csv_import_export_of_settings.yaml index 077c8a6..e312f4e 100644 --- a/testcases/pbx/configuration/pbx-configuration-check-bulk_csv_import_export_of_settings.yaml +++ b/testcases/pbx/configuration/pbx-configuration-check-bulk_csv_import_export_of_settings.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.040Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.892Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-configuration-check-bulk_csv_import_export_of_settings module: pbx @@ -24,13 +25,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Log in to the admin portal (if required) - expected: '' + expected: >- + Authentication succeeds using the provided credentials and the user is taken to the main + dashboard. - action: Navigate to the relevant settings section - expected: '' + expected: The correct configuration page or section for the feature is displayed. - action: Read current configuration values via UI or API - expected: '' + expected: >- + Current configuration values are successfully retrieved via the UI or API and match the known + baseline. automation_status: automated file: tests/pbx/configuration.spec.ts custom_fields: diff --git a/testcases/pbx/configuration/pbx-configuration-check-dialplan_route_and_outbound_rule_creation.yaml b/testcases/pbx/configuration/pbx-configuration-check-dialplan_route_and_outbound_rule_creation.yaml index dc1e01d..3982856 100644 --- a/testcases/pbx/configuration/pbx-configuration-check-dialplan_route_and_outbound_rule_creation.yaml +++ b/testcases/pbx/configuration/pbx-configuration-check-dialplan_route_and_outbound_rule_creation.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.041Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.893Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-configuration-check-dialplan_route_and_outbound_rule_creation module: pbx @@ -24,13 +25,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Log in to the admin portal (if required) - expected: '' + expected: >- + Authentication succeeds using the provided credentials and the user is taken to the main + dashboard. - action: Navigate to the relevant settings section - expected: '' + expected: The correct configuration page or section for the feature is displayed. - action: Read current configuration values via UI or API - expected: '' + expected: >- + Current configuration values are successfully retrieved via the UI or API and match the known + baseline. automation_status: automated file: tests/pbx/configuration.spec.ts custom_fields: diff --git a/testcases/pbx/configuration/pbx-configuration-check-initial_system_setup_and_network_settings.yaml b/testcases/pbx/configuration/pbx-configuration-check-initial_system_setup_and_network_settings.yaml index fb1229c..f8fa1aa 100644 --- a/testcases/pbx/configuration/pbx-configuration-check-initial_system_setup_and_network_settings.yaml +++ b/testcases/pbx/configuration/pbx-configuration-check-initial_system_setup_and_network_settings.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.042Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.893Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-configuration-check-initial_system_setup_and_network_settings module: pbx @@ -24,13 +25,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Log in to the admin portal (if required) - expected: '' + expected: >- + Authentication succeeds using the provided credentials and the user is taken to the main + dashboard. - action: Navigate to the relevant settings section - expected: '' + expected: The correct configuration page or section for the feature is displayed. - action: Read current configuration values via UI or API - expected: '' + expected: >- + Current configuration values are successfully retrieved via the UI or API and match the known + baseline. automation_status: automated file: tests/pbx/configuration.spec.ts custom_fields: diff --git a/testcases/pbx/extensions/pbx-extensions-check-create_modify_delete_sip_extensions.yaml b/testcases/pbx/extensions/pbx-extensions-check-create_modify_delete_sip_extensions.yaml index 6e08869..4134774 100644 --- a/testcases/pbx/extensions/pbx-extensions-check-create_modify_delete_sip_extensions.yaml +++ b/testcases/pbx/extensions/pbx-extensions-check-create_modify_delete_sip_extensions.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.043Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.894Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-extensions-check-create_modify_delete_sip_extensions module: pbx @@ -28,13 +29,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: automated file: tests/pbx/extensions.spec.ts custom_fields: diff --git a/testcases/pbx/extensions/pbx-extensions-check-device_provisioning.yaml b/testcases/pbx/extensions/pbx-extensions-check-device_provisioning.yaml index 7a9c704..2b90202 100644 --- a/testcases/pbx/extensions/pbx-extensions-check-device_provisioning.yaml +++ b/testcases/pbx/extensions/pbx-extensions-check-device_provisioning.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.045Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.895Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-extensions-check-device_provisioning module: pbx @@ -28,13 +29,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: partial file: tests/pbx/extensions.spec.ts custom_fields: diff --git a/testcases/pbx/extensions/pbx-extensions-check-extension_registration_with_deskphones_softphones.yaml b/testcases/pbx/extensions/pbx-extensions-check-extension_registration_with_deskphones_softphones.yaml index ccb8daf..b9d23d1 100644 --- a/testcases/pbx/extensions/pbx-extensions-check-extension_registration_with_deskphones_softphones.yaml +++ b/testcases/pbx/extensions/pbx-extensions-check-extension_registration_with_deskphones_softphones.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.046Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.896Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-extensions-check-extension_registration_with_deskphones_softphones module: pbx @@ -28,13 +29,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: manual file: tests/pbx/extensions.spec.ts custom_fields: diff --git a/testcases/pbx/features/core-features-check-integration_of_new_features_with_existing_call_processing_and_modules.yaml b/testcases/pbx/features/core-features-check-integration_of_new_features_with_existing_call_processing_and_modules.yaml index 40faf55..581ba71 100644 --- a/testcases/pbx/features/core-features-check-integration_of_new_features_with_existing_call_processing_and_modules.yaml +++ b/testcases/pbx/features/core-features-check-integration_of_new_features_with_existing_call_processing_and_modules.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.911Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.897Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-features-check-integration_of_new_features_with_existing_call_processing_and_modules module: pbx @@ -24,13 +25,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: partial file: tests/core/features.spec.ts custom_fields: diff --git a/testcases/pbx/features/core-features-check-performance_and_resource_impact_assessment_of_new_features.yaml b/testcases/pbx/features/core-features-check-performance_and_resource_impact_assessment_of_new_features.yaml index 908bdd1..9a4abd5 100644 --- a/testcases/pbx/features/core-features-check-performance_and_resource_impact_assessment_of_new_features.yaml +++ b/testcases/pbx/features/core-features-check-performance_and_resource_impact_assessment_of_new_features.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.915Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.898Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-features-check-performance_and_resource_impact_assessment_of_new_features module: pbx @@ -24,13 +25,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: manual file: tests/core/features.spec.ts custom_fields: diff --git a/testcases/pbx/logs/pbx-logs-check-call_quality_metrics_mos_jitter_loss_per_call.yaml b/testcases/pbx/logs/pbx-logs-check-call_quality_metrics_mos_jitter_loss_per_call.yaml index cbd23bf..ad5bc47 100644 --- a/testcases/pbx/logs/pbx-logs-check-call_quality_metrics_mos_jitter_loss_per_call.yaml +++ b/testcases/pbx/logs/pbx-logs-check-call_quality_metrics_mos_jitter_loss_per_call.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.048Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.899Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-logs-check-call_quality_metrics_mos_jitter_loss_per_call module: pbx @@ -24,13 +25,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: partial file: tests/pbx/logs.spec.ts custom_fields: diff --git a/testcases/pbx/logs/pbx-logs-check-cdr_generation_accuracy_completeness_and_export.yaml b/testcases/pbx/logs/pbx-logs-check-cdr_generation_accuracy_completeness_and_export.yaml index 9379f42..007e3ab 100644 --- a/testcases/pbx/logs/pbx-logs-check-cdr_generation_accuracy_completeness_and_export.yaml +++ b/testcases/pbx/logs/pbx-logs-check-cdr_generation_accuracy_completeness_and_export.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.049Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.899Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-logs-check-cdr_generation_accuracy_completeness_and_export module: pbx @@ -24,13 +25,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: automated file: tests/pbx/logs.spec.ts custom_fields: diff --git a/testcases/pbx/logs/pbx-logs-check-detailed_logging_levels_rotation_and_search.yaml b/testcases/pbx/logs/pbx-logs-check-detailed_logging_levels_rotation_and_search.yaml index a98da09..becc4ea 100644 --- a/testcases/pbx/logs/pbx-logs-check-detailed_logging_levels_rotation_and_search.yaml +++ b/testcases/pbx/logs/pbx-logs-check-detailed_logging_levels_rotation_and_search.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.050Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.900Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-logs-check-detailed_logging_levels_rotation_and_search module: pbx @@ -24,13 +25,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: automated file: tests/pbx/logs.spec.ts custom_fields: diff --git a/testcases/pbx/logs/pbx-logs-check-real_time_active_call_and_registration_monitoring.yaml b/testcases/pbx/logs/pbx-logs-check-real_time_active_call_and_registration_monitoring.yaml index 1dace51..fbae5ee 100644 --- a/testcases/pbx/logs/pbx-logs-check-real_time_active_call_and_registration_monitoring.yaml +++ b/testcases/pbx/logs/pbx-logs-check-real_time_active_call_and_registration_monitoring.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.051Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.900Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-logs-check-real_time_active_call_and_registration_monitoring module: pbx @@ -24,13 +25,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: automated file: tests/pbx/logs.spec.ts custom_fields: diff --git a/testcases/pbx/logs/pbx-logs-check-threshold_alarms_cpu_channels_disk_memory.yaml b/testcases/pbx/logs/pbx-logs-check-threshold_alarms_cpu_channels_disk_memory.yaml index de31cfb..83f5f24 100644 --- a/testcases/pbx/logs/pbx-logs-check-threshold_alarms_cpu_channels_disk_memory.yaml +++ b/testcases/pbx/logs/pbx-logs-check-threshold_alarms_cpu_channels_disk_memory.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.051Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.901Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-logs-check-threshold_alarms_cpu_channels_disk_memory module: pbx @@ -24,13 +25,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: automated file: tests/pbx/logs.spec.ts custom_fields: diff --git a/testcases/pbx/management/pbx-management-check-cli_management.yaml b/testcases/pbx/management/pbx-management-check-cli_management.yaml index d4d2059..c112f60 100644 --- a/testcases/pbx/management/pbx-management-check-cli_management.yaml +++ b/testcases/pbx/management/pbx-management-check-cli_management.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.052Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.901Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-management-check-cli_management module: pbx @@ -24,13 +25,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: partial file: tests/pbx/management.spec.ts custom_fields: diff --git a/testcases/pbx/management/pbx-management-check-gui_management.yaml b/testcases/pbx/management/pbx-management-check-gui_management.yaml index 9e09e66..3de7656 100644 --- a/testcases/pbx/management/pbx-management-check-gui_management.yaml +++ b/testcases/pbx/management/pbx-management-check-gui_management.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.053Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.902Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-management-check-gui_management module: pbx @@ -24,13 +25,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: automated file: tests/pbx/management.spec.ts custom_fields: diff --git a/testcases/pbx/performance/pbx-performance-check-cpu_memory_disk_io_utilization_under_sustained_load.yaml b/testcases/pbx/performance/pbx-performance-check-cpu_memory_disk_io_utilization_under_sustained_load.yaml index 382c32e..2dc331c 100644 --- a/testcases/pbx/performance/pbx-performance-check-cpu_memory_disk_io_utilization_under_sustained_load.yaml +++ b/testcases/pbx/performance/pbx-performance-check-cpu_memory_disk_io_utilization_under_sustained_load.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.055Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.902Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-performance-check-cpu_memory_disk_io_utilization_under_sustained_load module: pbx @@ -14,13 +15,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: manual file: tests/pbx/performance.spec.ts custom_fields: diff --git a/testcases/pbx/performance/pbx-performance-check-long_duration_stability_72h_test.yaml b/testcases/pbx/performance/pbx-performance-check-long_duration_stability_72h_test.yaml index 4a33859..e6dc379 100644 --- a/testcases/pbx/performance/pbx-performance-check-long_duration_stability_72h_test.yaml +++ b/testcases/pbx/performance/pbx-performance-check-long_duration_stability_72h_test.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.056Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.903Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-performance-check-long_duration_stability_72h_test module: pbx @@ -14,13 +15,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: manual file: tests/pbx/performance.spec.ts custom_fields: diff --git a/testcases/pbx/performance/pbx-performance-check-memory_leak_and_resource_cleanup_detection.yaml b/testcases/pbx/performance/pbx-performance-check-memory_leak_and_resource_cleanup_detection.yaml index 36c67b4..577dd9b 100644 --- a/testcases/pbx/performance/pbx-performance-check-memory_leak_and_resource_cleanup_detection.yaml +++ b/testcases/pbx/performance/pbx-performance-check-memory_leak_and_resource_cleanup_detection.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.057Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.903Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-performance-check-memory_leak_and_resource_cleanup_detection module: pbx @@ -14,13 +15,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: manual file: tests/pbx/performance.spec.ts custom_fields: diff --git a/testcases/pbx/regression/pbx-regression-check-core_call_features_after_any_code_change.yaml b/testcases/pbx/regression/pbx-regression-check-core_call_features_after_any_code_change.yaml index 9208511..0127a05 100644 --- a/testcases/pbx/regression/pbx-regression-check-core_call_features_after_any_code_change.yaml +++ b/testcases/pbx/regression/pbx-regression-check-core_call_features_after_any_code_change.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.059Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.903Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-regression-check-core_call_features_after_any_code_change module: pbx @@ -14,13 +15,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: partial file: tests/pbx/regression.spec.ts custom_fields: diff --git a/testcases/pbx/regression/pbx-regression-check-performance_baselines_comparison_against_previous_version.yaml b/testcases/pbx/regression/pbx-regression-check-performance_baselines_comparison_against_previous_version.yaml index b37df63..83d2a0f 100644 --- a/testcases/pbx/regression/pbx-regression-check-performance_baselines_comparison_against_previous_version.yaml +++ b/testcases/pbx/regression/pbx-regression-check-performance_baselines_comparison_against_previous_version.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.060Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.904Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-regression-check-performance_baselines_comparison_against_previous_version module: pbx @@ -14,13 +15,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: manual file: tests/pbx/regression.spec.ts custom_fields: diff --git a/testcases/pbx/regression/pbx-regression-check-previously_fixed_bugs_and_edge_cases_reverification.yaml b/testcases/pbx/regression/pbx-regression-check-previously_fixed_bugs_and_edge_cases_reverification.yaml index 81ddabc..317128c 100644 --- a/testcases/pbx/regression/pbx-regression-check-previously_fixed_bugs_and_edge_cases_reverification.yaml +++ b/testcases/pbx/regression/pbx-regression-check-previously_fixed_bugs_and_edge_cases_reverification.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.061Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.904Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-regression-check-previously_fixed_bugs_and_edge_cases_reverification module: pbx @@ -14,13 +15,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: partial file: tests/pbx/regression.spec.ts custom_fields: diff --git a/testcases/pbx/regression/pbx-regression-check-security_hardening_and_vulnerability_scan_baseline.yaml b/testcases/pbx/regression/pbx-regression-check-security_hardening_and_vulnerability_scan_baseline.yaml index 085c8a6..282bb6e 100644 --- a/testcases/pbx/regression/pbx-regression-check-security_hardening_and_vulnerability_scan_baseline.yaml +++ b/testcases/pbx/regression/pbx-regression-check-security_hardening_and_vulnerability_scan_baseline.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.062Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.904Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-regression-check-security_hardening_and_vulnerability_scan_baseline module: pbx @@ -18,13 +19,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: partial file: tests/pbx/regression.spec.ts custom_fields: diff --git a/testcases/pbx/security/core-security-check-sip_tls_and_srtp_encryption_enabled_by_default.yaml b/testcases/pbx/security/core-security-check-sip_tls_and_srtp_encryption_enabled_by_default.yaml index 83b1a2d..7bb1ef5 100644 --- a/testcases/pbx/security/core-security-check-sip_tls_and_srtp_encryption_enabled_by_default.yaml +++ b/testcases/pbx/security/core-security-check-sip_tls_and_srtp_encryption_enabled_by_default.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:11.987Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.905Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-security-check-sip_tls_and_srtp_encryption_enabled_by_default module: pbx @@ -24,13 +25,19 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Log in to the admin portal (if required) - expected: '' + expected: >- + Authentication succeeds using the provided credentials and the user is taken to the main + dashboard. - action: Navigate to the relevant settings section - expected: '' + expected: The correct configuration page or section for the feature is displayed. - action: Read current configuration values via UI or API - expected: '' + expected: >- + Current configuration values are successfully retrieved via the UI or API and match the known + baseline. automation_status: automated file: tests/core/security.spec.ts custom_fields: diff --git a/testcases/pbx/virtualization/core-virtualization-check-hypervisor_level_high_availability.yaml b/testcases/pbx/virtualization/core-virtualization-check-hypervisor_level_high_availability.yaml index 2a75a18..710fbb5 100644 --- a/testcases/pbx/virtualization/core-virtualization-check-hypervisor_level_high_availability.yaml +++ b/testcases/pbx/virtualization/core-virtualization-check-hypervisor_level_high_availability.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.008Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.905Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-virtualization-check-hypervisor_level_high_availability module: pbx @@ -26,13 +27,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: manual file: tests/core/virtualization.spec.ts custom_fields: diff --git a/testcases/pbx/virtualization/core-virtualization-check-live_migration_and_active_call_preservation.yaml b/testcases/pbx/virtualization/core-virtualization-check-live_migration_and_active_call_preservation.yaml index ee8d834..01cb384 100644 --- a/testcases/pbx/virtualization/core-virtualization-check-live_migration_and_active_call_preservation.yaml +++ b/testcases/pbx/virtualization/core-virtualization-check-live_migration_and_active_call_preservation.yaml @@ -1,5 +1,6 @@ -# Updated via Autotest Editor - 2026-05-25T21:52:12.009Z +# Updated via Autotest Editor - 2026-05-27T09:41:49.906Z # Source of truth: this YAML file +# Note: Expected results estimated based on step actions id: pbx-virtualization-check-live_migration_and_active_call_preservation module: pbx @@ -26,13 +27,21 @@ preconditions: [] postconditions: [] steps: - action: Open admin portal or repository URL in browser context - expected: '' + expected: >- + The admin portal or repository page loads successfully without errors, security warnings, or + redirects. - action: Execute the main verification or configuration action described in the test - expected: '' + expected: >- + The primary action described in the test completes successfully and produces the expected + state or output. - action: Capture evidence (screenshot, log, API response) - expected: '' + expected: >- + Relevant evidence (screenshot, log, or API response) is successfully captured and can be + reviewed. - action: Assert expected outcome - expected: '' + expected: >- + All verification assertions pass and the system is confirmed to be in the expected final + state. automation_status: manual file: tests/core/virtualization.spec.ts custom_fields: diff --git a/web/index.html b/web/index.html index fba256a..f8cffed 100644 --- a/web/index.html +++ b/web/index.html @@ -69,10 +69,12 @@ } .editable-list li { - display: flex; - align-items: center; - gap: 8px; - margin-bottom: 6px; + display: block; + margin-bottom: 0; + } + + #listSteps li { + margin-bottom: 0; } .editable-list input { @@ -93,6 +95,47 @@ color: var(--red); } + /* Step cards for better visual grouping in the modal */ + .step-card { + background: var(--input); + border: 1px solid var(--border); + border-radius: 8px; + padding: 8px 10px; + margin-bottom: 8px; + } + + .step-card input { + background: var(--bg); + border: 1px solid var(--border); + } + + .step-header { + display: flex; + gap: 6px; + align-items: center; + margin-bottom: 6px; + } + + .step-number { + font-size: 11px; + font-weight: 600; + color: var(--text-secondary); + min-width: 20px; + text-align: center; + } + + .step-label { + font-size: 10px; + color: var(--text-secondary); + margin-bottom: 2px; + display: block; + letter-spacing: 0.3px; + } + + .step-expected input { + font-size: 12px; + } + .dep-row { display: flex; gap: 8px; @@ -182,9 +225,9 @@ -
- -
+ +
+

@@ -195,10 +238,6 @@

-
- 0 test cases loaded -
-
+
- + +
@@ -231,6 +272,15 @@
+ +
+
+ Tests overview + 0 tests +
+ +
+
@@ -270,15 +320,10 @@
-
+
-
- +
Description
- + +
+
+ + +
+ + + +
+ + +
+
+
Dependencies
+ +
+
+
+ +
Test Steps
@@ -304,64 +377,14 @@
    - - -
    -
    -
    Automatable
    - -
    -
      -
      - - -
      -
      -
      Not Automatable Yet / Manual
      - -
      -
        -
        - - -
        -
        Code Generation (Automated)
        - -
        - - -
        - -
        -
        Implementation Notes (for generator / LLM)
        - -
        - - -
        -
        -
        Code Steps (for generator)
        - -
        -
        -
        -
        - - -
        -
        -
        Dependencies & Prerequisites
        - -
        -
        -
        - +
        @@ -381,7 +404,6 @@ renderTable(); renderGroupsOverview(); updateSelectionCount(); - document.getElementById('count').textContent = allTests.length; } catch (e) { alert('Could not load test cases. Make sure the server is running and data file exists.'); console.error(e); @@ -611,6 +633,7 @@ tbody.innerHTML = html; updateSelectionCount(); + updateVisibleCount(); } function resetFilters() { @@ -707,6 +730,14 @@ } } + function updateVisibleCount() { + const el = document.getElementById('visibleCount'); + if (el) { + const n = filteredTests.length; + el.textContent = `${n} test${n === 1 ? '' : 's'}`; + } + } + // Unified Plans modal (Create + Load) @@ -864,24 +895,26 @@ document.getElementById('modalId').textContent = currentTest.id; document.getElementById('modalGroup').textContent = `${currentTest.group} • ${currentTest.file}`; - document.getElementById('modalDescription').value = currentTest.description || ''; - document.getElementById('modalStatus').value = currentTest.status; + document.getElementById('modalDescription').value = currentTest.description || ''; - // Code Generation fields (Phase 1) - const fullyAutomatedEl = document.getElementById('fullyAutomated'); - fullyAutomatedEl.checked = !!currentTest.fullyAutomated; + // Automatable checkbox + tool selector + const autoCb = document.getElementById('automatableCheckbox'); + if (typeof currentTest.automatable === 'boolean') { + autoCb.checked = currentTest.automatable; + } else { + autoCb.checked = currentTest.status === 'automated'; + } - const notesEl = document.getElementById('implementationNotes'); - notesEl.value = currentTest.implementationNotes || ''; + const toolSelect = document.getElementById('automationTool'); + if (toolSelect) { + toolSelect.value = currentTest.automationTool || ''; + } - // Code Steps - renderCodeSteps(currentTest.codeSteps || []); + toggleAutomationTool(); - // Render lists - renderRichSteps(currentTest.steps || []); - renderList('listAutomatable', currentTest.automatable || []); - renderList('listNotYet', currentTest.notYet || []); - renderDependencies(currentTest.dependencies || []); + // Render the 4 definition fields + renderRichSteps(currentTest.steps || []); + renderDependencies(currentTest.dependencies || []); document.getElementById('editModal').classList.remove('hidden'); document.getElementById('editModal').classList.add('flex'); @@ -921,34 +954,45 @@ renderList(id, items); } - // === Simplified step editor (automation decision moved to testcase level) === + // === Step editor: action + expected result only (notes removed per definition rules) === function renderRichSteps(steps) { const ul = document.getElementById('listSteps'); ul.innerHTML = ''; const rich = steps.map(s => { if (typeof s === 'string') { - return { action: s, expected: '', notes: '' }; + return { action: s, expected: '' }; } return { action: s.action || s, - expected: s.expected || '', - notes: s.notes || '' + expected: s.expected || '' }; }); rich.forEach((step, idx) => { const li = document.createElement('li'); - li.style.flexDirection = 'column'; - li.style.alignItems = 'stretch'; - li.style.gap = '4px'; li.innerHTML = ` -
        - - +
        +
        + ${idx + 1} + + +
        +
        + Expected result + +
        - - `; ul.appendChild(li); }); @@ -973,10 +1017,18 @@ function addRichStep() { const ul = document.getElementById('listSteps'); const steps = JSON.parse(ul.dataset.richSteps || '[]'); - steps.push({ action: '', expected: '', notes: '' }); + steps.push({ action: '', expected: '' }); renderRichSteps(steps); } + function toggleAutomationTool() { + const cb = document.getElementById('automatableCheckbox'); + const container = document.getElementById('automationToolContainer'); + if (container) { + container.classList.toggle('hidden', !cb.checked); + } + } + function renderDependencies(deps) { const container = document.getElementById('depContainer'); container.innerHTML = deps.map((d, i) => ` @@ -1010,75 +1062,16 @@ renderDependencies(deps); } - // === Code Steps Editor (for automated generation) === - - function renderCodeSteps(codeSteps = []) { - const container = document.getElementById('codeStepsContainer'); - container.innerHTML = ''; - - codeSteps.forEach((step, index) => { - const div = document.createElement('div'); - div.className = 'flex gap-2 items-center bg-[var(--input)] p-2 rounded'; - const paramsValue = step.params ? JSON.stringify(step.params) : ''; - div.innerHTML = ` - - - - - `; - container.appendChild(div); - }); - - container.dataset.codeSteps = JSON.stringify(codeSteps); - } - - function updateCodeStep(index, field, value) { - const container = document.getElementById('codeStepsContainer'); - const steps = JSON.parse(container.dataset.codeSteps || '[]'); - if (!steps[index]) steps[index] = {}; - steps[index][field] = value; - container.dataset.codeSteps = JSON.stringify(steps); - } - - function updateCodeStepParams(index, value) { - const container = document.getElementById('codeStepsContainer'); - const steps = JSON.parse(container.dataset.codeSteps || '[]'); - if (!steps[index]) steps[index] = {}; - try { - steps[index].params = value ? JSON.parse(value) : undefined; - } catch (e) { - // keep previous value if JSON is invalid - } - container.dataset.codeSteps = JSON.stringify(steps); - } - - function removeCodeStep(index) { - const container = document.getElementById('codeStepsContainer'); - const steps = JSON.parse(container.dataset.codeSteps || '[]'); - steps.splice(index, 1); - renderCodeSteps(steps); - } - - function addCodeStep() { - const container = document.getElementById('codeStepsContainer'); - const steps = JSON.parse(container.dataset.codeSteps || '[]'); - steps.push({ stepName: '', actionKey: '' }); - renderCodeSteps(steps); - } - async function resetToSuggested() { if (!currentTest) return; - // Build a minimal test object from current modal values + // Build a minimal test object from current modal values (no status select anymore) const tempTest = { id: currentTest.id, group: currentTest.group, module: currentTest.module, action: currentTest.action, - description: document.getElementById('modalDescription').value.trim(), - status: document.getElementById('modalStatus').value, - manualReason: currentTest.manualReason, - partialNotes: currentTest.partialNotes + description: document.getElementById('modalDescription').value.trim() }; try { @@ -1089,15 +1082,19 @@ }); const rich = await res.json(); - // Repopulate lists with suggested values + // Repopulate only the fields the modal still edits currentTest.steps = rich.steps || []; - currentTest.automatable = rich.automatable || []; - currentTest.notYet = rich.notYet || []; currentTest.dependencies = rich.dependencies || []; - renderList('listSteps', currentTest.steps); - renderList('listAutomatable', currentTest.automatable); - renderList('listNotYet', currentTest.notYet); + // Set the simple automatable checkbox from the suggestion if possible + const autoCb = document.getElementById('automatableCheckbox'); + if (rich.automatable && rich.automatable.length > 0) { + autoCb.checked = true; + } + + toggleAutomationTool(); + + renderRichSteps(currentTest.steps); renderDependencies(currentTest.dependencies); } catch (e) { @@ -1109,33 +1106,27 @@ function saveCurrentTest() { if (currentIndex < 0) return; - // Collect values + // Collect the 4 definition fields (aligned with YAML) currentTest.description = document.getElementById('modalDescription').value.trim(); - currentTest.status = document.getElementById('modalStatus').value; - // Code Generation fields (Phase 1) - const fullyAutomatedEl = document.getElementById('fullyAutomated'); - currentTest.fullyAutomated = fullyAutomatedEl.checked; + // Automatable as boolean + keep status in sync for the rest of the system + const autoChecked = document.getElementById('automatableCheckbox').checked; + currentTest.automatable = autoChecked; + currentTest.status = autoChecked ? 'automated' : 'manual'; - const notesEl = document.getElementById('implementationNotes'); - currentTest.implementationNotes = notesEl.value.trim() || undefined; + // Save selected automation tool (only meaningful when automatable) + const toolSelect = document.getElementById('automationTool'); + if (autoChecked && toolSelect) { + currentTest.automationTool = toolSelect.value || undefined; + } else { + currentTest.automationTool = undefined; + } - // Code Steps - const codeStepsContainer = document.getElementById('codeStepsContainer'); - currentTest.codeSteps = JSON.parse(codeStepsContainer.dataset.codeSteps || '[]') - .filter(s => s.stepName || s.actionKey); - - // Collect steps (now simplified: action + expected + optional notes) + // Steps: only action + expected (notes are never written from the modal anymore) const stepsUl = document.getElementById('listSteps'); const richFromUI = JSON.parse(stepsUl.dataset.richSteps || '[]'); currentTest.steps = richFromUI.length > 0 ? richFromUI : (JSON.parse(stepsUl.dataset.items || '[]').filter(Boolean)); - const autoUl = document.getElementById('listAutomatable'); - currentTest.automatable = JSON.parse(autoUl.dataset.items || '[]').filter(Boolean); - - const notUl = document.getElementById('listNotYet'); - currentTest.notYet = JSON.parse(notUl.dataset.items || '[]').filter(Boolean); - const depContainer = document.getElementById('depContainer'); currentTest.dependencies = JSON.parse(depContainer.dataset.deps || '[]') .filter(d => d.label || d.value); @@ -1147,8 +1138,8 @@ closeModal(); renderTable(); - document.getElementById('status').classList.add('dirty'); - document.getElementById('status').innerHTML = 'Unsaved changes'; + const fb = document.getElementById('saveFeedback'); + if (fb) fb.textContent = 'Unsaved changes'; } function closeModal() { @@ -1178,10 +1169,10 @@ if (json.success) { isDirty = false; - document.getElementById('status').classList.remove('dirty'); - document.getElementById('status').innerHTML = `${allTests.length} test cases saved`; + const fb = document.getElementById('saveFeedback'); + if (fb) fb.textContent = 'Saved!'; - // Show temporary success feedback + // Show temporary success feedback on the button if (saveBtn) { saveBtn.innerHTML = ` Saved!`; saveBtn.style.borderColor = '#6cc76f'; @@ -1195,6 +1186,8 @@ saveBtn.style.color = ''; saveBtn.disabled = false; } + const fb = document.getElementById('saveFeedback'); + if (fb) fb.textContent = ''; }, 1800); } else { throw new Error(json.error || 'Unknown error'); @@ -1222,8 +1215,8 @@ if (isDirty && !confirm('You have unsaved changes. Reload anyway?')) return; await loadData(); isDirty = false; - document.getElementById('status').classList.remove('dirty'); - document.getElementById('status').innerHTML = `${allTests.length} test cases loaded`; + const fb = document.getElementById('saveFeedback'); + if (fb) fb.textContent = ''; } // Keyboard shortcuts @@ -1243,5 +1236,6 @@ loadData(); }; +