Rosetta 3.3
Different way to run unit tests.


Last edited 10/10/10. Matthew O'Meara

There is two option to run unit test:

Run all unit test suits at once.

This is the preferred method for running the Unit Tests before committing changes to Rosetta. To do this,

python test/ <optional command line args>

Important optional command line arguments include:

Currently run script execute following tests: apps, core, demo, devel, numeric, ObjexxFCL, protocols and utility.

Run A Single Unit Test or Test Suite

This method is useful if you working on unit test debugging, and want to save time by skipping some tests. To run all tests from a single test suite, use the --one option to test/

Sometimes it is necessary to run a test by hand. To do this, you need first to locate it executable. Currently all quilted unit test executable located in: build/test/... directory, executable files named by adding .test to the unit test suite name. Note: path may vary depending on platform you working on, for example for 32 bit Linux compiled with gcc it will be: 'build/test/debug/linux/2.6/32/x86/gcc'.

Test executable should be running from the build directory, this is important since some unit test will try to locate additional files needed using relative path. Example of command to run only core test executable:

cd build/test/debug/linux/2.6/32/x86/gcc

./core.test --database ~/minirosetta_database --mute core

If you want to run only one test or just one suite - you will need to supply name of the test function or name of the suite as a *first* argument to the test executable. Here the example of running only test_simple_min and suite MyTestSuite from core tests:

cd build/test/debug/linux/2.6/32/x86/gcc

./core.test test_simple_min --database ~/minirosetta_database --mute core

cd build/test/debug/linux/2.6/32/x86/gcc

./core.test MyTestSuite --database ~/minirosetta_database --mute core

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Friends Defines