15 Aug 16:25

clebergnu

d4d83d8

Downton Abbey

The Avocado team is proud to present another release: Avocado 70.0,
AKA "Downton Abbey", is now available!

Release documentation: Avocado 71.0 <http://avocado-framework.readthedocs.io/en/71.0/>_

Users/Test Writers

Avocado can now run on systems with nothing but Python 3 (and
"quasi-standard-library" module setuptools). This means that it
won't require extra packages, and should be easier to deploy on
containers, embedded systems, etc. Optional plugins may have
additional requirements.
A new and still experimental test runner implementation, known as
"N(ext) Runner" has been introduced. It brings a number of
different concepts, increasing the decoupling between a test (and
its runner) and the job. For more information, please refer to
:ref:the early documentation <nrunner>.
The new :func:avocado.cancel_on decorator has been added to the
Test APIs, allowing you to define the conditions for a test to be
considered canceled. See one example :ref:here <turning_errors_into_cancels>.
The glib plugin got a configuration option its safe/unsafe
operation, that is, whether it will execute binaries in an attempt to
find the whole list of tests. Look for the glib.conf shipped
with the plugin to enable the unsafe mode.
Avocado can now use tags inside Python Unittests, and not only on
its own Instrumented tests. It's expected that other forms or
providing tags for other types of tests will also be introduced in
the near future.
The HTML report will now show, as a handy pop-up, the contents of the
test whiteboard. If you set, say, performance metrics there, you'll
able to see straight from the report.
The HTML report now has filtering support by test status, and can
show all records in the table.
The :mod:avocado.utils.runtime module, a badly designed mechanism
for sharing Avocado runtime settings with the utility libraries, has
been removed.
The test runner feature that would allow binaries to be run
transparently inside GDB was removed. The reason for dropping such
a feature have to do with how it limits the test runner to run one
test at a time, and the use of the :mod:avocado.utils.runtime
mechanism, also removed.
Initial examples for writing custom jobs, using the so called Job
API, have been added to examples/jobs. These APIs are still
non-public (under core), but they're supposed to become public
and supported soon.
By means of a new plugin (merge_files, of type job.prepost),
when using the :ref:output check record <output_check_record>
features, duplicate files created by different tests/variants will
be consolidated into unique files.

Bug Fixes

The HTML plugin now correctly shows the date for tests that were
never executed because of interrupted jobs.
A temporarily workaround for a stack overflow problem in Python 3.7
has been addressed.
The pict plugin (a varianter implementaion) now properly yields the
variants paths as a list.
A Python 3 related fix to mod:avocado.utils.software_manager, that
was using Python 2 next on get_source.
A Python 3 related fix to the docker plugin, that wasn't caught
earlier.

Utility APIs

:mod:avocado.utils.partition now allows mkfs and mount
flags to be set.
:func:avocado.utils.cpu.get_cpu_vendor_name now returns the CPU
vendor name for POWER9.
:mod:avocado.utils.asset now allows a given location, as well as a
list, to be given, simplifying the most common use case.
:meth:avocado.utils.process.SubProcess.stop now supports setting
a timeout. Please refer to the documentation for the important
details on its behavior.
:mod:avocado.utils.memory now properly handles hugepages for POWER
platform.

Internal Changes

Removal of the stevedore library dependency (previously used for
the dispatcher/plugins infrastructure).
make check now runs selftests using the experimental N(ext)
Runner.
Formal support for Python 3.7, which is now on our CI checks,
documentation and module information.
The Yaml to Mux plugin now uses a safe version of the Yaml loader,
so that the execution of arbitrary Python code from Yaml input is
now no longer possible.
Codecov coverage reports for have been enabled for Avocado, and
can be seen on every pull request.
New tests have been added to many of the optional plugins.
Various pylint compliance improvements, including w0231, w0235,
w0706, w0715 and w0221.
Avocado's selftests now use tempfile.TemporaryDirectory instead of
mkdtemp and shutil.rmtree.
:class:avocado.core.job.Job instantiation now takes a config
dictionary parameter, instead of a argparse.Namespace instance,
and keeps it in a config attribute.
:class:avocado.core.job.Job instances don't have a references
attribute anymore. That information is available in the config
attribute, that is, myjob.config['references'].
Basic checks for Fedora and RHEL 8 using Cirrus CI have been added,
and will be shown on every pull request.

