How to Write Test Cases in Jira

How-to guides.

An example of test cases in Jira, with fields like issue type, test case steps, and expected results

When you’re building complex web applications, QA testing can turn into a nightmare.

There are so many flows and components to test — login flows, sign-up flow, payment flow, invite flow ... and a million more.

That’s why test cases are a QA testers’ secret weapon to align your team and make sure everything works as expected.

A good practice is to create a template for each test case.

Here is an example of a test case for a Google login flow created in a spreadsheet:

But using a spreadsheet is just not scalable, especially when your entire team runs on Jira.

The problem with Jira is that at its core, it’s “just” a bug & issue tracking tool. It wasn’t built for case testing, and trying to find a workaround for it is a massive pain.

But we have a solution for you!

In this post, we’ll show you:

  • How to setup Jira for case testing;
  • How to write test cases in Jira using custom issue types;
  • How to run your test cases when testing your applications.

Let’s dive right in.

1. Set up Jira for case testing

Since Jira does not have a test case feature built-in, we will use the issue type feature as a workaround.

Jira’s customization options are endless. All you need to do is create a new custom issue type specifically configured for case testing.

You’ll also need to set up custom subtasks — so reporters can submit results of test cases straight in Jira, too.

Here’s a visual representation of what we’re trying to put together:

For test cases, we recommend creating a “Test Case” issue type with at least the following fields:

  • Test Case Steps
  • Test Case Expected Results

Creating a custom issue in Jira is a simple, 9-steps process:

  • Inside Jira go to global Settings > Issues (you’ll need admin access for this).
  • Click Add Issue Type and create a new issue type (eg: Test Case).
  • Go to Issue type schemes settings, find your Jira classic project and click Edit .
  • Drag your new Issue type into your project’s current scheme.
  • Next, go to Screen settings > Add Screen.
  • Pick the fields you want in this Issue type, (e.g. Summary, Test Case Steps, Test Case Expected Results). Keep it simple.
  • Go to Screen Schemes > Add Screen Scheme, create a new Screen scheme (e.g. Test Case screen scheme). Link it to your custom Screen (e.g. Test Case Screen).
  • Go to Issue type screen schemes . Find the Jira Classic project you are looking to use your new Issue type with. Then, click Associate an issue type with a screen scheme, select your new issue type (e.g. Test Case) and its Screen scheme, then click Add .
  • Congratulations! You created a new custom Jira issue type with only selected fields, scoped to a specific Jira project.

Now, let’s set up a custom “Test Case Results” subtask where testers will fill in their reports.

Here’s how you create a custom subtask in Jira:

  • In the Jira admin go to Issues > Add Issue Type. This time pick Sub-Task Issue Type .
  • Then, go to Screens > Add Screen. Pick the fields for our Test Case Results subtask.
  • Head over to Screen schemes > Add Screen Scheme, create a new scheme and pick Test Case Screen as default.
  • In Issue type screen schemes , do not create a new screen scheme . Find the test case screen scheme we set up earlier. Then, click Configure under Actions , and Associate an issue type with a screen scheme.

If you’re new to Jira, all of this might be a little overwhelming.

We’ve got your back — check out our step-by-step guide on how to create custom issue types in Jira .

2. Create test cases in Jira

Once your project is properly set up, creating test cases is the same as opening a new issue.

Head over to your Jira project, click “Create”, pick the “Test Case” issue type you’ve just created, and start writing.

A good practice is to create one issue per test case.

Good test case instructions should include:

1) Detailed steps. What steps you’d like your tester/reviewer/end-user to take as they navigate through your site or web app.

2) Expected results. Even if your reviewer says everything went well — you want to make sure they landed on the proper page or experienced your app how you wanted to.

It really is this easy:

3. Report on test cases in Jira

On the other side of the equation — the reporter — the process is just as simple.

You’ve got two choices here:

  • The old school, manual route. Write your reports directly in Jira. Include screenshots, screen recordings, annotations, environment info, and anything else the developer needs.
  • Report from a third-party app. Streamline as much of the process as possible, and capture the “boring” stuff automatically.

Option 1: Manual reporting

Find the test case, hit “Create subtask”, and choose “Test Case Results”:

Every subtask you create this way will be linked to the main task, A.K.A. test case. This makes it very easy for the developer to trace back to the main issue.

Remember to include screenshots, as well as any relevant technical information. This will make it easy for anyone to reproduce any bugs you find during testing.

This process, unfortunately, is still very slow.

  • You have to switch back and forth between your app and Jira.
  • You have to manually record technical environment like URL, OS, console logs.
  • You have to use a third-party screenshot tool to capture and annotate your screenshots.

Just look at how many steps you have to take to report just one bug:

  • Find the bug.
  • Open screenshot tool, capture bug.
  • Open software to annotate screenshots and add comments.
  • Log into Jira.
  • Create a new issue.
  • Document the bug.
  • Add technical information.
  • Attach screenshot.
  • ...do we really need to go on?

Jira simply wasn’t built for this.

But don’t worry: there is a better way.

Option 2: Third-party app reporting

Our recommendation: use a bug reporting tool that seamlessly integrates with Jira — and use it for case testing.

This brings us to our next option.

How many times have you had to double check on a test case to figure out:

  • Environment information;
  • Console logs;
  • Steps taken by reporter;
  • ...and more?

Every time your developer needs to get in touch with the reporter for “clarification”, you waste valuable time.

That’s why we built Marker.io .

With the Jira configuration detailed above, reporting on test cases with our tool turns into a simple 3-steps process:

  • Go to the URL that needs to be tested and click on “Report a bug”.
  • Input details of your report.
  • Click on “Create issue” — done!

When we zoom-in on the widget form, you will find our “Test Case” issue type that we created earlier.

This works thanks to Marker.io’s 2-way synchronization with Jira.

And on the developer end, in Jira:

1 - Reporter name

2 - Technical info (URL, console logs...)

3 - Environment

4 - Test case results

5 - Screenshot attachment

All in one place.

Are you ready to take your case testing & bug reporting in Jira to the next level?

Check out how Marker.io integrates seamlessly with Jira .

Wrapping up...

So there you have it: our step-by-step guide on how to write test cases in Jira.

As a reminder, a good test case report should:

  • Be comprehensive: attach screenshots, annotations & comments;
  • Capture as much info as possible: use third-party tools or include recording & environment info in report;
  • Be traceable: ensure every test case is directly linked to an issue.

We hope this post helps you organize and run test cases efficiently for your next project!

how to write a test case in jira

Continue reading

We’re officially soc 2 type 2 compliant.

how to write a test case in jira

24 Best Website Feedback Tools in 2024: Comparison Guide

12 best beta testing tools in 2024: comparison guide, frequently asked questions, what is marker.io, who is marker.io for, how easy is it to set up, will marker.io slow down my website, do clients need an account to send feedback, how much does it cost, get started now.

How to Write & Manage Test Cases in Jira

How to Write & Manage Test Cases in Jira

Are you wondering about the best ways to write and manage test cases in Jira? In this guide we will look at the three most popular options on how to write your test cases in Jira . You can then decide on the best option for your team & your projects and start writing your test cases with Jira.

In addition to writing test cases, the explained options also allow you to enter test results, track your testing progress, work with test automation and generate reports for your quality assurance team or clients. So let's get started!

Option 1: Using Jira Issues for Test Cases

Option 2: basic jira testing marketplace apps, option 3: full test management with jira, start testing with testmo free.

Full test management & Jia integration

Test automation runs

This first option is what many teams start with and try first. With this approach you are using Jira issues and custom Jira issue types with custom fields for test cases and for test results. You start by adding a new issue type, e.g. Test case , and add a couple of relevant custom fields. For example, you could add a custom text field called Test steps and another field called Expected results . You then add a new issue for each test case.

how to write a test case in jira

Writing test cases in Jira using custom issue types

To enter test results for test cases, you would then add another sub-task issue type, e.g. called Test result . Every time you execute your test case (or plan to execute it), you can simply add another test result sub-task. This allows you to quickly see the results for a specific test case from the test case's issue page.

The advantage of this option is that you do not need another tool other than Jira, as you can configure the issue types and fields with Jira's built-in features. This is also where the advantages of this option end, as this approach doesn't make it easy to manage your test cases or track your test results. If you do not want to or cannot use one of the other options explained below, we would recommend using Google Spreadsheet or Excel for your test cases instead, as this Jira option is unlikely to work even for teams with basic very basic needs.

This option is best for: This option is not recommended for any team. Either use one of the other options below, or use a basic spreadsheet with Excel or Google Docs instead.

Pros & advantages:

✅   No need for another tool, you only use features already built into Jira ✅   Free or already paid via Atlassian Jira subscription

Cons & drawbacks:

❌   Only very basic features & no way to structure your test cases ❌   Cannot use even basic testing workflows or reuse test cases ❌   No test management reporting, metrics or relevant charts ❌   No support for test automation or exploratory testing

Another option is to use one of the many Jira marketplace apps for test management to write test cases in Jira. These apps extend Jira's functionality and use a mix of custom Jira issue types and fields (like option #1), plus some additional custom field types, reports and sometimes APIs. They make it easy to get started with basic test case management and can be useful for teams new to software testing to manage everything inside Jira.

The main problem with marketplace apps that use Jira issues for test case management is that they are heavily limited by the way Jira issues work. For development tasks, feature stories and bug reporting, Jira issues provide a good level of maintainability and structure. For test cases and results, you need to be able to group test cases by functionality (e.g. via folders), maintain a specific order of your tests (so testers can work through the tests in the right order faster), easily start & reuse test runs, and quickly view your test results at a glance. Jira issues aren't built to provide and support such basic & important testing features, making it difficult to use issues for larger testing efforts.

how to write a test case in jira

The Atlassian Marketplace offers many Jira apps, including basic test management apps

Nonetheless, if your team is just getting started with testing and you do not have a dedicated testing team, then using this option can be a good initial approach. Just be aware that you might need to switch to a dedicated test management tool once your team grows and once you get more serious about test management. Another caveat is that you always need to buy these apps for your entire team, even if only a small number of users need it (this is an Atlassian policy for all paid Jira apps). This can make it more costly to buy such basic apps even compared to full-featured dedicated test management tools. You can also review our list of the best Jira test management tools , which features both full and Jira-only apps.

This option is best for: Teams with very basic needs without dedicated testers or QA engineers can use this option to write test cases in Jira. Larger teams or teams with dedicated testers benefit from more scalable tools.

✅   Apps automatically add & configure Jira issue types & fields for you ✅   Provide additional custom field types optimized for test results ✅   Embeds inside Jira so everything is handled through the same interface ✅   Offer additional APIs so you can build your own test automation integrations

❌   You always need to buy apps for all Jira users, even if they do not use it ❌   Only very limited test case management features; limited reporting & metrics ❌   No support to structure your test cases; limited by Jira issues ❌   Cannot use integrations with other tools such as GitHub, GitLab etc. ❌   Intransparent hosting with external vendor (your data is stored outside of Jira/Atlassian without your team likely realizing it)

Many testing & QA teams use a dedicated, full test management tool and integrate it with Jira. This hybrid approach often provides a good combination of features, tester productivity, reporting & metrics and scalability. This also allows you to integrate test automation, CI pipelines, work with multiple Jira instances or even integrate other systems your team might use, such as GitHub and GitLab.

how to write a test case in jira

Full test management to track manual, exploratory & automated tests (here: Testmo )

