This target checks very basic function of avocado and is used
incrementally in travis to verify this functionality for each
commit up to the origin/master.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Last time it did not work, let's try it again to see whether it works.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

The new plugin architecture depends on setuptools entry points being
properly registered. These entry points are defined in a `setup.py`
file, as the `entrypoints` parameter, but they are only effective when
they become an `entry_points.txt` file inside a
`<your_project>.egg_info` directory.

This can happen in two ways:

1) installing the package, that is, running `$ python setup.py
install`

2) enabling the development mode, that is, running `$ python setup.py
develop`.

The approach chosen here is the latter, because it's faster, doesn't
require a full install and points to the checked out source code tree.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Those packages are not being installed anyway, and do not
interfere with general CI testing.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Add a check for leftover tmp dirs after our unittests run.
This will let us to catch mistakes made during their development
(for example, forgetting to clean up temporary dirs created during
setup stage). Add that to `make check` and Travis CI jobs.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

The unittest module, and unittest2 backport on Python 2.6, is capable of
finding unittests and running them. So, effectively, we do not need nose
at all.

This patch removes the dependency on nose, replacing the run script
with a version based solely on the unittest module.

One change of functionality is that run now looks and runs tests in the
standard selftests directories (unit, functional, doc), and does not
accept command line arguments. If one wants to run a subset of them,
it's pretty easy to just use the unittest module for that:

 $ python -m unittest discover -s selftests/unit
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Use addons to install packages instead of sudo.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

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

This check is being added to both to checkall and to travis.yaml,
s o that either in local and remote (CI) checks this can be quickly
flagged.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Add a new python 2.6 target so that we can make sure
avocado works on older distros (our specific focus here
is RHEL 6, but of course, we expect the work on RHEL 6
to be useful to other distros sticking with older versions
of the python runtime).

In order to do that, we added a new 2.6 related requirements
file, and changed the requirements a bit so that it all
works under the particular Travis CI environment.

Changes from v1:
 * Per ldoktor's suggestion, use conditional install of backports
   using $TRAVIS_PYTHON_VERSION
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

In case of timeout we might want to get the name of the last running
test, therefor setting verbose mode for them.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Since we have to install extra packages in the VM, some
of which might have been moved/updated, apt-get update
turns out necessary.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Document requirements.txt, split it into 3 files:

 * requirements.txt - Used to install deps for functionality
 * tests-requirements.txt - Used to install deps to test avocado
 * travis-requirements.txt - Used exclusively for Travis CI jobs

Also, clean up and simplify Travis install job section.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Usually coverage and xunit are unused and only slows down CI. This patch
disables it by default. In order to get coverage please run
`selftest/coverageall`.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

This patch wraps LZMA archive in order to work with python 2.7 tarfile.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

That change has to be made all at once for the sake of
bisectability. Update avocado.job and the multiplexer
plugin with the new multiplexing library code.

Also, update functional tests, the avocado sample tests
with the new YAML based config files, and the requirements.txt
file with the new prominent dependency of avocado, PyYAML.
Signed-off-by: NRuda Moura <rmoura@redhat.com>

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

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

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

In order for people to run all avocado tests at once,
move and reorganize tests under a directory called
selftests. For someone to run all self tests in
avocado, one would have to execute:

    selftests/run selftests/all

This is a shortcut for developers. .travis.yml
was also updated to run tests based on the new
directory structure.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

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>

Avocado should handle gracefully and not crash.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

In order to avoid errors and garbage creeping up in the
code base, look at the sphinx build output for errors and
warnings, and fail if we found any.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Let's certify that Sphinx documentation can be properly
built as well.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Let's actually execute avocado in scenarios where we
know what the produced outcome is:

* Execute a list of tests that pass, expected rc == 0
* Execute a list of tests where some fail, expected rc == 1

Although very simple, it's already a good start of
functional testing of the code during each travis job.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

It'll be necessary for the data_dir unittest.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Create the .travis.yml file, along with nose config
file and pip requirements file.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>