... especially when the problem is supposed to be fixed already:
we do want to make sure it is, and that no regression occurs.

This includes some guidelines for writing tests.

This reverts commit acd93758.

syslinux is already listed on the above line.

See recent commit with same commit subject.

Instead we let the test suite use its default (which is the same as
what --newest-iso was supposed to do) when no --iso is given.

Otherwise these tests fail for me.

Now all .feature:s reside directly in the root of features/, and they
are differentiated with tags: source tests are tagged '@source' and
product (i.e. Tails ISO image) tests are tagged '@product'. These tags
then set up the appropriate environment on a feature-by-feature basis.

In these scenarios the shutdown applet menu can be blocked by the
"running in a VM" notification.

We want to ignore any exception of the yielded code block, but if the
Timeout::Error from the timeout wrapping the loop is thrown when the
code block is being executed that may lead to an infinite loop (if the
code block never returns true). Hence we need to handle that exception
differently. This assumes that the code block cannot throw
Timeout::Error.

Conflicts:
	wiki/src/todo/automated_builds_and_tests/cucumber.mdwn