We're always here to help you. Please contact us during local business hours.
The product demonstration provides a start to finish overview of JIRA and if you have any questions while viewing the video you can live chat with a sales engineer.
View the recording.
Atlassian offers training modules for all users from first time users to experienced administrators. Read about our official training packages here.
 | JIRA Release Notes
Keep up to date with the latest features by browsing our summary release notes here. |
|
JIRA can be integrated with a dedicated, third-party test manager or customised to perform lightweight test management as described below:
Option A - Customisation
Because JIRA currently offers no direct integration with automated testing frameworks, the preferred approach is to handle automated testing via a continuous integration (CI) server and use JIRA primarily for manual testing. You can setup acceptance, integration, functional tests inside JIRA.
Features
Some specific features of JIRA that are useful for TCM:
 Link to bugs and requirements
Great for manual testing
Custom issue types such as test case and user story
Multiple affects/fix for versions
Create templates and bulk clone them
Automatic and manual issue assignment
Workflow controls QA, devs and tester actions
Subtasks for manual testing
Integrates with source code repository
Reporting
Issue comments and attachments
Customisable
Import from other systems
Uses an existing and known tool
 Only integrates with testing frameworks via CI server - could be addressed by developing your own JIRA plugin
No testing-specific functionality - specific features could be added by developing your own plugin
General Use Case
Using JIRA as your test case manager will support these following requirements:
- Test cases need to be defined before they can be run.
- Changes to the definitions of test cases may be made in parallel for different branches and their releases.
- The results of running the test cases have to be accumulated somewhere.
- Reports should contain information about many tests run over a period of time on a particular release.
- The reports should be easy to update when the underlying information changes, e.g. as ongoing tests pass and fail, or new tests are added and old tests are removed.
- The reports should contain a clear summary of the state of the testing activity for each release.
- The format of the reports should be such that they can be archived as self-contained collections of files such as test logs.
- If a large number of test cases are already defined, then automatic import into the test case manager.
Requirements
You will need the following tools to customise JIRA for internal TCM:
- A copy of JIRA for you to test with.
- A continuous integration (CI) server. This guide will assume that you are using the Atlassian Bamboo CI server as it offers JIRA integration.
- An automated testing framework able to output tests in a JUnit-compatible format, eg Selenium or JUnit.
- Optionally, you may like to store your test plan and internal project documentation in the Confluence wiki. See using Confluence for project documentation.
To proceed, please follow this guide to customising JIRA for test case management.
There is another helpful third party writeup here.
Option B - Integration
If the above features are insufficient then please consider integrating JIRA with a dedicated, external test case manager.
Also check out zAglie Teamwork and their great 1, 2, 3, 4 step introduction.
Discussion
For help or to ask questions, simply post to the JIRA test case thread in the user forums. |