Test Case, Use Case and Test Scenario
5 likes2,552 views
The document discusses the importance of writing test cases for software testing, detailing their purpose in tracking test coverage, maintaining consistency, and enabling reusability. It outlines when to start writing test cases, the types of test cases (formal and informal), and the difference between test cases and test scenarios. Additionally, it provides examples of test cases for specific objects such as pens and login buttons, illustrating various testing approaches.
Test Case, Use Case and Test Scenario
- 1. Test Case:- A test case is a set of conditions under which a tester will determine whether an application, software system or one of its features is working as it was originally established for it to do. ------------------------------------------------------------------------------------------------------- Why do we write test cases:- There are a few reasons why you need to design and write out your test cases: ● Tracking your test coverage: Let’s consider your system under test as a Disneyland park, which you want to explore. Of course, you can just buy tickets and explore the park as you wish. While it’s fun to do that, there are great chances that you will miss interesting places. In this case, all you need is a map of the park. Similar in your project, you need a map to know what you need to test, what you have tested, what you don’t need to test. ● Maintain consistency: Let’s say you can brainstorm 100 test cases to test your system, but you don’t write them out. You memorize them. Unless you are a genius, there’s no way to remember all these test cases and things entailed such input data, step to perform the test, where to look at the result, what’s expected. If you have a written test cases, you don’t have to rely on your memory to do this test to maintain consistency. ● Reusability: Now you are the only tester in the project. What if your manager added another tester in your project and your manager wanted him to perform the same test as you did. What you simply need to do is to give him your well-written test cases and he can follow these exact tests to perform the test. It’s as simple as that. ● Easy to automate: Also, if you are planning to do automated test in your project, these detailed test cases are perfect inputs for your test automation. --------------------------------------------------------------------------------------------------- When we should start writing Test Case:- When SRS is prepared by the business analyst he will send the drafts to testers and developers for review. After reviewing testers and developers will send their comments and after analysing them the SRS is modified. once the SRS is freezed TL prepares the TEST PLAN and after that testers start writing test cases. i..e testers start writing test cases when the requirement phase itself.
- 2. It will depends...But mostly..When the requirement specifications are completed. We can start writing Test Cases in parallel with Design phase itself.(but make sure u understand the requirements correctly. ---------------------------------------------------------------------------------------------------- Test case Types:- There are two types of Test case:- 1. Formal Test cases 2. Informal Test cases Formal test cases:- A formal test case is where a test case is designed with a certain standard format so that it will be user-friendly to understand and all the possible tests will be covered. ● Every requirement will have the two types of testing, Positive testing and Negative testing. These two will play a vital role in completing a testing requirement satisfactorily. ● As a tester we need to track between the requirements and the test case where this process is called a Traceability matrix. ● A formal test case will have a known input along with an expected output. ● It is also common that the known input should test a pre-condition and the expected output should test the post condition. Informal test cases :- An informal test case is a test case that is not at all designed during the execution of the testing but the results and activities will be made as a report once the process is finished. In these informal test cases the tester thinking level is complex and analytical. They will test it with a specified number of possibilities to test a specific scenario. There are no restrictions for testing except the timing given for testing. We can say an informal test case will be totally different from the formal test case format. ------------------------------------------------------------------------------------------------------ Positive Test case:- Checking for valid values only. Negative Test Case:- Checking for invalid values. ------------------------------------------------------------------------------------------------------ what documents need to write test case:- ● FRS (Functional Requirement Specification) ● SRS (System Requirement Specification) ● You can take the help of Use Case. ● Test scenario ------------------------------------------------------------------------------------------------------ Use Case:- A use case is a software and system engineering term that describes how a user uses a system to accomplish a particular goal. Use case diagram is given below:-
- 3. Create a use case index:- It will serve as a master inventory to help write effective use cases for the requirements phase of the project. ------------------------------------------------------------------------------------------------------ Test Scenario:- Test scenario is created from Use case, FRS, BRS. Test Scenarios are just a flow of the application. e.g. 1. Filling up all the fields on the form --> click on Ok button --> Next screen 1. Filling up all the fields on the form --> click on Cancel button --> All the will be erased. ------------------------------------------------------------------------------------------------------ Difference between Test cases and Test scenario:- A Test Scenario is what to be tested, and a Test Case is how to be tested. ------------------------------------------------------------------------------------------------------ Question:- Write the test case of Pen?
- 4. Answer:- 1. Verify the color of the pen. 2. Check GUI testing means logo of the pen maker. 3. Check Usability testing means grip of the pen. 4. Verify whether the pen is ballpoint pen or ink pen. 5. Check Integration Testing means cap of the pen should easily fit beside the body of the pen. 6. Check pen should be continuously in writing mode. Some Functional test cases for pen: 1. Check whether it writes on paper or not. 2. Verify whether the ink on the paper is belongs with the similar color as what we see in the refill. Performance and load test cases for pen: 1. Verify how it performs when writing on wet paper. 2. Verify how it performs when writing on rough paper. 3. Verify how it performs when writing on hand because we occasionally do that 4. Check load test means when pen is pressed very hard against the tough surface then pen refill should not come out of the pen. Negative test cases about pen: 1. Verify whether ink is available or not. 2. Check if ink is available, than the pen does not write on the paper. 3. Verify by bend the refill at multiple ends and then try to write with it. 4. Verify by dip the pen always into the water and then write it again. 5. Check whether it write on leaves or not. Additional test cases for pen: 1. Check usability testing means test by writing on a section of paper, Examine if you can write smoothly. It should not be writing and stopping among (with) breaks.
- 5. 2. Check capability or reliability testing means Test the writing capacity (the amount of writing that is possible from a single refill) of the pen. 3. Check Robustness testing means Test wherever you can carry the pen in to your shirt and pent pocket using its cap. The cap distension should be solid enough to grip your pocket. 4. Check Compatibility testing means Test by writing on distinct types of surfaces like: rough paper, packing material, glass, leather, cotton, wood, plastic, metals like aluminum or iron, polythene sheet etc. -------------------------------------------------------------------------------------------------------- Question:- Test case and Test scenario of a log-in Button Answer:- Test Scenario ID Test Scenario / Test Objective No. Of Test Cases TS_001 User is Successfully able to log-in in the Student Panel 7 TS_002 User is not able to log-in in the Student Panel 14 Test Case is given below:-
- 7. Thank you for your precious time. For any Feedback or Query, kindly contact on (lokeshapj@gmail.com)