Add section inside "Development Tips" to include a graph
of module dependencies.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

In the documentation, explain that the test API is everything
under avocado module, but excludes avocado.core.

Also, Avocado works with plugins, so let's talk about it,
in the introduction too.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Plugins improve list view [v2]

This is how I believe *plugin* dependencies should be handled. If
something that a plugin requires is not present, it simply fails to
load.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Pick the information collected while loading plugins to display to the
user clearly why some of their plugins are not working.

Changes from v1:

* Instead of guessing the plugin disable cause, use a more generic but
  accurate description.  The description chosen is to simply say that
  the plugin was disabled during configuration (`configure()`), which
  is often done, but not limited to, missing dependencies.
* Changed the presentation from having colored `Enabled` or `Disabled`
  at the RHS of the plugin description to a single colored header.
* Increased one space in the formatting string (`format_str`)
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Store failed plugins instead of logging them to stderr.  That will
allow us to give better information to the user as of why a given
plugin was disabled.

Changes from v1:
 * Dropped the use of FailedPlugin in favor of a simpler (name,
   reason) tuple.
 * Catch a single, and more broad `Exception` since `ImportError`s
   will also be caught and treated the same way.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

Avocado shouldn't crash, it should only notify user about the failure.
This patch modifies the existing mux exceptions to reflect this rule and
adds new exception handler for incorrect yaml file.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Revert "GDB: use gdbserver --server-sdtderr option if available"

avocado/utils/data_factory.py: replace prefix of temporary directory nam...

Move avocado.remote to avocado.core.remote, in conformance to our
purpose of keeping things not related to test developers,
inside avocado.core, isolated from users.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Move avocado.plugins to avocado.core.plugins, in conformance to our
purpose of keeping things not related to test developers,
inside avocado.core, isolated from users.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Move avocado.core.data_dir to avocado.data_dir so that test
developers can make use of it.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Move avocado.external.gdbmi_parser and avocado.external.spark
to avocado.core.gdmi_parser and avocado.core.spark, in conformance to
our purpose of keeping things not related to test developers,
inside avocado.core, isolated from users.

After this, `avocado.external` module is gone.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Move avocado.result to avocado.core.result, in conformance to
our purpose of keeping things not related to test developers,
inside avocado.core, isolated from users.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

The API ReST files that are generated dinamycally are actually put in
the source directory, and not in the build directory. This fixes a
mistake by yours truly.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Move avocado.sysinfo to avocado.core.sysinfo, in conformance to our
purpose of keeping things not related to test developers, inside
avocado.core, isolated from users.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Move avocado.runner to avocado.core.runner, in conformance to
our purpose of keeping things not related to test developers,
inside avocado.core, isolated from users.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

The prefix name is a leftover from a test refactor. Let's replace it
by a more sensible name.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

This reverts commit 71d47611.

The idea in the mentioned commit were sent to the upstream mailing
list and a better solution was proposed, so it makes no sense to
maintain support in Avocado for something that will never make into
GDB itself.

Trivial fixes 2015-04-27

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

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

Move avocado.loader to avocado.core.loader,
in conformance to our purpose of keeping things not related to
test developers, inside avocado.core, isolated from users.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

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

Test API: Isolate avocado.job from being used by test developers. [V2]

Makefile: replace source tarball generation from distutils to git

Export avocado.core.job.main as avocado.main, so that make it look
like an API for test developers to use.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Move avocado.job to avocado.core.job, in conformance to our
purpose of keeping things not related to test developers,
inside avocado.core, isolated from users.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

It was noted that, on some Python version, the generated tarballs
actually have a lot of files missing. IMHO, if we track a file on git,
then it should make into the tarball. Also IMHO, the distutils sdist
code is a nice thing to have if you can't export your code right from
your SCM.

This is kept simple on purpose so that if we hit any unintended side
effect we can revert to the previous way of generation source
tarballs.
Signed-off-by: NCleber Rosa <crosa@redhat.com>