Manual testing 34 - What is a test case? How to write test cases? Test case design techniques

Test cases:-

Test case is a document which covers all possible scenarios to test all the feature(s).

Or
Test case is a set of input parameters for which the s/w will be tested.

Or
A Test Case is simply a list of actions which need to be executed to verify a particular functionality or feature of your application under test.

Or
A test case is a set of conditions under which a tester will determine whether an application or one of its features is working as it was originally established for it to do.

The testing quality depends on,

• Mood of the TE
It’s not mandatory to write test case to test application. It’s possible to test application even by looking at the scenarios identified. The problem with this is, sometime due to bad mood there are chances testers may forget few scenarios. To avoid these situations we need to record all scenarios in the form of Test cases.

• Testing is not consistent
Sometimes we lose consistency in execution. This is because whenever we forget scenarios we will go back and start referring requirements. This will take additional time to complete testing. In this way we lose consistency.

• Varies from person to person
Sometimes we see new resource coming into team to test application. New tester may have different view for testing application. As we don’t have test cases created, some people will identify 100 scenarios and some testers will identify 80 scenarios. This way testing varies from person to person.

So we write test cases.

Why we write test cases?

• To have better test coverage – cover all possible scenarios and document it, so that we need not remember all the scenarios

• To have consistency in test case execution – seeing the test case and testing the products so that we can complete execution with in the defined time.

• To avoid training every new engineer on the product – when an engineer leaves, he leaves with lot of knowledge and scenarios. Those scenarios should be documented, so that new engineer can test with the given scenarios and also write new scenarios.
• To depend on process rather than on a person

• Test cases are part of the deliverables to the customer.
Some times during agreement with customer we commit to deliver few documents along with product. Test case is one among those deliveries. Hence, we have to create test case to fulfill deliveries.

• Test cases are good documentation for future proof.
• Test cases are required for automation process.
• Find Defects
• Maximize bug count
• Assure Quality
• Verify correctness of Product i.e. it meets the specifications

Characteristics of Good test cases:
Every tester writes test cases however many times the test cases are rejected by reviewers because of bad quality, in order to write good test cases, one should know what are the characteristics of a good test case.
1. Should be accurate.
Test case should test what it is intended to test. One test case should not be used to test other scenarios.
2. No unnecessary steps should be included in test case.
Steps which are not part of scenarios should not be included in test case.
3. It should be reusable.
• Automation team will re-use test cases in future. Hence, we need to create accurate test case so that automation team will not find difficulty in understanding.
• Sometimes there are chances other project may use your test cases. This is the case when both projects belong to same domain and functionality is similar. In this case other project may use test cases with small modifications. This is very rare case.
4. It should be traceable to requirements.
Test case should provide proper traceability to the requirements. By looking at test case people should understand for which requirement this particular test case is written. If tomorrow requirement changes, by using traceability it’s easy to update test cases and this will also save lot of time. Traceability can be done from requirement to test case or from test case to requirement.
5. It should be compliant to regulations.
Test case should be created proper template which is approved by customers. Test case template should have all parameters.
6. It should be independent
You should be able to execute it in any order without any dependency on other test cases.
7. It should be simple and clear
Any tester should be able to understand it by reading once. Use simple language to create test case.
8. Maintainable
Tester should not find difficulty in updating test case whenever requirement changes. Test cases should be easily maintainable.
9. Efficient
Test case should not take more time to execute. This is possible when we create simple test cases.
10. Potential to find defects
The test case should find the defects which are yet uncovered.
11. Uniqueness
The test case must be unique. There should be no duplicates of the previous.
12. Clearly provide environment details
13. Transparent
It should be clear what the purpose of each test case is.

[anuragreddy]

thanks a lot Madam
good Explenation, and looking forword your more videos

[nitinjangra]

Pahli baar kisi ne sahi test cases banane sikhaye hai

[pavankumarsriramagiri]

Hi my name is Pavan i have 2 years of experience in manual testing any openings for Bangalore..