#23 unit-tests for services

[Dmitry S. Makovey]

cpacman needs some sort of unit-tests for services on the host which could be run whenever things are changed on that host. For example:

1. ${CPACMAN_HOME} create "tests" directory containing test scripts. (or maybe tests/{local,remote} for 2 different types of tests)

2. under ${CPACMAN_HOME}/servers/foo.com create "tests" directory which containes configuration values for test scripts with the same filename under ${CPACMAN_HOME}/test

3. every time we run "confirm.py" run all tests for which configuration files exist under ${CPACMAN_HOME}/servers/foo.com/test after real pkgDB injection.

It doesn't seem proper to fail "confirm.py" if tests fail, but it does seem important to notify user of a problem, and here's why: user have already deployed packages on remote machine and refusing to register them locally just makes pkgDB inconsistent, however user must know that deployment introduced problems to the services.