There's no reason for having a separated simpletests directory, let's move
them to the tests directory.

Reference: https://trello.com/c/VFcxxwIpSigned-off-by: NAmador Pahim <apahim@redhat.com>

Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

updated module name in examples/tests/linuxbuild.py

Currently the sysinfo info on the HTML report only shows the pre-test
phase of sysinfo.  It should really include all three phases.

The content of the profiler section is, of course, dependant on that
type of collection having been activated (which is not by default).

Reference: https://trello.com/c/sXZQTftaSigned-off-by: NCleber Rosa <crosa@redhat.com>

The machine hostname is extracted from the sysinfo file, and it
contains a newline.  While really minor, it produces the following HTML code:

   <tr>
       <td>Host</td><td><tt>localhost.localdomain
 </tt></td>
   </tr>

Instead of:

   <tr>
       <td>Host</td><td><tt>localhost.localdomain</tt></td>
   </tr>

So, let's remove the trailing newline.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

The reason is that some test results, such as the HTML report, contain
sysinfo data.  Without this change, it's impossible to embed post-test
sysinfo data into such test results.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

The first commit is checked by the main check, don't re-check it with
the per-commit check.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

This patch fixes and improves resolving of the test aliases (paths
relative to `data_dir.get_tests_dir`).

1. It removes the magic `.py` suffix, which prevented non-python files
   from being resolved (simple.sh was resolved to $tests/simple.sh.py)
2. It adds the feature to filter the class/method from the test
   reference by parsing $test_reference:$class.$method for implicit
   resolver. (previously this worked only for absolute path resolver)

Visible changes are:

* `avocado run passtest` => fails (used to work)
* `avocado run passtest.py` => works (did not work)
* `avocado run env_variables.sh` => works (did not work)
* `avocado run passtest.py:PassTest.test` => works (did not work)
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Currently we have a travis script to run make check with every
commit on the PR. But the script is hard coded to get the commit
list using the branch master as reference.

This commit uses travis env variables to make the script branch
independent, so we can have the same .travis.yaml file for every
branch we create (LTS branches for instance).
Signed-off-by: NAmador Pahim <apahim@redhat.com>

Python ignores SIGPIPE on startup, because it prefers to check every
write and raise an IOError exception rather than taking the signal.

This patch changes SIGPIPE back to its default action in order to
behave correctly.

Reference: https://trello.com/c/ysKxcHEaSigned-off-by: NAmador Pahim <apahim@redhat.com>

Travis will clone the repo and then fetch the pull-request, regardless
the branch it's coming from. That's why a PR has to contain the correct
parenting. But the build will happen only if the PR is proposed to an
enabled branch. That's what this PR enables.
Signed-off-by: NAmador Pahim <apahim@redhat.com>

Fix travis build for python2.6

Fabric 1.10.0 has a dependency issue. This patch changes
the fabric version in travis to the highest available
version right now.
Signed-off-by: NAmador Pahim <apahim@redhat.com>

Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

There is a "make develop" target available in Makefile to develop
avocado, let's use it in documentation.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

If Ctrl+C is hit outside the loop waiting for the test, instead
of failing nicelly, Avocado crashes.

This patch adds a try/except for the run_suite function so we can
catch the KeyboardInterrupt outside the loop that waits for the test
addint 'INTERRUPTED' to the summary.

Reference: https://trello.com/c/lDj56sKWSigned-off-by: NAmador Pahim <apahim@redhat.com>

It is expected to be string, not integer.
Signed-off-by: NAmador Pahim <apahim@redhat.com>

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

This release introduces a new versioning scheme, so the "big bump"
from 0.34.0 to 35.0 is not such a big bump.

Some additional changes with regards to versioning were added, such as
the way the remote runner checks for Avocado on the remote host.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

It just makes sense that the subpackages of Avocado depend on the same
version.  This will avoid accidental mixing and matching of different
package versions.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Since DEB packages have seen much update in the last releases, instead
of pointing to very old and innacturate releases, let's move those to
contrib.  While at it, let's document what is officially distributed
and what's best effort (contrib level).
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Not all contrib content is created equal, so let's just move scripts
to a properly named directory, in anticipation for different types of
content.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

The backtrace goes like this:

     ...
     File "/home/docs/checkouts/readthedocs.org/user_builds/avocado-framework/envs/latest/local/lib/python2.7/site-packages/six.py", line 699, in exec_
       exec("""exec _code_ in _globs_, _locs_""")
     File "<string>", line 1, in <module>
     File "conf.py", line 12, in <module>
       from avocado import VERSION
     File "/home/docs/checkouts/readthedocs.org/user_builds/avocado-framework/checkouts/latest/avocado/__init__.py", line 19, in <module>
       from avocado.core.job import main
     File "/home/docs/checkouts/readthedocs.org/user_builds/avocado-framework/checkouts/latest/avocado/core/job.py", line 33, in <module>
       from . import dispatcher
     File "/home/docs/checkouts/readthedocs.org/user_builds/avocado-framework/checkouts/latest/avocado/core/dispatcher.py", line 19, in <module>
       from stevedore import ExtensionManager
   ImportError: No module named stevedore

Let's give readthedocs.org stevedore.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

The steps to perform a release have changed during the last few
versions, most importantly regarding the distribution of the packages.

Let's update the instructions to better match reality.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

This script introduces a pair of directories that will be searched
for executable files, to be run before and after the actual execution
of a job.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

These new plugin interfaces, to be registered under the
'avocado.plugins.job.prepost' namespace, allow for any custom action
to be executed before and/or after the job execution.

The JobPre plugin interface requires the `pre` method to be
implemented, while the JobPost plugin interface requires the `post`
method to be implemented.  The separation of the interfaces allows for
mandatory implementation of the given interfaces, which was the whole
point of using Abstract base classes, instead of having empty default
implementations.

One single class may implement either one, or both of those
interfaces.  Both `pre` and `post` methods receive the current Job
instance as an argument, which allows the plugin to fetch any job
information or even to tweak as it may seem fit.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Since one of the main goals of the Job is to run tests, and given the
initial use of the Job class internals, now by plugins and in the near
future as a full blown API, let's make the test suite public.

This will help plugins to take a look at what is going to be
(attempted to be) run, and react to that.
Signed-off-by: NCleber Rosa <crosa@redhat.com>