Test case fields

One of the key features of TestRail is its ability to create and manage test cases. Test cases are the building blocks of software testing, and they can have many fields that allow the user to add additional semantic information to them. Having this information as a field will enable the users to easily filter out the tests (e.g., for a test run) by criteria based on these fields. In this article, we'll provide an overview of the different fields that can be included in TestRail for creating a test case.

 

You can reorder case fields, create new case fields, or modify existing case fields from the Administration > Customizations page. For more information on how to customize your fields, please read the configuring custom fields article.

Below are the default test case fields found in TestRail.

Capture0.JPG

  • Title - The Title field is a mandatory field that summarizes the test case. This field should be descriptive enough to clearly indicate what the test case is testing.
  • Section - The Section field is a mandatory field that allows the tester to specify the section for the test case. This can be useful to organize test cases into a hierarchical structure, where sections are nested within other sections or subsections. You can find more information about how to use sections and subsections on the sections documentation.
  • Template - The Template field is a mandatory field that allows the tester to select a predefined test case template. This helps to ensure that the test case is structured correctly and that all necessary information is included. TestRail provides several pre-defined test case templates, including:
    • Test Case (Text)
    • Test Case (Steps)
    • Exploratory Session
    • Behaviour Driven Development
  • Type - The Type field is a mandatory field that allows the tester to categorize the test case. This includes types like functional, regression, performance, usability, among others. By categorizing the test cases, you can easily filter and search for specific types of tests and ensure that the testing effort is well-rounded.
  • Priority - The Priority field is a mandatory field that allows the tester to assign a priority level to the test case. This can help prioritize testing efforts and ensure that critical functionality is thoroughly tested. It can also help to identify which tests should be executed first if time or resources are limited. By default. this field includes the following priorities:
    • Critical
    • High
    • Medium
    • Low
  • Status TestRail Enterprise - The Status field is a mandatory field that indicates the current status of the test case. These statuses compose the test case review & approvals workflow. The use of status for the 'test case approvals' feature is for the TestRail enterprise only. The default statuses are:
    • Draft
    • Review
    • Approved
  • Assigned To TestRail Enterprise - The Assigned To field is an optional field that specifies the person responsible for designing the test case. This field is part of the test case review & approvals workflow used to delegate the responsibility of drafting/reviewing test cases to the corresponding team members.
  • Estimate - The Estimate field is an optional field that allows the tester to provide an estimate of the time it will take to execute the test case, for example, 10 seconds (10s), 1 minute (1m), 10 minutes (10m) or 1 hour (1h). This can be useful to assess the testing effort and ensure that the team can execute the necessary tests within the given timeframe. It can also help identify which tests are more time-consuming and may require additional resources.
  • References - The References field is an optional field that allows the tester to provide any relevant documentation or reference materials that are necessary to execute the test case. References are primarily used to specify the requirements the test case is covering in an issue tracker. Please refer to the introduction to reference and defect integrations article for more information regarding how this field can be used for references integration.

     

Was this article helpful?
11 out of 22 found this helpful