Test case management and requirements traceability
3 likes1,120 views
SafeNet is a cybersecurity company founded in 1983 that protects sensitive data for major brands. It protects $1 trillion in daily money transfers and the most digital identities and classified information worldwide. The presentation discusses using Jira for test case management and requirements traceability. Key requirements for test case management include seamless integration with Jira, treating test cases as normal issues, linking test cases to user stories and bugs, and executing test cases across multiple independent test plans in parallel.
Test case management and requirements traceability
- 2. Vladimir Belorusets, PhD • Quality Architect/Director • SafeNet, Inc. Test Case Management and Requirements Traceability in JIRA
- 3. SafeNet - Proven Technology Vendor Trusted to protect the world’s most sensitive data for the world’s most trusted brands. We protect the most money that moves in the world, $1 trillion daily. We protect the most digital identities in the world. We protect the most classified information in the world. FOUNDED 1983 REVENUE ~330m EMPLOYEES +1,400 In 25 countries OWENERSHIP Private GLOBAL FOOTPRINT +25,000 Customers in 100 countries ACCREDITED Products certified to the highest security standard
- 4. JIRA •JIRA is a framework with add-ons
- 5. Issues •JIRA issue types: •Bugs •Requirements •Tests
- 6. Requirements •User stories and epics •JIRA Agile supports Scrum
- 7. Tests Test Plan Test Suites Test Cases Test Cases
- 8. Traceability Requirements Test Cases Defects
- 9. Test Case Management Requirement – No 1 •Test case management implementation should be seamlessly integrated with the entire Atlassian suite.
- 10. Test Case Management Requirement – No 2 •Test cases and test plans should be presented as if they were just other JIRA issues.
- 11. Test Case Management Requirement – No 3 •Test engineers should be able to associate test cases with user stories and bugs they discover for traceability.
- 12. Test Case Management Requirement – No 4 •Engineers can execute the same test cases in multiple test plans independently and in parallel without overwriting the test case results
- 13. Test Cases vs. Sub-tests Sub-Test 3 Sub-Test 2 Sub-Test 1 Test Plan 1 Test Plan 3 Test Plan 2 Test Case •Sub-tests are independent instances of test cases
- 14. Test Case Management Requirement – No 5 •Aggregated and customizable view
- 15. Test Case Management Requirement – No 6
- 16. Test Case Management Requirement – No 7 •Integration with JIRA Agile
- 17. Test Case Management Requirement – No 8 •Test plan gadget
- 18. Test Case Management Requirement – No 9 •REST API Example: https://jira.safenet-inc.com/changeStateServlet?testPlanKey=<Test Plan ID> &<Test Case ID>=Passed&<Test Case ID>=Failed&<Test Case ID>=Passed
- 19. Demo
- 20. Thank you! Vladimir Belorusets, PhD • Quality Architect/Director • SafeNet, Inc.