For more information, please check out the complete
Avocado changelog <https://github.com/avocado-framework/avocado/compare/70.0...71.0>_.

Assets 2

26 Jul 14:28

clebergnu

39.0

ac98eb9

39.0 The Hateful Eight

The Avocado team is proud to present another incremental release:
version 39.0, aka, "The Hateful Eight", is now available!

The major changes introduced on this version are listed below.

Support for running tests in Docker container. Now, in addition to
running tests on a (libvirt based) Virtual Machine or on a remote host,
you can now run tests in transient Docker containers. The usage is as
simple as::

$ avocado run mytests.py --docker ldoktor/fedora-avocado

The container will be started, using ldoktor/fedora-avocado as
the image. This image contains a Fedora based system with Avocado
already installed, and it's provided at the official Docker hub.
Introduction of the "Fail Fast" feature.

By running a job with the --failfast flag, the job will be
interrupted after the very first test failure. If your job only
makes sense if it's a complete PASS, this feature can save you a lot
of time.
Avocado supports replaying previous jobs, selected by using their
Job IDs. Now, it's also possible to use the special keyword
latest, which will cause Avocado to rerun the very last job.
Python's standard signal handling is restored for SIGPIPE, and thus
for all tests running on Avocado.

In previous releases, Avocado introduced a change that set the
default handler to SIGPIPE, which caused the application to be
terminated. This seemed to be the right approach when testing how
the Avocado app would behave on broken pipes on the command line,
but it introduced side effects to a lot of Python code. Instead of
exceptions, the affected Python code would receive the signal themselves.

This is now reverted to the Python standard, and the signal behavior
of Python based tests running on Avocado should not surprise anyone.
The project release notes are now part of the official
documentation. That means that users can quickly find when a given
change was introduced.

Together with those changes listed, a total of 38 changes made into
this release. For more information, please check out the complete
Avocado changelog <https://github.com/avocado-framework/avocado/compare/38.0...39.0>_.

Sprint Theme

After so much love that we had on the previous version, let's twist
things a bit with an antagonist title. Info on this pretty good movie
by Tarantino can be found at:

http://www.imdb.com/title/tt3460252/?ref_=nm_flmg_wr_2

https://www.youtube.com/watch?v=6_UI1GzaWv0

The story line:

In the dead of a Wyoming winter, a bounty hunter and his prisoner
find shelter in a cabin currently inhabited by a collection of
nefarious characters.

Release Meeting

The Avocado release meetings are now open to the community via
Hangouts on Air. The meetings are recorded and made available on the
Avocado Test Framework YouTube channel <https://www.youtube.com/channel/UC-RVZ_HFTbEztDM7wNY4NfA>_.

For this release, you can watch the meeting on this link <https://www.youtube.com/watch?v=GotEH7SmHSw>_.

Assets 2

05 Jul 12:42

clebergnu

38.0

8b84df5

Avocado release 38.0: Love, Ken

Hello everyone,

You guessed it right: this is another Avocado release announcement:
release 38.0, aka "Love, Ken", is now out!

Another development cycle has just finished, and our community will
receive this new release containing a nice assortment of bug fixes and
new features.

The download of assets in tests now allow for an expiration time.
This means that tests that need to download any kind of external
asset, say a tarball, can now automatically benefit from the
download cache, but can also keep receiving new versions
automatically.

Suppose your asset uses an asset named myproject-daily.tar.bz2,
and that your test runs 50 times a day. By setting the expire time
to 1d (1 day), your test will benefit from cache on most runs, but
will still fetch the new version when the the 24 hours from the
first download have passed.

For more information, please check out the documentation on the
expire parameter to the fetch_asset() method[1].
Environment variables can be propagated into tests running on remote
systems. It's a known fact that one way to influence application behavior,
including test, is to set environment variables. A command line such as::

    $ MYAPP_DEBUG=1 avocado run myapp_test.py

Will work as expected on a local system. But Avocado also allows
running tests on remote machines, and up until now, it has been
lacking a way to propagate environment variables to the remote
system.

Now, you can use::

    $ MYAPP_DEBUG=1 avocado run --env-keep MYAPP_DEBUG \
      --remote-host test-machine myapp_test.py

The plugin interfaces have been moved into the
avocado.core.plugin_interfaces module. This means that plugin
writers now have to import the interface definitions this namespace,
example::

    ...
    from avocado.core.plugin_interfaces import CLICmd

    class MyCommand(CLICmd):
    ...

