Test cases in software Development

Test cases

Test cases are the foundation of quality assurance in software development. They will determine if the software product is working as designed or failing. They help the tester proceed to the next phase which may be user testing or roll to production for the customer to use. A test case is a set of conditions or inputs used by a tester or a software analyst to determine whether the system being tested works as designed. This inputs used by the tester also will help determine if the system is failing and needs to go back to development

Contents of a test case

A test case should be identified by the following features. Below are the most features that a test case should have

  • Test case Author
  • Test case ID
  • Test case description
  • Test case steps
  • Status which is either Pass or Fail
  • Author
  • Check boxes and so on

Types of test cases

The mainly two types of test cases written for testing a software

  • Formal test cases – These are test cases written to fully test the requirements. For each requirement described by the business analyst in the design document, a positive and negative test case will be written. These test cases are mainly described or characterized by a known input and expected output. These are the main test cases written by most testers
  • Informal test cases – These are test cases written based on the accepted operation of a program. These test cases are not written in detail. A Visio diagram can be used as a test case for these types of scenarios.

Benefits of well-written test cases

  • Saves Time – When a test case is written with all the requirements, it will help the tester validate the development code whether the system is working as designed or fails hence saving time which leads to quick delivery of the product. Also, defects will be easily identified since the steps will be easily followed and developers will fix them quickly.
  • Easy to use – More so, a well-written test case makes it easy to follow to execute the steps where by anyone can follow to validate the results. This means anyone who can read and follow steps can test a software and validate against the requirements described or the results expected
No Comments

Leave a Reply

Your email address will not be published. Required fields are marked *