1. Do the test the right way. We were checking the exact output in order
to validate the correctness of the cli. Randomness in FAK and other
issues interfered with this test schema. We now check specific output
string in the whole output.
Add test for the outomatica mode and the flow mode of the cli.
The downside to this test is that it probably wont work when
firstaidkit is installed in the system. The reason for this is
that it brings all the plugins that are installed in the system,
this means that the outputs will be different when the commands
are run. This must be addressed and if this turns into an
issue we should simply turn the test off untill its fixed.
Moreover this will make the build fail when changed that modify
the system messages are introduced. So from now on when those
types of messages are changed, the test mush be changed as well
(Which basically means changing the outputs files).
1. cli.py : add main test classes.
2. cli/outputs/*: these are the outputs that the various commands should
have when called with the plugins under testsuite/cli.
The files are called like the commands.
3. cli/plugin*: two plugins to server as the information providers. They
don't do anything interesting.
4. __init__.py: export the new test.
- Indendtation should be 4 spaces. There was a function indented with 8 spaces. - Lines should be shorted than 80 chars. It just looks pretty :) Think of terminals whith only 80 char of length. Think of debuging in rescue mode. - Change also the print statements. Just getting ready for python 3000. - Get some spaces between elifs - There should not be any lines ending in spaces. - This can all be read in the python code conventions http://www.python.org/dev/peps/pep-0008/
This will avoid the situation where old pyc or pyo files don't work with some python interpreter version.
This is necesary to run the testsuite