This is a way to keep ourselves honest, and say that there's no
difference from plugin interfaces to Avocado's core implementation,
that is, they may change at will. For greater stability, one should
be tracking the LTS releases.

Also, it effectively makes all plugins the same, whether they're
implemented and shipped as part of Avocado, or as part of external
projects.

A contrib script for running kvm-unit-tests. As some people are
aware, Avocado has indeed a close relation to virtualization
testing. Avocado-VT is one obvious example, but there are other
virtualization related test suites can Avocado can run.

This release adds a contrib script that will fetch, download,
compile and run kvm-unit-tests using Avocado's external runner
feature. This gives results in a better granularity than the
support that exists in Avocado-VT, which gives only a single
PASS/FAIL for the entire test suite execution.

For more information, please check out the Avocado changelog[2].

Also, while we focused on Avocado, let's also not forget that
Avocado-VT maintains it's own fast pace of incoming niceties.

s390 support: Avocado-VT is breaking into new grounds, and now has
support for the s390 architecture. Fedora 23 for s390 has been added
as a valid guest OS, and s390-virtio has been added as a new machine
type.
Avocado-VT is now more resilient against failures to persist its
environment file, and will only give warnings instead of errors when
it fails to save it.
An improved implementation of the "job lock" plugin, which prevents
multiple Avocado jobs with VT tests to run simultaneously. Since
there's no finer grained resource locking in Avocado-VT, this is a
global lock that will prevent issues such as image corruption when
two jobs are run at the same time.

This new implementation will now check if existing lock files are
stale, that is, they are leftovers from previous run. If the
processes associated with these files are not present, the stale
lock files are deleted, removing the need to clean them up manually.
It also outputs better debugging information when failures to
acquire lock.

The complete list of changes to Avocado-VT are available on its
changelog[3].

While not officially part of this release, this development cycle saw
the introduction of new tests on our avocado-misc-tests. Go check it
out!

Finally, since Avocado and Avocado-VT are not newly born anymore, we
decided to update information mentioning KVM-Autotest, virt-test on so
on around the web. This will hopefully redirect new users to the
Avocado community and avoid confusion.

Install avocado

Instructions are available in our documentation on how to install
either with packages or from source[4].

Updated RPM packages are be available in the project repos for EPEL 6,
EPEL 7, Fedora 22, Fedora 23 and the newly released Fedora 24.

Please note that on the next release, we'll drop support for Fedora 22
packages.

Happy hacking and testing!

[1] http://avocado-framework.readthedocs.io/en/38.0/WritingTests.html
[2] 37.0...38.0
[3] avocado-framework/avocado-vt@37.0...38.0
[4] http://avocado-framework.readthedocs.io/en/38.0/GetStartedGuide.html#installing-avocado

Assets 2

14 Jun 08:50

clebergnu

37.0

d5a8d29

Avocado release 37.0: Trabant vs. South America

This is another proud announcement: Avocado release 37.0, aka "Trabant
vs. South America", is now out!

This release is yet another collection of bug fixes and some new
features. Along with the same changes that made the 36.0lts
release[1], this brings the following additional changes:

TAP[2] version 12 support, bringing better integration with other
test tools that accept this streaming format as input.
Added niceties on Avocado's utility libraries "build" and "kernel",
such as automatic parallelism and resource caching. It makes tests
such as "linuxbuild.py" (and your similar tests) run up to 10 times
faster.
Fixed an issue where Avocado could leave processes behind after the
test was finished.
Fixed a bug where the configuration for tests data directory would
be ignored.
Fixed a bug where SIMPLE tests would not properly exit with WARN
status.

For a complete list of changes please check the Avocado changelog[3].

For Avocado-VT, please check the full Avocado-VT changelog[4].

Install avocado

Instructions are available in our documentation on how to install
either with packages or from source[5].

Updated RPM packages are be available in the project repos for
Fedora 22, Fedora 23, EPEL 6 and EPEL 7.

Happy hacking and testing!

[1] https://www.redhat.com/archives/avocado-devel/2016-May/msg00025.html
[2] https://en.wikipedia.org/wiki/Test_Anything_Protocol
[3] 35.0...37.0
[4] avocado-framework/avocado-vt@35.0...37.0
[5] http://avocado-framework.readthedocs.io/en/37.0/GetStartedGuide.html#installing-avocado

