<elopio> I'll just list some things I would like to see. We should probably choose only the ones that allow us to go faster and safer.
<elopio> the tests should be independent. You should be able to run them in any order, or select only one and get a good result.
<elopio> we need a better framework for setups, assertions, and test case definition. Moving to go would solve this, of course. There are also some bash frameworks, but (...)
<elopio> we need a better report of the results. subunit would be awesome, but junit or anything like that would do.
<elopio> the tests should define their own environment as much as possible. Asserting for regular expressions because we don't fully control the versions we are installing or the messages we are getting back is not so good.
<elopio> and I would like the tests to be more readable, at least the ones that are end-to-end from the point of view to the user.
<elopio> like have every statement in the test be an action, and that would make the test look more like what you get with behaviour-dd.
<elopio> finally (for now), we need to start thinking about tests that need actions both from the host and the testbed, like making sure that you can open webdm from your PC.
<elopio> maybe it's enough to make sure that it works in localhost, and that you can access the board's ip from outside. Or maybe we need an end-to-end test also for that.
<elopio> mvo: do you have any items you would like to see in the tests?