Difference between revisions of "Jira as a Test Case Management Software"
(→Run a test)
(→Report a bug)
|Line 63:||Line 63:|
====Report a bug====
====Report a bug====
Revision as of 03:43, 4 August 2008
- 1 Preface
- 2 Installing Jira (Linux)
- 3 Setup the entire Jira QA environment
- 3.1 Create a project
- 3.2 Create the QA environment
- 3.2.1 TestCase Issue Type
- 3.2.2 New custom fields
- 3.2.3 Test case screen
- 3.2.4 Test case screen scheme
- 3.2.5 Issue type screen scheme
- 3.2.6 Field configuration
- 3.2.7 Associate new Field configuration scheme to project
- 3.2.8 Create Test Case Execution sub-task
- 3.2.9 ??????
- 3.2.10 ?? Intall report tool as Timecharts plugin for Jira ??
- 3.2.11 Status and Workflow
- 4 Running a QA test cycle
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.
Installing Jira (Linux)
Download the zip file
Setup the entire Jira QA environment
Create a project
Create the QA environment
TestCase Issue Type
New custom fields
Test case screen
Test case screen scheme
Issue type screen scheme
Associate new Field configuration scheme to project
Create Test Case Execution sub-task
Issue Type Screen Scheme
Field Configuration Scheme (associate Test Case Execution to TC field conf)
?? Intall report tool as Timecharts plugin for Jira ??
Status and Workflow
Create three new status:
- Not Run (transition to Passed/Failed)
- Passed (transition to Not Run)
- Failed (transition to Not Run)
Associate project to Workflow
Running a QA test cycle
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
If you encounter a bug, create a new issue and link the bug to this test case execution. Mark this test case execution as failed.
Generate a report
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.
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.