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

Announcing TestRail 6.2 with Fast Track Editing, Improved Auditing & Save Validation and Dynamic Test Case Filters

We’re pleased to announce the general availability of TestRail 6.2 for both our cloud and server customers, with a number of feature improvements for both Classic and Enterprise TestRail users.

TLDR : The TestRail 6.2 release includes new features and enhancements in the following areas:

  • Fast Track Editing for quicker, more convenient test case editing.
  • Save validation for performance and auditing improvement.
  • Dynamic test case filtering on your test runs for improved flexibility when defining test runs.

We added a few fixes and minor additional features along the way. Keep reading for the details!

Fast Track Editing

If you spend a lot of time designing or executing tests inside of TestRail, you’ll be super happy to learn that we’ve streamlined the test case editing functionality. From 6.2 onwards, you can edit the content of your tests without leaving the fast track view (split-pane mode) - just by clicking the new Edit button while viewing either the case, or the test itself in the context of a run.

Once the fields are enabled, you can make whatever changes are needed before saving them - both while viewing your test case, or while viewing your test in the context of a run; making in-flight changes to your tests much easier and faster.

A common complaint from testers was that, if they needed to make a change to a test that was being executed, they had to go all the way back into the case in order to make the necessary changes. With this enhancement to the TestRail workflow, you can just make those changes directly, without leaving your current working context.

A massive improvement, we hope you’ll agree!

Save Validation

While we were making the Fast Track Editing changes, we also had a keen eye on improving the overall performance of TestRail. We wanted to make sure that the number of calls to the database was kept to a minimum, thereby improving the user experience for everyone.

We also wanted to make sure that any changes being recorded in the TestRail Enterprise audit logs were completely accurate - eliminating the possibility of audit logs being created when no actual changes had taken place.

For this reason, we implemented Save Validation on all the TestRail views. From 6.2 onwards, you won’t have the option of saving an entity (a case, a result, a milestone, a run, a custom field, an administration setting etc) unless a material change to that entity has been made.

Dynamic Test Case Filtering

In TestRail 6.2, we bring you another big change for TestRail; the option to apply a Dynamic Filter when creating your test runs.

image

Prior to TestRail 6.2, you could either select all test cases, or a set of specific test cases. Now, with Dynamic Filtering, you can simply define the filter you want to apply to your test cases, and any matching cases will be included in the run.

Here’s the rub though; any cases that are added to your suite or project, or changed such that they meet the filter criteria will also get added to the run. Dynamically!

Cases that get added to your dynamic run in this way will be highlighted in your runs with a new Dynamic Filter icon - so they’ll be nice and easy to spot.

Please note when using this feature that we still consider it a beta addition to TestRail. We expect to iterate and improve upon the functionality in future releases. For more details about using the feature, please refer to the documentation and caveats on our docs page, and please do let us know if you have some suggestions for improvements!

Miscellaneous fixes and enhancements

The TestRail 6.2 release includes a number of fixes and a couple of enhancements we added along the way:

  • We’ve made some improvements to the way we handle reports and report jobs in the database, ensuring that old reports and scheduled jobs are fully removed from the database once you delete a project.
  • We also fixed a bug that caused cases to be duplicated in the TestRail database when closing runs via the close_run API endpoint.
  • We identified a bug with the push defect dialog view when there was a required custom result field set. Going forward, required custom result fields and the push defect dialog should play together nicely!
  • We also fixed a problem with the Jira environment field that prevented the push dialog from being displayed.
  • Our TestRail for Jira plugin wasn’t allowing users to add Cases or Runs from Jira when using recent versions of Firefox. That’s now been fixed.
  • We fixed the update_project API endpoint so it works correctly when you don’t pass the 'name’ attribute in your request.
  • We also added a new feedback option. If you have some TestRail feedback, and want to give us a Net Promoter Score (NPS) in the process, you can now do so via the TestRail Survey option in the TestRail Help & Feedback menu.

Getting TestRail 6.2

Updating to TestRail 6.2

  • TestRail Cloud instances are automatically updated to the latest version. You can check your version via the TestRail Help > About TestRail menu item.
  • If you are using the on-premise version of TestRail, you can update to the new version as usual by installing it over your existing TestRail installation (there’s no need to uninstall your existing installation). The database upgrade wizard is automatically started when you access TestRail with your web browser. Please see the update instructions for details: http://docs.gurock.com/testrail-admin/installation-upgrading/
  • If you’re using Docker, please refer to the instructions here: http://docs.gurock.com/testrail-admin/installation-docker

TestRail Enterprise

Please ensure you make a backup of your current on-premise installation before upgrading to the new version.

Cheers,
Simon

Sending invitation email when add single user seems to be removed, any reasons why?
@sjpknight