Continuing where we left off last time, let’s add an issue tracker to our management system. TestLink supports many popular issue tracking systems including Bugzilla, JIRA and Mantis. In this tutorial we’ll configure TestLink to use Mantis. First of all, download and install Mantis, check out any of the multitude of tutorials on the web if you run into trouble.
Once that’s done head over to the Issue Tracker Management section in TestLink. Hit create and give your tracker a name. Select the mantis (Interface: soap) type and paste the following configuration in the textbox:
<!-- Template mantis soap Interface --> <issuetracker> <username>administrator</username> <password>root</password> <uribase>http://localhost/mantis/</uribase> <!-- IMPORTANT NOTICE --> <!-- You Do not need to configure uriwsdl,uriview,uricreate --> <!-- if you have done Mantis standard installation --> <!-- In this situation DO NOT COPY these config lines --> <uriwsdl>http://localhost/mantis/api/soap/mantisconnect.php?wsdl</uriwsdl> <uriview>http://localhost/mantis/view.php?id=</uriview> <uricreate>http://localhost/mantis/</uricreate> <!-- Configure This if you want be able TO CREATE ISSUES --> <project>YourProjectName</project> <category>YourCategory</category> <!-- Configure This if you want NON STANDARD BEHAVIOUR for considered issue resolved --> <resolvedstatus> <status><code>80</code><verbose>resolved</verbose></status> <status><code>90</code><verbose>closed</verbose></status> </resolvedstatus> </issuetracker>
I’ve put things you probably need to edit to match your settings in bold.
We still need to activate the issue tracker integration for our project, you can do so on the Test Project Management page. Tick the box next to “Active” and select mantis from the dropdown. When you go to Execute Tests you can see BUG management with two links, one to link an existing bug/issue using its Mantis bug ID and a second to create a new issue in Mantis.
Version 1.9.13 of TestLink does not give you any feedback when you hit Save (aside from throwing errors when you don’t fill in a description). If the page does not refresh automatically, just click on the given test again and the linked bug will appear.
If you have several of these, there’s a nice little overview in the Reports and Metrics section as well.
Clicking any of the bugs will take you directly to its respective Mantis page. The input in TestLink is quite limited which means you probably want to add additional information regarding the issue in Mantis.
Thanks to the integration with an issue tracker you can quickly file bugs while you’re busy executing tests, reducing the chance you forget about an issue you’ve encountered. As an added bonus, TestLink will also store on what build you filed this bug so the developer who will try to fix it can trace it back to a specific point in time and try to recreate it.
We’re coming to a close very soon! Let’s see what we’ve got so far:
- Requirement tracing
- Test Case management
- Automatic execution of a Test Plan using Jenkins
- Issue Tracking using Mantis
With all of this you’ve already accomplished quite an extraordinairy amount of tracking and tracing! But what if you do not use Jenkins and still want automatic reporting of test results? Next time we’ll take a look at the Python module that can interface with TestLink’s API.