When reviewing and selecting a full test management tool, you should also take a look at the Jira test management integration provided by the tool. Just because you are using a full test management tool doesn't mean that you cannot quickly create Jira issues or even view linked test cases and results inside Jira. Typically, good test management tools provide rich Jira integration:

  • Directly create Jira issues from your test management tool during testing
  • Reference Jira issues from test results, test cases, runs, exploratory sessions & more
  • Look up the status of linked Jira issues inside the test management tool in real-time
  • Provide additional (free) Jira app to view linked test cases & results inside Jira

how to write a test case in jira

Full Jira test management with Testmo integrated with Jira issue page

One reason many testing teams prefer a dedicated, full test management tool is that they can also easily integrate and manage test automation and exploratory testing in one tool, not just manual test cases. Teams also often use a variety of tools, such as GitHub, GitLab or even multiple Jira instances. Full test management tools usually make it easy to use and integrate all these DevOps tools very quickly for a fast and productive testing workflow. You can also review our list of the best test management tools to get an overview of available tools.

This option is best for: Teams with dedicated testers that want to build a scalable and repeatable testing process for their projects. Also recommended for teams using test automation, exploratory testing & teams who want to integrate with different tools.

✅   Advanced test management features; scales with projects and teams ✅   Group test cases in folders, start separate test runs, link milestones etc. ✅   Rich testing reports, manage test assignments, QA workflows & exploratory testing ✅   Ready-to-use test automation & CI support, no need for custom programming ✅   Integrate with multiple Jira instances, or GitHub, GitLab & more

❌   You have to add another tool to your DevOps toolkit ❌   Testers usually need both Jira and the test management tool during testing ❌   Need to configure the Jira integration initially for your team

Conclusion and Summary

Whether you are looking for a basic Jira app or a dedicated, full test management tool to manage your software tests, thinking about your software testing approach and choosing the right balance between structured testing, exploratory tests & automation for your projects will help you build better software.

Even choosing the best tool won't magically fix your quality assurance approach or improve your software quality if you are not using the right strategy for your projects. When choosing a new tool, it is also usually a good time to think about your testing approach and experiment with new ideas to test earlier, to cover more with fewer tests or to give your testers more time and freedom to explore testing outside of pre-defined test cases. Then choosing a matching tool to write & manage tests with Jira will make your and your team's lives much easier.

Full test management & Jira integration

PS: We regularly publish original software testing & QA research, including free guides, reports and news. To receive our next postings, you can layout--page#doShowSubscribeModal">subscribe to updates . You can also follow us on Twitter and Linkedin .

how to write a test case in jira

Start testing with Testmo for free today

  • Test Management
  • Terms of Service
  • Privacy Policy
  • About & Contact
  • Feature Tour
  • Pricing & Plans
  • Unified QA Testing
  • Test Case Management
  • Exploratory Testing
  • Test Automation
  • Projects & Milestones
  • Reporting & Metrics
  • QA Team Productivity
  • CI Pipelines & DevOps
  • IT Enterprise Cloud
  • Integrations & Jira
  • Testmo Blog
  • Testing Guides
  • Support & Docs
  • Testing Topics
  • layout--page#doShowSubscribeModal">Newsletter
  • Legal & Terms

Subscribe Subscribe to updates

No search results found!!!

How to Write and Manage Test Cases for Jira

How to Write and Manage Test Cases for Jira?

Ritika Kumari

Jira started out as an issue-tracking and project-management tool in 2002. Companies initially used Jira for bug tracking. But over the years, it has become a ubiquitous platform for businesses to manage projects and ensure collaboration. Yet one issue has remained constant since the beginning: Jira does not have an in-built testing infrastructure. So, you can feed the defect information but cannot reuse it for further testing processes in the tool. But the good part is Jira allows integrations with some of the top-rated test automation tools, including Testsigma, for complete test case management.

Let’s look at how you can write and manage test cases for Jira.

Table Of Contents

  • 1 What is Jira?
  • 2 How to Setup Jira for Case Testing?
  • 3 How to Create Test Cases in Jira?
  • 4.1 Step 1. Create a Test Case Issue and Keep It Active
  • 4.2 Step 2. Change a User Story to Be a Test Case
  • 4.3 Step 3. Add a Testing as a Status in Jira Workflow
  • 5.0.1 Dedicated Test Case Management Tool with Jira Integration
  • 6 Problems with Writing Test Cases in Jira
  • 7 Advantages of using Jira for Test Case Management
  • 8 Disadvantages of using Jira for Test Case Management
  • 9 Conclusion
  • 10.1 Does Jira work for test case management?
  • 10.2 What is the test case template in Jira?

What is Jira?

Jira is a widely used project management and issue-tracking tool by Atlassian. It provides a versatile platform for teams to plan, track, and manage their work efficiently. Multiple in-built features, such as customizable dashboards, real-time collaboration, and detailed reporting, make Jira a fan-favorite of many top companies.

But what stands out in the tool is its integration capabilities, extensive plugin marketplace, and compatibility with agile methodologies. For instance, businesses can easily combine their test automation platforms with Jira for easy and quick test case management and bug reporting. Our focus will be on this particular feature of the tool throughout the blog.

How to Setup Jira for Case Testing?

Jira does not have an inherent test case feature, but it has innumerable customization options. For case testing setup, we will use the Issue Type feature by creating a new custom issue that is specifically for case testing. Additionally, you will need to set up custom subtasks that testers can use to feed the test case results directly into Jira.

It is ideal to have your custom ‘Test Case’ issue type to have a summary, test case steps, and the expected results.

Once you have the vital information in place, let’s start with creating our custom issue type for case testing:

  • Go to Jira Settings by clicking on the gear icon in the top-right corner and selecting Issues . You will require admin access for this.
  • Under the Issues section, select Issue Types and click on the Add Issue Type button to create a Test Case issue.
  • Provide details for the new issue type, including description and icon.
  • Associate the new issue type with an issue type scheme . This determines which projects will use the new issue type. Go to Issue type schemes settings and click Edit on the Jira project you want to associate the issue type with.
  • Assign a field configuration to the issue type, specifying which fields will be available and required. Don’t forget to add a summary, test case steps, and the expected results. You will find it under Screen Settings to Add Screens.
  • After adding screens, go to Screen Schemes to add a screen scheme. This step is to add the screen scheme to the custom screen you created in the previous step.
  • Next, go to Issue type screen schemes . Look for the Jira project in which you want to use the new Issue type. Then, select Associate an issue type with a screen scheme , and select the new issue type (e.g. Test Case) and its Screen scheme. Lastly, click on Add .
  • And voila! You have successfully created a custom issue type for case testing with the necessary fields within the choice of your Jira project.
  • Verify by creating a test issue of the new type to check if it behaves as expected.

Next up, you have to create a custom subtask, Test Case Results, that QAs can use to log the test results directly.

Here are the steps to follow:

  • Follow the same first step to add the issue type. But this time, select Sub-Task Issue Type.
  • Re-trace the same steps. Add screens, select the fields for the subtask, add screen schemes, and select the previously created screen as default.
  • In the last step, when you are in the Issue type screen scheme, there is no need to create a new screen scheme. Look for the test case screen scheme set up prior and select Configure under Actions to Associate an issue type with a screen scheme.

How to Create Test Cases in Jira?

Creating test cases in Jira is easy now that you have an issue type and the necessary fields to describe and log your tests. It is similar to creating a new task.

Go to your Jira account and click on Create . Pick the issue type as Test Case and enter the details in the available fields. Remember to provide the steps to recreate the defect and the expected results for the developers to fully understand the issue.

Create Issue

Image source: maker.io

Steps for Writing Test Cases in Jira

All the essential elements are in place for you to start creating and managing test cases in Jira. The only thing left to do is start logging the issues.

Step 1. Create a Test Case Issue and Keep It Active

You can begin by creating a Jira task with the Issue Type Test Case that we made earlier. It will allow you to feed all the critical and important information about the issue in the task. However, there is a downside to this step. Jira tasks are not flexible. Once you create and publish it for everyone to see, it cannot be reused, which is a common practice in regression testing.

One way to tackle this is to keep the task open and update its description regularly with new tests that everyone in the project can follow.

Step 2. Change a User Story to Be a Test Case

Jira also enables users to create user stories, which you can use to serve as test cases. But again, these stories have the same problem as the tasks. Once they are pushed, you cannot use them to re-run the test cases.

Step 3. Add a Testing as a Status in Jira Workflow

Another way to handle tests in Jira is to add an extra status in the workflow, i.e., testing. When you add a Test Case issue type, which is still in the testing stage, keep the status as Testing. Once the process is over, mark it as Done or Closed.

But there might be cases where the tests are over, but the testing is still not done. So, you will have to find a workaround in that situation.

Report on Test Cases in Jira

The final round of testing is to prepare a comprehensive report that aids in analyzing and understanding the bugs. In Jira, you can rely on two ways for test reporting:

  • Writing it manually with all the necessary screenshots and steps

For this approach, you need to make a child issue to the parent issue, i.e., the test case. 

Click on Add a Child Issue and choose Test Case Results, which we created in the earlier section. Next, enter all your findings along with relevant screenshots and steps to help everyone relate the results with the right test case. This way of reporting simple but comes with a few disadvantages: it is manual, requires developers to keep switching between Jira and their application, and demands technical skills to log issues. Opting for an automated approach is the alternative here.

  • Integrating a third-party tool with the host to do all the reporting work automatically

Since Jira does not offer support for test case reporting automatically, a bug reporting tool takes the lead here. A well-thought integration with the right tool for case testing and bug reporting for Jira will assist both testers and developers in easily doing their work.

Dedicated Test Case Management Tool with Jira Integration

Testsigma is a dedicated test case management tool and comes equipped with features to aid bug reporting in Jira. Our test automation tool enables QAs to:

  • Push bugs directly to Jira’s project
  • Capture screenshots, annotate bugs, and share them with your team
  • Follow your choice of test case template and re-produced bugs with the right steps to feed in Jira

Bug reporting

Integrate Testsigma with Jira in a few easy steps to simplify your bug-reporting process.

But wait! That’s not all. Testsigma is a full-fledged web automated testing tool that provides end-to-end testing capabilities for mobile and API without coding.

Sign up to experience the best of no-code automation testing with Testsigma

Problems with Writing Test Cases in Jira

Every step we discussed that pertains to writing test cases in Jira has encountered a problem. It is a highly manual process, does not support re-running of test cases, and requires time and skill to create a single test case.

Jira is a dedicated project management tool, and even though there are ways you can make writing test cases possible within Jira, it is not good practice to do so.

Advantages of using Jira for Test Case Management

Despite all the backlogs Jira has when it comes to test case management, there exist a few advantages that must not be overlooked.

  • Jira provides a centralized repository for storing and organizing test cases. This centralization ensures easy access, version control, and efficient management of test artifacts.
  • Seamless integration between Jira and development tools streamlines communication between testing and development teams.
  • Jira offers robust traceability features, linking test cases to requirements, user stories, and defects.
  • Jira supports agile and Scrum methodologies, allowing testing teams to align with iterative development cycles.
  • Teams can design custom workflows in Jira to reflect their specific testing processes, incorporating stages for planning, execution, test case review , and closure.
  • Jira provides real-time visibility into testing progress through customizable dashboards and reports.

Disadvantages of using Jira for Test Case Management

Let’s look at some of the disadvantages as well.

  • Jira’s extensive customization options can lead to complexity during initial setup. Teams may face challenges in configuring workflows, screens, and issue types.
  • Jira can be resource-intensive, especially in instances with a large number of projects, issues, or concurrent users.
  • While customization is a strength, excessive customization can lead to maintenance challenges. Constantly changing configurations may create dependencies and impact the stability of the testing environment.
  • Jira’s native test management features are basic compared to specialized test management tools. Advanced test case management functionalities, such as test case design, traceability matrices, and test execution analytics, may require additional plugins or integration with dedicated test management tools.
  • The feature-rich interface of Jira can overwhelm users, especially those focused primarily on test case management.

