Best Practices for Test Cases
- Clear: Test cases should be clear, transparent, and easy to understand.
- Avoid repetition: Design test cases to avoid repetition.
- Never make assumptions: When writing test cases, it is considered a best practice to never make assumptions about the features of the software.
- Easily distinguishable: Test cases must be designed in such a way they are easily distinguishable.
- Check all software requirements: Write test cases to check all software requirements mentioned in the specification document.
Test Case vs Test Scenario
The article focuses on discussing the difference between test cases and test scenarios. Before proceeding with the difference let’s first discuss each term in detail.
Test cases are the set of actions to execute and test a particular feature of the application on the other hand test scenarios are any functionality that can be tested. Test cases are derived from test scenarios whereas test scenarios are derived from SRS, BRS, etc. Test cases help in the exhaustive testing of the application and test scenarios help in the agile way of testing the application. Test cases are focused on how to test and what to test on the other hand test scenarios are focused on what to test. Test cases require more time and resources as compared to test scenarios. Test cases are low-level actions and test scenarios are high-level actions.