Assets 2

17 May 18:19

clebergnu

36.0lts

a794586

Avocado 36.0lts Release

This is a very proud announcement: Avocado release 36.0lts, our very
first "Long Term Stability" release, is now out!

LTS in a nutshell

This release marks the beginning of a special cycle that will last for
18 months. Avocado usage in production environments should favor the
use of this LTS release, instead of non-LTS releases.

Bug fixes will be provided on the "36lts"[1] branch until, at least,
September 2017. Minor releases, such as "36.1lts", "36.2lts" an so
on, will be announced from time to time, incorporating those stability
related improvements.

Keep in mind that no new feature will be added. For more information,
please read the "Avocado Long Term Stability" RFC[2].

Changes from 35.0:

As mentioned in the release notes for the previous release (35.0),
only bug fixes and other stability related changes would be added to
what is now 36.0lts. For the complete list of changes, please check
the GIT repo change log[3].

Install avocado

The Avocado LTS packages are available on a separate repository, named
"avocado-lts". These repositories are available for Fedora 22, Fedora
23, EPEL 6 and EPEL 7.

Updated ".repo" files are available on the usual locations:

Those repo files now contain definitions for both the "LTS" and
regular repositories. Users interested in the LTS packages, should
disable the regular repositories and enable the "avocado-lts" repo.

Instructions are available in our documentation on how to install
either with packages or from source[4].

Happy hacking and testing!

[1] https://github.com/avocado-framework/avocado/tree/36lts
[2] https://www.redhat.com/archives/avocado-devel/2016-April/msg00038.html
[3] 35.0...36.0lts
[4] http://avocado-framework.readthedocs.io/en/36lts/GetStartedGuide.html#installing-avocado

Assets 2

27 Apr 19:41

clebergnu

35.0

523c0e4

Avocado release 35.0: Mr. Robot

This is another proud announcement: Avocado release 35.0, aka "Mr
Robot", is now out!

This release, while a "regular" release, will also serve as a beta for
our first "long term stability" (aka "lts") release. That means that
the next release, will be version "36.0lts" and will receive only bug
fixes and minor improvements. So, expect release 35.0 to be pretty
much like "36.0lts" feature-wise. New features will make into the
"37.0" release, to be released after "36.0lts". Read more about the
details on the specific RFC[9].

The main changes in Avocado for this release are:

A big round of fixes and on machine readable output formats, such
as xunit (aka JUnit) and JSON. The xunit output, for instance,
now includes tests with schema checking. This should make sure
interoperability is even better on this release.
Much more robust handling of test references, aka test URLs.
Avocado now properly handles very long test references, and also
test references with non-ascii characters.
The avocado command line application now provides richer exit
status[1]. If your application or custom script depends on the
avocado exit status code, you should be fine as avocado still
returns zero for success and non-zero for errors. On error
conditions, though, the exit status code are richer and made of
combinable (ORable) codes. This way it's possible to detect that,
say, both a test failure and a job timeout occurred in a single
execution.
[SECURITY RELATED] The remote execution of tests (including in
Virtual Machines) now allows for proper checks of host keys[2].
Without these checks, avocado is susceptible to a man-in-the-middle
attack, by connecting and sending credentials to the wrong machine.
This check is disabled by default, because users depend on this
behavior when using machines without any prior knowledge such as
cloud based virtual machines. Also, a bug in the underlying SSH
library may prevent existing keys to be used if these are in ECDSA
format[3]. There's an automated check in place to check for the
resolution of the third party library bug. Expect this feature to
be enabled by default in the upcoming releases.
Pre/Post Job hooks. Avocado now defines a proper interface for
extension/plugin writers to execute actions while a Job is runnning.
Both Pre and Post hooks have access to the Job state (actually, the
complete Job instance). Pre job hooks are called before tests are
run, and post job hooks are called at the very end of the job (after
tests would have usually finished executing).
Pre/Post job scripts[4]. As a feature built on top of the Pre/Post job
hooks described earlier, it's now possible to put executable scripts
in a configurable location, such as /etc/avocado/scripts/job/pre.d
and have them called by Avocado before the execution of tests. The
executed scripts will receive some information about the job via
environment variables[5].
The implementation of proper Test-IDs[6] in the test result
directory.

