Test Suite
Test Suites provide a way to group tests together. This allows for a batch of tests to be run all at once, instead of having to indivdually kick off tests. This is especially useful in CI/CD applications or where different types of tests need to be run together.
In order to create a test suite, select one or more test from the Main Test listing page. Once the desired tests are chosen, choose "Add to Suite" at the bottom of the page.
To view all of the existing Test Suites, select the "Suites" option from the testing menu.
A test suite can be executed against any of the parent application's test environments. Tests in the suite are run with defaulse parameters and can be bulk edited when preparing to run the suite.
By defaults the sequence number for tests in a test suite are denoted the be "50". This just means that the order of execution for that test does not matter. However, if a user desires to execute tests in a sequential order, they can change what number is executed first through the pencil icon next to "SEQ NO" in the Details page of the Test Suite. The maximum number of parallel test executions can also be changed here, the defualt for this value is "100".
You can designate a test suite as "Primary". At any given time, only one test suite can be designated as a primary test suite which is used to determine the release risk score. Relicx recommends that you integrate your primary test suite with your CI/CD release pipeline. Before every release, you can execute the primary test suite and based on the risk score decide whether to go ahead with the release.
The primary test suite can be identified by a star icon next to its name. This is also the Test Suite that is used to verify the "Test Status" in the Flows Page.
To change the primary test suite, click on the star icon next to any test suite. You will be prompted with a cautionary message that this may impact your release risk score.
