Difference between revisions of "Jira as a Test Case Management Software"

Jump to: navigation, search
(Run a test)
(obsolete template)
 
(32 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
{{obsolete}}
 
=Preface=
 
=Preface=
==Introduction ==
+
===Introduction ===
 
Moodle team uses Atlassian Jira as a Bug Tracker system. With a bit of tweaking Jira can become a Test Case Management software. For Moodle 2.0, we improved our QA department. We've been through testing a range of test management software that we could integrate to Jira. We tried more deeply Test Link, an open source software. It gave a us a good understanding of the basic Test Case Management software functionalities. Finally we decide to setup Jira for QA testing purpose. The main reason is that people working on Moodle are well familiar with Jira interface, and it will be easy for them to learn how to create, run test case, or generate report.
 
Moodle team uses Atlassian Jira as a Bug Tracker system. With a bit of tweaking Jira can become a Test Case Management software. For Moodle 2.0, we improved our QA department. We've been through testing a range of test management software that we could integrate to Jira. We tried more deeply Test Link, an open source software. It gave a us a good understanding of the basic Test Case Management software functionalities. Finally we decide to setup Jira for QA testing purpose. The main reason is that people working on Moodle are well familiar with Jira interface, and it will be easy for them to learn how to create, run test case, or generate report.
  
==Jira and Test Case Management==
+
===Jira and Test Case Management===
 
Jira as a Test Case Management is attractive since it:
 
Jira as a Test Case Management is attractive since it:
 
#Uses an existing and known tool
 
#Uses an existing and known tool
Line 10: Line 11:
 
#Supports multiple releases
 
#Supports multiple releases
  
==Scope of this document==
+
===Scope of this document===
 
This document describes how to install and setup Jira as a Test Case Management software.
 
This document describes how to install and setup Jira as a Test Case Management software.
  
=Installing Jira (Linux)=
+
=Running a QA test cycle=
Download the zip file
+
For the first QA cycle we will need to set up Jira and write the test cases.
 +
=== How to use Jira ===
 +
The way to use Jira is explained below. However it has never been fully tested, it needs to be approved:
 +
# ''Jira admin'' creates a new Jira project
 +
# ''Jira admin'' creates a Jira task that will be a QA cycle template. In this QA cycle template the ''Moodle test case writer'' creates multiple subtasks. Every subtask will be one test case. ''Moodle testers'' should never execute any test cases of this QA cycle template. 
 +
# ''QA manager'' clones the QA cycle template every time he wants to run a new QA cycle. ''QA manager'' sets the correct Moodle version on the cloned QA cycle. ''QA manager'' assigns people to the test cases if needed.
 +
# ''Moodle testers'' execute the test cases.
 +
# At the end of the test cases execution, ''QA manager'' should be able to do a search on the cloned test cases only, in order to check all Passed/Failed.
 +
 
 +
===Report a bug===
 +
If a tester finds a bug, he creates a new issue and associates the test case to this issue. He finally marks the test case as failed.
 +
 
 +
===Generate and Analyze a report===
 +
We search for all test cases with the Moodle Version field . The resulting set of test cases can then be sorted and counted by number passed, failed, not run etc. Producing historical reports can be done with the Timecharts plugin for Jira, which shows a graph of how the results in a report change over time.
  
 
=Setup the entire Jira QA environment=
 
=Setup the entire Jira QA environment=
==Create a project==
+
A demo has been installed [http://tracker.moodle.org/jiratest/secure/IssueNavigator.jspa?reset=true&pid=10040&status=1|on the tracker]
==Create the QA environment==
+
===Installing Jira (Linux)===
===TestCase Issue Type===
+
Download the enterprise edition zip file on the Jira website. Extract the the files. Run jira-enterprise/bin/startup.sh. You should be able to connect to http://localhost:8080
===New custom fields===
 
===Test case screen===
 
===Test case screen scheme===
 
===Issue type screen scheme===
 
  
===Field configuration===
+
=== Create a project "===
===Associate new Field configuration scheme to project===
+
it could be called "Moodle QA"
 +
=== create a main task ===
 +
create a new Issue type: "QA Cycle"
 +
=== Create as many subtask as test case ===
 +
create a new Issue type: "Test case"
 +
=== Create new fields===
  
===Create Test Case Execution sub-task===
+
"QA cycle" issue type should have these fields
====Issue Type====
+
* Summary:
====Screen====
+
* Description:
====Screen scheme====
+
* Build Run Against/Moodle Version: Moodle Version List
====Issue Type Screen Scheme====
 
====Field Configuration Scheme (associate Test Case Execution to TC field conf)====
 
  
===??????===
+
"Test case" issue type should have these fields:
 +
* Steps: test case steps (it's like a normal description field)
 +
* Component: should be same list as the one in Moodle project
 +
* Assignee:
 +
* Build Run Against/Moodle Version: it should be an automatic copy of the parent task. Use the plugin parentfield [http://confluence.atlassian.com/display/JIRAEXT/Parent+Field+Plugin]
  
===?? Intall report tool as Timecharts plugin for Jira ??===
+
===Create three new status:===
 
 
===Status and Workflow===
 
====Status====
 
Create three new status:
 
 
* Not Run (transition to Passed/Failed)
 
* Not Run (transition to Passed/Failed)
 
* Passed (transition to Not Run)
 
* Passed (transition to Not Run)
 
* Failed (transition to Not Run)
 
* Failed (transition to Not Run)
 +
* Obsolete/Inactive (transition to Not Run)
  
====Workflow====
+
=== Add Timecharts plugin ===
====Workflow Scheme====
+
# Download the Charting plugin http://confluence.atlassian.com/display/JIRAEXT/JIRA+Charting+Plugin
====Associate project to Workflow====
+
# Download the Timechart plugin http://confluence.atlassian.com/display/JIRAEXT/Timecharts
 
+
# Install the two file jar files into WEB-INF/lib
=Running a QA test cycle=
+
# Run shutdown.sh and startup.sh
===Write Test Case===
 
==== Create a task: Test Case=====
 
This will be created probably only once. It has to been written when you decide that your project get a new functionality.
 
The description contains
 
==== Create a subtask: Test Case Execution=====
 
This will be created everytime you need to run a new bunch of test case. There should be a unique subtask by Affected Version, so we can generate correct report. The description of the subtask describes Steps and Expected Results. Note that these steps and expected results can be different in each substaks of a test case, if the affected versions should behave differently.
 
 
 
===Run Test Case===
 
====Run a test====
 
You should follow the steps from the subtask which is assigned to you.
 
 
 
====Report a bug====
 
 
 
===Read Report===
 
  
====Generate a report====
+
=== Add clone plugin ===
When a QA report need to be created for the current state of a release, we search for all TestCase issues with the Affects Version field set to the required release. The resulting set of issues can then be sorted and counted by number passed, failed, not run etc. Producing historical reports can be done with the Timecharts plugin for Jira, which shows a graph of how the results in a report change over time.
+
In order to clone the QA cycle and all test cases, we need to add the clone functionality to Jira. [http://confluence.atlassian.com/display/JIRAEXT/JIRA+Clone+and+Move+Plugin]
====Interpret the report====
 
We created a new link type to connect test cases to the bugs that they created or are verifying. This is the biggest advantage that I see of using an issue tracker to track test cases and bugs together. TBD: we could also add a box to all bugs to indicate whether a Test Case is expected by someone for a bug.
 

Latest revision as of 06:31, 12 June 2014

Warning: This page is no longer in use. The information contained on the page should NOT be seen as relevant or reliable.

Preface

Introduction

Moodle team uses Atlassian Jira as a Bug Tracker system. With a bit of tweaking Jira can become a Test Case Management software. For Moodle 2.0, we improved our QA department. We've been through testing a range of test management software that we could integrate to Jira. We tried more deeply Test Link, an open source software. It gave a us a good understanding of the basic Test Case Management software functionalities. Finally we decide to setup Jira for QA testing purpose. The main reason is that people working on Moodle are well familiar with Jira interface, and it will be easy for them to learn how to create, run test case, or generate report.

Jira and Test Case Management

Jira as a Test Case Management is attractive since it:

  1. Uses an existing and known tool
  2. Provides an easy way to link bugs to test cases and results
  3. Provides decent reporting of the state of testing
  4. Supports multiple releases

Scope of this document

This document describes how to install and setup Jira as a Test Case Management software.

Running a QA test cycle

For the first QA cycle we will need to set up Jira and write the test cases.

How to use Jira

The way to use Jira is explained below. However it has never been fully tested, it needs to be approved:

  1. Jira admin creates a new Jira project
  2. Jira admin creates a Jira task that will be a QA cycle template. In this QA cycle template the Moodle test case writer creates multiple subtasks. Every subtask will be one test case. Moodle testers should never execute any test cases of this QA cycle template.
  3. QA manager clones the QA cycle template every time he wants to run a new QA cycle. QA manager sets the correct Moodle version on the cloned QA cycle. QA manager assigns people to the test cases if needed.
  4. Moodle testers execute the test cases.
  5. At the end of the test cases execution, QA manager should be able to do a search on the cloned test cases only, in order to check all Passed/Failed.

Report a bug

If a tester finds a bug, he creates a new issue and associates the test case to this issue. He finally marks the test case as failed.

Generate and Analyze a report

We search for all test cases with the Moodle Version field . The resulting set of test cases can then be sorted and counted by number passed, failed, not run etc. Producing historical reports can be done with the Timecharts plugin for Jira, which shows a graph of how the results in a report change over time.

Setup the entire Jira QA environment

A demo has been installed the tracker

Installing Jira (Linux)

Download the enterprise edition zip file on the Jira website. Extract the the files. Run jira-enterprise/bin/startup.sh. You should be able to connect to http://localhost:8080

Create a project "

it could be called "Moodle QA"

create a main task

create a new Issue type: "QA Cycle"

Create as many subtask as test case

create a new Issue type: "Test case"

Create new fields

"QA cycle" issue type should have these fields

  • Summary:
  • Description:
  • Build Run Against/Moodle Version: Moodle Version List

"Test case" issue type should have these fields:

  • Steps: test case steps (it's like a normal description field)
  • Component: should be same list as the one in Moodle project
  • Assignee:
  • Build Run Against/Moodle Version: it should be an automatic copy of the parent task. Use the plugin parentfield [1]

Create three new status:

  • Not Run (transition to Passed/Failed)
  • Passed (transition to Not Run)
  • Failed (transition to Not Run)
  • Obsolete/Inactive (transition to Not Run)

Add Timecharts plugin

  1. Download the Charting plugin http://confluence.atlassian.com/display/JIRAEXT/JIRA+Charting+Plugin
  2. Download the Timechart plugin http://confluence.atlassian.com/display/JIRAEXT/Timecharts
  3. Install the two file jar files into WEB-INF/lib
  4. Run shutdown.sh and startup.sh

Add clone plugin

In order to clone the QA cycle and all test cases, we need to add the clone functionality to Jira. [2]