Scenario tests
Scenario testing is a type of software testing that involves testing a system or application by simulating real-world scenarios or use cases. It is a black-box testing technique that focuses on testing the system's functionality and behavior under different scenarios or conditions.
In scenario testing, testers create test cases that simulate real-world scenarios or use cases that the system is expected to handle. These scenarios can be based on user stories, business requirements, or other specifications. The test cases are designed to cover a wide range of scenarios, including normal and abnormal scenarios, edge cases, and error conditions.
Scenario testing is useful for identifying defects or issues that may not be caught by other types of testing, such as unit testing or integration testing. It can also help to ensure that the system meets the requirements and expectations of end-users and stakeholders.
You can increase test coverage without writing complex code by creating your tests in the graphical test creation tool on the Scenario Testing landing page. From there, you can view and run scenario test cases, as well as view reports to identify case types and portals that did not pass scenario testing.
On the Scenario Testing landing page, you can complete the following tasks:
- View test run and coverage information for case type tests and portal tests.
- Open a test case rule where you can add assertions to your test.
- View the results of the most recent test run.
- Select and run individual test cases or group tests into test suites that you can use to run multiple tests in a specified order.
- Download a list of tests, their type, the name of a portal or case that every test checks, and the time and result of the last run.
- View the history of all your test runs so that you can quickly analyze historical data.
- View which scenario tests restarted automatically if they failed.
Application quality improvement with scenario tests
To improve the quality of the application, Lead System Architects (LSAs) should periodically review the results of scenario testing and complete the following actions:
- Review the failed test cases and take corrective actions.
- Add more test cases for case type and portal rules to increase test coverage.
- Review and instruct the team members to update the existing test cases if new changes impact application functionality.
Scenario testing limitations
When you design and run your scenario tests, the following limitations apply:
- You cannot run a scenario test in a different portal than the one in which you record it.
- Every portal that needs testing requires a separate scenario test.
- You cannot run scenario tests by using different personas or logins because testing ends when you log out; as a result, you cannot run the same test with a different user.
- Scenario tests do not support file uploads or downloads because these actions require interaction with the operating system.
- CSS styles that are related to the hover functionality, such as on-hover actions, are not available during scenario testing.
- A scenario test cannot include another scenario test.
- Scenario tests do not support the setup or cleanup of test data.
For more information, see Scenario testing.
Check your knowledge with the following interaction:
This Topic is available in the following Module:
If you are having problems with your training, please review the Pega Academy Support FAQs.
Want to help us improve this content?