Test Scenarios and Scripts
![Picture](/uploads/1/1/2/6/11260941/2428989.jpg?271)
Test Scenarios: identify which specific area or function(s) of the software will be tested, and ensure that all important business processes are tested. Any identified area of software can have from one to tens of test scenarios depending on its size and the complexity of the software. Large scenarios can be further broken down into smaller sections, and these are referred to as “Test Cases.” Scenario and Test Case documents are created by the Testing Manager or Testing Lead.
Example of Test Scenario with Test Cases
Test Scripts: list the specific test steps, conditions and test data which are used for testing, along with expected and actual results of the test. The main goal is to identify whether the software passes or fails the test: do executed test steps result in the expected outcome/result?
Test Scripts are written by the test team and are a component of Test Scenarios and Cases. Business software requirements document(s) are used as the source for creating test steps. Test Scripts typically include:
Example of a Test Script
Example of Test Scenario with Test Cases
Test Scripts: list the specific test steps, conditions and test data which are used for testing, along with expected and actual results of the test. The main goal is to identify whether the software passes or fails the test: do executed test steps result in the expected outcome/result?
Test Scripts are written by the test team and are a component of Test Scenarios and Cases. Business software requirements document(s) are used as the source for creating test steps. Test Scripts typically include:
- Test Scenario/Case ID
- Test Level/Cycle
- High Level Purpose of the Test
- Individual Test Steps, including any Test Data that needs to be entered
- Expected Result
- Actual Result
- Pass/Fail Indicator
- Defect Number/Detailed Information for failed test steps
Example of a Test Script
“More than the act of testing, the act of designing tests is one of the best bug preventers known. The thinking that must be done to create a useful test can discover and eliminate bugs before they are coded – indeed, test-design thinking can discover and eliminate bugs at every stage in the creation of software, from conception to specification, to design, coding and the rest.” – Boris Beizer