Rewrite tests #27
Description
The tests have become extremely fragile. They must be re-written to:
- Separate them properly out into individual test cases.
- Work against the library APIs primarily
- Test the commands for correct output (stdout, stderr, returncode, effect on components; etc.) in relation to input
- More cleanly manage starting and stopping the name server, manager, and components, to guarantee a clean slate for each test.
A major cause of the fragility is the fragility of the rtcd daemon and component managers. They regularly segfault in the middle of tests.