mejoras en el modal de los testcases

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),
+    steps: (yamlTest.steps || []).map(s => {
-    automatable: cf.original_automatable || [],
+      if (typeof s === 'string') {
-    notYet: cf.original_notYet || [],
+        return { action: s, expected: '' };
-    dependencies: cf.original_dependencies || [],
+      }
+      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

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();

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

web/index.html

@@ -69,10 +69,12 @@
     }
 
     .editable-list li {
-      display: flex;
+      display: block;
-      align-items: center;
+      margin-bottom: 0;
-      gap: 8px;
+    }
-      margin-bottom: 6px;
+
+    #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 @@
   </style>
 </head>
 <body class="text-sm">
-  <div class="max-w-[1600px] mx-auto">
+  <!-- Full-width Navbar -->
-    <!-- Header -->
+  <div class="bg-[var(--bg-secondary)] border-b border-[var(--border)]">
-    <div class="bg-[var(--bg-secondary)] border-b border-[var(--border)] px-8 py-5 flex items-center justify-between">
+    <div class="max-w-[1600px] mx-auto px-8 py-5 flex items-center justify-between">
       <div>
         <h1 onclick="resetToHome()" 
             class="text-2xl font-bold flex items-center gap-3 cursor-pointer hover:text-[var(--accent)] transition-colors">
@@ -195,10 +238,6 @@
       </div>
 
       <div class="flex items-center gap-3">
-        <div id="status" class="text-xs px-3 py-1 rounded bg-[var(--card)] text-[var(--accent-warm)] font-medium">
-          <span id="count">0</span> test cases loaded
-        </div>
-
         <button onclick="saveAll()" 
                 class="h-10 px-4 nav-button rounded-lg font-semibold flex items-center gap-2 text-sm">
           <i class="fa-solid fa-save"></i>
@@ -219,8 +258,10 @@
         </button>
       </div>
     </div>
+  </div>
 
-
+  <!-- Constrained content -->
+  <div class="max-w-[1600px] mx-auto">
 
     <!-- Groups Overview (high-level bird's eye view) -->
     <div class="px-8 pt-2">
@@ -231,6 +272,15 @@
       <div id="groupsOverview" class="min-h-[120px]"></div>
     </div>
 
+    <!-- Tests overview -->
+    <div class="px-8 pt-3 pb-1 flex items-center justify-between">
+      <div class="flex items-center gap-2">
+        <span class="text-sm font-semibold text-[#a0a0b0]">Tests overview</span>
+        <span id="visibleCount" class="text-xs text-[var(--accent-warm)] font-medium">0 tests</span>
+      </div>
+      <span id="saveFeedback" class="text-xs text-amber-400"></span>
+    </div>
+
     <!-- Table -->
     <div class="px-8 pt-4 pb-12">
       <!-- Selection Toolbar -->
@@ -270,15 +320,10 @@
       <!-- Modal Header -->
       <div class="px-6 py-4 border-b border-[var(--border)] flex items-center justify-between bg-[var(--input)] rounded-t-2xl">
         <div>
-          <div id="modalId" class="font-mono text-sm text-[#94a3b8]"></div>
+          <div id="modalId" class="font-mono text-sm text-[var(--accent-warm)]"></div>
           <div id="modalGroup" class="text-xs text-[#64748b]"></div>
         </div>
         <div class="flex items-center gap-3">
-          <select id="modalStatus" class="bg-[var(--input)] border border-[var(--border)] text-sm rounded px-3 py-1">
-            <option value="automated">Automated</option>
-            <option value="partial">Partial</option>
-            <option value="manual">Manual</option>
-          </select>
            <button onclick="resetToSuggested()" 
                    class="text-xs px-3 py-1 bg-[var(--input)] text-[var(--accent)] border border-[var(--accent)] hover:bg-[#2f2a3f] rounded flex items-center gap-1 whitespace-nowrap">
              <i class="fa-solid fa-magic"></i>
@@ -289,14 +334,42 @@
       </div>
 
       <div class="p-6 overflow-auto flex-1 space-y-6 text-sm">
-        <!-- Description -->
+        <!-- 1. Description -->
         <div>
           <div class="section-title mb-1.5">Description</div>
           <textarea id="modalDescription" rows="2" 
                     class="w-full bg-[var(--input)] border border-[var(--border)] rounded-lg p-3 text-sm"></textarea>
         </div>
 
-        <!-- Steps -->
+        <!-- 2. Automatable -->
+        <div>
+          <div class="flex items-center gap-2">
+            <input type="checkbox" id="automatableCheckbox" class="w-4 h-4" onchange="toggleAutomationTool()">
+            <label for="automatableCheckbox" class="section-title text-emerald-400 cursor-pointer">Automatable</label>
+          </div>
+
+          <!-- Automation tool selector (shown only when Automatable is checked) -->
+          <div id="automationToolContainer" class="mt-2 hidden">
+            <div class="text-xs text-[#64748b] mb-1">Automation tool</div>
+            <select id="automationTool" class="bg-[var(--input)] border border-[var(--border)] rounded px-3 py-1 text-sm w-full">
+              <option value="">Select tool...</option>
+              <option value="agent-ai">Agent AI</option>
+              <option value="playwright">Playwright</option>
+              <option value="paramiko">Paramiko</option>
+            </select>
+          </div>
+        </div>
+
+        <!-- 3. Dependencies -->
+        <div>
+          <div class="flex justify-between items-center mb-1.5">
+            <div class="section-title">Dependencies</div>
+            <button onclick="addDependency()" class="text-xs px-2.5 py-0.5 bg-[var(--border)] hover:bg-[var(--border-light)] rounded">+ Add</button>
+          </div>
+          <div id="depContainer" class="space-y-1"></div>
+        </div>
+
+        <!-- 4. Test Steps (action + expected result only) -->
         <div>
           <div class="flex justify-between items-center mb-1.5">
             <div class="section-title">Test Steps</div>
@@ -304,64 +377,14 @@
           </div>
           <ul id="listSteps" class="editable-list text-sm"></ul>
         </div>
-
-        <!-- Automatable -->
-        <div>
-          <div class="flex justify-between items-center mb-1.5">
-            <div class="section-title text-emerald-400">Automatable</div>
-            <button onclick="addListItem('automatable')" class="text-xs px-2.5 py-0.5 bg-emerald-900/60 hover:bg-emerald-800 rounded">+ Add</button>
-          </div>
-          <ul id="listAutomatable" class="editable-list text-sm"></ul>
-        </div>
-
-         <!-- Not Yet -->
-         <div>
-           <div class="flex justify-between items-center mb-1.5">
-             <div class="section-title text-red-400">Not Automatable Yet / Manual</div>
-             <button onclick="addListItem('notYet')" class="text-xs px-2.5 py-0.5 bg-red-900/60 hover:bg-red-800 rounded">+ Add</button>
-           </div>
-           <ul id="listNotYet" class="editable-list text-sm"></ul>
-         </div>
-
-         <!-- Code Generation (for automated tests) -->
-         <div>
-           <div class="section-title mb-1.5 text-[#a277ff]">Code Generation (Automated)</div>
-
-           <div class="flex items-center gap-2 mb-2">
-             <input type="checkbox" id="fullyAutomated" class="w-4 h-4">
-             <label for="fullyAutomated" class="text-sm">Mark as <strong>fullyAutomated</strong> (ready for code generation)</label>
-           </div>
-
-           <div class="mb-2">
-             <div class="text-xs text-[#64748b] mb-1">Implementation Notes (for generator / LLM)</div>
-             <textarea id="implementationNotes" rows="2"
-                       class="w-full bg-[var(--input)] border border-[var(--border)] rounded p-2 text-sm"
-                       placeholder="Hints for the code generator..."></textarea>
-           </div>
-
-           <!-- codeSteps editor -->
-           <div>
-             <div class="flex justify-between items-center mb-1">
-               <div class="text-xs text-[#64748b]">Code Steps (for generator)</div>
-               <button onclick="addCodeStep()" class="text-xs px-2 py-0.5 bg-[var(--border)] hover:bg-[var(--border-light)] rounded text-[var(--accent-warm)]">+ Add Step</button>
-             </div>
-             <div id="codeStepsContainer" class="space-y-2 text-sm"></div>
-           </div>
-         </div>
-
-         <!-- Dependencies -->
-        <div>
-          <div class="flex justify-between items-center mb-1.5">
-            <div class="section-title">Dependencies &amp; Prerequisites</div>
-            <button onclick="addDependency()" class="text-xs px-2.5 py-0.5 bg-[var(--border)] hover:bg-[var(--border-light)] rounded">+ Add dependency</button>
-          </div>
-          <div id="depContainer" class="space-y-1"></div>
-        </div>
       </div>
 
       <div class="px-6 py-4 border-t border-[var(--border)] bg-[var(--input)] rounded-b-2xl flex justify-end gap-3">
         <button onclick="closeModal()" class="px-5 py-2 text-sm rounded-lg bg-[var(--border)] hover:bg-[var(--border-light)]">Cancel</button>
-        <button onclick="saveCurrentTest()" class="px-6 py-2 text-sm rounded-lg bg-sky-600 hover:bg-sky-500 font-semibold">Save Changes to Test</button>
+        <button onclick="saveCurrentTest()" 
+                class="px-5 py-2 text-sm rounded-lg bg-[var(--input)] text-[var(--accent)] border border-[var(--accent)] hover:bg-[#2f2a3f] font-semibold">
+          Save
+        </button>
       </div>
     </div>
   </div>
@@ -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)
@@ -865,22 +896,24 @@
       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;
 
-       // Code Generation fields (Phase 1)
+      // Automatable checkbox + tool selector
-       const fullyAutomatedEl = document.getElementById('fullyAutomated');
+      const autoCb = document.getElementById('automatableCheckbox');
-       fullyAutomatedEl.checked = !!currentTest.fullyAutomated;
+      if (typeof currentTest.automatable === 'boolean') {
+        autoCb.checked = currentTest.automatable;
+      } else {
+        autoCb.checked = currentTest.status === 'automated';
+      }
 
-       const notesEl = document.getElementById('implementationNotes');
+      const toolSelect = document.getElementById('automationTool');
-       notesEl.value = currentTest.implementationNotes || '';
+      if (toolSelect) {
+        toolSelect.value = currentTest.automationTool || '';
+      }
 
-       // Code Steps
+      toggleAutomationTool();
-       renderCodeSteps(currentTest.codeSteps || []);
 
-        // Render lists
+      // Render the 4 definition fields
       renderRichSteps(currentTest.steps || []);
-        renderList('listAutomatable', currentTest.automatable || []);
-        renderList('listNotYet', currentTest.notYet || []);
       renderDependencies(currentTest.dependencies || []);
 
       document.getElementById('editModal').classList.remove('hidden');
@@ -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 || '',
+          expected: s.expected || ''
-          notes: s.notes || ''
         };
       });
 
       rich.forEach((step, idx) => {
         const li = document.createElement('li');
-        li.style.flexDirection = 'column';
-        li.style.alignItems = 'stretch';
-        li.style.gap = '4px';
         li.innerHTML = `
-          <div style="display:flex; gap:8px; align-items:center;">
+          <div class="step-card">
-            <input value="${(step.action || '').replace(/"/g, '&quot;')}" placeholder="Action" style="flex:1" oninput="updateRichStep(${idx}, 'action', this.value)">
+            <div class="step-header">
-            <button onclick="removeRichStep(${idx})" style="color:#f87171;"><i class="fa-solid fa-trash text-xs"></i></button>
+              <span class="step-number">${idx + 1}</span>
+              <input 
+                value="${(step.action || '').replace(/"/g, '&quot;')}" 
+                placeholder="Action / Description" 
+                style="flex:1; font-size:13px;"
+                oninput="updateRichStep(${idx}, 'action', this.value)">
+              <button onclick="removeRichStep(${idx})" style="color:#f87171; padding: 2px 4px;">
+                <i class="fa-solid fa-trash text-xs"></i>
+              </button>
+            </div>
+            <div class="step-expected">
+              <span class="step-label">Expected result</span>
+              <input 
+                value="${(step.expected || '').replace(/"/g, '&quot;')}" 
+                placeholder="What should happen after this step"
+                style="width:100%;"
+                oninput="updateRichStep(${idx}, 'expected', this.value)">
+            </div>
           </div>
-          <input value="${(step.expected || '').replace(/"/g, '&quot;')}" placeholder="Expected result (optional)" style="font-size:12px; margin-top:2px;" oninput="updateRichStep(${idx}, 'expected', this.value)">
-          <input value="${(step.notes || '').replace(/"/g, '&quot;')}" placeholder="Notes (optional)" style="font-size:12px; margin-top:2px; color:#94a3b8;" oninput="updateRichStep(${idx}, 'notes', this.value)">
         `;
         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 = `
-            <input placeholder="Step Name" value="${step.stepName || ''}" class="flex-1 text-xs" oninput="updateCodeStep(${index}, 'stepName', this.value)">
-            <input placeholder="Action Key" value="${step.actionKey || ''}" class="flex-1 text-xs" oninput="updateCodeStep(${index}, 'actionKey', this.value)">
-            <input placeholder='Params (JSON)' value='${paramsValue}' class="flex-1 text-xs" oninput="updateCodeStepParams(${index}, this.value)">
-            <button onclick="removeCodeStep(${index})" class="text-red-400 hover:text-red-500 px-1">×</button>
-          `;
-          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(),
+        description: document.getElementById('modalDescription').value.trim()
-        status: document.getElementById('modalStatus').value,
-        manualReason: currentTest.manualReason,
-        partialNotes: currentTest.partialNotes
       };
 
       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);
