Hi guys,
i searched for the topic to integrate TL 1.9.14 with mantis(interface:db) BUT unfortunately i didn't get enogh information & i questioned on Mantis forum where i was redirected to TL Forum.
If i am re-posting this question then i am sorry about it. i am not here to spam. i have read the guidelines to use this forum and in creation of new topics.
My Scenario: I am trying to use issue tracker management. We use Mantis DB in the company i work. So, i need to integrate this with Mantis DB. I selected "Mantis (interface: db)" as Soap UI is not used as interface. The configuration is as follows:
<dbhost>DATABASE SERVER NAME</dbhost>
<dbname>DATABASE NAME</dbname>
<dbtype>mysql</dbtype>
<dbuser>USER</dbuser>
<dbpassword>PASSWORD</dbpassword>
I have entered the DB servername where the database is hosted. I have entered the database type which is "mySQL". The name, username & PW are too entered. So , this part is clear.
<uriview>http://localhost:8080/development/manti ... =</uriview>
<uricreate>http://localhost:8080/development/manti ... /uricreate>
For the above part: Here i have a problem. The DB admin created a folder namely „TestLink“ on Mantis & provided me the URL of this folder. So that i can connect to this folder from issue tracker management. I pasted it between „uriview“ tags. I could not have a connection established & there was a warning in Test Execution pane displayed „Attention please: Something is preventing connection to Bug Tracking system, and is going to create performance issues. Please contact your TestLink Administrator“.
My understanding with "http://localhost:8080/development/manti ... ew.php?id="
1) localhost:8080 -> This points the interface which shows the information & doesn't point to the storage place itself (i.e. the DB). This is not the DB hostname.
2) view.php?id= -> This means the frontend (or) the form where entered data can be viewed
What should i insert in "uricreate" tab?
If i had got a specific message about the problem i could have pasted it here or looked out for solution elsewhere. Unfortunately i couldn't.
TestLink 1.9.14 integration with Mantis(interface:db)
Moderators: Amaradana, TurboPT, TL Developers
-
testtools420
- Advanced user
- Posts: 16
- Joined: Sun Nov 22, 2015 10:52 am
-
testtools420
- Advanced user
- Posts: 16
- Joined: Sun Nov 22, 2015 10:52 am
Re: TestLink 1.9.14 integration with Mantis(interface:db)
Continuation of earlier message about my configuration.
OS Version: Windows Server 2012 R2
php – Version: 5.5.29
MySQL Server: 5.6
Apache: 2.4.16
OS Version: Windows Server 2012 R2
php – Version: 5.5.29
MySQL Server: 5.6
Apache: 2.4.16
-
testtools420
- Advanced user
- Posts: 16
- Joined: Sun Nov 22, 2015 10:52 am
Re: TestLink 1.9.14 integration with Mantis(interface:db)
Hi guys,
can anyone atleast tell me what i need to enter in <uriview> & <uricreate>???
i will list out what i did:
1) As "fman" in his post mentioned (http://forum.testlink.org/viewtopic.php?f=25&t=6972) i checked for the library named issuetrackerintegration. This library does exist & a module named "mantisdbInterface.class.php" is too integrated. But i have no idea about the methods
completeCfg() - I don't know what is present there
getCfgTemplate() - This method had the template in it
2) Checked out this link (http://forum.testlink.org/viewtopic.php?f=44&t=7191) which explained integration with "interface:SOAP UI" & not with "interface:db"
3) I tried different paths for <uriview> & <uricreate> but didn't succeed. I am pretty sure that i am making a mistake in this place but don't know what the mistake is.
can anyone atleast tell me what i need to enter in <uriview> & <uricreate>???
i will list out what i did:
1) As "fman" in his post mentioned (http://forum.testlink.org/viewtopic.php?f=25&t=6972) i checked for the library named issuetrackerintegration. This library does exist & a module named "mantisdbInterface.class.php" is too integrated. But i have no idea about the methods
completeCfg() - I don't know what is present there
getCfgTemplate() - This method had the template in it
2) Checked out this link (http://forum.testlink.org/viewtopic.php?f=44&t=7191) which explained integration with "interface:SOAP UI" & not with "interface:db"
3) I tried different paths for <uriview> & <uricreate> but didn't succeed. I am pretty sure that i am making a mistake in this place but don't know what the mistake is.
Re: TestLink 1.9.14 integration with Mantis(interface:db)
Have you give a look to http://forum.testlink.org/viewtopic.php?f=44&t=7203 ?
IMHO if you use SOAP it will be better
IMHO if you use SOAP it will be better
-
testtools420
- Advanced user
- Posts: 16
- Joined: Sun Nov 22, 2015 10:52 am
Re: TestLink 1.9.14 integration with Mantis(interface:db)
My Problem:
There was an issue faced during configuration of Issue Tracker Management (ITM). The problem was that the example code as shown in TestLink's (TL) ITM was not functioning. i.e. a connection was not being established. A message was being displayed which was a known bug in 1.9.9 & was fixed in 1.9.10. Below ist he screenshot oft he message.
Known Bug in TL: http://mantis.testlink.org/view.php?id=6089
Duplicate Bug in TL (which resembles the message in my problem): http://mantis.testlink.org/view.php?id=6221
Our findings:
• A connection between TL database and Mantis database were checked. The connection was established
• But in the Bitnami user logs we could see a warning & an error message stating that a connection could not be established
• Many permutation and combinations were tried like enabling and disabling password (or) giving access rights in every level
Solution:
A patch was inserted in TL application packet. This patch contains commands (on HeidiSQL) which was written in excel sheet. The information in the patch is the same as that is present in configuration of ITM
Functionalites of ITM:
• A bug can be created from TL's GUI – at the moment not working
• A already existing bug can be added to a test case with the status of the bug. The status which can be seen in TL are assigned, resolved and closed – This functionality is working
There was an issue faced during configuration of Issue Tracker Management (ITM). The problem was that the example code as shown in TestLink's (TL) ITM was not functioning. i.e. a connection was not being established. A message was being displayed which was a known bug in 1.9.9 & was fixed in 1.9.10. Below ist he screenshot oft he message.
Known Bug in TL: http://mantis.testlink.org/view.php?id=6089
Duplicate Bug in TL (which resembles the message in my problem): http://mantis.testlink.org/view.php?id=6221
Our findings:
• A connection between TL database and Mantis database were checked. The connection was established
• But in the Bitnami user logs we could see a warning & an error message stating that a connection could not be established
• Many permutation and combinations were tried like enabling and disabling password (or) giving access rights in every level
Solution:
A patch was inserted in TL application packet. This patch contains commands (on HeidiSQL) which was written in excel sheet. The information in the patch is the same as that is present in configuration of ITM
Functionalites of ITM:
• A bug can be created from TL's GUI – at the moment not working
• A already existing bug can be added to a test case with the status of the bug. The status which can be seen in TL are assigned, resolved and closed – This functionality is working
Re: TestLink 1.9.14 integration with Mantis(interface:db)
OK this is going not to be easy or pleasant
I've already explained to you that posting same topic on multiple areas is wrong, but it seems that you do not care or in your company do you like to do double or triple work.
Why do not add a link to the other post instead of duplication info ? well is a mystery for me.
Then I'm going to do a simple thing => I'm going to lock one post.
Returning to technical matters your are confusing things because you have added a link to an issue related to JIRA INTEGRATION while you are using MANTIS.
In addition the explanation you have provided for your solution is far from clear, you talk about an excel sheet . what excel sheet?
If Bitnami logs said connection can not be stablished may be this is the true.
You have also ignoring suggestion to use SOAP integration.
>> A bug can be created from TL's GUI – at the moment not working
what does this means?
Bug can created FROM TL GUI only if you use SOAP INTEGRATION you can ONLY LINK when you use DB integration.
I've already explained to you that posting same topic on multiple areas is wrong, but it seems that you do not care or in your company do you like to do double or triple work.
Why do not add a link to the other post instead of duplication info ? well is a mystery for me.
Then I'm going to do a simple thing => I'm going to lock one post.
Returning to technical matters your are confusing things because you have added a link to an issue related to JIRA INTEGRATION while you are using MANTIS.
In addition the explanation you have provided for your solution is far from clear, you talk about an excel sheet . what excel sheet?
If Bitnami logs said connection can not be stablished may be this is the true.
You have also ignoring suggestion to use SOAP integration.
>> A bug can be created from TL's GUI – at the moment not working
what does this means?
Bug can created FROM TL GUI only if you use SOAP INTEGRATION you can ONLY LINK when you use DB integration.
-
testtools420
- Advanced user
- Posts: 16
- Joined: Sun Nov 22, 2015 10:52 am
Re: TestLink 1.9.14 integration with Mantis(interface:db)
OK this is going not to be easy or pleasant
I've already explained to you that posting same topic on multiple areas is wrong, but it seems that you do not care or in your company do you like to do double or triple work.
Why do not add a link to the other post instead of duplication info ? well is a mystery for me.
Then I'm going to do a simple thing => I'm going to lock one post.
testtools420: if i didn't care i would not have even written the solution what we found. i questioned in different topics and i thought it is my responsibility to answer in those multiple areas myself. You are right that i could (or) should have just pasted a link. I didn't think about it at that moment because my aim was to pass information which might be useful to others. i respect the moderators and try to follow their way of working coz u guys are doing a great job. My intention was/is/will never be to flood the community or topics with some posts.
Returning to technical matters your are confusing things because you have added a link to an issue related to JIRA INTEGRATION while you are using MANTIS.
testtools420: The issue created is for JIRA (Bug 0006089) and i saw the same issue on MANTIS (1.9.14). I didn't want to raise an issue because it is already a known issue but on different BTS and rather just link the fixed bug to my comments for further information. Bug 0006221 (The message displayed in the screenshot is exactly what i am experiencing) which is already a duplicate issue of Bug 0006089. I thought this issue would have been checked on other BTS too and fixed.
In addition the explanation you have provided for your solution is far from clear, you talk about an excel sheet . what excel sheet?
If Bitnami logs said connection can not be stablished may be this is the true.
You have also ignoring suggestion to use SOAP integration.
testtools420: To be honest it is far from clear for me too because i am not the one who patched it up. The DB admin did that & i am not so good with MySQL DB. The information i have written was my understanding from my DB admin.
I am not ignoring ur suggestion my friend but i work in a company where many different teams are using MANTIS DB. My suggestion should be feasible to everyone. Many of them have less know how on using different kind of GUI or SW. I am not the one to implement these things. There needs to be approval form higher levels.
>> A bug can be created from TL's GUI – at the moment not working
what does this means?
Bug can created FROM TL GUI only if you use SOAP INTEGRATION you can ONLY LINK when you use DB integration.
testtools420: An extract from ITM configuration example is pasted below with my understanding next to it
<uriview>http://localhost:8080/development/manti ... =</uriview> : Means linking the bug from DB integration
<uricreate>http://localhost:8080/development/manti ... /uricreate>: Means creating a bug from TL GUI from DB integration
I was not aware of the limitation of TL's integration with interface DB as u have mentioned. If i am wrong i will update your information and kindly forgive my ignorance & confusion in the post.
I've already explained to you that posting same topic on multiple areas is wrong, but it seems that you do not care or in your company do you like to do double or triple work.
Why do not add a link to the other post instead of duplication info ? well is a mystery for me.
Then I'm going to do a simple thing => I'm going to lock one post.
testtools420: if i didn't care i would not have even written the solution what we found. i questioned in different topics and i thought it is my responsibility to answer in those multiple areas myself. You are right that i could (or) should have just pasted a link. I didn't think about it at that moment because my aim was to pass information which might be useful to others. i respect the moderators and try to follow their way of working coz u guys are doing a great job. My intention was/is/will never be to flood the community or topics with some posts.
Returning to technical matters your are confusing things because you have added a link to an issue related to JIRA INTEGRATION while you are using MANTIS.
testtools420: The issue created is for JIRA (Bug 0006089) and i saw the same issue on MANTIS (1.9.14). I didn't want to raise an issue because it is already a known issue but on different BTS and rather just link the fixed bug to my comments for further information. Bug 0006221 (The message displayed in the screenshot is exactly what i am experiencing) which is already a duplicate issue of Bug 0006089. I thought this issue would have been checked on other BTS too and fixed.
In addition the explanation you have provided for your solution is far from clear, you talk about an excel sheet . what excel sheet?
If Bitnami logs said connection can not be stablished may be this is the true.
You have also ignoring suggestion to use SOAP integration.
testtools420: To be honest it is far from clear for me too because i am not the one who patched it up. The DB admin did that & i am not so good with MySQL DB. The information i have written was my understanding from my DB admin.
I am not ignoring ur suggestion my friend but i work in a company where many different teams are using MANTIS DB. My suggestion should be feasible to everyone. Many of them have less know how on using different kind of GUI or SW. I am not the one to implement these things. There needs to be approval form higher levels.
>> A bug can be created from TL's GUI – at the moment not working
what does this means?
Bug can created FROM TL GUI only if you use SOAP INTEGRATION you can ONLY LINK when you use DB integration.
testtools420: An extract from ITM configuration example is pasted below with my understanding next to it
<uriview>http://localhost:8080/development/manti ... =</uriview> : Means linking the bug from DB integration
<uricreate>http://localhost:8080/development/manti ... /uricreate>: Means creating a bug from TL GUI from DB integration
I was not aware of the limitation of TL's integration with interface DB as u have mentioned. If i am wrong i will update your information and kindly forgive my ignorance & confusion in the post.