Running Tests

relicx allows users to validate their test runs before implementing in order to sort out any data or parameterization issues after validation, relicx offers several options for regularly running tests whether manually kicking off test in the relicx platform or integrating tests in your ci/cd pipeline, users can execute tests directly within relicx running tests validate test if you have created a new test, it will be marked as a draft after creation you can select the test and click on the validate test button in the upper right corner this will run the test for the first time to help you validate any data and parametrization issues once the validation run is successful, the test can be activated clicking on the validate test will bring up the test run modal, where you can specify environment against which the validation run should be performed relicx will pick your pre release environment by default but you can pick any environment from the pick list execution location you can run tests from our default cloud location if your test environment is accessible on the internet relicx also supports a private tunnels for test environments that are behind a firewall test parameters default to values entered by the user, unless those inputs are redacted you can update the defualt values based on the data available in your test environment the updated values will be saved for the future run run a test once a test has been validated, the option to "run test" will automatically appear tests with this option have already gone through the validation process environment parameters environment parameters allow users to override individually defined test parameters in order to make bulk editing easier once these test have been executed, running states will show where the test in the execution timeline parameters can be defined at the applicaiton environment level for example, the base url for staging will be different than the base url for production and can affect the outcome of the test relicx handles these changes across environments by allowing parameters to be assigned at the environment level so that if the location where the test is being run against changes, the user does not have to remember which parameters will need to be changed as a result below "environment override" and "test default" are denoted by which variables will be used based on the environment chosen