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

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

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

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

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

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

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

In module avocado.core.plugins.builtin, There is a calling of
os.listdir() to iterate files in the installed python directory.

If avocado is installed in an .egg file which is compressed, it will
fail to load because that path does not really exists.

To avoid this failure, this patch set zip_safe to False explicitly.
So setuptools will install package to a real directory instead of a
zipped .egg file.
Signed-off-by: NHao Liu <hliu@redhat.com>

One standard setuptools command is "test". That command does some useful
setup and then runs the test in a verbose mode.

There are a couple of reasons for activating that, including that
setuptools can help us support a Python 3 version of Avocado by
running 2to3 and even custom fixers before running the tests, or even
builds and installs.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

This fixes #628.

Add a couple of simple shell scripts that can be listed
and executed with avocado. Let's update our documentation
to use this new dir and avoid people confused with our
wrappers.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

While still making the VERSION symbol available in the top level
Avocado module. Even though this is very simple information that
could live under the avocado module itself, it would break the
consistency of having avocado.core importing from avocado (toplevel).
Signed-off-by: NCleber Rosa <crosa@redhat.com>

The new location was not reflected on the setup.py script, resulting
in the module not being present after installation.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

The initial idea about the avocado.restclient namespace was that
eventually users could write scripts using that as an API to
interact with avocado-server using Python code.

While the idea is still valid, the avocado-server interface is
a simple and standards compliant RESTful interface. Thus, users
can still easily interact with it without us having to support
a formal Python API at this point.

In the future, if need arises, we can improve the Python REST
client API and promote it to a public namespace.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

And while doing that, also remove avocado.linux for good, since no one else
lives there.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

The GDB config file was not being installed and packaged in the RPM
package. This should fix it.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

Move avocado.restclient.cli to avocado.core.restclient.cli,
related to `avocado-rest-client` script.

Users can make use of `avocado.restclient.connection` and
`avocado.restclient.response`.
These are very lightweight and intended to let users query and manipulate
avocado-server data without starting from scratch.
Signed-off-by: NCleber Rosa <crosa@redhat.com>
Signed-off-by: NRudá Moura <rmoura@redhat.com>

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.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.cli.app and avocado.cli.parser to avocado.core,
in conformance to our purpose of keep things not related to
test developers, inside avocado.core.

Now the package avocado.cli is gone.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

This change adds flexibility to the current sysinfo implementation in
the sense that the commands to be executed and files to be collected
are no longer hard coded, but configurable.

The configuration file gains a section for that, and the files
themselves are plain text files that can be easily customized by users
to include extra commands/files.

Also, the the configuration for the profilers has been adjusted for a
uniform look, feel and experience.

Changes from v1:
 * Return the default `profiler` parameter value to None, so that it
   looks at the configuration value by default
Signed-off-by: NCleber Rosa <crosa@redhat.com>

This patch is initial support for people using custom bash scripts
with avocado. Tests should use:

    PATH=$(avocado "exec-path"):$PATH

and then they can utilize the helpers.

This version contain functions to write to Test.log the same way it's
possible from python including failing the test with TestWarn in case
avocado_warn was used.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

No actual change, only refactor code to use single function to get all
paths.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

* Include `avocado.module` inside setup.py.
* Check if htmlresult plugin is installed from the import,
  to set the HTML result feature on or off.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Introduce a new command line application that is designed to interact
with avocado-server.

Changes from v1:
* Fixed reference in the docstrings to arcli (from arc)
* Release number bump on spec file
* Add missing avocado.restclient.cli.actions module to setup.py
Signed-off-by: NCleber Rosa <crosa@redhat.com>

An essential part of a client interacting with avocado-server is to handle
the reponse of a request. The most common type of response type is a
results reponse, when one performs a GET to a resource "root" path and
and expects to return a list of resources.

To make that more pythonic, this commit introduces a ResultResponse class
that accepts the JSON response data and checks for completeness. If
results response fails to comply with the required data members, meaningful
exceptions will be raised.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

This way, we fix a bug of avocado unable to list tests
from its own tree (it'll try to import them and then
fail due to recursively trying to import the already
loaded avocado modules).
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

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>

Whatever is in the system wide settings can be later
overriden by users. Also, change the settings.config_path
attribute to settings.config_paths, and change it to
a list. This way users can see the order in which their
config files are parsed. Also, Introduce a system wide conf.d
directory, that is supposed to ship config files for avocado
plugins. The order for config parsing is:

 * System wide avocado config (/etc/avocado/avocado.conf)
 * System wide avocado plugins config (/etc/avocado/conf.d/*.conf)
 * Local config for the user running avocado (~/.config/avocado/avocado.conf)
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

As discussed in the Trello card

https://trello.com/c/WsDMg7RP/161-initial-support-for-avocado-config-files-server-and-client

Move settings.ini to avocado.conf. The basic idea is
that the name is more intuitive.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Include all examples/wrappers/*.sh scripts when building
the `avocado-examples` package. The scripts will live under
`/usr/share/avocado/wrappers` when installed.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

setuptools is not a standard module and makes things
unpredictable and forces us to push MANIFEST.in to
include more files so the binary distributions get
filled appropriately. In a retrospect, it was a bad
idea. Let's revert it.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

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

Making justice to all our contributors, change this
silly instance of myself as the author of the whole
thing. Sorry about that.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Use setuptools's option install_requires, to signal
the dependencies avocado requires for full functionality.
Important for publishing avocado in PyPi [1].

[1] https://pypi.python.org/pypiSigned-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Package plugin resource files, as they're necessary to
the given plugin's functionality. Update MANIFEST.in
with the new data dir.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

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