If we have an error at test setup stage, avocado will
completely crash. This happens because the setup()
method is not properly wrapped inside the avocado
execution loop.

So, trust exception handling to the job level,
putting all test executions under a single try/except
block with appropriate status and test attribute handling.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Add support for Test Results report.

Add option -v | --version to the application.

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

Actually pass parameter for version when calling ArgumentParser,
so we're leaving -V for --verbose.

Plus: simplify code for utils.unique().
Signed-off-by: NRuda Moura <rmoura@redhat.com>

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

Self runnable tests

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>

As it is not necessary in avocado anymore.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

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

A Job is a sequence of operations executed on a
machine. This patch implements the class, which
is a refactor of the test run function, and a
class that implements a convenience found in
python unittests: the main() method. This allows
test modules to be executable in stand alone
mode, without the need of the avocado test runner.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

So that we can make avocado test modules self runnable.
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>

Add support for loading external plugins.

Create new option --plugins to pass a directory for loading external plugins.
Also, add some plugins examples in examples/avocado_example_plugins.py.

The external plugins are loaded from avocado_*.py modules and the plugins are
subclasses of Plugin().
Signed-off-by: NRuda Moura <rmoura@redhat.com>

Also, app.run() now returns an exit code -- requires further
udpates to pass the exit code back from plugins.

To load external plugins:

p = MyPlugin()
app = avocado.cli.app.AvocadoApp(external_plugins=[p])
app.run()

and here's a MyPlugin example:

import sys
import avocado
from avocado.plugins import plugin

class MyPlugin(plugin.Plugin):
    def configure(self, parser):
        myparser = parser.add_parser('hello',
                                     help='Hello World!')
        myparser.set_defaults(func=self.hello)
	self.enabled = True

    def hello(self, args):
        print 'Hello World!', args

And how to execute:

python myplugin.py hello
Hello World! Namespace(func=<bound method MyPlugin.hello of <__main__.MyPlugin object at 0x1574f90>>, log_level='', logdir='', verbose=False)
Signed-off-by: NRuda Moura <rmoura@redhat.com>

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

Ignore files from git and fix script name in setup.py.

Make sysinfo into a runner Plugin.

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

Make sysinfo into a runner Plugin,
rename application from AvocadoRunnerApp to AvocadoApp,
due all options are now implemented as plugins and
Avocado is now a core application.
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>

Basic structure for plugins.

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

Fill logs with better information for dropin tests,
such as return code, stdout, stderr, duration, among
others.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Dropin tests are executables with no knowledge of
avocado whatsoever, they only return 0 (PASS) or
!=0 (FAIL). They can be executed with the test
runner so output and sysinfo can be captured,
creating another utility for the runner script.

scripts/avocado run "mytest.sh failtest.sh"
DEBUG LOG: /home/lmr/Code/avocado/logs/run-2014-03-13-00.12.20/debug.log
TOTAL TESTS: 2
(1/2) mytest.1: PASS (0.00 s)
(2/2) failtest.1: FAIL (0.00 s)

Where

 $ cat mytest.sh
 #!/bin/bash
 true

 $ cat failtest.sh
 #!/bin/bash
 false
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

We'll start with a different convention than the one
used in autotest: We'll have a separate unittests/
directory with unittests, and those will load the
avocado libraries using simple import tricks (no
common.py).

This first version of the sysinfo unittest only
exercises the Loggable classes and their comparison
methods. More is to come (hopefully).
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Leave only avocado.app and avocado.test loggers, the
former for console output, and the later, for test and
job logs.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Rename Bcolors to TerminalColors, and add new methods
that will already yield common strings ready for exibition:

1 - A colored header string
2 - Colored PASS, FAIL, ERROR, SKIP strings
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>

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