TestRail 7.2 changes tooling to turn charts interactive

TestRail 7.2

Test management platform TestRail is now available in version 7.2 and provides testers with the option to jump from dashboard to product activity by clicking on data points for most given charts.

To realise this feature, the TestRail team made use of a library developed by FusionCharts, a company bought by TestRail parent-org Idera in 2020. While things might mostly look the same, the added interactivity will surely be useful to keep track of the testing process and simplify the investigation of failed tests. Teams can for example click into the status bars in the Milestone view to find out quicker which tests need to be run again to reach their goals.

Testers who need to turn their results into reports have some new sorting and filtering capabilities in the print report feature available, so that they don’t have to include all tests and results anymore. The UI in v7.2 also displays buttons to either extract charts as images or get the associated metrics in CSV formats next to each graph, which can then be integrated into notifications or other records.

In other reporting news, TestRail administrators have gained an option to delete reports in bulk and fit scheduled automatic reports with a “run until” date. Bulk deletion has also been made available in the Milestones, Plans, and Runs views, so keeping the interface clean and overseeable has become a bit easier as well.

TestRail and FusionCharts aren’t the only children in the Idera family. In 2019, the company made its probably most well-known purchase in the form of Continuous Integration expert Travis CI. Since then, news about Travis has rarely been great and ranged from a change in pricing felt by quite a few open-source projects to the silent closing down of the company’s diversity initiative Travis Foundation. 

Only last week public repository operators relying on Travis CI had to learn through a security bulletin that sensitive keys, credentials, and tokens were potentially exposed from at least September 3 through to September 10. The issue has since been resolved, but teams that are uncertain about its impact on their own repos can check using a scanner tool shared by Tal Aviel, software engineer at IBM, last Friday.