Component testing

[nokome]

Each component should have a test method which searches for tests in the component e.g.:

• a tests directory
• tests.* files e.g. tests.R

The tests will get called by a system call from C++ e.g python tests.py. The tests should load the component, run tests and output a standard format output file (probably JUnit XML). The component repo should be tagged with:

• datetime of test
• number of tests performed; number passed (parsing of XML can be done in C++)

That allows any updates of a local component to only use the latest version which has passed all tests. Tests will get inherited when a component is forked. Testing is most likely to be useful for stencil because they often contain code.

The might be a specific case of a general type of component methods that execute corresponding scripts in the component's directory e.g.

• method test() runs test.R dumping stdout and stderr to a unique filename in the tests subdirectory which is parsed by test() for results; method tests() parses all files in the tests subdirectory.
• method update() runs update.py .... (for updating Tables, Arrays etc)