Difference between Test Scenario and Test Case

Test scenario is the environment in which we execute the test cases, Test Case is a set of input we execute in the system to check the system or project whether it is working correctly or not.

Test scenarios and/or cases are prepared by reviewing functional requirements of the release and preparing logical groups of functions that can be further broken into test procedures. Test procedures define test conditions, data to be used for testing and expected results, including database updates, file outputs, report results. Generally speaking...
1. Test cases and scenarios are designed to represent both typical and unusual situations that may occur in the application.
2. Test engineers define unit test requirements and unit test cases. Test engineers also execute unit test cases.
3. It is the test team that, with assistance of developers and clients, develops test cases and scenarios for integration and system testing.
4. Test scenarios are executed through the use of test procedures or scripts.
5. Test procedures or scripts define a series of steps necessary to perform one or more test scenarios.
6. Test procedures or scripts include the specific data that will be used for testing the process or transaction.
7. Test procedures or scripts may cover multiple test scenarios.
8. Test scripts are mapped back to the requirements and traceability matrices are used to ensure each test is within scope.
9. Test data is captured and base lined, prior to testing. This data serves as the foundation for unit and system testing and used to exercise system functionality in a controlled environment.
10. Some output data is also base-lined for future comparison. Base-lined data is used to support future application maintenance via regression testing.
11. A pretest meeting is held to assess the readiness of the application and the environment and data to be tested. A test readiness document is created to indicate the status of the entrance criteria of the release.
Inputs for this process:
12. Approved Test Strategy Document.
14. Test tools, or automated test tools, if applicable.
15. Previously developed scripts, if applicable.
16. Test documentation problems uncovered as a result of testing.
17. A good understanding of software complexity and module path coverage, derived from general and detailed design documents, e.g. software design document, source code and software complexity data.
Outputs for this process:
18. Approved documents of test scenarios, test cases, test conditions and test data.
19.? Reports of software design issues, given to software developers for correction.

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

Satyapriya Nayak14y ago
Test scenario is the environment in which we execute the test cases, Test Case is a set of input we execute in the system to check the system or project whether it is working correctly or not.

Test scenarios and/or cases are prepared by reviewing functional requirements of the release and preparing logical groups of functions that can be further broken into test procedures. Test procedures define test conditions, data to be used for testing and expected results, including database updates, file outputs, report results. Generally speaking...
1. Test cases and scenarios are designed to represent both typical and unusual situations that may occur in the application.
2. Test engineers define unit test requirements and unit test cases. Test engineers also execute unit test cases.
3. It is the test team that, with assistance of developers and clients, develops test cases and scenarios for integration and system testing.
4. Test scenarios are executed through the use of test procedures or scripts.
5. Test procedures or scripts define a series of steps necessary to perform one or more test scenarios.
6. Test procedures or scripts include the specific data that will be used for testing the process or transaction.
7. Test procedures or scripts may cover multiple test scenarios.
8. Test scripts are mapped back to the requirements and traceability matrices are used to ensure each test is within scope.
9. Test data is captured and base lined, prior to testing. This data serves as the foundation for unit and system testing and used to exercise system functionality in a controlled environment.
10. Some output data is also base-lined for future comparison. Base-lined data is used to support future application maintenance via regression testing.
11. A pretest meeting is held to assess the readiness of the application and the environment and data to be tested. A test readiness document is created to indicate the status of the entrance criteria of the release.
Inputs for this process:
12. Approved Test Strategy Document.
14. Test tools, or automated test tools, if applicable.
15. Previously developed scripts, if applicable.
16. Test documentation problems uncovered as a result of testing.
17. A good understanding of software complexity and module path coverage, derived from general and detailed design documents, e.g. software design document, source code and software complexity data.
Outputs for this process:
18. Approved documents of test scenarios, test cases, test conditions and test data.
19.? Reports of software design issues, given to software developers for correction.