Testopia for Jira?
Does anyone know of a tool that integrates testopia with Jira?
Has anyone ported the code to Jira and can provide the code?
Does anyone know of a tool that integrates testopia with Jira?
Has anyone ported the code to Jira and can provide the code?
Comments
Testopia is a Bugzilla extension, so i don't think you can find its integration to Jira
Hi Liya thanks,
Yes I know its a Bugzilla plug-in. Unless I find a matching plug in for Jira I have to port it myself ...
Then you'll have to rewrite it completely.. :)
We can try to use ALM 2.0 to create the integration. What this means is to write simple plugins that will embed jira and testopia pages in the ALM gui (tabs). Then write a plugin that will rewrite links from testopia so they go to jira instead of bugzilla.
This can be done by attaching our own javascript file to the testopia page where the javascript file either rewrites functions in the original testopia page, or iterates over the component collections and reconfigures them. Note that adding the javascript reference will be done on top of the existing testopia, not by going into it and changing its code.
Embedded systems can be shown standalone (outside of tabs in the main ALM view), so the systems will still look independent.
The downsides are that ALM is not yet production ready and this is our first real use case.
I'm not sure javascript changes will be enough here - Testopia uses some of Bugzilla data structures, and the server side part works against Bugzilla database (mysql).
I suggest check other test management tools for Jira
Check out this forum discussion http://forums.atlassian.com/thread.jspa?messageID=257249015
I don't think the goal is to make testopia work over jira, just allow more integrated work between them. that is, allow testopia cases to link to jira bugs and maybe link from jira bugs to testopia cases.
I think it won't be enough - you would want to use the Products and Versions for your Test Plans/Cases.
obviously, what i suggested was very raw, not a complete design.
still, about products and versions. from a quick look, products are loaded using a function called ProductStore that creates an object. the object uses a url to fetch the list of products. if we change it to use a different url....
again, more research and design is needed. the question is whether this is something the client is willing to try out.
You're right.
I didn't get into technical details as well. In general, I don't think that Testopia is such a good tool, so i think it's better to look for a tool that already integrated with Jira before considering doing anything with Testopia.
Thank you both for your comments. There is really no alternative to testopia, I searched and searched and came up with nothing. Moreover, the client insists on having testopia or a very similar tool. I shall present the decision maker with this information and see what he has to say.