SlideShare a Scribd company logo

XRAY for Jira

•
•
Mike Brosnan
Mike Brosnan

This document provides an overview of using Jira for quality assurance and testing. It discusses leveraging Jira's built-in features for test management and how Xray enhances Jira's capabilities. Key phases of testing like specification, organization, planning, execution and reporting are covered. It also highlights test automation integration and compares Xray to other test management tools for Jira.

Related slideshows

Jira
JiraJira
Jira
 
Jira as a Tool for Test Management
Jira as a Tool for Test ManagementJira as a Tool for Test Management
Jira as a Tool for Test Management
 
JIRA
JIRAJIRA
JIRA
 
1 of 47
Download to read offline
XRAY for Jira
2 +4 Years Making kickass software +5 Offices In 3 different countries +4.500 Customers Using our products +65 Countries With customers +350 Reviews In the Marketplace +360.000 Lines of Code Written by our team 4 Languages Available in English, German, Spanish and French +4.000 Support Tickets Closed by our Support Team +300 Features In our roadmap
XRAY for Jira
4 Our Clients
5 Agenda 1. Faster and better software releases 2. Why Jira for Quality Assurance? 3. Leverage Jira for testing with Xray 4. The life of a ”tester” I. Specifying, organizing, planning, executing II. Reporting 5. Test Automation 6. Xray vs competition 7. Using Jira for testing, today
1. Faster and better software releases
7 Speed vs Quality Are they real enemies? Let these help you out: ü Agile ü DevOps ü Continuous Integration ü Automated Testing ü Continuous Testing ü Continuous Delivery Release often, with confidence. Motivate your team, make your customers happy. Image by www.genalice.com
8 Why is Test Management so important? Software is everywhere, including in critical systems from health, finance, transports, space, IoT, just to name a few…
2. Why Jira for Quality Assurance?
10 Using Jira for software development Requirements Defects Tests
11 In the ”dark ages”…. … there was Excel… or even other “legacy Test Management tools” J
12 Welcome to “modern ages” with Jira § Built-in features • Focus on teams • Collaboration / Comments • Agile project management & waterfall • Workflow control • Customizable and adaptable • Searching • Assignment • Track changes • Linking between issues • Importing issues from CSV
13 Jira as a Test Management tool What is missing? 1. Test related artifacts (tests, executions, plans) 2. Visibility of testing results and progress in Agile boards 3. In-context information about tests for requirements 4. Advanced reporting for generating documents and drill-down on data
3. Leverage Jira for testing with Xray
15 Dedicated Jira issue types for testing Specification: Tests and Pre-Conditions Organization: Test Sets Planning: Test Plans Execution: (sub)Test Executions
16 The benefits of using Jira issue types 1. Leverages Jira’s built-in features 2. Permission control 3. Implementation of Workflows 4. Custom fields 5. Screens customization 6. Assignment, Changes tracking 7. Collaboration 8. And much more…
4. The life of a “tester”
18 Testing phases
19 Specifying “Manual Tests” • Composed by a list of steps • Each Step is defined by: • Action/Step • Data • Expected Result • Input Attachments • Jira Wiki markup support • Importing steps, including from Excel using copy & paste
20 Specifying “Automated Cucumber Tests” • Cucumber supported natively • BDD – Specify tests in a business-readable domain-specific language • Test definition serves as documentation • Automated test steps may be implemented in Ruby, Java, .Net, etc • Export specification and execute it during Continuous Integration
21 Complement specifications with “Pre-Conditions” Abstracts initial steps that must be done or ensured before starting the test. • Manual or Automated • Reusable; may be linked to multiple Tests
22 Organizing Tests in multiple ways Flat, with “Test Sets” A issue that represents a list of tests organized by some logical way. The natural “JIRA way”. Hierarchical (v3.0) For the “hierarchy/folder mindset”…
23 Planning with “Test Plans” A testing plan for aggregating and consolidate results from multiple iterations (i.e. Test Executions) • Tracks a group of tests and their results independently of the number of executions • Create planned test cycles (i.e. Test Executions) for the Test Plan
24 Executing with “Test Executions” A “task” for executing a group of tests on a given version of the system. • Contains a list of tests and their results (i.e. test runs) • Can be labeled, prioritized, assigned to components, etc. • May be created manually or during Continuous Integration
25 At the execution screen of a Test Run… 1. Set Execution Result 2. Create Defect issues 3. Attach Evidence 4. Add comments 5. Check the Execution Activity Log
Ok… but how does this gets visible in our requirements?
27 “Requirements” as they come by default in Jira • You may track the implementation through the workflow status but it lacks testing related info • “Soft-binding” between implementation and expected result
28 Real status of requirements with in-context information With Xray: ü Real-time information about the coverage status of the requirement for a given version ü Real-time information about the associated test results, for a given version ü A ”requirement” may be any issue type you may have; test coverage can be made in any issue type
Reports
30 Multiple ways of reporting, the Jira way 1. Built-in reports 2. JIRA gadgets in Jira dashboards 3. Agile boards 4. Through other top-notch Jira
31 Built-in reports: Traceability Report Shows the requirement traceability, from requirements to defects. This helps you analyze the requirements and related Tests, Test Runs and defects, for quickly identifying uncovered or incomplete/faulty requirements.
32 Jira Dashboards: Requirement Coverage Gadgets Provides a quick way of evaluating the current (coverage) status of your project's requirements, so you will be able to see if they are ready to be or not.
33 Standard Agile Boards Useful, yet lack quality related information.
34 Enhanced Agile Boards with Xray Xray gives you visibility of your testing results and its progress.
35 Reports as deliverable assets Use Xporter to generate fully customizable Word, Excel or PDF files with your testing reports to give to your management, colleagues or to your customers (e.g. Test specification, Test Execution progress and respective results, Test Plan details).
5. Test Automation
37 The cost of bugs • The cost of fixing bugs grows exponentially depending on the phase in which they are detected • The fix cost also depends on the stage where bugs are initially introduced => Automated testing to the rescue! Code Complete, Steve McConnell, 2004
38 Integrating with automated test frameworks Supported formats: ü Xray JSON ü Cucumber ü Behave ü Junit ü Nunit ü TestNG ü Robot framework ü Calabash ü … more to come Automation in mind…
39 Enabling Automated Tests
6. Xray vs competition
41 Xray vs Zephyr for Jira Xray Zephyr Native support for BDD with Cucumber - Jira issues for all testing phases - Data consistency - JUnit, NUnit, Robot, Behave, TestNG - Hierarchical, multi-level folder Tests organization at project level - Hierarchical, multi-level folder Tests organization per each Test Plan - REST API built-in - Integration with Xporter for fully customized reports in Word, PDF, XLS -
7. Using Jira for testing, today!
43 Migrating tests to Jira Xray provides: 1. A built-in Test Case Importer, that is able to import tests (including attachments and additional fields) from a friendly CSV 2. A built HP ALM 12.5x importer 3. An open REST API, that can be used to import Tests and also results
44 Fitting all together
Additional Resources
46 Resources • Xray documentation • http://confluence.xpand-it.com/display/XRAY • Xray web site & blog • getxray.app • getxray.app/blog/ • Xray in social networks • Twitter • Facebook • LinkedIn • YouTube • Xray Sandbox (shared environment) • http://sandbox.xpand-it.com
Thank you! Xpand IT getxray.app Happy Testing! mail@getxray.app @XrayApp

