This will do functional testing of avocado behaving
according to the use cases specified.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Make sure avocado is behaving the way we expect on different
situations:

 * Simple executable test
 * Non executable (not a test)
 * Simple avocado test
 * Simple avocado test (non executable)
 * Buggy test
 * Buggy test (non executable)
 * Py module
 * Py module (executable)
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Now that we don't enforce a silly correspondence test
module name -> class name, we can call our test classes
whatever we want as long as it inherits from avocado.test.Test.

Let's then rename our tests to something more CamelCase.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

When avocado analyzes a path that looks like a python module,
first it'll try to import the module, then look for an appropriate
test class inside this module. Improve the test load heuristics
by looking for classes that inherit from avocado.test.Test, and
not the rudimentary detection, inspired by autotest.

If the module import went fine, but we simply can't find an
avocado test inside of it, if the file is executable we'll
try to execute it as a simple test. If it's not executable,
it'll be considered as not a test (same count as not_found tests).
If we can't import the module due to a test bug, once again we'll
check if the file is executable - if executable, we'll execute it
as a simple test, if not, we'll consider it a buggy test.

Unfortunately there's no way to tell apart a buggy avocado test
and a random py module with a bug, so both will be treated the same.
Adjust code to reflect this new status.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

The code was unnecessarily convoluted. Be simple and
straightforward.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Fix compatibility problem with vm and remote plugins and htmlresult feature.

At the time it seemed a good idea to have an exit_code.AVOCADO_CRASH
integer, but since we also use it for option validation errors, it's
misleading a good deal of the time. Let's use a more generic
AVOCADO_FAIL, update usages and description.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Due the changes on RemoteTest class, use the attributes start and end.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Fix compatibility with htmlresult on remote and vm plugins:

* Use time_start/start and time_end/end attributes.
* Move self.result.end_tests() close to tear_down() in order
  to have sysinfo files unarchived.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

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

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

Component Isolation: Linux Distribution Support [v1]

[V1] Redirect output fix

Verify if we are not printing terminal codes inside
redirected outputs, when we in fact shouldn't.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

We were printing a throbber even though output was being
redirected, mainly because throbber was not following the
same rules as the rest of the colored output. Fix that
problem.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Trivial misc license/doc commits

The file was introduced by commit e1363982, but
is missing a proper license header.

Minor improvement to the initial description in the man page
and update links to point to the (new) project page everywhere.
Signed-off-by: NAdemar de Souza Reis Jr <areis@redhat.com>

Avocado itself is released under GPLv2 (explicit version), but most of the code
is currently licensed under GPLv2+, so make that clear in the documentation.
Signed-off-by: NAdemar de Souza Reis Jr <areis@redhat.com>

avocado.runner: optimize the run of quick tests

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

If the test is very quick, it may run in less than 0.1 secs, which is the
minimum time we wait for the result to be available in TestRunner::run_suite().

Since utils.wait_for() accepts a "first" parameter, documented as "Time to sleep
before first attempt", let's use it with a very aggressive low value, just
enough for the main process to be put to sleep by the scheduler and give time
for the other process to run.

Benchmark using multiplextest:
    $ TESTS=""; for f in $(seq 1 100); do TESTS="$TESTS examples/tests/multiplextest.py"; done
    $ time scripts/avocado run $TESTS > /dev/null

Before this change:
    real    0m12.114s
    user    0m1.549s
    sys     0m1.038s

After:
    real    0m2.639s
    user    0m1.065s
    sys     0m0.764s
Signed-off-by: NAdemar de Souza Reis Jr <areis@redhat.com>

Now that we gather values from the config files, 'Current'
becomes more proper term.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

As a subcommand (option, really) of the plugin command. The generated
distro file is supposed to be portable and be named canonically based
on the name, version, release and arch.

Changes from v0:
 * Return proper exit status when required command line arguments are
   missing
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Calling `load_from_tree()` with the right parameters will create a
distro definition instance from a distribution tree. Chaining it to
`save_distro` will save it in the portable format that is supposed
to be used for interchange or simple persistence.

Changes from v0:
 * Make save_distro do better error checking (and look better) by
   using the `with` keyword
Signed-off-by: NCleber Rosa <crosa@redhat.com>

By implementing DistroPkgInfoLoaderDeb and adding it to the registry,
the plugin will know how to deal with DEB based linux distributions.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

By implementing DistroPkgInfoLoaderRpm and adding it to the registry,
the plugin will know how to deal with RPM based linux distributions.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

This class defines an interface that subclasses specific to distribution
should implement.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

A distro definition is an expansion of the distro class that includes
packages that are shipped with the distro.

Changes from v0:
 * Fixed typos on commit message
Signed-off-by: NCleber Rosa <crosa@redhat.com>

At this stage, the distro plugin is very simplistic and prints the
detected distribution of the current machine. One could algue that
this is rather useless, but, with the component isolation work this
command is going to be helpful for troubleshooting purposes.

Also, this plugin is a placeholder where other functionality will
live, including (but not limited to):

 * the ability to create "distro definition" files, akin to
   autotest's autotest-distro-def-create.
 * the ability to view "distro definition" files, akin to
   autotest's autotest-distro-def-view.
 * the ability to download "distro definition" files from a
   repository
 * (maybe) the ability to push a distro definition file to
   avocado-server. This may be delegated to a full blown REST
   client though.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

avocado/linux/distro.py, ported from Autotest, included a unittest.
This ports that unittest module to avocado, adjusting the namespaces
and using flexmock instead of Autotest's own mock system.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

The mentioned utility function, get_os_vendor() is actually an Autotest
specific thing and it has no place in avocadoland.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Component Isolation: sysinfo installed packages collection

So that users can decide to enable this costly but, depending on
use case, very useful piece of information.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Signed-off-by: NCleber Rosa <crosa@redhat.com>

docs/Configuration: Update Configuration section

To reflect the latest status quo regarding Configuration.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

avocado.test: Add missing argument to test.MissingTest