Also, while not everything is (yet) translated into code, this release
saw various and major RFCs, which are definitely shaping the future of
Avocado. Among those:

Introduce proper test IDs[6]
Pre/Post test hooks[7]
Multi-stream tests[8]
Avocado maintainability and integration with avocado-vt[9]
Improvements to job status (completely implemented)[10]

For a complete list of changes please check the Avocado changelog[11].

For Avocado-VT, please check the full Avocado-VT changelog[12].

Install avocado

Instructions are available in our documentation on how to install
either with packages or from source[13].

Updated RPM packages are be available in the project repos for
Fedora 22, Fedora 23, EPEL 6 and EPEL 7.

Packages

As a heads up, we still package the latest version of the various
Avocado sub projects, such as the very popular Avocado-VT and the
pretty much experimental Avocado-Virt and Avocado-Server projects.

For the upcoming releases, there will be changes in our package
offers, with a greater focus on long term stability packages for
Avocado. Other packages may still be offered as a convenience, or
may see a change of ownership. All in the best interest of our users.
If you have any concerns or questions, please let us know.

Happy hacking and testing!

[1] http://avocado-framework.readthedocs.org/en/35.0/ResultFormats.html#exit-codes
[2] https://github.com/avocado-framework/avocado/blob/35.0/etc/avocado/avocado.conf#L41
[3] https://github.com/avocado-framework/avocado/blob/35.0/selftests/functional/test_thirdparty_bugs.py#L17
[4] http://avocado-framework.readthedocs.org/en/35.0/ReferenceGuide.html#job-pre-and-post-scripts
[5] http://avocado-framework.readthedocs.org/en/35.0/ReferenceGuide.html#script-execution-environment
[6] https://www.redhat.com/archives/avocado-devel/2016-March/msg00024.html
[7] https://www.redhat.com/archives/avocado-devel/2016-April/msg00000.html
[8] https://www.redhat.com/archives/avocado-devel/2016-April/msg00042.html
[9] https://www.redhat.com/archives/avocado-devel/2016-April/msg00038.html
[10] https://www.redhat.com/archives/avocado-devel/2016-April/msg00010.html
[11] 0.34.0...35.0
[13] avocado-framework/avocado-vt@0.34.0...35.0
[12] http://avocado-framework.readthedocs.org/en/35.0/GetStartedGuide.html#installing-avocado

Assets 2

22 Mar 15:43

clebergnu

0.34.0

c71e2c8

Avocado release 0.34.0: The Hour of the Star

Hello to all test enthusiasts out there, specially to those that
cherish, care or are just keeping an eye on the greenest test
framework there is: Avocado release 0.34.0, aka The Hour of the Star,
is now out!

The main changes in Avocado for this release are:

A complete overhaul of the logging and output implementation. This
means that all Avocado output uses the standard Python logging library
making it very consistent and easy to understand [1].
Based on the logging and output overhaul, the command line test
runner is now very flexible with its output. A user can choose
exactly what should be output. Examples include application output
only, test output only, both application and test output or any
other combination of the builtin streams. The user visible command
line option that controls this behavior is --show, which is an
application level option, that is, it's available to all avocado
commands. [2]
Besides the builtin streams, test writers can use the standard
Python logging API to create new streams. These streams can be shown
on the command line as mentioned before, or persisted automatically
in the job results by means of the --store-logging-stream command
line option. [3][4]
The new avocado.core.safeloader module, intends to make it easier
to to write new test loaders for various types of Python
code. [5][6]
Based on the new avocado.core.safeloader module, a contrib script
called avocado-find-unittests, returns the name of
unittest.TestCase based tests found on a given number of Python
source code files. [7]
Avocado is now able to run its own selftest suite. By leveraging the
avocado-find-unittests contrib script and the External Runner [8]
feature. A Makefile target is available, allowing developers to run
make selfcheck to have the selftest suite run by Avocado. [9]
Partial Python 3 support. A number of changes were introduced that
allow concurrent Python 2 and 3 support on the same code base. Even
though the support for Python 3 is still incomplete, the avocado
command line application can already run some limited commands at
this point.
Asset fetcher utility library. This new utility library, and
INSTRUMENTED test feature, allows users to transparently request
external assets to be used in tests, having them cached for later
use. [10]
Further cleanups in the public namespace of the avocado Test class.
[BUG FIX] Input from the local system was being passed to remote
systems when running tests with either in remote systems or VMs.
[BUG FIX] HTML report stability improvements, including better
Unicode handling and support for other versions of the Pystache
library.
[BUG FIX] Atomic updates of the "latest" job symlink, allows for
more reliable user experiences when running multiple parallel jobs.
[BUG FIX] The avocado.core.data_dir module now dynamically checks
the configuration system when deciding where the data directory
should be located. This allows for later updates, such as when
giving one extra --config parameter in the command line, to be
applied consistently throughout the framework and test code.
[MAINTENANCE] The CI jobs now run full checks on each commit on
any proposed PR, not only on its topmost commit. This gives higher
confidence that a commit in a series is not causing breakage that
a later commit then inadvertently fixes.

