Test Case Management using JIRA Customization - Version 2.0

In the last Post we have seen how we can do Test Management by creating a Custom field "Test Status at Build". But due to change in requirements I tried another approach.

 Now go to Issues page from JIRA Administration->Issues as shown in below picture

Then Add Issue Type like below

Now go to Issue Type Schema and associate it with some Issue Type Schema

Now go to Workflows and Import from Marketplace a new Workflow called "Test Case Management Workflow" 

Assign this workflow to Workflow Scheme at Workflow Schemes and Assign "Test Case" issue type to this Workflow Scheme

Add a new Screen 

Now Add a New Screen Scheme

Associate Issue Type with a Screen Scheme

Create following Custom Fields and associate with Screens

Project/Component/Story

• In JIRA Project will be top level entity
• Every Project will be having several Components
• Stories will be created per Project and will be associated with one or more Components

New IssueType called Test Case added into JIRA with CFs 

Requirement Traceability

Test Case should be linked to Requirement

 This allows Requirement Traceability

Test Cases for Different Platforms(OS)

Test Cases for Different Platforms(OS)

• Create Test Case for a Platform and upon review Clone them if Test Steps are same for all the Platforms
• Create Different Test Cases for different Platforms if they are platform dependent Test Cases
• Link a Test Case of different Environments

Test cycle creation

Clone Regression Tests from Previous Test Cycle

• Get All Test Cases from Test Case Repository which are not invalid
• Clone them
• Change the Test Cycle and Assign them

Assign Test Cases for Execution - Using JQL and Bulk Upload

Test case assignment for automation

• Change Automation Status as “To be Automated” in Test Case
• Create a Sub-Task for Test Case
• Add to appropriate Test Cycle
• Assign it to a QA Engineer

Test cycle execution assignments

Automation assignments

User Dashboard

Test Execution

Automation Activity

• QA Engineer looks at User Dashboard for Automation Activities

• QA Engineer will put it in Progress
• Complete it and mark it as Done
• Change Automation Status as “Automated” in Test Case
• Update “Automation Code” with Fully Qualified Class Name and @Test Method Name

Test progress in a Test cycle

Test progress at Component level

Test progress at Feature Level

Automation Progress

Test execution report with teststeps

No. of Test Cases added in Latest Release

No. of Regressions across Versions

• Bug should be linked to Test Case with “is regressed by” link type, if it a regression Bug.

• If not it should be linked to Test Case with “is caused by”

No. of regressions within Release

Test execution history for a Test Case

Add-ons Required

JQL Extensions for Querying linked issues https://marketplace.atlassian.com/plugins/jql-extensions/cloud/pricing

Issue Links Used

Filters Used

 

Filter Name	JQL
Bugs with Test Cases	project = MFS AND linkType = "is regressed by" AND issuetype = Bug AND affectedVersion = "Version 3.0"
Test Case Repository	project = MFS AND issuetype = "Test Case" AND (linkType not in (clones) OR linkType is EMPTY)
Test Cases Added in Latest Version	project = MFS AND issuetype = "Test Case" AND affectedVersion = "Version 4.0"
Test Cases Caused Regression	project = MFS AND linkType = regresses AND issuetype = "Test Case"
Test Cases With Open Bugs	project = MFS AND issuetype = "Test Case" AND status = "TC - Failed" AND linkedIssueType = Bug AND linkedIssueStatus = "To Do"
Test Execution of Latest Test Cycle	project = MFS AND issuetype = "Test Case" AND "Test Cycle" = "Version 4.0 - Cycle 1"
Requirement Traceability	project = MFS AND issuetype = Story AND linkType = "is requirement of"
All Bugs with Test Cases	project = MFS AND (linkType = "is caused by" OR linkType = "is regressed by") AND issuetype = Bug AND affectedVersion = "Version 3.0"
Automation Progress	project = MFS AND issuetype = Sub-task AND "Test Cycle" = "Version 4.0 - Cycle 1"
Regression Bugs with Test Cases	project = MFS AND linkType = "is regressed by" AND issuetype = Bug AND affectedVersion = "Version 3.0"

~Yagna