The Jira project management tool can serve as a test case management and bug-tracking tool. But when the stakes are high, it is not always the right way to go. There are multiple ways you can use Jira for your testing purposes, and the majority of them include improving collaboration and focusing on getting the right information across to the developers.

If you wish to use Jira as a case management tool, this blog can help you get a hold of the tool’s capability in every way. Alternatively, multiple integration possibilities exist as well. But no matter your choice, remember to focus on creating a clear and concise test case report that captures as much information as possible.

Frequently Asked Questions

Does jira work for test case management.

Yes, Jira can be used for test case management. It provides a flexible and customizable platform that supports various testing methodologies, including manual and automated testing. The latter is done using third-party integrations.

What is the test case template in Jira?

In Jira, a test case template serves as a predefined structure or blueprint for creating test cases with consistent formatting and information. This template includes standard sections, fields, and steps that testers can use as a starting point when designing test cases.Particularly, a test case template in Jira would be a new issue type that we created in this blog in one of the sections.

Ritika Kumari

A writer for 4+ years with QA and Engineering background, I have always liked to blend creativity with technology. Although my experience plays an important role in making every article ‘my own piece of work,’ I believe writing is a never-ending learning process where I am still a student. Besides creating content, I try to read every book there ever existed and travel to places that are within reach (for now).

Like what you see?

Subscribe to get all our latest blogs, updates delivered directly to your inbox.

Test automation made easy

Start your smart continuous testing journey today with Testsigma.

SHARE THIS BLOG

Related posts.

What is Rapid Software Testing & How to Perform

MarketSplash

How To Write A Test Case In Jira

Creating a clear test case in Jira ensures that features are vetted for functionality and robustness. Let's begin!

Ever struggled to ensure every feature works as intended in your project?

Jira can help with that. Beyond just logging bugs or tasks, Jira offers the ability to document detailed test cases, crucial for the QA process. Understanding how to properly structure these cases ensures clear and accurate testing. In this guide, we'll walk you through the process of creating effective test cases in Jira.

Tips To Optimize Your Test Case

Structure for writing a test case, test cases in jira vs other tools, frequently asked questions.

Important disclosure: we're proud affiliates of some tools mentioned in this guide. If you click an affiliate link and subsequently make a purchase, we will earn a small commission at no additional cost to you (you pay nothing extra). For more information, read our affiliate disclosure.

Using A Third-Party App

  • Open your project and click on "Create" .

how to write a test case in jira

  • Click on "Issue type" and click on "Test Case" .

how to write a test case in jira

  • Add your "Summary" which should highlight your goal.

how to write a test case in jira

  • In your description, add your Preconditions , Test Steps , Expected Result (Objective) , and Actual Result and click on "Create" .

how to write a test case in jira

  • You can view your issue and edit your description and add to "Actual Result" .

how to write a test case in jira

  • In your Work page, click on "Apps" and click on "Explore more apps" .

how to write a test case in jira

  • In the search bar above type in "Test Case" then choose your preferred app. (Staff Pick apps are highly recommended when choosing a third-party app).

how to write a test case in jira

  • Click on "Start free trial" .

how to write a test case in jira

  • Once it has downloaded click on "Apps" and open the app.

how to write a test case in jira

  • Click on "+ New Test Case" .

how to write a test case in jira

  • Fill in the necessary information and create your test case.
  • If you're using Jira and not a third-party app, use custom fields to optimize your test cases.

how to write a test case in jira

  • Create a "Checkboxes" field type.

how to write a test case in jira

  • Create a "Paragraph" field type.

how to write a test case in jira

  • After creating your field type, create a test case issue and click on the three dots and click on "Show fields" .

how to write a test case in jira

  • Add the custom field types and click on "Apply" .

how to write a test case in jira

  • Now you have a separate "Actual Result" field and a "Tested" yes or no checkbox field.

how to write a test case in jira

Writing a test case in Jira requires a clear structure to ensure that it's comprehensive and easy for QA testers to understand and follow. Here's a suggested structure for crafting a test case in Jira:

  • A brief, descriptive name for the test case that indicates what it is testing.
  • Description:
  • A concise summary of what the test case will cover.
  • Include the objective or the purpose of the test.
  • Preconditions:
  • Any prerequisites or conditions that must be met before the test can be executed.
  • This can include setup requirements, specific data points, configurations, or software versions.
  • Test Steps:
  • A detailed, step-by-step breakdown of how the test should be executed.
  • Each step should be clearly numbered.
  • Provide any necessary input data for each step.
  • Expected Result:
  • Clearly describe the expected outcome after each test step is executed.
  • This serves as the benchmark to determine if the test has passed or failed.
  • Actual Result:
  • Document the actual result of the test once it's been executed. This will be filled out during the testing phase.
  • Indicate whether the test passed or failed based on comparing the expected and actual results.
  • Comments/Notes:
  • Any additional observations or notes that might be relevant during or after the test.
  • Attachments:
  • Include any screenshots, logs, or other files that might be relevant for reference or to provide evidence of the test result.
  • Indicate the importance of the test case. This can be set as High, Medium, or Low, depending on your test strategy.
  • Assigned to:
  • The person responsible for executing the test.
  • Labels/Tags:
  • Useful for categorizing or filtering test cases.

Having a reliable platform to manage and track test cases is indispensable . Jira, Asana, and monday.com are well-known names in this domain, but how do they compare when it comes to handling test cases?

Let's get into a comparison.

Jira vs Asana vs monday.com

While Jira offers complex test case management tools suitable for large enterprises, and Asana caters more to basic task management, monday.com stands ou t with its perfect blend of visual project overviews, intuitive design, and feature-packed capabilities.

It's not just about managing test cases, but doing so with clarity and collaboration at the forefront. For teams looking for an efficient, visually appealing, and highly collaborative platform, monday.com is a compelling choice .

Can I link my test case to a requirement or user story?

Yes, Jira allows you to link different issue types. So, you can link your test case to a requirement, user story, or bug to maintain traceability.

Is there a way to clone a test case in Jira?

Yes, just like other issues in Jira, you can clone a test case. This is especially useful when creating test cases with similar steps or data.

Can I automate my test cases using Jira?

While Jira itself doesn't offer test automation, plugins like Zephyr or Xray integrate with automation tools, allowing you to manage and trigger automated tests.

Can I group multiple test cases in Jira?

Yes, with test management plugins, you can group test cases into test cycles or test suites for better organization and batch execution.

Can I import/export test cases in Jira?

Many test management plugins for Jira offer import/export functionality. You can usually import or export test cases using formats like CSV or Excel.

What To Create For Test Cases?

Crafting test cases in Jira, it's evident that precision and clarity are paramount. While Jira offers strong tools for test management, especially with the aid of plugins, it's important to consider alternative platforms that could bring a fresh perspective to your process.

monday.com offers a more unified experience, especially for teams seeking simplicity without compromising on functionality.

If you're searching for the right project management and task-tracking tool, don't shy away from giving monday.com a try. After all, the right tool is the one that fits your team's rhythm best and for us that's monday.com !

Subscribe to our newsletter

Subscribe to be notified of new content on marketsplash..

How to write Test Cases in Jira?

When we are into building complex projects, testing can become uneasy to handle. This is where test cases come into action as they make sure all things work as expected. By default, JIRA does not provide any feature for test case handling. So the question boils down to How to write test cases in JIRA. In 2013, this problem was tackled by the introduction of Xray as a Jira add-on which is now considered one of the most popular JIRA add-ons.

What is a test?

A test is a way of verifying if the application or component is working as it was expected from it according to requirements. It can be considered a type of check which focuses on checking the correctness or quality of a target.

A test typically consists of variables with some conditions, test inputs, and expected outcomes to maintain the required performance and quality of a software application.

A test is considered successful only if the expected outcome matches the real outcome for the component being tested. This is why every functional requirement is usually mapped to one or more test cases.

Test process in Xray

