We want avocado tests to not require specific directories,
the user should be able to arrange them in the dir structure
they see fit. Also, if a test requires data, we suppose their
data dir is located in the same directory as the source file,
with the name:

[modulename].data

Re arrange the test dir to reflect this new structure.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

They raise the following exceptions:

1) TestError (failure)
2) TestNAError (skip)
3) TestWarn (failure)

The corresponding functional tests for them go
in the Travis CI file.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

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

Improvements for using xUnit  with Jenkins (Junit).
Now the actual XML result is handled in class XmlResult.
Also minor fix (cosmetics) in tests.failtest.
Signed-off-by: NRuda Moura <rmoura@redhat.com>

I went through all python files in avocado code, and
some changes were made:

* Files entirely written by the current avocado dev
team were changed to be GPL v2+
* Files with a significant portion of code derived
from autotest remain GPL v2 strict, and original
authorship was re-established
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

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

Introduce the job.main() entry point in all avocado
test modules. This way all of them can be
executed. The functionality depends on
having avocado installed system wide, though.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

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