More Related Content

XRAY for Jira

  • 2. 2 +4 Years Making kickass software +5 Offices In 3 different countries +4.500 Customers Using our products +65 Countries With customers +350 Reviews In the Marketplace +360.000 Lines of Code Written by our team 4 Languages Available in English, German, Spanish and French +4.000 Support Tickets Closed by our Support Team +300 Features In our roadmap
  • 5. 5 Agenda 1. Faster and better software releases 2. Why Jira for Quality Assurance? 3. Leverage Jira for testing with Xray 4. The life of a ”tester” I. Specifying, organizing, planning, executing II. Reporting 5. Test Automation 6. Xray vs competition 7. Using Jira for testing, today
  • 6. 1. Faster and better software releases
  • 7. 7 Speed vs Quality Are they real enemies? Let these help you out: ü Agile ü DevOps ü Continuous Integration ü Automated Testing ü Continuous Testing ü Continuous Delivery Release often, with confidence. Motivate your team, make your customers happy. Image by www.genalice.com
  • 8. 8 Why is Test Management so important? Software is everywhere, including in critical systems from health, finance, transports, space, IoT, just to name a few…
  • 9. 2. Why Jira for Quality Assurance?
  • 10. 10 Using Jira for software development Requirements Defects Tests
  • 11. 11 In the ”dark ages”…. �� there was Excel… or even other “legacy Test Management tools” J
  • 12. 12 Welcome to “modern ages” with Jira § Built-in features • Focus on teams • Collaboration / Comments • Agile project management & waterfall • Workflow control • Customizable and adaptable • Searching • Assignment • Track changes • Linking between issues • Importing issues from CSV
  • 13. 13 Jira as a Test Management tool What is missing? 1. Test related artifacts (tests, executions, plans) 2. Visibility of testing results and progress in Agile boards 3. In-context information about tests for requirements 4. Advanced reporting for generating documents and drill-down on data
  • 14. 3. Leverage Jira for testing with Xray
  • 15. 15 Dedicated Jira issue types for testing Specification: Tests and Pre-Conditions Organization: Test Sets Planning: Test Plans Execution: (sub)Test Executions
  • 16. 16 The benefits of using Jira issue types 1. Leverages Jira’s built-in features 2. Permission control 3. Implementation of Workflows 4. Custom fields 5. Screens customization 6. Assignment, Changes tracking 7. Collaboration 8. And much more…
  • 17. 4. The life of a “tester”
  • 19. 19 Specifying “Manual Tests” • Composed by a list of steps • Each Step is defined by: • Action/Step • Data • Expected Result • Input Attachments • Jira Wiki markup support • Importing steps, including from Excel using copy & paste
  • 20. 20 Specifying “Automated Cucumber Tests” • Cucumber supported natively • BDD – Specify tests in a business-readable domain-specific language • Test definition serves as documentation • Automated test steps may be implemented in Ruby, Java, .Net, etc • Export specification and execute it during Continuous Integration
  • 21. 21 Complement specifications with “Pre-Conditions” Abstracts initial steps that must be done or ensured before starting the test. • Manual or Automated • Reusable; may be linked to multiple Tests
  • 22. 22 Organizing Tests in multiple ways Flat, with “Test Sets” A issue that represents a list of tests organized by some logical way. The natural “JIRA way”. Hierarchical (v3.0) For the “hierarchy/folder mindset”…
  • 23. 23 Planning with “Test Plans” A testing plan for aggregating and consolidate results from multiple iterations (i.e. Test Executions) • Tracks a group of tests and their results independently of the number of executions • Create planned test cycles (i.e. Test Executions) for the Test Plan
  • 24. 24 Executing with “Test Executions” A “task” for executing a group of tests on a given version of the system. • Contains a list of tests and their results (i.e. test runs) • Can be labeled, prioritized, assigned to components, etc. • May be created manually or during Continuous Integration
  • 25. 25 At the execution screen of a Test Run… 1. Set Execution Result 2. Create Defect issues 3. Attach Evidence 4. Add comments 5. Check the Execution Activity Log
  • 26. Ok… but how does this gets visible in our requirements?
  • 27. 27 “Requirements” as they come by default in Jira • You may track the implementation through the workflow status but it lacks testing related info • “Soft-binding” between implementation and expected result
  • 28. 28 Real status of requirements with in-context information With Xray: ü Real-time information about the coverage status of the requirement for a given version ü Real-time information about the associated test results, for a given version ü A ”requirement” may be any issue type you may have; test coverage can be made in any issue type
  • 30. 30 Multiple ways of reporting, the Jira way 1. Built-in reports 2. JIRA gadgets in Jira dashboards 3. Agile boards 4. Through other top-notch Jira
  • 31. 31 Built-in reports: Traceability Report Shows the requirement traceability, from requirements to defects. This helps you analyze the requirements and related Tests, Test Runs and defects, for quickly identifying uncovered or incomplete/faulty requirements.
  • 32. 32 Jira Dashboards: Requirement Coverage Gadgets Provides a quick way of evaluating the current (coverage) status of your project's requirements, so you will be able to see if they are ready to be or not.
  • 33. 33 Standard Agile Boards Useful, yet lack quality related information.
  • 34. 34 Enhanced Agile Boards with Xray Xray gives you visibility of your testing results and its progress.
  • 35. 35 Reports as deliverable assets Use Xporter to generate fully customizable Word, Excel or PDF files with your testing reports to give to your management, colleagues or to your customers (e.g. Test specification, Test Execution progress and respective results, Test Plan details).
  • 37. 37 The cost of bugs • The cost of fixing bugs grows exponentially depending on the phase in which they are detected • The fix cost also depends on the stage where bugs are initially introduced => Automated testing to the rescue! Code Complete, Steve McConnell, 2004
  • 38. 38 Integrating with automated test frameworks Supported formats: ü Xray JSON ü Cucumber ü Behave ü Junit ü Nunit ü TestNG ü Robot framework ü Calabash ü … more to come Automation in mind…
  • 40. 6. Xray vs competition
  • 41. 41 Xray vs Zephyr for Jira Xray Zephyr Native support for BDD with Cucumber - Jira issues for all testing phases - Data consistency - JUnit, NUnit, Robot, Behave, TestNG - Hierarchical, multi-level folder Tests organization at project level - Hierarchical, multi-level folder Tests organization per each Test Plan - REST API built-in - Integration with Xporter for fully customized reports in Word, PDF, XLS -
  • 42. 7. Using Jira for testing, today!
  • 43. 43 Migrating tests to Jira Xray provides: 1. A built-in Test Case Importer, that is able to import tests (including attachments and additional fields) from a friendly CSV 2. A built HP ALM 12.5x importer 3. An open REST API, that can be used to import Tests and also results
  • 46. 46 Resources • Xray documentation • http://confluence.xpand-it.com/display/XRAY • Xray web site & blog • getxray.app • getxray.app/blog/ • Xray in social networks • Twitter • Facebook • LinkedIn • YouTube • Xray Sandbox (shared environment) • http://sandbox.xpand-it.com
  • 47. Thank you! Xpand IT getxray.app Happy Testing! mail@getxray.app @XrayApp