Which is the preferred way of saying that a parameter is a file,
and, makes pylint happy on Python 3.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Recent pylint update is more pedantic about module level spacing. There
are no changes to code, only couple of extra spaces to make it happy.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Usually we want to include all the commits of related projects to the
report. Let's add a convenient way to list all siblings HEAD shas.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

This is an automated mass import cleanup across all
avocado source files:

1) Imports follow the order:
 * Standard library imports
 * Non standard library external imports
 * Internal imports
 All separated by a single line
2) One line between imports and the rest of the code
3) Remove unused imports in the process
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Handle Ctrl+C while executing the test plan more cleanly.
Also, make each code path executed by app.run() return
either 0 on success or 1 on failure, so that we get
proper exit codes for the script.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

The description might contain valuable information.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Some test routines can not yet be easily automated in Avocado, and for those, we
rather test things manually then not at all.

The idea behind this tool is to use a predefined test plan (a simple JSON file)
that has test names and descriptions with how to perform the test and what to
expect. The tool will ask for the results for each test (either PASS, FAIL or
SKIP) and possibly additional notes. These results will then be saved to a JSON
file or to a human readable report.

The human readable report can, for instance, be part of a release commit message,
or if preferred, the JSON result file can be committed to keep track of what is
working and what is known to be broken at a given time.
Signed-off-by: NCleber Rosa <crosa@redhat.com>