+        // Set the simple automatable checkbox from the suggestion if possible
-        renderList('listAutomatable', currentTest.automatable);
+        const autoCb = document.getElementById('automatableCheckbox');
-        renderList('listNotYet', currentTest.notYet);
+        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)
+      // Automatable as boolean + keep status in sync for the rest of the system
-      const fullyAutomatedEl = document.getElementById('fullyAutomated');
+      const autoChecked = document.getElementById('automatableCheckbox').checked;
-      currentTest.fullyAutomated = fullyAutomatedEl.checked;
+      currentTest.automatable = autoChecked;
+      currentTest.status = autoChecked ? 'automated' : 'manual';
 
-      const notesEl = document.getElementById('implementationNotes');
+      // Save selected automation tool (only meaningful when automatable)
-      currentTest.implementationNotes = notesEl.value.trim() || undefined;
+      const toolSelect = document.getElementById('automationTool');
+      if (autoChecked && toolSelect) {
+        currentTest.automationTool = toolSelect.value || undefined;
+      } else {
+        currentTest.automationTool = undefined;
+      }
 
-      // Code Steps
+      // Steps: only action + expected (notes are never written from the modal anymore)
-      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)
       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');
+      const fb = document.getElementById('saveFeedback');
-      document.getElementById('status').innerHTML = '<span class="text-amber-400">Unsaved changes</span>';
+      if (fb) fb.textContent = 'Unsaved changes';
     }
 
     function closeModal() {
@@ -1178,10 +1169,10 @@
 
         if (json.success) {
           isDirty = false;
-          document.getElementById('status').classList.remove('dirty');
+          const fb = document.getElementById('saveFeedback');
-          document.getElementById('status').innerHTML = `<span id="count">${allTests.length}</span> test cases saved`;
+          if (fb) fb.textContent = 'Saved!';
 
-          // Show temporary success feedback
+          // Show temporary success feedback on the button
           if (saveBtn) {
             saveBtn.innerHTML = `<i class="fa-solid fa-check"></i> <span>Saved!</span>`;
             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');
+      const fb = document.getElementById('saveFeedback');
-      document.getElementById('status').innerHTML = `<span id="count">${allTests.length}</span> test cases loaded`;
+      if (fb) fb.textContent = '';
     }
 
     // Keyboard shortcuts
@@ -1243,5 +1236,6 @@
       loadData();
     };
   </script>
+  </div> <!-- close max-w content container -->
 </body>
 </html>