is there an easy free way to create test case management in Jira

Question

I think the only part I dont get is how you handle the run results. So if I set up a new project in Jira for test cases how would I make it so I can run mark a test case as pass or fail but not close out the jira.

So I basically want the original jira to be always open then be able to mark it passed or failed against a specific release. the original jira should stay unchanged just somehow log a result set?

I do not have bamboo

that make any sense

Answer 1

We have setup a simple custom workflow in Jira without using Confluence. We added one new issue type - Test Case. And we have a new sub-task - Test Run.

Test Case has only three workflow actions: Pass, Fail and Invalid (the last one is to make Test Case redundant). And two statuses - Open and Invalid.

Test Run is automatically created when Test Case passes or fails. Users do not manually create test runs. We use one of the plugins to create a subtask on transition. Test Run can be in a Passed or Failed state and has version info, user who passed or failed and a comment.

This is it.

Here are some links that I used to setup Jira for Test Case Management:

• Test Case Management in Jira
• Using Jira for Test Case Manangement
• Create On Transition Plugin

Answer 2

The approach we are following is as follows

We use Confluence for implementing our test cases. Each test case has its own page describing the setup, the scenario to run and all possible outcomes.

We have a test library page which is the parent of all these test cases. When we want to start a validation cycle on a particular release, we use a script which generates for each test case in confluence, a corresponding 'test run' issue. (@DennisG - JIRA allows to define different issue types, each with its own workflow)

The summary is the summary of the testcase The description is the scenario and outcome of the testcase We have a specific confluence link referring the testcase

The testrun issue workflow contains 4 stages

• Open
• In Progress
• Blocked
• Closed

And 3 resolutions

• Success
• Failure
• Review testcase

We then start validating all 'test run' isuses. Using dashboard gadgets it is easy to see how many testcases still need to be run, how many are blocked, how many have been done, and how many have failed ...

In case the resolution is 'review testcase' we have the ability to adapt the testcase itself. Conclusion - JIRA is certainly usable as a test execution management environment. Confluence, as a wiki provides an environment to build the necessary hierarchies (technical, functional).

Last point. We start to extensively use Bonfire (a plugin for JIRA) http://www.atlassian.com/en/software/bonfire This shortens the 'manual' testing cycle considerably.
For us it had an ROI of a couple of weeks.

Hope this helps,

Francis

PS. If you're interested to use the script send me a note.