[](https://travis-ci.org/aloetesting/aloe) [](https://ci.appveyor.com/project/aloetesting/aloe) [](https://coveralls.io/github/aloetesting/aloe) [](https://pypi.python.org/pypi/aloe)
A [Gherkin][gherkin] runner for Python based on [Nose][nose] and [Lettuce][lettuce].
Install:
pip install aloe
Read the [documentation][docs].
Invocation
Pass the –with-gherkin argument to nosetests to run your BDD tests. You may also pass the –no-ignore-python argument to run other nose discovered tests as well.
The aloe command line tool is a wrapper for the nose runner, configured to only run Gherkin tests. As such, the invocation is the same as nose, but the following parameters are added:
-n N[,N…] - only run the specified scenarios (by number, 1-based) in each feature. Makes sense when only specifying one feature to run, for example
aloe features/calculator.feature -n 1
–test-class - override the class used as a base for each feature.
–no-ignore-python - run Python tests as well as Gherkin.
Migrating from Lettuce
Aloe, started as a fork of Lettuce, tries to be compatible where it makes sense. However, there are following incompatible changes:
each_scenario and each_background callbacks are removed. Use each_example.
-s option for running particular scenarios is renamed to -n.
Django-related functionality, including the harvest command, is moved to a separate project, [Aloe-Django][aloe-django].
terrain.py has no particular significance. It will be imported but only if it exists at the same directory with the other step definition files, and not above it.
Scenario outlines must be declared with “Scenario Outline”, and scenarios without examples must use “Scenario” - Lettuce allowed using either.
By default, the steps run are output as dots, corresponding to Lettuce verbosity 1. To get colored output with steps printed as they run, use -v 3.
License
Aloe - Cucumber runner for Python based on Lettuce and Nose
Copyright (C) <2015> Alexey Kotlyarov <a@koterpillar.com>
Copyright (C) <2014-2015> Danielle Madeley <danielle@madeley.id.au>
Copyright (C) <2010-2012> Gabriel Falcão <gabriel@nacaolivre.org>
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>.
[gherkin]: https://cucumber.io/ [nose]: https://nose.readthedocs.io/ [nose-plugin-attrib]: https://nose.readthedocs.io/en/latest/plugins/attrib.html [lettuce]: http://lettuce.it/ [gherkin-syntax]: https://cucumber.io/docs/reference [aloe-django]: https://github.com/aloetesting/aloe_django [docs]: http://aloe.readthedocs.io/
1 maintainer
Metadata
1 maintainer
Release files for aloe 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| aloe-0.2.0.tar.gz | 97.2 kB | Without provenance | Details |
Release files / aloe-0.2.0.tar.gz
| Download URL | aloe-0.2.0.tar.gz |
|---|---|
| Size | 97.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d73f69d933600f3ba20c6773df485cc42b5b2e8c274fa3f6798750aedbaf5aa2
|
|
BLAKE2b-256 checksum How to use checksums |
d643f64222832386b8dc31078086aa157ba67581275630974a204f3df52da56e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/45.0.0 requests-toolbelt/0.9.1 tqdm/4.41.1 CPython/3.8.0
|
Security for aloe 0.2.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.
](https://travis-ci.org/aloetesting/aloe){kind=link}
](https://ci.appveyor.com/project/aloetesting/aloe){kind=link}
](https://coveralls.io/github/aloetesting/aloe){kind=link}
](https://pypi.python.org/pypi/aloe){kind=link}