How to map requirements to test cases in jira

How to map requirements to test cases in jira

Test planning

Want to know how to map requirements to test cases in jira? Before we jump into showing you all these “new new” AI-driven continuous test automation things in Vitaq (https://vitaq.io/2020/11/01/why-vitaq-ai-and-why-now/). We first need to talk about test planning. Failing to plan is planning to fail. So let’s begin with success in mind and take a look at how we approach test requirement planning.

There are many ways to gather our web or mobile applications test requirements into a test plan. We typically take our story board and break it down into user stories and then into detailed user-journey definitions. One of the most common ways to capture this is to document them directly into Jira. Let’s look at how to map requirements to test cases in jira for our example project :-

Test requirements

1) Start with our Product Requirements which needs to be tested.

As mentioned in the earlier Blog (https://vitaq.io/2020/11/01/selenium-automation-practice-site/). We have chosen to use the AutomationPractice.com application site for our example project because it is representative of many e-commerce websites.

For this example project we have identified many test requirements which include searching for a product, adding it to cart and completing the payment process.

2) Communication of key features.

Our Test Cases need to communicate the key features of the application under test. (http://automationpractice.com/index.php)

In our example project, one of the key features is to purchase items successfully. To do this the user needs to go from the registration of a user to the payment of an item. This is one test case out of many such cases.

3) Outline goals, business objectives, and strategic fit.

The team goals and business objectives section are meant to give you a chance to add some color and context to your requirement.

A good way to think about your goals is from your customer’s perspective (i.e. your app users). What exactly are they trying to achieve? How does the solution you’re proposing fit into it?

4) Creation of User Stories.

When all of the requirements of what to test are clearly agreed by all the team we now need to turn this into a story board that captures the User Story’s in the best possible way. See below how we have created this in Jira (https://www.atlassian.com/software/jira) and then mapped it to our test requirements.

how to map requirements to test cases in jira

In the above screenshot, you can see some examples of our User Stories.

User Stories

Let’s walk you through how we created these user story’s one by one:-

1) If We need user registration of 10 Users on AutomationPractice.com

Then we can simply create user story such as:- User Registration for 10 Users on AutomationPractice.com

2) If we want a user without login to be able to place an order on AutomationPractice.com

Then we create a user story: Verify As a Guest User, A User should be able to search T-shirt in Search Box and proceed to Checkout Page

3) If we want a user to be able to subscribe to our newsletter on AutomationPractice.com to get information about the latest products.

So we create a user story: Verify User should be able to Subscribe to the WebSite Newsletter.

4) If we want that a Registered user to be able to order an Item through completing the payment of that item.

Finally we can simply create a user story: Verify as a Registered User, A user should be able to search Printed Dress in Search Box and able to Add it into his shopping cart and complete the payment process.

So now toy can see how easy it is to create many more user stories like this on Jira by mapping the test requirements to user stories.