Scenario-based testing uses test scenarios created from use cases and user requirements. Scenario testing focuses on users completing specific tasks by following a series of steps and interacting with the software. The purpose of these tests is to evaluate the software from the user's perspective rather than the system's.
Attributes of Scenario Based Testing
It is recommended that scenario-based tests possess the following four attributes:
Realistic Tests - Tests should accurately reflect the user's interactions with the software.
Complex Tests with Multiple Features - Tests should include various features from different user perspectives.
Clear, Concise, and Understandable - Test case descriptions for software functions should be clear, concise, and understandable for the tester to determine a pass or fail result.
Failed Tests - Failed tests need to be resolved in accordance with the stakeholders' requirements.
An Example of Scenario Testing
Every day, financial institutions, healthcare systems, the hospitality industry, and other service oriented businesses service numerous customers. These customers perform tasks and transactions at different times. Executing realistic network testing scenarios is beneficial for gaining insights into customer activity during peak and off peak hours.
Below are some network testing scenarios designed for systems that have a large customer base:
Adjust Customer Volume - In a simulation you can change the customer volume on the network and evaluate the network's performance for usage spikes, transaction interruptions, and server crashes. Testers should modify traffic patterns and monitor the network's behavior accordingly.
Customer Inquiry Simulation - You can simulate customer inquiries for account information and transactions. Different inquiry and transaction types can be tested. For instance, a banking customer can check their account balance, transfer funds between accounts, and view their bank statement in a specific sequence. Observe the network behavior while performing these actions one after another.
Response Time Testing - Evaluate the server response times for different transactions. For example, response times can be measured when you access account information and download documents like bank statements.
Although it may take several days to develop ideal test scenarios, they prove valuable in uncovering software failures, defects, errors, and other issues.
References: Copeland, L. (2004). A Practitioner's Guide to Software Test Design. Boston, MA. Artech House Publishers. Kaner, C., Bach, J., & Pettichord, B. (2002). Lessons Learned in Software Testing: A Context-Driven Approach. Toronto. Wiley Computer Publishing. Joch, A. (1998). Tooling Into Financial Markets -- New generation of Web site- testing products opens doors to financial markets. VARbusiness, 14(20). pg.83
Comments