To test-drive YourBase Test Acceleration’s test selection without actually skipping any tests, you can run it under the “Observation Mode”.
When “Observation Mode” is set, in addition to running all the tests, YourBase Test Acceleration will also monitor if its test selection would have skipped any tests that would have failed. As its output, it will print out the names of any tests that would have been incorrectly skipped.
Table of contents
You can follow the below steps to verify:
- Install YourBase Test Acceleration.
- Enable Observation Mode in your environment. For example, if you use a bash shell to set environment variables, you can set is as follows:
Else if you use an environment specific configuration file, set YOURBASE_OBSERVATION_MODE in that file.
- Run all your tests as usual.
- Check your logs manually:
- If YourBase Test Acceleration is accelerating tests correctly, it will log the total amount of time that could have been saved, to stdout or your log file.
- Else if, it’s accelerating tests incorrectly, i.e. it’s skipping one or more tests that would have failed, then it’ll complain about this loudly by outputting the details of the errors in your log file or your shell-prompt. Note that if this happens, it means that there’s a bug in YourBase Test Acceleration’s tracing or acceleration. Please report these to firstname.lastname@example.org.
- Ensure that you disable YOURBASE_OBSERVATION_MODE only after you’ve verified that YourBase Test Acceleration accelerates tests correctly.
We strongly recommend that you run YourBase Test Acceleration in the “Observation “Mode” every time before rolling out code-changes to your production.