Xray allows us in planning, design, and execute` test cases and can also help in generating reports by using specific JIRA issue types. The testing phase is as follows :

  • Plan phase: Test plan issues
  • Design phase: Specification is generally defined using the pre-conditions and test issue types.
  • Execute phase: Test execution issues
  • Report phase: Built-in Reports generation in test execution issues

How to Write Test Cases in Jira (with steps)

To write test cases in JIRA, one can follow the following steps:

How to Write Test Cases in Jira

  • Click on any Project.
  • Select 'Test' in the 'Issue type' option.

How to Write Test Cases in Jira2

  • Finally, Select the 'Create' button.

Configuring Jira to Accept Test Results for Your Cases (with steps)

Now that we are in the position of creating test cases in JIRA, we may want to assign the PASS/FAIL/SKIP status to each of them upon execution.

This functionality further requires some configurational steps in JIRA which are as follows:

1. Custom Issue Type

  • In the main menu, Select 'Settings' , then 'Issues', and then select 'Custom Fields'.
  • Select 'Add custom field' and add 2 fields to it.

Name: "Test Case Result", Field Type : Radio Button, Field Options: Pass, Fail, Skip Name: "Test Case Actual Results", Field Type: Text field, Multiline

2. Create a Screen for the Result

Now, there is a need for a new screen for the test case's results which we will add as another sub-task.

  • In the main menu, Select 'Settings' , then 'Issues', and then 'Screens'
  • Select 'Add Screen'
  • Create an entry as follows:

Form field values : Name : "Test Result Screen"

Create a Screen for the Result

3. Create a Screen Schema for the Result

Now, we need to create a schema for the result by following the steps:

  • In the main menu, Select 'Settings', then 'Issues', and then 'Screen Schemes'
  • Select 'Add screen scheme'
  • Form field values : Name : "Test Result Scheme" Default Screen : "Test Result Screen"

4. Configure the Issue Type Screen Scheme

Finally, we need to link the newly created schema to a Jira sub-task.

  • In the main menu, Select 'Settings', then 'Issues', and then 'Issue Type Screen Schemes'.
  • Select 'Configure' beside the existing scheme created with the name "Test Case Screen Scheme".
  • Select "Associate an issue type with a screen scheme".

Form field values: Issue Type : "Sub-task" Default Screen : "Test Result Scheme"

5. Add a Test Case Result

Now, we need to add results to our test cases in the following way:

  • Select any existing test cases and open the drop-down menu.
  • Select the 'Create sub-task option.
  • To enter a result, enter the following fields: Summary – Can either be a date/release number/test run name Test case result – Radio buttons for assigning PASS/FAIL/SKIP to a test case Test case actual result – If the actual result differs from the expected, use this box to provide further information.

Test Case Reporting

Test case reporting is not a simple thing in JIRA as it was not specifically designed for test case management. But, below are some tips to have reports and test cases in one list:

  • 'All Issues' option enables us to view all things together
  • We can select 'List View' using options present at the top
  • Select the 'Type' filter and then select 'Test Case' to have only test cases in the view.
  • In a similar way, we can only have the results in the view.
  • Free text search field can also be used to enhance the search experience if some name was added to your test cases.

Test Case Reporting

Problems with writing test cases in Jira

There are some problems associated with test cases in JIRA , some of them are listed below:

  • Test cases management task in JIRA involved a lot of customization work .
  • A good amount of time is needed to configure JIRA to work for test cases and also needs a good experience as a Jira administrator.
  • Originally, JIRA was not built for test case management so the customization part takes up a lot of time.
  • A lot of screens one needs to go through while preparing test cases and their results which results in low productivity.
  • JIRA does not provide the count of how many times a test had run or had failed which further is a big disadvantage.

Quick Tips for Writing Test Cases in Jira

Following are some quick tips for efficient test case writing in JIRA:

  • Use clear and concise language

Make sure your test cases are easy to understand and written in clear language. Using bullet points and headings can help organize the test steps.

  • Be specific and detailed

The test cases should be clear and easy to follow so that testers can reproduce the steps described.

  • Test cases should be independent of each other

Each test case should be executable on its own, without any dependencies on other test cases.

  • Test cases should be testable

This means that there should be a way to measure whether or not the test case has passed or failed.

  • Test cases should be up-to-date

We must make sure to update the test cases regularly to reflect the latest changes to the software under development.

  • Include expected results

We must make sure that each test case includes the expected results to ensure the application is working correctly.

In this article, we learned about:

  • How to write test cases in JIRA as JIRA doesn't have the native functionality
  • How the test process in Xray while creating test cases looks like
  • Configuring JIRA for accepting test cases for test case reporting functionality
  • Some of the problems that may be encountered while dealing with tests in JIRA and how we can deal with them
  • Quick tips on how to speed up the test case writing process.

A guide to using Jira for test case management

Tricentis staff, various contributors.

We’ve recently fielded a lot of questions about using Jira for test case management . From how to use Jira for testing to which solutions best complement a Jira process, both Jira and testing seem to be the topics of the hour these days.

This popularity is not necessarily surprising given a recent Tricentis poll in which 66% of respondents reported having used Jira for the past several months or years.

So what exactly do you need to know when it comes to using Jira for test case management? This guide will walk you through everything from soup to nuts, including:

Challenges of using Jira for testing

How to customize jira for testing, pros and cons of using strictly jira for test case management, options for integrating testing tools with jira.

  • Tips for finding the best solution mix for your needs

A quick b ackground on Jira

For those who don’t know, Jira is an issue and project tracking software from Atlassian. Currently, it’s the number one software development tool used by Agile teams, and as Agile adoption continues to grow, more and more organizations are introducing Jira. The recent IPO as well as the massive wave of companies leaving legacy ALM providers have only fueled the widespread adoption of Jira.

Although JIRA is designed for issue and project tracking, many teams are using it for test case management so that development and testing can stay in one system. But how exactly is JIRA set up for testing? Let’s take a look.

Going back to the question of how JIRA is set up for testing, the short answer is that JIRA isn’t. The reality is a lot more complicated, especially given how many organizations are using it for testing today.

When you begin looking at how you can build a testing process in Jira, the most common place to start is with an issue type. You’ll see that Jira has several different types of issues (Bug, Epic, Improvement), but nothing specifically for tests. This is because Jira is not a test case management solution. It’s really meant for issue tracking.

You can customize Jira in certain ways to use it for some test case management processes , but these are makeshift customizations and they have limitations as a result. For example, every workflow built inside Jira has an endpoint of “done.” But in testing, even if you complete a test, that doesn’t necessarily mean that you’re actually done with that test.

This setup means that if you customize Jira or certain issues for test case management, you’ll always find yourself moving to a done status when you might not be “done” once a test executes. What you really want is to be able to use that test case for multiple types of testing, whether it be for regression testing or running the same test case under various parameters and configurations to validate a new feature. However, since Jira issues are always meant to be pushed to “done,” you are limited in the flexibility to reuse the issue for testing.

Atlassian’s own documentation on Jira says that it can work for manual testing, acceptance testing and so on, but it clearly warns that there is no testing-specific functionality built naively into Jira. Also, if you are using any type of automation, you need to use another solution.

Even with manual and acceptance testing, there are some limitations. Let’s say that Jira does a really good job of running a manual test case. It might work one time or for a brand new feature, but then you move it to the done status and what happens next? What if you want to do regression or session-based testing? How are you going to reuse those objects across projects, assign multiple ticket items and show that coverage? Due to the way Jira is set up, you can’t.

Despite the limitations posed, many teams are using JIRA for test case management, and they’re typically doing so by customizing issues in one of two ways: adding a “test case” issue type, or using the “user story.” Let’s take a closer look at how each of these options works:

Deep dive: Adding a “Test Case” issue type

To customize Jira for test case management by adding a “Test Case” issue type, you need to take the following steps:

  • Create a “Test Case” issue type
  • Add in the steps required to complete an expected outcome
  • Make that test case the parent issue for the testing you need to do
  • Create a subtask and label that subtask as “Test Run” in order to execute the test
  • Put in the outcomes, the affected versions, the results of that and the assignee who’s running the test within the “Test Run” subtask

While this approach works in theory, in reality it presents several challenges:

  • Rerunning tests:  If you need to rerun a test execution or test a new version, you need to add more test runs as subtasks, and you have to add a subtask every single time you want to log the history of that test case.
  • Reusing tests:  With test case management, you often need to reuse test runs and have visibility into logs of those test runs, but you can’t reuse subtasks in JIRA because they are marked as “done”.
  • Creating coverage reports: Because all the subtasks are assigned under one parent issue, you can’t group several test runs to different configurations and show a coverage report.

Deep dive: Using the “User Story”

Alternatively, you can customize Jira for test case management by tweaking the “User Story”. Here’s how this approach works:

  • Create a User Story (this will act as the test case in the same way that the new parent issue did in the first option)
  • Add a subtask that acts as a test case or a test run that refers back to that User Story
  • If all the subtasks pass, then the User Story is ready to go into production

Once again, this approach poses challenges because the subtask acts as the test case and the test run. Specifically, it poses challenges around:

  • Note: With Jira’s workflow, all issues that are marked as done get closed out. If you have to re-open a subtask and then convert it to a test case template or a test case type, you end up with a lot of overhead maintenance.
  • Aligning test cases: Due to this setup, if you have multiple test cases that link to multiple user stories, aligning test cases becomes extremely difficult.

As the above examples illustrate, while Jira is not designed for testing you can customize it to fulfill certain test case management needs. But, should you do this? Let’s consider the pros and cons of using strictly Jira for test case management:

Pros of using Jira for test case management:

  • Ability to create custom issue types such as test cases
  • One workflow for QA, developer and testing actions
  • Ability to use existing reporting (and Jira does offer excellent reporting)
  • Ability to use an already purchased and known tool (if you already have Jira in place)
  • Good for one-time manual execution

Cons of using Jira for test case management:

  • No testing specific functionality (this is something that Atlassian itself calls out)
  • Only integrates with testing frameworks via the CI server
  • Inability to create a test case coverage report that covers manual execution, automation execution and session-based execution
  • No traceability reporting between issues and test case coverage
  • No way to run executions more than once, which means significant duplication of effort
  • Limitations around test cycle and suite execution, test step execution status, version control and environment configuration

All of this means that things you would normally do with a test case and environment execution tool, such as grouping testing cycles and test executions, running test configurations and handling version control, are not supported. This makes you think: Is Jira really built for testing or are you forcing the issue (no pun intended, since everything in JIRA is an issue)? In most cases, you’re forcing the issue and there is likely a better way.

Because Jira is not designed for testing, it poses many limitations when it’s used for testing purposes. Arguably the biggest limitation is the inability to reuse and centralize testing efforts.

So if you’ve made the transition to Jira and your developers love it, what can you do? Is there any way for your test team to get value out of Jira? Integrations can help.

There are two types of integrations you can use to add testing functionality to Jira:

  • Add-ons, which are internal integrations that live inside the Jira application and extend some of the test case functionality
  • An external integration with a dedicated test case management tool

Let’s take a closer look at what each of these integration options entails:

What about Jira apps or add-ons?

Add-ons are available via the Atlassian Marketplace . A few commonly used add-ons for testing include:

  • Xray for Jira and Zephyr for Jira for manual test execution (Xray also offers a bit of functionality around BDD testing)
  • Behave Pro and Tricentis qTest Scenario for BDD, TDD and ATDD testing (these are best for smaller teams or those that are embracing more of an Agile 2.0 space inside of JIRA)

These types of add-ons extend the functionality of Jira to make it better equipped for test case management. For example, Xray automatically adds a “Test” issue type to the list of issues and allows you to add test case steps to the Test issue type. This setup alleviates the problem of creating a custom issue type that requires you to add in a bulk section that includes completed steps and expected outcomes (which in turn leaves you with huge chunks of testing that you have to do all at once and the inability to put in line by line where the steps failed, where it was executed and what your actual execution was).

Meanwhile, if you’re trying to do BDD testing, it’s hard to follow the Gherkin “given, when, then” syntax in JIRA alone, but an add-on like Tricentis qTest Scenario makes it possible. Tricentis qTest Scenario allows you to import your dot feature files along with your scenarios as issue types so that you no longer have to create standard issue types. Instead, you can add in the Gherkin style test scripting language in the scenario piece, where you can then create a dot feature file. You can also create scenario files that attach to those dot feature files inside of JIRA, which allows you to add them to a User Story.

Pros of using add-ons

In general, the testing add-ons try to bring together the groups of testing occurring in Jira so that you can pull all of the test cases you have into cycles or suites. They also allow you to see the latest execution results of the test cases for each grouping, which creates visibility into the grouping of test executions.

Other pros of using add-ons to improve the testing functionality of Jira include:

  • Maintaining a similar look and feel to Jira
  • Getting to use the dashboards inside of Jira
  • Simplifying purchasing by handling it online through the Atlassian Marketplace
  • Receiving access to testing specific functionality
  • Gaining the ability to link test objects to other issues

Cons of using add-ons

While the add-ons do help a lot, you’ll still be a bit strapped in terms of what you can and can’t do with your text execution because the add-on functionality is limited based on what the Jira infrastructure allows.

For example, the add-ons create a bit more of a manual process than you would have with a dedicated test case management solution. Additionally, everything you do inside the add-on is limited to the particular project at hand, meaning you can’t put the same issue in multiple projects.

The add-ons also present some version limitation when you’re creating a test case. Typically, if you create an issue and go to run the issue, the run is simply a duplication of the test case. Let’s say you have five steps in a test case that’s in a cycle to be run and you add another step. Jira will automatically push that data over into every test case run, meaning you can’t keep different versions. With Tricentis qTest and some other tools, you can actually keep track of different versions of test cases and run past versions when you execute, but you need to have a one-to-one version history of that test case execution in order to do that.

Finally, when you’re using an add-on, a test case equals a Jira issue. It may not appear that way, but that’s how it is with all the add-ons, and that setup poses limitations.

Other cons of using add-ons to improve the testing functionality of Jira include:

  • Zero or limited availability to reuse test cycles (you might be able to clone a test cycle or you may have to move test cases into an ad hoc test cycle that’s not attached to a release)
  • No logical folder structures
  • Unknown change history for test case versions and limited visibility into test execution history
  • Inability to share test case objects across Jira projects, which makes scaling difficult and creates a lot of duplicate work since you can’t run the same test with different variables
  • Limited scalability for storing a high volume of test result data, which often becomes a problem when teams transition to automated testing

Deep dive: Dedicated test case management solution

Most testing teams struggle to be very efficient. Often it’s because they’re simply not using the right tool. A dedicated test case management tool can help improve efficiency, and there are many that now offer some level of external integration with JIRA in order to bring more testing-specific functionality to your testing process while still allowing you to use JIRA.

Most testing teams struggle to be efficient. Often it’s because they’re simply not using the right tool.

What do test management tools do?

Test management tools:

  • Consolidate all of your automated and manual execution: A lot of the add-ons focus on just manual execution, BDD or TDD, but if you’re doing a Selenium automation or a custom framework, you’ll want to consolidate all of your executions in a way that also communicates with JIRA. A dedicated test case management tool can help you accomplish that objective.
  • Offer enhanced execution setup and the ability to reuse executions: Add-ons can group test cases into cycles, but they can’t put testing cycles inside other cycles or have a cycle that tests suite execution. Dedicated test case management tools, on the other hand, can do that. These tools also allow for scalability by making it so that you don’t have to go back to the source record and copy and change test cases.
  • Display the entire history of execution inside Jira: By displaying the entire history of execution inside Jira, a dedicated test case management tool can help you determine how a test case performs through testing phases. This view helps you easily see things like why a test case failed.
  • Allow you to share test cases with multiple projects: Dedicated test case management tools can also eliminate the isolation of test cases by making it easy to share test cases with multiple projects. For example, with Tricentis qTest , you can have multiple test runs of the same test case and each test run can have a different configuration, environment setup, results, assignees, etc., but they can all be tied to the same test case. This setup allows you to use the test case as a template instead of having to duplicate it over and over again.
  • Offer enterprise scalability: Unlike Jira apps and add-ons, Tricentis qTest does not rely on the Jira database or data structures to house data. To learn more about the storage limitations of Jira, read the results of our experiment with Jira Server and a common test management app .

Pros of using a dedicated test case management tool

By offering the functionality described above, integrating a dedicated test case management tool can go a long way toward improving testing within Jira. Pros of this approach include:

  • Access to enterprise test features like configuration manager, CI integrations with Jenkins and Bamboo and automated testing support
  • Ability to use test case repositories that are customized based on templates
  • Ability to reuse test cases and share objects across different projects
  • Support for multiple testing strategies

Cons of using a dedicated test case management tool

Despite all the value integrating a dedicated test case management tool with JIRA can provide, it still has its limitations. Cons of this approach include:

  • Handling constant database synchronization between the tool and Jira (more on this to follow)
  • Managing permissions for artifact mapping
  • Working around browser restrictions (e.g. HP requires Internet Explorer)
  • Missing a full integration with Jira
  • Working around varying degrees of open source friendliness among dedicated test case management tools

With these downsides in mind, there are a couple points to consider to help determine whether or not the pros of an external integration with a dedicated test case management tool outweigh the cons:

  • Does your team have a wide range of testing methodologies? If you’re a small team that’s only doing manual testing and there’s no push for automation, an add-on or Jira alone might work. However, if you have a wide range of testing methodologies, you likely need a dedicated test case management tool.
  • Does your test strategy warrant an enterprise testing tool? If it’s something you need, then an external integration is the way to go. If it’s simply a nice to have, an add-on or Jira alone might work.

Getting the best of both worlds

While a dedicated test case management tool offers the best experience for testing inside of Jira, it typically still poses some downsides. However, it is possible to get the best of both worlds between an enterprise test case management tool and Jira.

The key to achieving this balance is understanding that not all integrations are created equal and identifying the type of solution that offers the optimal integration experience for your needs. For example, most test solutions use a scheduled sync , but Tricentis qTest Manager has a real-time integration that uses webhooks.

best-in-class Jira integration chart

Which option is right for your organization?

Ultimately, which mix of solutions — Jira only, Jira plus an add-on or Jira plus an external integration — is right for your team depends a lot on the size of your team and the types of testing your doing.

To help you determine the solution mix that best fits your needs, we’ve mapped out our recommendations in the following chart:

Tricentis comparison matrix

Related resources

Featured image

Automated software testing: Optimizing DevSecOps for the public sector

Extra-functional testing: why we stopped using the term non-functional testing.

Featured image

Increase performance test coverage and minimize script fragility with Tricentis NeoLoad’s codeless test design

Tricentis vera™ + qtest: streamlining quality and compliance in life sciences, elevate software quality in 2024: quarterly roadmap update for customers.

Five best practices for managing test cases in Jira

Five best practices for managing test cases in Jira

Go agile for Jira success

The benefits of consolidating multiple Jira instances

The benefits of consolidating multiple J...

Expand your Jira hierarchy and sum up numerical fields with our new apps

Expand your Jira hierarchy and sum up nu...

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 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.

Keep your test cases simple and easy to understand 1 700x396

The benefits of consolidating multiple Jira instances

Expand your Jira hierarchy and sum up numerical fields with our new apps

Expand your Jira hierarchy and sum up numerical fields with our new apps

Shared understanding in seconds: shareable Enhanced Search filters in Jira

Shared understanding in seconds: shareable Enhanced Search filters in Jira

Jira Software

Project and issue tracking

Content collaboration

Jira Service Management

High-velocity ITSM

Visual project management

  • View all products

Marketplace

Connect thousands of apps and integrations for all your Atlassian products

Developer Experience Platform

Jira Product Discovery

Prioritization and roadmapping

You might find helpful

Cloud Product Roadmap

Atlassian Migration Program

Work Management

Manage projects and align goals across all teams to achieve deliverables

IT Service Management

Enable dev, IT ops, and business teams to deliver great service at high velocity

Agile & DevOps

Run a world-class agile software organization from discovery to delivery and operations

BY TEAM SIZE

Small Business

BY TEAM FUNCTION

Software Development

BY INDUSTRY

Telecommunications

Professional Services

What's new

Atlassian together.

Get Atlassian work management products in one convenient package for enterprise teams.

Atlassian Trust & Security

Customer Case Studies

Atlassian University

Atlassian Playbook

Product Documentation

Developer Resources

Atlassian Community

Atlassian Support

Enterprise Services

Partner Support

Purchasing & Licensing

Work Life Blog

Support for Server products ends February 15, 2024

With end of support for our Server products fast approaching, create a winning plan for your Cloud migration with the Atlassian Migration Program.

Assess my options

how to write a test case in jira

Atlassian Presents: Unleash

Product updates, hands-on training, and technical demos – catch all that and more at our biggest agile & DevOps event.

  • Atlassian.com

Interactive Guides

How to create and manage test cases with xray and jira.

Sergio Freire

Sérgio Freire

Head of Solution Architecture and Testing Advocacy, Xray

Step-by-step instructions on how to write, specify, organize, and execute test cases

Eight-minute read. Complete in one session (two hours)

You are new to Xray Test Management. You've created a project and want to learn how to write, specify, organize, and execute test cases.

Prerequisites

You’ve installed Xray in your Jira instance. Get started with Xray for Jira here.

You’ve created or added Xray to your project.

You have an active Jira project with the GitLab application installed and configured.  Get started with Jira here.

What is a test?

A test is an abstraction of a test idea/scenario and a way to verify/validate associated requirement(s). It’s one or more checks, an experiment, or an investigation with the goal of obtaining information about a quality attribute of the test target.

A traditional, manual test involves a sequence of steps coupled with conditions or variables, test inputs, and expected results. It is intended to establish the quality, performance, and/or reliability of a piece within a system. 

Usually, every requirement or objective of the test target is expected to achieve at least one test.

The success of a test is determined by comparing the expected and actual results.

 A test can be: 

  • Scripted (e.g. test case or automated test) or exploratory 
  • Specified using Gherkin (scenario)
  • Executed manually or through automation
  • Linked to/cover one or more requirements
  • Like any other Jira issue type, it can be labeled, prioritized, assigned to components, and commented on

Tests and testing in general don’t ensure quality. They provide information about quality.

100 percent coverage is a myth. Adding more tests doesn’t ensure better information about the quality that matters to you.

It’s often better to focus on assessing what stakeholders are concerned about, consider risks, and specify and perform testing based on these metrics. 

There will always be some bugs. It’s important to understand what’s valuable so testing can focus on what threatens those values.

Test process in Xray

Xray allows you to plan, design, and execute tests, as well as generate test reports. Xray uses specific Jira issues types for this process. 

Each testing phase allows you to use the following issues:

  • Plan phase : Test plan issues
  • Design phase : The specification is defined using precondition and test issue types. The organization of the tests can be defined using test sets
  • Execute phase : Test execution issues
  • Report phase : Test execution issues including built-in requirement coverage reports and custom issues using Jira Software tools

To start, it’s useful to add tests to a small project. You can use test issues to create tests for your requirements and execute ad hoc, unplanned test executions. Here’s how:

Step 1: How to write and specify tests

There are three default test types:

  • Cucumber : Write tests in a business-readable domain and specific language (Gherkin)
  • Generic : An unstructured test, without steps. This is a way to abstract and have visibility of traditional automated tests or exploratory tests
  • Manual : A traditional test case composed of a list of steps that are scripted

Each test type has one of three kinds of tests:

  • Unstructured

Actions you can perform on Xray tests: 

To create a new test issue follow these steps: 

Step 1 : Click Create Issue at the top of the screen to open the Create Issue dialog box/page.

Create button

Step 2 : Select the Project . On Issue Type , select Test .

Step 3 : Type a Summary for the test and fill at least all mandatory fields marked with an asterisk.

Create issue

Step 4 : When you are satisfied with the content of your test, click the Create button.

Step 2: How to organize tests

Organizing tests is a crucial part of daily testing activities. Since you might start with a large number of tests and your tests may grow over time, it’s important to organize them in an efficient and effective way that works for you. 

Xray provides two different ways to organize your tests:

  • Use the test sets issues
  • Use the test repository

The test set is a simple way to create different groups of tests, since it is a flat list of tests. You may have as many test sets as you wish and a test may be included in multiple test sets. Test sets are ideal if you want to have full control over certain groups of tests.

Create test sets

To create a new test set issue:

Step 1 : Click the Create Issue at the top of the screen to open the Create Issue dialog/page.

Step 2 : Select the Project and on Issue Type , select Test Set .

Step 3 : Type a Summary for the test set and complete at least all fields marked by an asterisk.

Step 4 : When you are satisfied with the content of your test set, click the Create button.

The test repository is a tree-like organizational structure at the project level. It allows you to hierarchically organize tests within folders and sub-folders. This folder concept is common in some tools and resembles file organization in a computer's operating system.

Create a test repository

To create a test repository, create a new folder:

Step 1 : Click on the parent folder.

Step 2 : Click on the add icon at the top of the folders section.

Test repository

Step 3 : Type the name for the folder on the create folder dialog.

Create Folder

Step 4 : Press "Create" to create the folder.

Step 3: How to plan tests

Test planning allows you to decide your testing strategy , including the issues you want to validate, how to validate them, if tests will be manual or automated, how resources will be allocated, and when and who will execute the tests.

Depending on several factors, you may want to prioritize some tests or focus on specific requirements.

Create a test plan

Here’s how to create a new test plan Issue: 

Step 1 : Click Create on the top of the screen to open the Create Issue dialog box/page or press the " C " key on the keyboard.

Step 2 : Select the Project . On the Issue Type , select Test Plan .

Step 3 : Type a Summary for the test plan and fill out at least all mandatory fields marked with an asterisk. 

Step 4 : When you are satisfied with the content of your test plan, click Create .

Create button

Step 4: How to execute tests

Test execution occurs between developing test scripts and reporting and analyzing test results. 

A test execution is an issue type that aggregates a user-determined collection of tests. It monitors and verifies if tests work as expected in a target context and environment. The overall execution status, updated after each test is performed, informs you about the progress of the test execution, including which tests passed, failed, are being executed, or are waiting to be performed.

Create a test execution issue

Step 1 : Click the + at the left of the screen to open the Create Issue dialog box.

Create Issue dialog box

Step 2 : Select Project . On Issue Type , select Test Execution .

Step 3 : Type a Summary for the test execution and fill out at least all mandatory fields marked with an asterisk.

Step 4 : In the Create Issue dialog populate the test execution custom fields provided by Xray, including the Begin/End date and Revision . 

Optional : To create a series of similar test executions within the same Project , check Create another at the bottom of the dialog.

Step 5 : When you are satisfied with the content of your test execution, click Create .

For more detailed information on how to create and manage test cases in Jira and Xray, check out the Xray Academy .

See more  integrations for Atlassian Open DevOps .

Sérgio Freire

Sérgio Freire is the Head of Solution Architecture and Testing Advocacy for Xray, a cutting-edge Test Management app for Jira. He works closely with many different teams worldwide to help them achieve great, high-quality, testable products. He believes that by understanding how organizations work, processes and quality can be improved while development and testing can "merge" and act as a unique team, with a common goal: provide the best product that stakeholders need.

Share this article

Recommended reading.

Bookmark these resources to learn about types of DevOps teams, or for ongoing updates about DevOps at Atlassian.

Devops illustration

DevOps community

Devops illustration

DevOps learning path

Map illustration

Get started for free

Sign up for our devops newsletter.

Thank you for signing up

Home Blog Application lifecycle management

7 ways to structure software requirements and test cases in Jira

  • Application lifecycle management

' src=

There’s a very good reason why more and more teams start using Jira for testing. The interface every Jira user knows well,   extended with a dedicated test management app,   turns out to be a perfect solution  to track the whole software development process  in one place . One of such apps, Requirements and Test  Management  for Jira  (RTM), brings  the organization  of all the testing objects to a higher level.  The tool allows structuring Requirements, Test Cases, Test Plans, Test Executions, and Defects into transparent trees of  folders and subfolders. That kind of view not only makes  collaboration between all the stakeholders easier but also  helps see how particular elements look in the context of the overall project. In this article, we would like to present how you and your team can make the most of that RTM’s functionality. 

Why is structurization so important?  

When it comes to test management, the most valuable thing is time – and time is exactly what good object structure and work organization can give you and your team. Transparent folders and subfolders speed up defining priorities, assigning tasks to team members, and executing them.

Besides that, testing activities are strongly connected with each other. Well-designed requirements, all covered by related test cases, minimize the number of possible defects in the end and thereby help to economize the time and effort spent on fixing them. Considering the numerous steps involved in the testing process, consistently performing them is essential for ensuring the final product’s quality. So, it’s definitely worth a while to prepare an intuitive list of Requirements  and  Test Cases . It will later on help with setting up  Test Plans  and  Test Executions .

Having said that, organization of testing elements must be adjusted to the type of the project and particular needs of the team. Below we present some ideas on how to structure requirements and test cases in Jira with  RTM ‘s tree view.

1. Structure by priority

Requirements and test cases differ when it comes to priority. Some of them have to be done as soon as possible, some can  wait,  and some are strictly connected to each other so  it’s  better not to proceed with them before finishing the previous ones. The best way to verif y p riority is by checkin g the  Prio rity  field , which one sets up on  New Requirement   and  New Test Case  creation screens. When  they’re  ready, the  tree view  allows to arrange them from  Critical  to  Trivial . That way, you put  the most urgent ones on top of the list.

Thanks to ‘ drag and drop’ repositioning,   m odifying the order is simple and fast. Testing is a dynamic  process, and  so the flexibility  of the tools you use is extremely important. If p riorities of the objects change throughout analysis or later, during test execution,  RTM lets you easily adjust to all those changes and preserve continuous progress.

2. Structure by feature

When the product testing process contains many requirements and test cases, categorization by feature will surely help with keeping track of  what’s going on with the project. On the screen below, product requirements are visibly organized in folders and subfolders. After preparing a  software requirements specification document, it  should be easy to  design a similar scheme for test cases .  Here we should describe which functionalities of the upcoming product should w e test to achieve the project’s goal. Plus, we need to find relations and dependencies between them . In  Requirements and Test Management for Jira, it’s  a good idea to enter  Components  and  Labels  on the   Details  tab and  sort cases based on that information. Doing that at the very beginning prevents the risk of having a mess in the process later.

Test cases Tree of folders on the left hand side. On the right hand side DEMO-64 Sharing account number via email: details, requirements, steps, relations. Description, Attachments, Activity

3. Structure by types of requirements

There are different types of requirements. To describe a project we can start with the basic four

  • Business requirements – mostly project managers but also software designers, investors, or even marketing teams create business cases to maximize profits or develop their services;
  • UI requirements – crucial information for users from the level of the user interface;
  • Functional requirements – features of the final product that can solve potential user’s difficulties
  • Non-functional requirements – additional development functions which are important also for the stakeholders.

Requirements of each type are equally significant. With the tree structure, it ‘s simple to divide them so your list would be transparent for  everyone i nvolved. Thanks to appealing data presentation, where  the types have their own colors and icons, the organization of items is clear at a  glance . On the Relations tab, we can immediately view the number and type of requirements to be covered by test cases. This allows us to generate a comprehensive task list for the testing team members. This kind of  structure  is  best when you  test a single product.  Otherwise, it  may become a bit chaotic during execution.

Jira screen view showing how to create a New Requirement: Details, type of requirement: UI Requirement

RTM for Jira Live Demo

Join us at Requirements and Test Management for Jira Cloud Live Demo conducted by the Deviniti Support team. Sign up with Calendly by clicking the button below!

4. Structure by environme nt

In RTM, the choice of your project’s  requirements and test case structure  is wide. You can arrange folders and subfolders however you see fit. In order to make sure that your  final product  will work in all the environments you want it to, you need to test requirements in every condition individually. That’s  why in  Test Cases  we have a field named  RTM   Environment .  Running test cases in various browsers, on desktop, mobile or tablet is absolutely necessary to avoid any surprises after the product release. In the process of testing on different systems, both requirements and test cases may be similar or even exactly the same. That’s why it’s smart to divide them by environment in order to spot the slight differences.

Jira screen view showing how to create a New Test Case: Details, Issue type, Summary: Languages, Description: App translation: English, Polish, German, French

5. Structure by Assignee

Another example that shows how useful  customized  folders  are  is the  possibility  to structure requirements and test cases by  Assignee.  Imagine how much easier it would be for each team member to have a dedicated folder. It  will certainly help  to save time that they usually spend searching for the cases they should do. What’s more, well-organized  objects  eliminate the risk of double execution of particular test cases. As we know , a clear definition of people responsible for particular elements of the whole  project  motivates and speeds up the process.

6. Structure by testing level or type

When organizing  Test Cases  in  RTM  it is possible to sort them by  testing   levels or types . We distinguish four basic levels of test cycles:

how to write a test case in jira

  • Unit Testing –  at this level we test individual  features  of a final product to verify if each unit of the software works as designed. It’s worth remembering that this stage doesn’t require test cases, as unit testing is performed during coding. F or tree-structured view it’s better to perform  Module Testing , meaning, testing every module of a product’s system one by one ;
  • Integration Testing –  level of a testing process where functionalities are tested as a group to prevent  bugs that  may occur during their integration;
  • System Testing –  where the whole, combined product’s system is tested to check its compliance with presumed requirements and sometimes also with external software;
  • Acceptance Testing –  final testing of a complete  piece of software ,  where the goal  is to confirm if the product meets  all the business requirements , works in expected use cases, and is ready to release.

If it comes to  types of testing , people name up to  9 of them  and the most common are:

  • Regression Testing  – performed to make sure if the whole system and previously implemented cases work well, despite the changes made during further development;
  • Smoke Testing  – relies  on  checking general functionalities to confirm if the  product is ready for more detailed tests;
  • Stress Testing –  testing the software in unusual conditions (for example when the memory of the environment is full);
  • Performance Testing  – verifies the final speed and effectiveness of the  product.

Managing test cases in Jira with  RTM  per testing level defines the order of their  execution, and organizing per testing type  sends  a clear message  to Jira users about what to focus on in  each  category.

7. Structure by  software   version

Even after a major software release, we can expect subsequent updates. The common problem with new versions is the consequences of changes. Modification of one unit can impact the other, not necessarily in a good way. It’s important to control all actions and their results from end to end, especially in such a complex process. That’s why sorting test cases per software version allows preserving the order of the executed changes. It makes it easier to track which version caused possible bugs. When it comes to the organization of the objects by software version, we can distinguish two possible ways:

  • by  Release Version  – where we focus on all the released updates and extensions of our product;
  • by  Fix Version,  or actualizations resulting from bugs in the software. On the  Defects   tab, we  have the  Fix Version  field, which can help with assigning particular test cases to the right version.

It’s possible to re-execute the Test Plans in our app . So, if something doesn’t go our way, we can always execute test runs all over again and spot the cause.

Shape up your testing with test cases in Jira

Methods we’ve listed before are only a few examples of how can you structure your software requirements and test cases in Jira using  Requirements and Test  Management for Jira (RTM) . The truth is that  RTM gives you the  possibility  to customize the tree view according to your project’s needs. Given that there’s no limit for nesting folders, you can use all the mentioned ways on one view! Make a good plan of collected requirements, assign test cases and bring your software project organization to a higher level.

Learn more on topic

Post thumbnail

TestFLO – How to use test steps 

Post thumbnail

Incident management process in Jira: 4 effective and secure practices

Post thumbnail

Optimize Your Test Case Chart. How To Write Tests For Clear Reporting?

Katarzyna kornaga.

Katarzyna is a Content Specialist, responsible for writing on the Deviniti blog. As an SEO enthusiast, most of all she values helpful, unique content where users can find answers to their questions. When not writing, you can find her at the theatre, at home with a good non-fiction book, or passing on city streets on her bike.

Let's explore the galaxy of possibilities

Subscribe to the newsletter and don't miss the most interesting articles and videos! Don't worry, we won't flood your inbox with a wave of cosmic debris.

BugHerd Logo

How To Write Test Cases [Excel, Jira, And More]

Test new software or code before pushing it live. learn how to write test cases that ensure user success and complete functionality..

author profile image

BugHerd Dev

December 5, 2022

how-to-write-test-cases

From broken links to missing images, there’s no doubt about it: a janky website isn’t good for business.

Each test needs to be documented, but first explained, which is done in the form of a test case.

This article will explain how to write a test case in various common scenarios. 

  • What Is A Test Case

The 9 Basic Steps Of Writing A Test Case

Test case templates, tips for writing good test cases, what is a test case.

A test case is a list of instructions for specific actions to ensure the website functions as expected.

Its purpose is to provide direction to software testing engineers to verify that each website component is bug-free. 

One website design could require hundreds of test cases. These test cases are grouped and organized in what is considered the test suite as part of the overall test plan.

Typically, designers can create test cases. But if the test case design is complex, testing engineers may also be involved in test case writing.

Functional testing has three different types of test cases, and their differences concern input versus outcome. 

Positive Test Case

A positive test case is when the inputs produce a positive outcome. 

For example, when testing login functionality, a positive test case would result in the arrival of the welcome page when clicking on the login button and entering the correct credentials.

Negative Test Case

In a negative test case, the purpose is to test the results of a negative outcome.

For the same example, a negative test case would involve the user experience clicking on the login button and entering the wrong credentials.

This negative test case will be successful if the wrong credentials result in a notification that the password was entered incorrectly. 

Destructive Test Case

Destructive test cases are meant to test how much load a webpage can handle. 

Destructive tests may include applying a heavier load than normal, fast-clicking, or implying malicious intent. 

There are nine basic steps to writing a complete test case. With these elements in place, test execution should always be possible from the written test case. 

1. Test Case ID

A unique ID should be created for each test case. 

These IDs should follow a numerical or alphabetical pattern for less confusion in identifying individual cases. 

2. Test Description

The test description outlines what is being tested and how that will be verified.

A common sentence structure for the test description is as follows:

“Verify ‘function’ by ‘action’ with ‘another action.’”

i.e., verify authentication by using a correct password in Gmail. 

3. Preconditions

Preconditions (or prerequisites) are conditions that need to be met before testing can begin.

Without these in place, test coverage will be invalid.

4. Test Data

Test data is any input or data necessary to perform the test. These could include the login and password, test script, or exact URL.

5. Steps To Be Executed

These steps from the end user’s perspective will need to be followed to verify the end goal.

They must be written clearly and concisely for the testing team to understand. Using a traceability matrix can ensure that every condition and function is tested.

6. Expected Results

The expected result is what should happen with a bug-free website if all the steps in the test case are followed.

7. Postconditions

A postcondition is something that should happen as a result of a successful test outcome.

For example, if your expected result of inputting your username and password into the login page is to gain admittance to the home page, a postcondition is to have the home page load. 

8. Actual Result

Did the test case result in the expected results?

If not, what was the result?

This is the actual result, which may or may not differ from the expected results.

9. Pass/Fail

steps-for-writing-test-cases

If the expected results were met, the test passed. If not, it failed.

What if a test fails?

Time for a bug report!

The bug lifecycle will need to be followed and corrected. Then regression testing must be conducted. 

Read more: Bug Reporting: What Is A Bug Report And How To Create Good Bug Reports

Would you like to see some test case examples?

Take a look at some of these templates using test case management tools and programs to see how you can structure your next test case. 

Google Sheets

By using Google Sheets, you’ll have a dynamic hub for a test case.

The key advantage here is that if you have multiple people working on this project, you can give them edit access too to make changes or add their own notes.

Check out the template made by BugHerd just for you!

Microsoft Excel

Using an excel spreadsheet is old school but still viable for standard test cases.

You can fill the spreadsheet horizontally or vertically to fit the format that best suits your preferences. 

You can see an example of a horizontal spreadsheet test case here . 

There are several more downloadable excel spreadsheets for test cases here .

There are no set presets for test cases in Jira, but you can use the “issue type” feature and customize it for test cases.

To complete the test case, add subtasks that correlate to the nine steps for test cases.

Or, use Zapier to connect your BugHerd bugs to Jira. 

Read more: Combine BugHerd With Jira For The Ultimate Bug Tracking Tool

You can use Trello as a management tool by following the test steps laid out below: 

  • Create a workspace.
  • Create a board.
  • Make your board workspace visible to allow testers to use the board.
  • Change the list names for each website or software application you are testing.
  • Create cards for each function you write a test case for.
  • Assign these cards a test ID and description, and attach the test data.
  • Add a checklist to the card as the steps to follow.
  • You can create different checklists for positive, negative, and destructive test cases.
  • Testers can check off the steps as they go.

Or, like with Jira, you can connect BugHerd to Trello using Zapier . 

monday.com is another great task management tool that can be used to create test cases. They have the process outlined on their blog here , along with a free template to use. 

You can also connect BugHerd to monday.com to make test case creation super convenient.

Well-written test cases can make the testing process more efficient and accurate. 

Here are some tips to follow when writing test cases:

Use Testing Techniques

There are several different testing techniques available to use. Of course, you can’t expect to use every technique in your testing process.

However, selecting the technique that will provide the greatest possibility of detecting bugs is best.

The testing of one website may employ several different testing techniques in its testing execution. 

Some of the most popular testing techniques include:

Equivalence Partitioning

With this technique , you divide the test cases into groups. These groups should all work under one condition.

Then if one test case works under that condition, all in the group should also work. 

State Transition Testing

This technique is used when previous actions may dictate the transition from one input to the next. 

Boundary Value Analysis

With boundary value analysis (BVA), a specific range of values is used to test the website function. 

For example, for a website about beer, you would want to test a prompt asking for the user’s age. 

The minimum acceptable value for admittance to the site is 21. BVA would be the correct testing technique to put in place for this function. 

Error Guessing Technique

Error guessing doesn’t follow any rules, but instead uses the tester’s prior experience with the website to test scenarios at random. 

What kind of random situations would a software tester think of testing?

How about entering alphabetical values into a numerical field, or submitting an email signup form without entering a valid email address?

Implementing this technique may require creativity, but it certainly aids in ensuring complete test coverage. 

Decision Table Technique

The decision table technique follows the cause-and-effect pattern for functions with relationships between inputs. 

To use this technique , testers would create a table with conditions or actions followed by columns for each test case. After testing the conditions, testers would mark the columns accordingly.

Keep End-User Perspective

The user is who you are testing for, so it only makes sense to write test cases with the end user in mind. 

Whether testing for functionality or compatibility, user experience is always key to ensuring your website is well-designed. Go through all your test cases and consider the practical value they provide to the end user. 

Use Clear And Concise Language Throughout

Effective test cases cannot be vague in any manner. Clear and concise language must be used throughout the test case.

This includes the test description and expectations. It is especially important when writing out the steps to follow. 

Test cases need to be written without assuming testers have background knowledge. Even new testers should be able to execute the test from the steps in the test case.

Make Sure It Is Reusable

When any updates are done on your website or any of the coding is changed, the testing process will need to be repeated.

For that reason, it is always a good idea to make your test cases reusable. 

Always keep a master copy and then make a duplicate for use to perform the test. 

That way, you can simply make another duplicate for your next update or even use it for a new website project in the future. 

Also, remember that test cases will need many revisions and updates, as website requirements are always changing. 

Get Peer Review

Before issuing a test case, allow others to read it. They may catch things you missed or offer some advice on clarity or word usage. 

Getting a peer to review your test case is one of the best forms of quality assurance.

Make Sure They’re Self-Cleaning

While conducting the test cases, no permanent change should be made to the test environment. Testers should be able to return to the pre-test state after completing the test.

Stick To Specification Documents

When writing test cases, do not assume any functions of the website. Instead, use the specification documents to dictate the parameters of your test case. 

The role of testing in website design cannot be overemphasized. If a company rolls out a website with insufficient testing, the results could be catastrophic for their consumer relations. 

Good test cases are to ensure your website is bug-free and works as the user expects.

BugHerd’s bug tracking tool can simplify testing execution by integrating with just about any test management tool out there and enabling a point-and-click process that is far simpler than any other method.

Try it out for free with our  14-day trial .

Recent articles

Bugherd makes g2's top 25 anz software companies for 2024.

G2 award

Marina Domoney

link arrow white

4 months in 4 minutes - What's new in BugHerd?

image of the BugHerd team

Merrin Hughes

11 Best Bug Tracking Tools: Features, Integrations, Pricing, and What Dev Teams Love About Them

Two software engineers working in front of a computer monitor

19 Chrome Extensions for Web Developers: Streamline Your Debugging and Testing

Two office workers facing each other with computer monitors between them.

11 Chrome Extensions for Web Designers: Tools You Didn't Think You Needed

Male working in front of two computer monitors

Best Screen Recording Software Options in 2023: The Ultimate Guide to Choosing the Best Screen Recording Tool

Man in Dark Crew Neck T-shirt Wearing Black Headphones Talking into Microphone Sitting in a Workspace Home Office

Want more resources like these? Subscribe to the BugHerd Blog. 📥

how to write a test case in jira

What is BugHerd?

BugHerd is the best tool to collect, organise and act on website feedback. It's bug tracking software that's like sticky-notes on a webpage.

how to write a test case in jira

logo

  • All COURSES
  • CORPORATE Skill Flex Simulation Agile Implementation SAFe Implementation

call-back1

Register Now and Experience Scrum in Action! Learn, Implement and Succeed.

diwaliDesktop

Fill in the details to take one step closer to your goal

Tell Us Your Preferred Starting Date

  • Advanced Certified Scrum Master
  • Agile Scrum Master Certification
  • Certified Scrum Master
  • Certified Scrum Product Owner
  • ICP Agile Certified Coaching
  • JIRA Administration
  • view All Courses

Master Program

  • Agile Master’s Program

Governing Bodies

ICagile

  • Artificial Intelligence Course
  • Data Science Course
  • Data Science with Python
  • Data Science with R
  • Deep Learning Course
  • Machine Learning
  • SAS Certification

how to write a test case in jira

  • Automation Testing Course with Placement
  • Selenium Certification Training
  • AWS Solution Architect Associate
  • DevOps Certification Training
  • DevOps With Guaranteed Interviews*
  • Dockers Certification
  • Jenkins Certification
  • Kubernetes Certification
  • Cloud Architect Master’s Program
  • Big Data Hadoop Course
  • Hadoop Administrator Course
  • Certified Associate in Project Management
  • Certified Business Analyst Professional
  • MS Project Certification
  • PgMP Certification
  • PMI RMP Certification Training
  • PMP® Certification
  • PMP Plus Master's Program

how to write a test case in jira

  • Full Stack Developer Certification Training Course
  • Lean Six Sigma Black Belt
  • Lean Six Sigma Green Belt
  • Lean Six Sigma Master’s Program
  • Pay After Placement Courses
  • Scrum Master Interview Preparation Bootcamp

how to write a test case in jira

3 Essential Steps for Creating How To Write Test Cases in Jira

calender

Table of Content :

How to write test cases in Jira 

Top 3 steps on how to write test cases in jira, how to view the test cases and results – important lesson in jira learning.

  • Expert tips to make your test case in Jira work perfectly fine 

How Jira training course helps in test management in Jira 

Conclusion .

When the how and what of the testing process are covered means a good test case is built as it makes testing organized suitable for all future updates as well. Agile methodology widely uses Jira software and hence one needs to know the steps involved in writing test cases in Jira. Also, one must be aware of the right way to create a test case with Jira to include all the necessary essentials with the obvious questions.  Jira is a project management tool that was initially designed as an issue and bug tracker. However, currently, it is used for use cases as well as test case management.  The Jira training course covers in detail all the steps involved in using the tool. In this section, we will specifically cover the steps involved in preparing the test cases in Jira. Also, we will provide some tips to make the best use of Jira in your project. 

Jira allows different options in the configuration. But one must know the right steps to customize the workflow. Otherwise, it will become difficult to handle the numerous features in a precise way. Let us walk you through the 3 simple steps now. 

1. Create User login  and create projects 

Log in as a user with global admin permission which will let you configure

• Custom fields

• Screens and 

• Jira schemas

Followed by this create the project-specific to writing test cases in Jira.

2. Jira configuration for handling test cases 

Include a fresh issue type ahead of including the test case as an issue. 

  • Then include custom fields for defining the inputs needed in the test case. 
  • Allocate a custom screen for adding these custom fields along with a screen schema to be associated with the screen. 
  • Keep updating the screen schema with the project uses. 
  • Now include the type of the test case and generate test cases. 

3. Jira configuration for accepting the test results of the created test cases 

• Make a custom field for recording the results and then make a screen 

• Follow the above action by a schema for the results

• At the end construct the issue type for adding the test case results

  •  Select all issues to view everything at a time 
  •  Choose list view to navigate easily 
  •  Make use of the filter to take a look at the test cases you created 

1. Difficulties in writing test cases in Jira 

  •  As mentioned earlier Jira was not designed as a test management tool and hence it consumes a lot of time to customize it for entering the test cases.
  • The delay in entering and viewing test cases reduces the productivity of the entire process 
  • Reporting has its limitations that include difficulty in tracking the number of times the test has been run or the times the test failed. 

2. An example test case in Jira 

  • Click create a button on the main page 
  •  Select a project 
  • Select test option from issue type 
  •  Enter the summary, description, assignee, priority, environment under the general tab 
  • Then enter the test details like test type, test steps 
  • Then in the test plan tab, select the test plan and link the test 
  •  Now the test is created and is under To Do
  •  Run the test and write a comment in every step attaching evidence 
  • Finally flag them as pass or fail and press defect to create a bug  

Expert tips to make your test case in Jira work perfectly fine  

Follow these expert tips to write test cases in Jira for maximizing its efficiency. 

1. Test Case issue creation and keeping it open In general, issues marked as done in Jira cannot be tested or used again. Therefore: make sure not to mark done on the issue but leave it open. This will allow you to make changes in the future. Make sure to write test cases in Jira in this way to use it again. 

2. User story tweaked as a test case Jira does not have a built-in testing function and hence you must tweak the user story as a test case for best results. 

3. Inclusion of testing status to the workflow  Remember that completing the test is not considered as done and hence you must manually mention the status of testing in the workflow.

4. Testing process automated  Use the same test case for different types of testing as automation will reduce the time and the resources allocated to manage all the tests. 

5. Tools integration  Integrate all the tools used by the team during the entire workflow to have control over the process. 

6. Project component creations  It is possible to include subsections to each project in Jira and thus you can create components to simplify the reporting process, statistics generation, and data displaying. 

how to write a test case in jira

Training Course

2 Days of live virtual training

The challenges mentioned above about writing test cases in Jira are well understood and hence the training module, will explain the correct way to use Zephyr in Jira test management. You can learn to integrate testing in the project life cycle and hence it becomes easy to write test cases, clone them, search test cases, export, and execute test cases. 

From this article, we are sure you got some idea about the tool Jira and the right way to create test cases in Jira. However, we strongly recommend you to enroll in the Jira certification course to deep dive into all the detailed usage of Jira.

Trending Now

Scrum master certification cost.

calender

Benefits of Scaled Agile Framework

Scrum master certification levels, scrum master salary - freshers & experienced[2024], top 100+ scrum master interview questions and answers in 2024, upcoming jira tool training workshops:, keep reading about.

Card image cap

CSM Certification vs CSPO Certification

calender

Overview of PMI-ACP Certification

Card image cap

Do We Need an Agile Coach

Related articles.

  • Data Science for Marketing
  • CSPO Renewal
  • What are the 5 Scrum Ceremonies
  • Python Devops Examples
  • Pmi-Acp Exam Prep

Find JIRA in India cities

  • JIRA Hyderabad
  • JIRA Bangalore
  • JIRA Mumbai
  • JIRA Chennai

We have successfully served:

professionals trained

sucess rate

>4.5 ratings in Google

Drop a Query

Ask a question

Start a discussion.

  • Jira Jira Software
  • Jira Service Desk Jira Service Management
  • Jira Work Management
  • Confluence Confluence
  • Trello Trello

Community resources

  • Announcements
  • Technical support
  • Documentation

Atlassian Community Events

  • Atlassian University
  • groups-icon Welcome Center
  • groups-icon Featured Groups
  • groups-icon Product Groups
  • groups-icon Regional Groups
  • groups-icon Industry Groups
  • groups-icon Community Groups
  • Learning Paths
  • Certifications
  • Courses by Product

Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar

Level 1: Seed

25 / 150 points

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

questions

Get product advice from experts

groups

Join a community group

learning

Advance your career with learning paths

kudos

Earn badges and rewards

events

Connect and share ideas at events

  • Atlassian Automation
  • Navigating Test Execution Workflows: A Beginner's Guide to Jira Automation Rules

Navigating Test Execution Workflows: A Beginner's Guide to Jira Automation Rules

image-20240208-195911.png

Was this helpful?

Heather Ronnebeck

Heather Ronnebeck

About this author

Project Manager | Atlassian Admin

Work Wranglers

Winnipeg, MB

27 accepted answers

181 total posts

  • +22 more...
  • addon-com.xpandit.plugins.xray
  • atlassian-marketplace
  • jira-software-server
  • quality-assurance
  • test-management
  • Community Guidelines
  • Privacy policy
  • Notice at Collection
  • Terms of use
  • © 2024 Atlassian

IMAGES

  1. How To Write Test Cases In Jira

    how to write a test case in jira

  2. How to Write Test Cases in Jira

    how to write a test case in jira

  3. 4 best practices of Jira test case management

    how to write a test case in jira

  4. Test Case Creation in JIRA. Best Practices

    how to write a test case in jira

  5. How to Write & Manage Test Cases in Jira

    how to write a test case in jira

  6. How To Write Test Cases In Jira

    how to write a test case in jira

VIDEO

  1. How To Write Test Cases For Gmail In Telugu😍

  2. How to Write Test Cases For Facebook Profile and Notification In Telugu😍| Software Testing in Telugu

  3. Test Execution and Test Plan in XRAY

  4. How to write Test case in Zephyr Scale (JIRA)

  5. How to Write Test Cases in Manual Testing

  6. How to write Test Case Report in Bangla? Test Case Report বাংলায় কিভাবে লিখবেন?

COMMENTS

  1. Best Practices to Write and Manage Test Cases in Jira

    a] Configure Your Jira Workflow This will require some time-consuming configurations of the Jira interface and what you need to do is configure the workflow such that the workflow does not mark itself as 'Done' before you're actually done with the process. b] Choose to Create a 'Test Case' Issue Type

  2. How to Write Test Cases in Jira

    1. Set up Jira for case testing 2. Create test cases in Jira 3. Report on test cases in Jira Wrapping up... When you're building complex web applications, QA testing can turn into a nightmare. There are so many flows and components to test — login flows, sign-up flow, payment flow, invite flow ... and a million more.

  3. How to Write & Manage Test Cases in Jira

    Are you wondering about the best ways to write and manage test cases in Jira? In this guide we will look at the three most popular options on how to write your test cases in Jira. You can then decide on the best option for your team & your projects and start writing your test cases with Jira.

  4. How To Write Test Cases In Jira

    A step-by-step guide on how to write test cases in Jira, a popular tool for software testing and bug tracking. Learn how to configure Jira to handle test cases and their results, and how to view them by release. Also, discover the advantages and disadvantages of using Jira as a test case management tool.

  5. How to Write and Manage Test Cases for Jira?

    Step 1. Create a Test Case Issue and Keep It Active Step 2. Change a User Story to Be a Test Case Step 3. Add a Testing as a Status in Jira Workflow Report on Test Cases in Jira Dedicated Test Case Management Tool with Jira Integration Problems with Writing Test Cases in Jira Advantages of using Jira for Test Case Management

  6. How to create and manage test cases in Jira and BrowserStack Test

    Click on Settings icon >> Apps >> click on BrowserStack from Apps section. Next you need to authorise the BrowserStack app to access Jira. Click on the Allow Access button. This will redirect to another tab, click on the Accept button. Add the BrowserStack API key from the API key page and save the configuration.

  7. JIRA Tutorial #11

    Share 111K views 3 years ago JIRA TUTORIAL - Jira Course for Development Teams - FULL COURSE 🔸FREE Training's at https://training.rcvacademy.com 🔔SUBSCRIBE to CHANNEL: https://bit.ly/38hDaww...

  8. How To Write A Test Case In Jira

    Open your project and click on "Create". Click on "Issue type" and click on "Test Case". 💡 You can create your own issue type. Add your "Summary" which should highlight your goal. In your description, add your Preconditions, Test Steps, Expected Result (Objective), and Actual Result and click on "Create".

  9. How to write Test Cases in Jira?

    To write test cases in JIRA, one can follow the following steps: Select the 'Create Issue' option. Click on any Project. Select 'Test' in the 'Issue type' option. Enter 'Summary' for the test case. Finally, Select the 'Create' button. Configuring Jira to Accept Test Results for Your Cases (with steps)

  10. How To Use Jira For Test Case Management

    The first one is to write the tests directly in Jira by creating a new issue type for test cases. The second is to use a test case management tool integrated with Jira. Of course, both methods above have their own advantages and disadvantages.

  11. A Guide To Using Jira For Test Case Management

    A Guide To Using Jira For Test Case Management Get a complete rundown on using Jira for test case management, including how to customize Jira for testing with Tricentis.

  12. Five best practices for managing test cases in Jira

    4. Ensure traceability. Tracing a test case from start to go-live is a critical part of any 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 nothing is missed between teams. 5.

  13. How to create and manage test cases with Xray and Jira

    Learn how to write, specify, organize, and execute test cases with Xray and Jira, a testing tool that supports different test types and phases. Follow the step-by-step instructions on how to create test issues, test sets, test plans, and test executions using Xray and Jira.

  14. How To Write and Execute a Test Case in 5 Minutes

    Step 1: Define Requirements We begin creating a test case by establishing its requirements. AgileTest simplifies this process with a repository section where users can track each feature, resolving the version control issues common in document-based methods. Step 2: Create Test Case

  15. How To Write Test Cases in Jira

    On the main page, click on the Create Button. Select the test option from the issue type. Under the general tab, enter the summary, description, assignee, priority, and environment. Then provide the test specifics, such as test type and test steps. Then, on the test plan tab, select the test plan and link it.

  16. 7 ways to structure requirements and test cases in Jira

    Performance Testing - verifies the final speed and effectiveness of the product. Managing test cases in Jira with RTM per testing level defines the order of their execution, and organizing per testing type sends a clear message to Jira users about what to focus on in each category. 7. Structure by software version.

  17. How to use Jira as a test management tool

    Product requirements First, you'll need a place to create and update product requirements, which serve as the basis for quality applications and, therefore, guide tests. Regardless of the development methodology, organizations must document desired outcomes for software.

  18. Tips for Creating Test Management for Jira

    Jira test case management is possible, though not ideal. But there are some hacks you can use to make Jira work for managing test cases — creating a "test case" issue, tweaking a user story to be a test case, and adding a testing status to your workflow. Steps for Writing Test Cases in Jira. Here are some potential steps you can take to make ...

  19. How To Write Test Cases [Excel, Jira, And More]

    / Blog / How To Write Test Cases [Excel, Jira, And More] How To Write Test Cases [Excel, Jira, And More] Test new software or code before pushing it live. Learn how to write test cases that ensure user success and complete functionality. BugHerd Dev | December 5, 2022

  20. 3 Essential Steps for Creating How To Write Test Cases in Jira

    1. Create User login and create projects Log in as a user with global admin permission which will let you configure • Custom fields • Screens and • Jira schemas Followed by this create the project-specific to writing test cases in Jira. 2. Jira configuration for handling test cases

  21. JIRA Tutorial #17

    Subscribed 240 Share 34K views 3 years ago JIRA TUTORIAL - Jira Course for Development Teams - FULL COURSE In this JIRA Tutorial we will learn how to execute test cases in Jira. We will be...

  22. How to Write Test Cases: A Step-by-Step QA Guide

    Capitalizing the first letter of the email address Test scenarios, also called test conditions or test possibilities, represent typical tasks users might want to accomplish with the software. A simple test scenario may require multiple test cases to cover the different outcomes.

  23. How to create (write) a test case in AIO Tests in Jira

    This video demonstrate how to create or write a test case in AIO TestsFind out more about AIO Tests (All-in-one Test Management for Jira): https://aiojiraapp...

  24. Streamlining Test Execution: Jira Automation & Xray Guide

    The Use Case: Automating Test Execution Creation in Xray. Use Case: Automatically Creating Test Executions with Tests assigned via Xray, based on a Story ticket that already had tests linked to it using Issue Linking. Products Used: Jira Software. Xray Plugin. Jira Automation. Additional Items Used: Xray API Documentation. Jira API Documentation