Skip to main content
Description
===========

Framework for testing ebuilds.

Using Docker to provide consistent sandboxed environments, etest runs ebuilds
through several tests (implicitly and explicitly defined). Every ebuild gets
many containers created to run every testing scenario in isolation. Testing
scenarios are created from combinations of USE flags, features (test or no
test), as well as custom commands provided in the hints files.

Installation
============

This package is available in my overlay, alunduil, and can be installed on
Gentoo quite easily::

layman -a alunduil
emerge app-portage/etest

This package is also stored in PyPI and can be installed the standard way::

pip install etest

The latest release available is:

.. image:: https://badge.fury.io/py/etest.png
:target: http://badge.fury.io/py/etest


``etest`` does require a running docker daemon but does not explicitly list it
as a requirement. It's not explicitly listed since the docker daemon doesn't
necessarily need to be local. Non-local docker daemons are not currently
supported.

Using etest
===========

.. note::
etest requires a running docker daemon (either local or remote). If using
a remote docker instance you must set the DOCKER_HOST environment variable
with the hostname (just like compose).

To get started simply run ``etest`` in a directory that contains ebuilds in a
valid overlay.

Alternatively, while still in a valid overlay directory or subdirectory, a list
of ebuilds can be passed to ``etest`` to run tests only against those ebuilds::

# Run all etest tests for all ebuild versions.
cd /var/lib/layman/alunduil
etest app-portage/etest

# Run all etest tests for the specified ebuild.
cd app-portage/etest
etest etest-9999.ebuild

More advanced usage of this package is outlined in the built-in help::

etest --help

Developing etest
================

If you would prefer to clone this package directly from git or assist with
development, the URL is https://github.com/alunduil/etest.

etest is tested continuously by Travis-CI and running the tests is quite
simple::

flake8
python setup.py test

System tests can be run as well but require a working docker daemon as well as
approximately two and half hours::

nosetests test_etest/test_system

The current status of the build is:

.. image:: https://secure.travis-ci.org/alunduil/etest.png?branch=master
:target: http://travis-ci.org/alunduil/etest

Known Issues
============

Known issues can be found in the github issue list at
https://github.com/alunduil/etest/issues.

Troubleshooting
===============

If you need to troubleshoot an issue or submit information in a bug report, we
recommend obtaining the following pieces of information:

* output with verbose output turned on
* any relevant stack traces

Metadata

Release files for etest 1.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for etest 1.0.0
File Size Uploaded Provenance
etest-1.0.0.tar.gz 60.5 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for etest 1.0.0
File Interpreter ABI Platform
etest-1.0.0-py2.py3-none-any.whl Python 2, Python 3 none any Details

Total release size: 149.7 kB

Release files / etest-1.0.0.tar.gz

Download URL etest-1.0.0.tar.gz
Size 60.5 kB
Tags Source
SHA-256 checksum
How to use checksums
1a135181cdf96df2cd32aa853715f5e9a468f1d10292542e684a929ee1183c5d
BLAKE2b-256 checksum
How to use checksums
18f751a8dd4ef5491a8477cbbd5601cc4b4298db435e61bbc5e429294f369824
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Release files / etest-1.0.0-py2.py3-none-any.whl

Download URL etest-1.0.0-py2.py3-none-any.whl
Size 89.2 kB
Tags Python 2 Python 3
SHA-256 checksum
How to use checksums
a8dc4fc1a1170488e030a45afb07b5e7f9a795ec67837dba95ab8f22f6b8a142
BLAKE2b-256 checksum
How to use checksums
d05a8b668055310dbe94de58030c71ba1b8cf74fcc57a094b6869e7e9e05d304
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for etest 1.0.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

1.0.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page