AWS connect documentation change
Summary
Restructured test case documentation: removed sections about security profile permissions, test execution limits, timeout behaviors, and best practices to prevent simulated contacts from reaching live agents. Added channel-specific configuration details (voice/chat) and updated navigation steps.
Security assessment
The removed content included security-related best practices (e.g., preventing simulated contacts from reaching live agents) and security profile permissions, but there is no explicit evidence this was done to address an active security vulnerability. The changes appear to be general documentation restructuring rather than patching a specific security issue. However, removal of queue interaction warnings could reduce awareness of operational security practices.
Diff
diff --git a/connect/latest/adminguide/testing-simulation-test-cases.md b/connect/latest/adminguide/testing-simulation-test-cases.md index 8a68a7e24..d2c68669a 100644 --- a//connect/latest/adminguide/testing-simulation-test-cases.md +++ b//connect/latest/adminguide/testing-simulation-test-cases.md @@ -7,33 +7 @@ Create test case -# Create and run test cases - -The following section shows how to create and execute test cases. Before you use Connect's testing and simulation capabilities, you must have access to all test case permissions. If you use an admin security profile, all testing and simulation permissions are granted by default. Admin can grant permissions to onboard other user profiles with the new testing and simulation security profile. - - - -During test execution, please be aware of the following limitations and behaviors: - - * **Concurrent Test Limit:** You can run up to 5 concurrent tests. Additional tests will remain in Queue state while 5 test cases are actively running. - - * **Test Execution Queue Capacity:** The system accepts up to 100 test executions in the queue including the two running tests. Any requests exceeding this limit will be rejected. - - * **Test Duration Limit:** Each test simulation has a maximum duration of 5 minutes. If a simulation exceeds this time limit, the test execution will automatically timeout and terminate. - - * **Automatic Timeout:** Tests that are not manually ended using Action block test commands will automatically timeout after 5 minutes of total execution time. - - * **Agent Queue Interaction:** If you do not end the test before the simulated contact is transferred to a queue, the simulated contact may reach the agent queue and connect with a live agent as a contact. - - * **Test Execution Record Retention:** Test runs and their respective test result records are retained for 30 days from the execution date for any test cases run before February 9th, 2026. Tests run on or after that date will have their records kept indefinitely. - - - - -To prevent simulated contacts from reaching live agents, consider these approaches: - -###### Best practice to handle simulated contact in the agent queue - - * **Proactive Test Termination:** Use Action blocks to end tests before simulated contacts reach agents, preventing disruption to live operations if applicable. - - * **Test Queue Substitution:** Use Action blocks to replace production queues with dedicated test queues in your test case configuration, ensuring real agents are not impacted. - - - +# Create test cases @@ -49 +17,3 @@ The following procedure shows how to create a test case. - 2. In the main navigation pane, choose **Routing** , and then **Tests**. + 2. In the main navigation pane, choose **Routing** , and then **Tests** to open the Test case management page to view list of existing test cases. + + @@ -57 +27,5 @@ The following procedure shows how to create a test case. - 5. Choose the **Settings** tab to specify channel, starting point including contact flow, phone number, contact flow to start, incoming phone number, simulated contact data or other metadata to be used during test case execution. + 5. On the **Settings** tab, specify the channel for your test case. The following channels are supported: + + * **Voice call** – Configure the starting point by specifying the contact flow, incoming phone number, and any contact data to be initialized during test case execution. + + * **Chat** – Configure the starting point by specifying the contact flow and any contact data to be initialized during test case execution. @@ -63 +37 @@ The following procedure shows how to create a test case. - 7. Choose **New interaction** to create a new interaction. This represents a simulated interaction with a call center. + 7. Choose **New interaction** to create a new interaction. This represents a simulated interaction with a contact center. @@ -71,14 +44,0 @@ The following procedure shows how to create a test case. - 9. Choose **Run Test** to execute the test case. - - - - 10. Once the test case is running, choose the **Test runs** tab to view a list of in progress and completed test runs for the tests case. - - - - 11. Choose a test run to see the interaction block execution status, the simulated contact ID, and the pass or fail status of each step. - - - - - @@ -86 +45,0 @@ The following procedure shows how to create a test case. -You can also view all the test runs across all test cases in the **Test runs** tab. This page lists all of the test executions in the same Amazon Connect instance. You will only see the detail test results for the test cases you created or test cases you have permission to view. @@ -88 +46,0 @@ You can also view all the test runs across all test cases in the **Test runs** t - @@ -96 +54 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Call simulation concepts +Simulation concepts @@ -98 +56 @@ Call simulation concepts -Analyze test results +Execute test cases