View all products
Project and issue tracking
Jira Service Management
Visual project management
New products from Point A
Innovations from Atlassian
Developer experience platform
Connect thousands of apps for all your Atlassian products
Browse by solution
Agile & devops.
Run a world-class agile software organization from discovery to delivery and operations
IT Service Management
Enable dev, IT ops, and business teams to deliver great service at high velocity
Empower autonomous teams without losing organizational alignment
Browse by team type
Small business, by team size.
Great for startups, from incubator to IPO
Get the right tools for your growing business
Learn how we make big teams successful
By team function
Plan, build, & ship quality products
Bring together a winning strategy
Streamline people management
Operate securely and reliably
Efficient, secure, mission focused
Run your business efficiently
Provide great service and support
Simplify all finance processes
Respond, resolve, & learn from incidents
Apps that enhance Atlassian products
Docs and resources to build Atlassian apps
Trust & security
Compliance, privacy, platform roadmap, and more
Work Life blog
Stories on culture, tech, teams, and tips
Guides to all of our products
Atlassian Migration Program
Tools and guidance for migrating
Upcoming feature releases
Purchasing & licensing
FAQs about our policies
Personal support for large teams
Trusted third-party consultants
A resource hub for teams and admins
Learn & connect
Our mission and history
Job openings, values, and more
Training and certifications for all skill levels
A forum for connecting, sharing, and learning
How to create and manage test cases with xray and jira.
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.
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:
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.
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.
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.
Step 3 : Type the name for the folder on the create folder dialog.
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 .
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.
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 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
Bookmark these resources to learn about types of DevOps teams, or for ongoing updates about DevOps at Atlassian.
DevOps learning path
Get started for free
Sign up for our devops newsletter.
Thank you for signing up
How to Write Test Cases in Jira
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 .
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!
12 Best WordPress Plugins for Developers in 2023
8 voice of the customer (voc) templates & examples, 21 best chrome extensions for web developers in 2023, 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
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
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.
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.
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.
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
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 .
Start testing with Testmo for free today
- Test Management
- Terms of Service
- 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
Subscribe Subscribe to updates
- Get started
- Create a company-managed project
- Jira permissions
- Supported fields
- Issue Types
- Tree Structure
- Migration to Cloud
- RTM Process
- User's guide
- Project view
- Impact analysis
- Create Requirement
- Bulk linking
- Export Test Case
- Create Test Plan
- Manage Test Plan
- Execute Test Plan
- Execute Test Case
- Create Defect
- Requirement Coverage
- Test Case Execution
- Test Execution
- Jira REST API
- Example of use
- Jira automation
Create a Test Case
This chapter provides information about creating Test Cases.
- Test Cases can be created as regular Jira issues in Create Issue dialog box. You can also add Test Case by clicking on + in particular folder in the Test Case tree.
- If you haven’t created any new folder yet, go to All .
To create a Test Case navigate to Project > Test Management > Test Cases . Click + .
In the Details section, complete all fields added to the screen:
- Select folder
- RTM Environment
- Fix Version
There are three ways to add steps to your Test Case:
- Create group of steps , where you can create your own step’s procedure
- Link from other TC , where you can copy group of steps from other Test Case
Fill in the Preconditions field if your Test Case requires an additional condition before running the procedure.
Create a group of steps
Right after clicking +Create a group of steps , a Default group with first step is added. Now you can:
- Change step’s group name
Use the text tools to diversify your text.
- Copy group of steps
- Add Attachment. Info Each step can have own attachments. Attachments can be added after creating an issue. Info Use drag and drop to reorder the steps or group of steps.
Use existing steps and implement them to your Test Case with Link steps and Import from CSV buttons.
Link from other TC
You don’t have to rewrite Test Case’s steps. Use existing steps from other Test Case and copy them to your new TC:
- Click Link from other TC . A drawer displays.
- Choose Test Case where target steps are stored.
- Select groups of steps.
As a result, steps from other TC are copied to your Test Case.
Import from CSV
Click Import from CSV and choose a .csv file with steps.
Steps add automatically.
Sample file to import can be found here . The file contains three Steps, with columns named Action , Input , Expected result . Each step is located in a separate group.
Open Test Case’s Requirements tab. There are two ways to add Requirements to your Test Case:
- by adding Requirements, that already exist
- by creating new requirements
Create New Requirement
As soon as you click Create New Requirement , you will be transferred to Requirements tab.
For further information, navigate to Create Requirement chapter.
Confirm Test Case creation
- 5 best practicies for creating transparent test cases
If you can’t find the answer you need in our documentation, raise a support request *. * Include as much information as possible to help our support team resolve your issue faster.
ON THIS PAGE
Version Control in Virtual Production Field Guide
Tips on Creating Test Management for Jira
By Nico Krüger
Your company needs to deliver the best software possible. And to do that, you need to test, test, and test some more.
But many organizations lack the tools to manage testing properly. This is a particularly common issue for those who use Jira to track issues throughout the development process.
That’s because Jira doesn’t have built-in testing functionality. So, for organizations who haven’t added testing tools, test cases are managed manually.
And that’s a big problem.
🖥 Need to host your issues and test management on-prem? Read the blog 👉🏽 On-Premise Jira
How to Use Jira for Test Case Management
Jira test 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.
Quick Tips for Writing Test Cases in Jira
Step 1. create a “test case” issue — and keep it open..
But Jira issues are meant to be pushed to done. That makes it challenging to rerun or reuse tests. Plus, it’s hard to keep track of all of your testing if you’re managing test cases as Jira issues. Trying to create test coverage reports from disparate sources will be difficult.
Step 2. Tweak a User Story to Be a Test Case.
Jira user stories have the same problems that Jira issues have. So, you’ll still have a challenge if you want to reuse tests. That’s made all the more difficult by the fact that Jira doesn’t have built-in testing functionality.
Step 3. Add a “Testing” Status to Your Jira Workflow.
But you might find yourself moving to a “done” status before you’re actually done with that test. After all, completing a test is not the same as being done with a test.
You could configure a workflow, so a test isn’t “done” before you’re actually done. But that will add more steps to an already manual process.
When Writing Jira Test Cases Does not Work
If you want to write test cases and manage them in Jira, these workarounds will help you in a pinch. But Jira wasn’t designed to create test cases. And it’s still a pretty manual process to get Jira to support test case management.
So, using workarounds for testing in Jira won’t solve your problems. It will still take manual effort (and your valuable time) to manage your testing efforts.
👉🏼 Explore easier options. Out-of-the-box Jira integration for test case management. Try it out free. See how the integration works
How to Add Test Management to Jira
Testing is an essential part of software development. For organizations practicing Agile development, continuous testing is the best way to provide a good experience for users — while pushing product development forward.
Whether you’re Agile or not, every test you run is important. And you need a way to track the results of your tests and manage data from both manual and automated tests.
Jira helps development stay on track when it comes to managing issues. But when you get to testing and QA, you get stuck. Jira doesn’t have the built-in testing functionality you need to effectively manage test cases.
So, your processes become manual. And that makes it difficult to get visibility over the development process and match issues up with test cases.
Adding test case management to Jira will help you keep your software development cycle running smoothly.
Find the best test management tool for Jira >
How to Write Better Test Cases (and Keep Using Jira ).
1. automate your testing processes.
Many organizations are using a combination of manually maintained documents, spreadsheets, and Jira add-ons to get by with software testing. But these methods are time-consuming and exhausting. They don’t easily lend themselves to reuse.
Remember: you don’t always need to create new test cases. One of the best ways to gain efficiency in your testing process is to use the same test case for many types of testing .
Reusing tests and test cases reduces manual effort. And adding automated testing tools can help you do more testing faster. You can set up a test, and schedule it to run again — and again.
By automating manual processes, you’ll free your team up to focus on the important stuff — the tests and their results.
2. Integrate Your Tools
Integration should be a top priority. And that means both integration with Jira (if you want to keep using Jira for bug tracking ) and integration within the testing process.
You need to be able to link QA tracking, testing, and testing data for analysis. This makes it easy for your team to get insight into what tests have been run — and whether or not those tests passed. And, if you’re integrating testing with Jira, it makes it easy to map which tests detected or resolved which issues.
Integrated testing helps you maximize efficiency and produce quality products faster.
3. Use Traceability
Testing doesn’t happen in a bubble. It’s an integral part of the software development lifecycle, and it needs to be connected with requirements and issues. That’s hard to do when you’re tracking bugs in Jira, requirements in a Word document, and test cases in Excel spreadsheets.
That’s why traceability — the ability to trace your test cases to a requirement or issue — is important.
It’s much better to rest assured that the necessary tests have been run before going to production.
You’ll have a problem if you don’t have test cases, or records of passed tests (and success rates or bugs found). That’s because if a bug shows up in production, you need to be able to answer when the last time that component was tested. If you can’t, you’re toast.
Jira Test Case Management Doesn't Work Alone
Writing test cases in Jira doesn't work.
If you want to:
- Write better test cases
- Get visibility over testing
- Add traceability to Jira
Then it's time to find a Jira alternative — such as Helix ALM .
Helix ALM makes it easy to create test cases and manage tests. It integrates with Jira out of the box. And it can be hosted in the cloud or on-premise. So you can keep tracking bugs in Jira. Try Helix ALM — and see how your test cases will be more effective.
Write a Test Case in Helix ALM
Former Director of Global Sales Engineering, Perforce Software, Perforce Software
Nico Krüger is the former Director of Global Sales Engineering at Perforce. He specializes in technical guidance and product development efficiency for global organizations. An expert in software development, he is dedicated to helping customers drive quality product strategy.
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
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)
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
3. To view just your test cases, choose the 'Type' filter, and then filter by 'Test Case.' 4. Similarly, if you
JIRA : A Complete Tutorial for Beginners || JIRA Agile Test Management · JIRA Tutorial #17 - How to Execute Test Cases in JIRA · How To Write TEST
[email protected] How to write test cases in JIRA? JIRA Tutorials | ITlearn360 Learn about how to add test cases in JIRA for software
jira #jiratutorial #jiratestcase #jiradashboard #testcase #testingwithjiraIn our last video https://www.youtube.com/watch?v=-Jgp1N6jtBQ
Navigate to Project > Test Management > Test Plans. · Click +. · In the Details section, complete all fields added to the screen. Jira Test Plan
Test Cases can be created as regular Jira issues in Create Issue dialog box. You can also add Test Case by clicking on + in particular folder in
Quick Tips for Writing Test Cases in Jira · Step 1. Create a “Test Case” Issue — and Keep It Open. · Step 2. Tweak a User Story to Be a Test Case.