* Related tests are stored in a python module `test/<testmodule>` to create a suite of tests. All tests are stored in files test_*.py, there can be many tests per file, and many files per module
* Each test module has a rspec.yml that provides the baseline "fixture" for the tests in the module
* Tests are executed against fixtures. Fixtures are modular "setups" created for a test, that are inserted into the python code using dependancy injection. This offers more flexibility than the *unit style testing. The baseline deployment is created using `vagrant up` with an appropriate rspec, and the pytest fixture reads the rspec.yml and makes the configuration available to the test.
* Tests are executed from a guest VM (not the host) in the repo root using the command `pytest test/<testmodule>`
* Pytest will scan the directory for all tests including in files test_*.py and run them
#### Creating a deployment for a test
To set up a simualtion of the adaptive streaming use case scenario
...
...
@@ -64,7 +81,9 @@ The **clmc-service** vm includes influx, Kapacitor and Chronograf. The following
* Chronograf: 8888
* Kapacitor: 9092
#### Running the simulation using the fixture
#### Running the streaming-sim test
**needs to be updated once we have this in pytest format**
"""Returns the service configuration deployed for the streaming simulation test. In future this needs to be a parameterised fixture shared with other rspec.yml based tests"""