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

Jump to: navigation, search

Note: You are currently viewing documentation for Moodle 2.0. Up-to-date documentation for the latest stable version is available here: Jira as a Test Case Management Software.

m
(Shifted to dev docs)
 
Line 1: Line 1:
{{stub}}[[Category:Quality Assurance]]
+
{{Moved_to_dev_docs}}
=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:
 
#Uses an existing and known tool
 
#Provides an easy way to link bugs to test cases and results
 
#Provides decent reporting of the state of testing
 
#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:
 
# ''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=
 
A demo has been installed [http://tracker.moodle.org/jiratest/secure/IssueNavigator.jspa?reset=true&pid=10040&status=1|on 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 [http://confluence.atlassian.com/display/JIRAEXT/Parent+Field+Plugin]
 
 
 
===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 ===
 
# Download the Charting plugin http://confluence.atlassian.com/display/JIRAEXT/JIRA+Charting+Plugin
 
# Download the Timechart plugin http://confluence.atlassian.com/display/JIRAEXT/Timecharts
 
# Install the two file jar files into WEB-INF/lib
 
# 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. [http://confluence.atlassian.com/display/JIRAEXT/JIRA+Clone+and+Move+Plugin]
 

Latest revision as of 08:41, 15 September 2011

This development related page is now located in the Dev docs.

See the Jira as a Test Case Management Software page in the Dev docs.