Five best practices for managing test cases in JIRA

Adaptavist Test Management for JIRA

If you’re a tester or test manager, one of the most important processes in your testing lifecycle is the creation and maintenance of test case specifications. This blog looks at five ways to get your test cases running more effectively in JIRA with Adaptavist Test Management.

A single test case contains step-by-step procedures for executing a test. It should provide traceability with its requirements and describe the environmental needs and the pass/fail criteria. Adaptavist Test Management for JIRA leverages the power of JIRA to create test cases that increase productivity, reduce re-testing and minimise duplication.

1. Keep test cases simple and easy to understand

While great for creating tasks and issues, JIRA on its own wasn’t designed for Test Management. Traditional JIRA workflows don’t fit in with most test case models.

By using Adaptavist Test Management, test cases can be created as separate entities in JIRA so they exist outside of the traditional task/workflow structure. This means that you can keep them clear, simple and distinct, while still benefiting from JIRA’s intuitive user interface and ease of use.

 

2. Standardise naming conventions

As business needs expand, scaling a test library can become a challenge. Ensuring a meaningful and standardised test case naming convention is one way that test libraries can be kept healthy. Adaptavist Test Management for JIRA clearly displays the names of your test cases on the grids. It also ships with an as-you-type search filter that, combined with your consistent naming convention, lets users easily filter to the relevant test case(s).

 

3. Describe detailed steps and include data

A well-written test case specification should clearly describe the steps, test data and the expected result(s) of the application or system under test. Adaptavist Test Management both allows you to detail test steps. It additionally allows you to reuse steps from other test cases, cutting down on time spent on the writing of individual test cases and ensuring standardisation. The simple, functional test case interface also allows users to drag and drop test steps.

Describe detailed steps and include data

 

4. Ensure traceability

Tracing a test case from start to go-live is a critical part of the testing lifecycle. Enhancing JIRA with Adaptavist Test Management enables you to establish clear traceability between test cases, test runs, test plans and issues – all right inside JIRA – ensuring that nothing is missed between teams.

Describe detailed steps and include data

 

5. Design a reusable and modular test case library

Test case libraries can grow large, becoming hard to navigate and maintain. Testers and test managers should look to organise test case libraries using hierarchical folders. Luckily, Adaptavist Test Management allows you to do that as well as letting you reuse test cases and test scripts across your projects, releases and sprints for regression testing. It’s also been built to let you reuse test steps between test cases.

Best practices for managing test cases in JIRA - design a reusable and modular test case library

 

If you’re not already using Adaptavist Test Management, start a free trial today and find out how it helps teams improve their test management and productivity right inside JIRA.