Inconsistencies with configurations handling in the flow test is annoying

[benlapETS]

As it is now, the flow test cannot be run if we got trailing config from other cases. We have to cleanup everything manually each time we want to run a test (and backup what we would like to keep for later recovering it). This is due to the fact that we properly filter examples needed, when gathering and removing it, but we use sr start, stop, cleanup to do the rest which use everthing. I see three way to fix this issue:

• We start each component separately within the flow test script (the same way we are filtering component with add and remove), this is my first idea and this does not work well because of issues with logging that are too complicated to solve right now, because of poor design Logging structure is poorly designed and poorly implemented #185 .
• We use a custom config path for testing (ie. ~/git/sarracenia/sarra/example/*/<flow_test_file>.conf), thus directly from examples config instead of copying them...
• We backup the config before the flow test and we recover everything after it (ie. using tar).

[benlapETS]

We decided to go with the by component solution (1st option) and I figured out to manage the logging by piping output through the flow scripts, to log files related to flow_ (action in {setup, cleanup}). It cleaned a bit the output of the flow test in the console while keeping a trace of the last run problems.

[benlapETS]

Nothing bad happened with our flow test after this implementation, resolved.