Currently, unity runs tests declared in the cue.mod/tests manifest against a copy of the repository that contains the CUE module under test (setting an appropriate working directory at the start of the test).
This allows the tests declared in the manifest to run concurrently, but most importantly for us to be sure the tests are independent of each other.
However, it does mean that any side effects of a test (e.g. the results of cue export) are not reflected within the repository from which the tests originated.
This might well prove to be more of a pain than the pain of tests interfering with each other.
This raises the question of the overlap between:
the test scripts declared in the manifest
regular shell scripts that might well be defined and used as part of regular administrative tasks in a project
cue cmd commands
It's not clear at this stage where the lines need to be drawn (if at all).
Currently,
unityruns tests declared in thecue.mod/testsmanifest against a copy of the repository that contains the CUE module under test (setting an appropriate working directory at the start of the test).This allows the tests declared in the manifest to run concurrently, but most importantly for us to be sure the tests are independent of each other.
However, it does mean that any side effects of a test (e.g. the results of
cue export) are not reflected within the repository from which the tests originated.This might well prove to be more of a pain than the pain of tests interfering with each other.
This raises the question of the overlap between:
cue cmdcommandsIt's not clear at this stage where the lines need to be drawn (if at all).