Common mistakes found during test case review

-

  1. Spelling mistakes: Sometimes, spelling mistake can create a lot of confusions or make a sentence difficult to understand.
  2. Grammar: If grammar is not proper then test case can be interpreted in a wrong way, resulting in wrong results.
  3. Template format: If proper template is followed then it becomes easy to add/modify test cases in future and test case plan looks organized.
  4. Standard/Guidelines: While review process, it is very important to check whether all the standards and guideline are properly followed.
  5. Language used: Test cases should have a very simple language which is easy to understand.
  6. Functionality coverage: It is highly recommended that all the functionality associated with the system under test should be covered so that major defects are not missed.
  7. Replication: It refers to the duplicate test cases removal. It is possible that two or more test cases test the same thing and can be merged into one, this would save time and space.
  8. Redundancy: It refers to uselessness of a test case due to change in requirements or some modifications. Such test cases must be removed.

After checking all the above points, reviewer notes down all the changes/modifications required. Now, either he can have a discussion/meeting with the tester or he can send him the mail with the changes noted so that tester can go through them and make all the necessary modifications.



Comments

Post a Comment

Popular posts from this blog

What is Test case

-
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 Creating test cases can also help find problems in the requirements or design of a Software. Test Case Format Test scenario id test case id test  case Summary Related Requirement Prerequisites Test Procedure Test Data Expected Result Actual Result Status Comment Created By execution Date Tester Test Environment
Read more

The tester should have skill

-
The tester should have skill A destructive Mindset to crack or crash system under test frequently Bring bad news Under worst time pressure  Need to take a different view, a different mindset  How should fault information be communicated 
Read more

Priority vs Severity

-
High Severity – High Priority bug This is when major path through the application is broken, for example, on an eCommerce website, every customers get error message on the booking form and cannot place orders, or the product page throws a Error of page not found. High Severity – Low Priority bug This happens when the bug causes major problems, but it only happens in very rare conditions or situations, for example, customers who use very old browsers cannot continue with their purchase of a product. Because the number of customers with very old browsers is very old version, it is not a high priority to fix the issue. High Priority – Low Severity bug The logo or name of the company is not displayed on the website. It is important to fix the issue as soon as possible, although it may not create cause a System and other component. Low Priority – Low Severity bug The privacy policy page take a long time to load. Not many people view the privacy policy page and slow...
Read more