mejoras en el modal de los testcases

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: