Join 34,000+ subscribers and receive articles from our blog about software quality, testing, QA and security.
 

Defect status information in 3.0 release?


#1

With version 3.0, does TestRail now support viewing defect status without mouseover? Is this now a piece of data that can be selected as a column (not just the defect ID)? Is this a data point that can be used in the new reporting section?

Specifically looking for the ability to map defect (JIRA) status to tests, group/filter/sort on it and display something like failed tests with defect status of resolved (for example). Is this functionality present in the stock reports, if not within the execution/definition interface of TestRail itself?

Either of these topics would go a long way towards this as well:
http://forum.gurock.com/topic/921
http://forum.gurock.com/topic/1251

We currently don’t have a TestRail license, previously due to a few areas it was felt TestRail was lacking, but now it amounts to just this one item.

Our “required, but not yet there” list for TestRail is now:
[list=]
[
]Integration with JIRA for defect status without “mouseover” being required for retrieval (filter/sort/report alongside test information)[/]
[
]DONE IN 3.0 - Completed reporting interface, with ability to create custom reports and reasonable set of semi-flexible out of the box reports[/]
[
]DONE IN 3.0 - Completed API for automated tests and data retrieval/modification from outside systems[/*]
[/list]

Features that are currently important/useful yet missing, though not required currently:
[list=]
[
]Better definition/documentation on “Forcast” predictions, how is determined, etc.[/]
[
]Access to Defect (JIRA) field data through UI Script[/]
[
]DONE IN 3.0 - Less Flash usage throughout, especially where navigation is concerned[/]
[
]DONE IN 3.0 - Standardized API type, inclusion in TestRil out of box, with documentation and user auth[/]
[
]DONE IN 3.0 - Custom naming of statuses (including system statuses)[/]
[
]DONE IN 3.0 - Out of the box “Daily Summary” type report (exec level, “pretty colors”)[/]
[
]DONE IN 3.0 - Ability to email and/or print stats and aggregate information (report and/or within existing interface)[/*]
[/list]


#2

Hello,

Thanks for your posting. That’s still not supported unfortunately out of the box but it would be possible to implement this as a custom report and integrate it into the new reporting area (just like the built-in reports). We currently work on finishing the documentation for writing custom reports and it’s similar to how you can already write custom defect plugins:

http://docs.gurock.com/testrail-integration/defects-plugins-custom

We are also happy to help with this, of course.

That said, it is also planned to support this directly as well but it didn’t make it into this release. One reason why this is not included as part of the standard tables is that looking up the status for each bug/issue requires an API request to the issue tracker and this can be very slow. While this would be okay for the reports (which are generated asynchronously in the background task) this wouldn’t really be acceptable for normal pages in TestRail.

It is planned to look into this, though, and the option we currently favor is to use some kind of status cache for the defects, e.g. via a database table, but we aren’t there yet. I hope this explains the current situation and please let me know in case you have any further questions or feedback.

Regards,
Tobias