Turn your manual testers into automation experts! Request a DemoStart testRigor Free

Release Notes: Disable in bulk, View Steps, Exclude labels, Folders for rules, Individual runs via API, Execution reports

Last month, we released several exciting new features.

Disable/Enable test cases in bulk

Users can now disable and enable test cases in bulk.

  1. Click the Select multiple button in the Test Cases section. If necessary, use search filters to help sort out the right ones.
  2. Click the checkbox on the left of the test cases to disable/enable.
  3. Click the Disable/Enable button

View steps

We added a View steps button. This button does not allow users to edit steps, but greatly improves the user experience by allowing steps to be viewed while the case is in progress or where there were not previously accessible. Places where the button can be found:

  • Hooks
  • Test cases
  • Test cases executed in previous Runs
  • Inherited test cases

Run by labels (Exclude labels)

Users can now specify which test cases NOT to run by their label.

  • To exclude labels from retest API use "excludedLabels": [ "some-label", "other-label"
    as parameters on data.
  • To exclude labels via UI, go to Additional run settings in the Test Suite
    section and enter the label(s) to exclude into the Do not run tests
    with the following labels (comma separated)

Folder structure (for Reusable Rules)

Reusable rules can be organized into folders.

  • When using rule search filters, testRigor will consider the rules in the folder that is currently selected.
  • To search for rules regardless of folder location, select All folders from the folder filter dropdown.

Run individual test cases via API

Customers have the option to indicate which test cases they want to be triggered in a run on retest API passing "testCaseUuids": ["UUID-1", "UUID-2"] as parameters on data.

Report for test case executions (data sets, multiple browsers, multiple devices)

testRigor now reproduces a report at the bottom of each execution page for test cases executed on data sets, multiple browsers, and multiple devices. The purpose of this feature is to allow users to easily understand the results of cases with multiple executions or combinations.