forked from biologic/stylus
-
Notifications
You must be signed in to change notification settings - Fork 0
/
TESTING
21 lines (14 loc) · 1.15 KB
/
TESTING
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
==================
Testing
==================
======================
Whole-Application Test
======================
The script tests/collect.py will create a test_data directory containing the results of running stylus against the sample plans and genes. This should be run while the code is in a known working condition.
The script tests/verify.py will run the plans and genes checking them against the data stored in test_data to make sure nothing has changed. This should be run after making changes to make sure that the behavior of Stylus has not changed.
The test_data is deliberately not included in the repository because I don't think I can be sure that the behavior of floating point (and possible other items) will be consistent across different computers or platforms. For that reason, any working copy needs to generate it own copy of test_data
The scheme also doubles as a quick and dirty performance testing scheme by timing the runtime of tests/verify.py.
=========================
Unit Testing
=========================
The build process will produce an executable src/test/run_tests which will execute the unit tests and report if anything goes wrong.