For a complete list of changes please check the Avocado changelog[11].

For Avocado-VT, please check the full Avocado-VT changelog[12].

Avocado Videos

As yet another way to let users know about what's available in
Avocado, we're introducing short videos with very targeted content on
our very own YouTube channel:

https://www.youtube.com/channel/UCP4xob52XwRad0bU_8V28rQ

The first video available demonstrates a couple of new features
related to the advanced logging mechanisms, introduced on this
release:

https://www.youtube.com/watch?v=8Ur_p5p6YiQ

Install avocado

Instructions are available in our documentation on how to install
either with packages or from source[13].

Updated RPM packages are be available in the project repos for
Fedora 22, Fedora 23, EPEL 6 and EPEL 7.

Happy hacking and testing!

Assets 2

29 Dec 18:35

lmr

0.31.0

d4364ff

Lucky Luke

Hi everyone! Right on time for the holidays, Avocado reaches the end
of Sprint 31, and together with it, we're very happy to announce a brand
new release! This version brings stability fixes and improvements to
both Avocado and Avocado-VT, some new features and a major redesign of
our plugin architecture.

For Avocado the main changes are:

It's now possible to register callback functions to be executed when
all tests finish, that is, at the end of a particular job[1].
The software manager utility library received a lot of love on the
Debian side of things. If you're writing tests that install software
packages on Debian systems, you may be in for some nice treats and
much more reliable results.
Passing malformed commands (such as ones that can not be properly
split by the standard shlex library) to the process utility library
is now better dealt with.
The test runner code received some refactors and it's a lot easier
to follow. If you want to understand how the Avocado test runner
communicates with the processes that run the test themselves, you
may have a much better code reading experience now.
Updated inspektor to the latest and greatest, so that our code is
kept is shiny and good looking (and performing) as possible.
Fixes to the utility GIT library when using a specific local branch
name.
Changes that allow our selftest suite to run properly on virtualenvs.
Proper installation requirements definition for Python 2.6 systems.
A completely new plugin architecture[2]. Now we offload all plugin
discovery and loading to the Stevedore library. Avocado now defines
precise (and simpler) interfaces for plugin writers. Please be aware
that the public and documented interfaces for plugins, at the
moment, allows adding new commands to the avocado command line app,
or adding new options to existing commands. Other functionality can
be achived by "abusing" the core avocado API from within
plugins. Our goal is to expand the interfaces so that other areas of
the framework can be extended just as easily.

For a complete list of changes please check the Avocado changelog[3].

Avocado-VT received just too many fixes and improvements to
list. Please refer to the changelog[4] for more information.

Install avocado

Instructions are available in our documentation on how to install
either with packages or from source[5].

Within a couple of hours, updated RPM packages will be available in
the project repos for Fedora 22, Fedora 23, EPEL 6 and EPEL 7.

Happy hacking and testing!

[1] http://avocado-framework.readthedocs.org/en/0.31.0/ReferenceGuide.html#job-cleanup
[2] http://avocado-framework.readthedocs.org/en/0.31.0/Plugins.html
[3] 0.30.0...0.31.0
[4] avocado-framework/avocado-vt@0.30.0...0.31.0
[5] http://avocado-framework.readthedocs.org/en/0.31.0/GetStartedGuide.html

Assets 2

10 Nov 20:37

clebergnu

0.30.0

bde85d5

Avocado release 0.30.0: Jimmy's Hall

Hello! Avocado reaches the end of Sprint 30, and with it, we have a new release available! This version brings stability fixes and improvements to both Avocado and Avocado-vt.

