When reading paths, expand paths that begins with ~ to
user's home directory, like shell expansion do.
Signed-off-by: NRuda Moura <rmoura@redhat.com>

avocado.tests: Add new test "fiotest".

avocado.test: If main test action fails, cleanup still needs to be execu...

So we don't incur in the bug we just fixed.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

This was quite the brown paper bag bug I made: If the
main action fails, we need to call cleanup() no matter
what.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

tests: Add trinity wrapper

Fix xunit bug

Trinity is a popular linux system call wrapper

http://codemonkey.org.uk/projects/trinity/

By implementing it we noticed a number of shortcomings
with avocado that have to be fixed in order to provide
a smoother developer experience.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Doublefree functional

Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

tests.doublefree: Add 'double free' test.

Run avocado with the xunit output plugin, parsing and
verifying the sanity of the outputs.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

The extra double quotes left by mistake in the error
reporting code made the XML invalid. Fix that, and make
sure it stays that way with follow up functional tests.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Signed-off-by: NRuda Moura <rmoura@redhat.com>

Double free performs a build of doublefree.c and execution,
that triggers a double free() function calling, for the same malloc()
region.

The motivation behind this test is to catch libc errors and log inside
Avocado execution (see bug #79).
Signed-off-by: NRuda Moura <rmoura@redhat.com>

Fix bug #79.
Fix by setting environment variable LIBC_FATAL_STDERR_ to 1
to force all libc errors to be redirected to STDERR.
Signed-off-by: NRuda Moura <rmoura@redhat.com>

Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

avocado: Make each test to print its label at the beginning of each test

Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

The heuristics to determine wether a test is a dropin
was wrong since we introduced multiplexing. This patch
fixes it.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Fixes bug #78

In order to make process.run() and friends to log stdout/err
as they are generated, create a BgSubProcess object that has
threads that poll those streams continuously, channeling the
outputs through the logging system, and also storing it in
the result attribute.

Maybe this implementation could use some more love to make
it fully thread safe, with locks. This is just a first
version to show it is possible in a cleaner fashion than
what is implemented in autotest currently.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

When performing tests with the latest LTP tarball, I found
a bad return from Tarfile().extract_file(), that could be
either a badly formed tarball or a Tarfile() bug. Either
way, the archive module was equipped to deal with such a
situation, not failing the test altogether.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Reorganize and reduce code repetition by creating functions
to conveniently log/store tracebacks.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Fixes bug #77.

Replace the basic logging.StreamHandler used to control
avocado stdout for a version that allows us to skip printing
newlines at each message. Then use this stream handler to
log the test label at the beginning of each test, rather
than at the end. When the tests are done, they can now simply
print STATUS strings appropriately, therefore not requiring
to log the test label.

Both the HumanTestResult and VMTestResult classes were
adapted to use this new soluton.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

avocado.utils.virt: Improve implementation.

Improve the current implementation by adding properties
to get status, names and domains. Add support functions
to start, stop, resume, suspend, shutdown, etc machines.

Clear documentation about what kind of snapshot: system checkpoint.
Signed-off-by: NRuda Moura <rmoura@redhat.com>

Add new test "fiotest" based on Autotest fio test.
Signed-off-by: NRuda Moura <rmoura@redhat.com>

Job  class owns execution of start_file_logging()

Signed-off-by: NRuda Moura <rmoura@redhat.com>

Signed-off-by: NRuda Moura <rmoura@redhat.com>

Call start_file_logging inside avocado.job, so Test Results
just need to use output_manager/stream object.
Signed-off-by: NRuda Moura <rmoura@redhat.com>

Run tests on an VM environment set by the user.

Signed-off-by: NRuda Moura <rmoura@redhat.com>

Use option --vm-cleanup to enable the snapshot feature.
Signed-off-by: NRuda Moura <rmoura@redhat.com>

The test runner will start the VM, copy and run the tests,
collect the results and return the VM to its previous
state via snapshots.

Results are shown in the user's machine, transparently.
Signed-off-by: NRuda Moura <rmoura@redhat.com>

Signed-off-by: NRuda Moura <rmoura@redhat.com>

avocado.plugins.jsonresult: JSON test result.

JSON test result output plugin, obsoletes avocado.plugins.collector.
Use parameters `--json` and (optionally) `--json-output <filename>`.
Signed-off-by: NRuda Moura <rmoura@redhat.com>