Test Management System (TMS) using JIRA Customization
Download as PPTX, PDF1 like897 views
The document outlines a comprehensive JIRA customization for test management, detailing project structures, test case creation, automation processes, and integration with Jenkins. It emphasizes the importance of requirement traceability, test cycle execution, and management of test cases across different platforms. Furthermore, it provides specific JQL filters for querying linked issues, importing test cases from CSV, and generating reports to monitor test execution progress.
Test Management System (TMS) using JIRA Customization
- 1. TMS using JIRA Customization Yagnanarayana Dande
- 2. Project/Component/Story-Feature • In JIRA Project will be top level entity • Every Project will be having several Components • Example - Project-1 is a Project and Comp-1,Comp-2 are components • Stories will be created per Project and will be associated with one or more Components
- 3. Test Case New IssueType called Test Case added into JIRA with CFs
- 4. Template Test Summar y Test Steps Expected Results Automatio n Status Test Group Componen ts Requirem ent Issue Type Affects Version Create …. *Test Steps* 1…. 2 …. 3…. *Expected Results* 1….. 2…. Manual Smoke Comp-1 Project1-1 Test Case v1.3.0
- 6. Requirement Traceability Test Case should be linked to Requirement This allows Requirement Traceability
- 7. No. of Test Cases added in Latest Release
- 9. Assign Test Cases for Execution Using JQL and Bulk Upload
- 10. Test cycle execution assignments
- 11. User Dashboard
- 12. Test Execution
- 13. Test progress in a Test cycle
- 14. Test progress at Component level
- 15. Test progress at Feature Level
- 16. Test execution report with teststeps
- 17. Test Cases for Different Platforms(OS)
- 18. 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
- 19. Creation of Automation Tasks using CSV upload
- 20. 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
- 21. 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
- 24. Create Regression Tests • Get All Test Cases from Test Case Repository which are not invalid • Export them to CSV • Change the Test Cycle and Assignee • Import CSV • Use Issue Key as Cloners in import menu
- 25. 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”
- 26. No. of regressions within Release
- 27. Test execution history for a testcase
- 28. JIRA Jenkins Integration Pull Issue Details Execute Test Cases Update Test Results in JIRA
- 29. Jenkins Integration • Get all issues of given Filter • Get custom field from every Test Case • Maintain a Map of JIRA ID to Custom Field • Create a TestNG XML suite Programmatically and run it • Get results programmatically from TestNG • Update the issues by using Reverse mapping of Custom Field to JIRA ID
- 30. Jenkins Integration • https://github.com/rcarz/jira-client • Create a Filter • project = Project-1 AND issuetype = "Test Case" AND "Test Cycle" = "Version 4.0 - Cycle 1" AND "Automation Status" = Automated AND status = "In Progress" • Build jar from the code in last slide and run on Jenkins. • This code needs following inputs – JIRA URL – JIRA Credentials – Filter like “filter=10112” – customField="customfield_10032" – Note: You can get custom field name from JIRA Rest API and this name is different from what you see in JIRA UI
- 31. Add-ons Required JQL Extensions for Querying linked issues https://marketplace.atlassian.com/plugins/jql-extensions/cloud/pricing
- 32. Import Test Cases from CSV https://confluence.atlassian.com/adminjiracloud/importing-data- from-csv-776636762.html#ImportingdatafromCSV-format
- 33. Import Test Cases from CSV
- 34. Import Test Cases from CSV
- 35. Jenkins Integration package com.company.qa.project.test; import java.util.ArrayList; import java.util.Arrays; import java.util.Collection; import java.util.HashMap; import java.util.List; import java.util.Map; import org.testng.IReporter; import org.testng.ISuite; import org.testng.ISuiteResult;
- 36. Issue Links Used
- 37. Filters Used Filter Name JQL Bugs with Test Cases project = Project1 AND linkType = "is regressed by" AND issuetype = Bug AND affectedVersion = "Version 3.0" Test Case Repository project = Project1 AND issuetype = "Test Case" AND (linkType not in (clones) OR linkType is EMPTY) Test Cases Added in Latest Version project = Project1 AND issuetype = "Test Case" AND affectedVersion = "Version 4.0" Test Cases Caused Regression project = Project1 AND linkType = regresses AND issuetype = "Test Case" Test Cases With Open Bugs project = Project1 AND issuetype = "Test Case" AND status = "TC - Failed" AND linkedIssueType = Bug AND linkedIssueStatus = "To Do" Test Execution of Latest Test Cycle project = Project1 AND issuetype = "Test Case" AND "Test Cycle" = "Version 4.0 - Cycle 1" Requirement Traceability project = Project1 AND issuetype = Story AND linkType = "is requirement of" All Bugs with Test Cases project = Project1 AND (linkType = "is caused by" OR linkType = "is regressed by") AND issuetype = Bug AND affectedVersion = "Version 3.0" Automation Progress project = Project1 AND issuetype = Sub-task AND "Test Cycle" = "Version 4.0 - Cycle 1" Regression Bugs with Test Cases project = Project1 AND linkType = "is regressed by" AND issuetype = Bug AND affectedVersion = "Version 3.0" Automated Tests Ready to Run project = Project1 AND issuetype = "Test Case" AND "Test Cycle" = "Version 4.0 - Cycle 1" AND "Automation Status" = Automated AND status = "In Progress" Test Execution History project = Project1 AND issuetype = "Test Case" AND linkType in (clones) AND linksIssue = Project1-32 ORDER BY "Test Cycle" DESC
- 38. Configuration for Environments { "config.version" : "2.0", "config.project.from.csv" : "false", "config.encoding" : "UTF-8", "config.email.suffix" : "@", "config.field.mappings" : { "Custom field (Test Group)" : { "existing.custom.field" : "10026" }, "Issue Type" : {