As software doesn't spring out of life itself, we'd like to acknowledge the major contributions by Lucas (AKA lmr) since the dawn of time for Avocado (and earlier projects like Autotest and virt-test). Although the Avocado team at Red Hat was hit by some changes, we're already extremely happy to see that this major contributor (and good friend) has not gone too far.

Now back to the more informational part of the release notes. For Avocado the main changes are:

New RPM repository location, check the docs[1] for instructions on how to install the latest releases
Makefile rules for building RPMs are now based on mock, to ensure sound dependencies
Packaged versions are now available for Fedora 22, newly released Fedora 23, EL6 and EL7
The software manager utility library now supports DNF
The avocado test runner now supports a dry run mode, which allows users to check how a job would be executed, including tests that would be found and parameters that would be passed to it. This is currently complementary to the avocado list command.
The avocado test runner now supports running simple tests with parameters. This may come in handy for simple use cases when Avocado will wrap a test suite, but the test suite needs some command line arguments.

Avocado-vt also received many bugfixes[3]. Please refer to the changelog for more information.

Install avocado

Instructions are available in our documentation on how to install either with packages or from source[1].

Happy hacking and testing!

[1] http://avocado-framework.readthedocs.org/en/0.30.0/GetStartedGuide.html
[2] 0.29.0...0.30.0
[3] avocado-framework/avocado-vt@0.29.0...0.30.0

Assets 2

08 Oct 11:05

lmr

0.29.0

a64f35e

Avocado release 0.29.0: Steven Universe

Hello! Avocado reaches the end of Sprint 29, and with it, we have a great release coming! This version of avocado once again brings new features and plenty of bugfixes:

The remote and VM plugins now work with --multiplex, so that you can use both features in conjunction.
The VM plugin can now auto detect the IP of a given libvirt domain you pass to it, reducing typing and providing an easier and more pleasant experience.
Temporary directories are now properly cleaned up and no re-creation of directories happens, making avocado more secure.
Avocado docs are now also tagged by release. You can see the specific documentation of this one at our readthedocs page [1]
Test introspection/listing is safer: Now avocado does not load python modules to introspect its contents, an alternative method, based on the Python AST parser is used, which means now avocado will not load possible badly written/malicious code at listing stage. You can find more about that in our test resolution documentation [2]
You can now specify low level loaders to avocado to customize your test running experience. You can learn more about that in the Test Discovery documentation [3]
The usual many bugfixes and polishing commits. You can see the full amount of 96 commits at [4]

For our Avocado VT plugin, the main changes are:

The vt-bootstrap process is now more robust against users interrupting previous bootstrap attempts
Some issues with RPM install in RHEL hosts were fixed
Issues with unsafe temporary directories were fixed, making the VT tests more secure.
Issues with unattended installed were fixed
Now the address of the virbr0 bridge is properly auto detected, which means that our unattended installation content server will work out of the box as long as you have a working virbr0 bridge.

Install avocado

As usual, go to https://copr.fedoraproject.org/coprs/lmr/Autotest/ to install
our YUM/DNF repo and get the latest goodies!

Happy hacking and testing!

[1] http://avocado-framework.readthedocs.org/en/0.29.0
[2] http://avocado-framework.readthedocs.org/en/0.29.0/ReferenceGuide.html#test-resolution
[3] http://avocado-framework.readthedocs.org/en/0.29.0/Loaders.html
[4] 0.28.0...0.29.0

Assets 2

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Users/Test Writers

Bug Fixes

Utility APIs

Internal Changes

Sprint Theme

Release Meeting

Install avocado

Install avocado

LTS in a nutshell

Changes from 35.0:

Install avocado

Install avocado

Packages

Avocado Videos

Install avocado

Install avocado

Install avocado

Releases: avocado-framework/avocado

Downton Abbey

Users/Test Writers

Bug Fixes

Utility APIs

Internal Changes

39.0 The Hateful Eight

Sprint Theme

Release Meeting

Avocado release 38.0: Love, Ken

Install avocado

Avocado release 37.0: Trabant vs. South America

Install avocado

Avocado 36.0lts Release

LTS in a nutshell

Changes from 35.0:

Install avocado

Avocado release 35.0: Mr. Robot

Install avocado

Packages

Avocado release 0.34.0: The Hour of the Star

Avocado Videos

Install avocado

Lucky Luke

Install avocado

Avocado release 0.30.0: Jimmy's Hall

Install avocado

Avocado release 0.29.0: Steven Universe