26 | Test Case
Published on Aug 18, 2021 | By Tesvan team
A TEST CASE is a set of conditions or variables under which a tester will determine whether a system under test satisfies requirements or works correctly. The process of developing test cases can also help find problems in the requirements or design of an application.
Test Case template
| Test Case Field | Description |
|---|---|
| Test case ID: | Each test case should be represented by a unique ID. To indicate test types follow some convention like "TC_UI_1" indicating "User Interface Test Case#1." |
| Test Priority: | It is useful while executing the test Low Medium High |
| Name of the Module: | Determine the name of the main module or sub-module being tested |
| Test Designed by: | Tester's Name |
| Date of test designed: | Date when test was designed |
| Test Executed by: | Who executed the test- tester |
| Date of the Test Execution: | Date when test needs to be executed |
| Name or Test Title: | Title of the test case |
| Description/Summary of Test: | Determine the summary or test purpose in brief |
| Pre-condition: | Any requirement that needs to be done before execution of this test case. To execute this test case list all pre-conditions |
| Dependencies: | Determine any dependencies on test requirements or other test cases |
| Test Steps: | Mention all the test steps in detail and write in the order in which it requires to be executed. While writing test steps ensure that you provide as much detail as you can |
| Test Data: | Use of test data as an input for the test case. Deliver different data sets with precise values to be used as an input |
| Expected Results: | Mention the expected result including error or message that should appear on screen |
| Post-Condition: | What would be the state of the system after running the test case? |
| Actual Result: | After test execution, actual test result should be filled |
| Status (Fail/Pass): | Mark this field as failed, if actual result is not as per the estimated result |
| Notes: | If there are some special condition which is left in above field |
Test Case vs Test Scenario
- Test Case is a set of actions executed to verify particular features or functionality whereas Test Scenario is any functionality that can be tested.
- Test Case is mostly derived from test scenarios while Test Scenarios are derived from test artifacts like BRS and SRS.
- Test Case is mostly derived from test scenarios while Test Scenarios are derived from test artifacts like BRS and SRS.
- Test Case helps in exhaustive testing of an application whereas Test Scenario helps in an agile way of testing the end to end functionality.
- Test Cases are focused on what to test and how to test while Test Scenario is more focused on what to test.
- Test Cases are low-level actions whereas Test Scenarios are high-level actions.
- Test Case requires more resources and time for test execution while Test Scenario requires fewer resources and time for test execution.
- Test Case includes test steps, data, expected results for testing whereas Test Scenario includes an end to end functionality to be tested.
- Here, are significant differences between Test scenario and a Test Case
| Test Scenario | Test Case |
|---|---|
| A test scenario contains high-level documentation which describes an end to end functionality to be tested. | Test cases contain definite test steps, data, expected results for testing all the features of an application. |
| It focuses on more "what to test" than "how to test". | A complete emphasis on "what to test" and "how to test.". |
| Test scenarios are a one-liner. So, there is always the possibility of ambiguity during the testing․ | Test cases have defined a step, pre-requisites, expected result, etc. Therefore, there is no ambiguity in this process. |
| Test scenarios are derived from test artifacts like BRS, SRS, etc. | Test case is mostly derived from test scenarios. Multiple Test case can be derived from a single Test Scenario․ |
| It helps in an agile way of testing the end-to-end functionality․ | It helps in exhaustive testing of an application․ |
| Test scenarios are high-level actions. | Test cases are low-level actions. |
| Comparatively less time and resources are required for creating & testing using scenarios. | More resources are needed for documentation and execution of test cases. |
2. Test case article/eng/
3. Test case video tutorial/rus/
4. Test case video tutorial/eng/
5. Test case, Test plan video tutorial/arm/
Next Lessons
27 | Test Script
Aug 18, 2021
Test Script A TEST SCRIPT is a set of instructions (written using a scripting/programming language) that is performed on a system under test to verify that the ...
By Tesvan team
28 | Test Plan
Aug 18, 2021
A TEST PLAN is a document describing software testing scope and activities. It is the basis for formally testing any software/product in a project.Test Plan tem...
By Tesvan team
29 | Agile model
Aug 18, 2021
Agile is a coding practice that follows the rules and principles of agile software development. In this Agile Tutorial, you will learn the fundamentals of Agile...
By Tesvan team
30 | Agile VS Waterfall
Aug 18, 2021
Agile VS Waterfall Key Difference Useful links1. Agile vs Waterfall article/eng/2. Agile vs Waterfall article/rus/3. Agile vs Waterfall video tutorial/eng/4....
By Tesvan team
31 | Scrum methodology
Aug 18, 2021
Scrum methodology Scrum MasterThe Scrum Master helps the Scrum Team perform at their highest level. They also protect the team from both internal and external d...
By Tesvan team
Interesting For You
27 | Test Script
Aug 18, 2021 | By Tesvan team
Test Script A TEST SCRIPT is a set of instructions (written using a scripting/programming language) that is performed on a system under test to verify that the ...
03 | 7 Software Testing Principles
Aug 11, 2021 | By Tesvan team
7 Principles of Software Testing Exhaustive testingYes! Exhaustive testing is not possible. Instead, we need the optimal amount of testing based on the risk a...
