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

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

Signed-off-by: NAmador Pahim <apahim@redhat.com>

The package names have changed, let's sync that with what's used
in the release example testplan.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Signed-off-by: NAmador Pahim <apahim@redhat.com>

Signed-off-by: NAmador Pahim <apahim@redhat.com>

Simply because this file won't be available when being installed
from any method outside the source tree.

The downside is obvious: it requires extra steps when doing a new
release.  But that is still better than not being able to ship
these plugins to users using the standard Python mechanisms.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Now that the optional plugins have been excluded from the main
git archive, let's create them (currently with setuptools sdist
command).

Also, let's adjust the upload instruction a bit to signal that
other packages may be in PYPI_UPLOAD too.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

PyPI understands (rightfully so) one Python module per archive.  So,
it doesn't make sense to bundle all the plugins there for users of
`pip install avocado-framework`.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

So users will now be able to find Avocado plugins on PyPI, and install
them via `pip`.  Let's try to be consistent with the naming on those
packages, so that users don't fall into naming traps such as
installing Django related extensions.

Also, those packages map more closely to their (RPM) packaged versions.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

Downstream file contains a conditional for the execution of
selftests.  Let's port that to the upstream SPEC file too.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

I have to say that having one requirement per line is really verbose,
but I have to admit that it makes diffs a lot easier to grasp.

Again, this syncs with the downstream SPEC file.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

The first line says it all.  While this change wouldn't be really
required, it brings the SPEC file close to the Fedora/EPEL downstream
version.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

* https://github.com/avocado-framework/avocado:
  Added -y to pvcreate in lv_utils

Added '-y' to pvcreate since pvcreate asks for confirmation
if previous filesystem signature exists.
Signed-off-by: NNarasimhan V <sim@linux.vnet.ibm.com>

The write to /proc/sys/vm/drop_caches requires root, let's use the
`sudo` to allow the execution for non-root executions as well.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

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

* https://github.com/avocado-framework/avocado:
  robot plugin: pylint fixes
  robot: fix error on unknown tests

Fixing pylint messages for the robot plugin module.
Signed-off-by: NAmador Pahim <apahim@redhat.com>

When robot plugin cannot determine the tests from the test references we
should return an empty list instead of an exception.
Signed-off-by: NAmador Pahim <apahim@redhat.com>

Signed-off-by: NAmador Pahim <apahim@redhat.com>

When the "sudo" is present in the PATH but is broken, the
"process.system" raises OSError. Let's address this issue and report
False in such case (as sudo is unusable)
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

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

Improved linux_modules [v4]

avocado.utils.linux_modules: Improved the module.
Added the following parameters to the return value of
loaded_module_info()
* filename
* version
* parameters list
* depends list
Signed-off-by: NLucas Meneghel Rodrigues <lookkas@gmail.com>

robot: fix issue on missing test references
Signed-off-by: NLucas Meneghel Rodrigues <lookkas@gmail.com>

We have to consider that `avocado list` may be executed without the test
references.
Signed-off-by: NAmador Pahim <apahim@redhat.com>

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

* https://github.com/avocado-framework/avocado:
  Robot Plugin

Recently we added a check for canceled test, let's also check the
"cancel" number of tests are reported correctly in json plugin.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

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

* https://github.com/avocado-framework/avocado:
  Deprecate message in self.skip()
  Accept self.cancel() in setUp() and tearDown()
  Don't execute setUp()/tearDown() on SKIP

Signed-off-by: NAmador Pahim <apahim@redhat.com>

This updates the mentions of the Avocado packages to new package
names.

Also, it tries to bring a more focused content to the README file,
that is, something more brief and direct, while using the updated
package names.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

With a single item, but as a place holder for all docs, articles and
even videos out there covering Avocado usage.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

The current README talks about a vision for Avocado.  This made sense
a while ago, but right now, it's better to describe what Avocado
currently is.

The project vision can be seen from our planning boards.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

self.skip() is to be deprecated. This is the first step, adding a
message to the exception raised by the self.skip() and adjusting the
examples tests accordingly.
Signed-off-by: NAmador Pahim <apahim@redhat.com>

self.cancel() should be accepted everywhere, including setUp()
and tearDown().
Signed-off-by: NAmador Pahim <apahim@redhat.com>

Skip decorators are intended to skip the test. Skipping the test means
also no setUp() and no tearDown(). This patch makes the setUp() and
tearDown() to be also skipped when using the skip decorators.
Signed-off-by: NAmador Pahim <apahim@redhat.com>

avocado/utils/linux_modules: Docstring changes and pylint
changes.
Signed-off-by: NNarasimhan V <sim@linux.vnet.ibm.com>

avocado.utils.linux_modules: Improved the module.
Added the following parameters to the return value of
loaded_module_info()
    * filename
    * version
    * parameters list
    * depends list
Signed-off-by: NNarasimhan V <sim@linux.vnet.ibm.com>

This patch creates an optional plugin to run Robot Framework tests
inside Avocado.
Signed-off-by: NAmador Pahim <apahim@redhat.com>

In many cases when you are developing a test suite using
avocado libraries, you want to flag certain exceptional
conditions as real test failures, rather than something
that will be converted to an ERROR status (the current
default behavior).

Consider QEMU testing: An exception involving a QEMU core
dump should be considered a failure in pretty much every
scenario one can think of. So it makes sense to have code
similar to:

from avocado import TestFail

QEMUCoreDump(TestFail):
    pass

so that when said exception happens inside library code,
the test can be immediately flagged as a failure, without
having to introduce boilerplate code to check for error
conditions.

So at least the 3 main test related exceptions (TestFail,
TestError and TestCancel) should be directly exposed in
the test writer API. Methods such as self.fail() are
neat shortcuts for simpler cases and should be used,
but entirely isolating access to *all* avocado exceptions
is detrimental to the goal of reducing boilerplate code
in tests.

This patch adds the mentioned 3 test exceptions to the
avocado namespace, making them part of the test writer
API.
Signed-off-by: NLucas Meneghel Rodrigues <lookkas@gmail.com>