Application tests » History » Revision 6
Applications tests are designed to test that the applications work properly. Here we check that the workflow ties together okay, produces correct physics, etc. The sorts of things anticipated to be done at application level are:
- Integration testing: check that we can work through a workflow okay - units tie together correctly and the code interfaces external libraries correctly
- Physics validation: simulation produces expected distributions and we reconstruct with appropriate residual distributions.
- Load testing: check that we can run big data files or for long periods without crashing
Usually application tests will check code executing at the level of applications in the bin directory. This is not enforced, but it's probably good practice to get in the habit of exercising these applications as part of the testing regime.
Making a test¶
Application tests are done in python. There is a directory tree tests/integration/ that contains the application tests. There is a script tests/integration/integration_tests.bash that runs nosetests. This walks down the tree looking for folders like test_<dir> and files like test_<dir1>/test_<name>.py. It executes them in the same way as for the unit tests (look at the examples, or look at the unittest documentation).
Physics validation plots¶
There is a directory in tests/integration/plots that is intended to contain physics validation plots. If you do make some plots, for example plotting emittance change through the experiment or detector residuals, it would be great to put those plots in here. As the code base matures, I would like to publish these plots along with the code release, by way of "proving" that the code works. Can even add some comment/legend on what the plot is and what it should look like to make these plots standalone - but at least if a question comes up, we should be able to push a link with a few lines of explanation.