Hi,
TestLink is an effective test management tool. We are now looking for integration with a bug tracking tool like Mantis.
We installed Mantis and TestLink, also, done configuration settings for integration. We are not getting any bug tracking link section in the Execution screen. Please help!!
There is no difference to testlink before and after integration configuration.
We are working on a new project and need Mantis integration immediately. Can anyone give suggestions??
TestLink and Mantis
Moderators: Amaradana, TurboPT, TL Developers
Firts suggestion is check on our mantis site for documentation.
In forums home there is some pointer to last documents about BTS integration.
you can also download from testlink sourceforge a modified xampp lite with mantis, tl configured to work togheter and all you need to work, then you can compare your config with yours
In forums home there is some pointer to last documents about BTS integration.
you can also download from testlink sourceforge a modified xampp lite with mantis, tl configured to work togheter and all you need to work, then you can compare your config with yours
Please use :
http://www.teamst.org/phpBB2/viewtopic.php?t=661
download the sw from sourceforge, put it up and running, and check
your config against the config done in our xampp package
http://www.teamst.org/phpBB2/viewtopic.php?t=661
download the sw from sourceforge, put it up and running, and check
your config against the config done in our xampp package
integration
The current testlink/mantis integration isn't very useful. All it does is give you a text box where you tel testlink the number of the bug you just entered in Mantis, but the entire rest of the process is manual.
I had a brainstorm about how to do this in a much more automated way. Today I was investigating what was needed, and it starts with an expert knoweldge of TestLink internals. The second part, of course, requires an expert knowledge of Mantis internals. I decided that my time right now is better spent on writing test cases. Nevertheless, here's a description of the approach I want to take. Perhaps someone else can run with it.
I replaced the code in the file bug_add.php with a fairly simple html frame page with some glue to transfer parameters from the call to the original code, which I moved to bug_add_top.php. This file lives in the top half of the page. In the bottom half of the page it was my intent to make a form that has the following fields:
user-name (filled in with TestLink user name)
password (blank)
bug title ("failure in " + $test_case_title)
bug description (test case steps and expected results)
bug results (empty field for actual results)
priority (taken from the TestLink importance field)
And there would be a button "Submit".
So when you click the bug in TestLink, this page would pop up with as much information as was already known about the bug already populated. The user supplies password and results, then clicks Submit. That would submit the form to a second .php file ...
A second php file would live in Mantis. It would be coded to receive fields as described above. It would first validate the user-name and password pair against the Mantis bugbase. Then it would make a simple set of MySQL queries to add a new record to the bugbase and populate its fields. This php file would finally, after some delay, refresh itself to the appropriate Mantis bug view page. The user could then see the bug as it was submitted and make any necessary changes. The user would note the bug number and enter it in the text field in the top frame. (that's ugly; I hope someone can automate this part as well.)
This system is test-base and bug-base independent. The test-base owns the submit form and the bug-base owns the receive page. The bug-base does its own user validation; the test-base doesn't have to keep any passwords. The only thing the submit form and the receive page have to have in common is the names of the variables used to pass the bug report from the test-base to the bug-base.
I could code this; the hard work for me is slogging though the testLink code to figure out where to get the information I need. (And then, of course, through the bug-base code to do the user validation and new bug report population.) I read DevGuide.pdf but that did not describe the architecture of TestLink.
If someone can give me a clue or some suggestions (I probably need a whole boxful) then I could start on this.
I had a brainstorm about how to do this in a much more automated way. Today I was investigating what was needed, and it starts with an expert knoweldge of TestLink internals. The second part, of course, requires an expert knowledge of Mantis internals. I decided that my time right now is better spent on writing test cases. Nevertheless, here's a description of the approach I want to take. Perhaps someone else can run with it.
I replaced the code in the file bug_add.php with a fairly simple html frame page with some glue to transfer parameters from the call to the original code, which I moved to bug_add_top.php. This file lives in the top half of the page. In the bottom half of the page it was my intent to make a form that has the following fields:
user-name (filled in with TestLink user name)
password (blank)
bug title ("failure in " + $test_case_title)
bug description (test case steps and expected results)
bug results (empty field for actual results)
priority (taken from the TestLink importance field)
And there would be a button "Submit".
So when you click the bug in TestLink, this page would pop up with as much information as was already known about the bug already populated. The user supplies password and results, then clicks Submit. That would submit the form to a second .php file ...
A second php file would live in Mantis. It would be coded to receive fields as described above. It would first validate the user-name and password pair against the Mantis bugbase. Then it would make a simple set of MySQL queries to add a new record to the bugbase and populate its fields. This php file would finally, after some delay, refresh itself to the appropriate Mantis bug view page. The user could then see the bug as it was submitted and make any necessary changes. The user would note the bug number and enter it in the text field in the top frame. (that's ugly; I hope someone can automate this part as well.)
This system is test-base and bug-base independent. The test-base owns the submit form and the bug-base owns the receive page. The bug-base does its own user validation; the test-base doesn't have to keep any passwords. The only thing the submit form and the receive page have to have in common is the names of the variables used to pass the bug report from the test-base to the bug-base.
I could code this; the hard work for me is slogging though the testLink code to figure out where to get the information I need. (And then, of course, through the bug-base code to do the user validation and new bug report population.) I read DevGuide.pdf but that did not describe the architecture of TestLink.
If someone can give me a clue or some suggestions (I probably need a whole boxful) then I could start on this.