Data analysis and monitoring through auto-balancing

Verify and improve the quality of your application by recording a set of interactions for a case type or portal in scenario tests. As a result, you ensure that your application runs correctly and that the end-user experience that you deliver is error-free and works as expected.

• Create a test ruleset in which to store the scenario test. For more information, see Creating a test ruleset to store test cases.
• Add the pxScenarioTestAutomation privilege to your access role. For more information, see Granting privileges to an access role.
• Set the pzPegaSUT dynamic system setting to true. For more information, see Configuring dynamic system settings.

1. Launch the portal in which you want to do the test. For example: In the header of Dev Studio, click Launch portal, and then select the portal in which you want to create a scenario test. Scenario testing works best with portals that you build on UI Kit.
2. In the footer of the portal, click Toggle runtime toolbar, and then click Toggle Automation Recorder, as shown in the following figure:

   

   

3. In the Scenario tests pane, click Create test case, and then select the test type:
   • To record a test for a portal, select Portal.
   • To record a test for a case, select Case type, and then select the type of case for which you want to record the test.Note: When you select the case type, the system creates a new case of that type.
4. Record the steps for the test by clicking the user interface elements.
   When you hover over a testable element, an orange highlight box appears. When you click an element, you record an implicit assertion and add the interaction to the list of test steps, as shown in the following figure:

   

   

5. Optional: To provide specific UI attributes, add an explicit assertion to the test:
   1. Hover over an element.
   2. Click the Mark for assertion icon on the orange highlight box.
   3. In the Expected results section, click Add assertion.
   4. Define the assertion by completing the Name, Comparator, and Value fields.
   5. Click Save step.
6. To add latency to a web browser and actions on a web page to prevent tests from failing during complex processing or slow UI rendering, delay the processing of a step:
   1. Click the Mark for assertion icon on the orange highlight box.
   2. In the Wait field, enter the number of milliseconds by which to delay the processing of the step.
   3. Click Save step.
      Tip: You can add delays to all steps in all scenario tests in your application at once. For more information, see Delaying scenario test execution.Note: Delaying the processing of a single step takes precedence over delaying all of the steps at the application level.
7. When you finish adding steps, in the Test case pane, click Stop and save test case.
8. On the New test case form, save the test:
   1. In the Name field, enter a name for the test.
   2. Optional: To provide additional information about the test, in the Description field, enter extra information.
   3. In the Context section, select a branch or ruleset in which you want to save the test.
   4. In the Apply to field, enter the name of a class that is relevant to the test.
   5. Click Save.
   Result: The test case appears on the Scenario testing landing page.