What are Main Attributes of a Test Case?

by Nataliia Vasylyna | December 29, 2014 10:00 am

Note: this article was updated in May 2019

Creation of a clear test case is quite challenging because it forms the entire testing and serves as a guide. Since a test case stipulates a basis of future testing, it has to be meaningful to provide the strategy of testing.

Let’s define the origins of a test case and its nature. A test case is a set of input data, conditions and expected results, designed to verify the stated product properties. Test cases, assembled in particular order to achieve some goal form a test suite.

Project managers and team leads [1]have to specify the input data, execution conditions, testing procedure, and expected results to define how the test must be performed. He also should know the practical side of how to write test cases. A test case is a tool for the team lead to direct the team for achieving a specific software testing goal. For example, performing a specific program path or examination of compliance with a specific requirement needs a proper test case. That is why a test case must be clear both for the project manager and each particular tester.

Watch the differences

To avoid the misunderstandings at the stage of test case creation, you need to be well aware of issues which may intervene a proper composition of the test case (basing on sample test cases):

The key test case attributes

A test case has its common attributes, which allow recognizing the peculiarities of each module:

test case components

  1. ID is a unique identifier which is often generated automatically[2]. If it is assigned manually, it is advisable to make it meaningful to understand the purpose of a test case clearly.
  2. Priority (priority test case) – an attribute that indicates the priority of the TC, and takes the value according to the company’s classification (A-B-C-D-E, High-Medium-Low, etc.).
  3. Version – version of a test case, which is specified automatically.
  4. Req. ID – an attribute indicating the test item associated with the test.
  5. Module – this indicates the module associated with the test case.
  6. Sub-Module – similar to the previous item, only the smaller structural unit fits in.
  7. Type – to verify functionality, interface, usability or intended for automation.
  8. Test description (description of test cases) – an important attribute, which specifies the title (the essence of the test), the conditions for its implementation, steps and actions before/during/after passing the test. Test description, respectively, can and should contain precondition (preparative steps for setting the program and testing environment), steps, postcondition.
  9. Expected result (expected results of the test case) – reflects the expected result for each step and proper reaction of the program to these steps. It should be meaningful, clear and simple.
  10. Result – data about the result of the passed test is entered here (passed/failed, etc.).
  11. Created on…by/Last modified…by – date of creation and name of the creator/last amendments and modifications and name of operator. Automatically specified.
  12. Comment – here you can make your notes to the test (questions to the customer, any observations or details).
  13. Add attachment – attached file, comment or srсeenshot.

Here is a test case example for your review:

example of a test case

How to monitor a proper preparation of test case

A test case also has its attributes of proper preparation, as each element of testing. Here are the tips from QATestLab on how to succeed in test case creation (we consider test case example for manual testing):

Test case creation and management. Summary.

Test cases, a test plan, and its test strategy can be used as a source of information for the following projects. In addition to the above, case testing helps to meet customer requirements[3]. Often the customer checks cases, sometimes not, but in general, most projects should have case studies. The systematic approach of test case creation is a warranty of proper test case, which is the aim not only of testers but of the team leads at the same time. Project managers are responsible to provide as much information, requirements, and expectations, as possible before composing test case and control the procedure of its creation and further use.

Learn more from QATestLab

Related Posts:

  1. team leads : https://blog.qatestlab.com/2019/04/25/qa-leads-responsibilities/
  2. generated automatically: https://qatestlab.com/services/test-automation/
  3. to meet customer requirements: https://blog.qatestlab.com/2018/07/02/no-software-testing/
  4. Test Design Specification: https://blog.qatestlab.com/2020/05/15/test-design-specification/
  5. Testing at a Complex Project: QATestLab Real Case: https://blog.qatestlab.com/2019/09/03/complex-project-testing/
  6. How to Create Efficient QA Team in Startup: https://blog.qatestlab.com/2019/03/29/qa-in-startup/

Source URL: https://blog.qatestlab.com/2014/12/29/what-are-main-attributes-of-a-test-case/