pytest-bdd implements a subset of the Gherkin language to enable automating project requirements testing and to facilitate behavioral driven development.
Current build status
All platforms:
Current release info
Name
Downloads
Version
Platforms
Installing pytest-bdd
Installing pytest-bdd from the conda-forge channel can be achieved by adding conda-forge to your channels with:
Once the conda-forge channel has been enabled, pytest-bdd can be installed with conda:
conda install pytest-bdd
or with mamba:
mamba install pytest-bdd
It is possible to list all of the versions of pytest-bdd available on your platform with conda:
conda search pytest-bdd --channel conda-forge
or with mamba:
mamba search pytest-bdd --channel conda-forge
Alternatively, mamba repoquery may provide more information:
# Search all versions available on your platform:
mamba repoquery search pytest-bdd --channel conda-forge
# List packages depending on `pytest-bdd`:
mamba repoquery whoneeds pytest-bdd --channel conda-forge
# List dependencies of `pytest-bdd`:
mamba repoquery depends pytest-bdd --channel conda-forge
About conda-forge
conda-forge is a community-led conda channel of installable packages.
In order to provide high-quality builds, the process has been automated into the
conda-forge GitHub organization. The conda-forge organization contains one repository
for each of the installable packages. Such a repository is known as a feedstock.
A feedstock is made up of a conda recipe (the instructions on what and how to build
the package) and the necessary configurations for automatic building using freely
available continuous integration services. Thanks to the awesome service provided by
Azure, GitHub,
CircleCI, AppVeyor,
Drone, and TravisCI
it is possible to build and upload installable packages to the
conda-forgeanaconda.org
channel for Linux, Windows and OSX respectively.
To manage the continuous integration and simplify feedstock maintenance
conda-smithy has been developed.
Using the conda-forge.yml within this repository, it is possible to re-render all of
this feedstock’s supporting files (e.g. the CI configuration files) with conda smithy rerender.
feedstock - the conda recipe (raw material), supporting scripts and CI configuration.
conda-smithy - the tool which helps orchestrate the feedstock.
Its primary use is in the construction of the CI .yml files
and simplify the management of many feedstocks.
conda-forge - the place where the feedstock and smithy live and work to
produce the finished article (built conda distributions)
Updating pytest-bdd-feedstock
If you would like to improve the pytest-bdd recipe or build a new
package version, please fork this repository and submit a PR. Upon submission,
your changes will be run on the appropriate platforms to give the reviewer an
opportunity to confirm that the changes result in a successful build. Once
merged, the recipe will be re-built and uploaded automatically to the
conda-forge channel, whereupon the built conda packages will be available for
everybody to install and use from the conda-forge channel.
Note that all branches in the conda-forge/pytest-bdd-feedstock are
immediately built and any created packages are uploaded, so PRs should be based
on branches in forks and branches in the main repository should only be used to
build distinct package versions.
In order to produce a uniquely identifiable distribution:
If the version of a package is not being increased, please add or increase
the build/number.
If the version of a package is being increased, please remember to return
the build/number
back to 0.
About pytest-bdd-feedstock
Feedstock license: BSD-3-Clause
Home: https://github.com/pytest-dev/pytest-bdd
Package license: MIT
Summary: BDD for pytest
Development: https://github.com/pytest-dev/pytest-bdd
Documentation: https://github.com/pytest-dev/pytest-bdd
pytest-bdd implements a subset of the Gherkin language to enable automating project requirements testing and to facilitate behavioral driven development.
Current build status
Current release info
Installing pytest-bdd
Installing
pytest-bdd
from theconda-forge
channel can be achieved by addingconda-forge
to your channels with:Once the
conda-forge
channel has been enabled,pytest-bdd
can be installed withconda
:or with
mamba
:It is possible to list all of the versions of
pytest-bdd
available on your platform withconda
:or with
mamba
:Alternatively,
mamba repoquery
may provide more information:About conda-forge
conda-forge is a community-led conda channel of installable packages. In order to provide high-quality builds, the process has been automated into the conda-forge GitHub organization. The conda-forge organization contains one repository for each of the installable packages. Such a repository is known as a feedstock.
A feedstock is made up of a conda recipe (the instructions on what and how to build the package) and the necessary configurations for automatic building using freely available continuous integration services. Thanks to the awesome service provided by Azure, GitHub, CircleCI, AppVeyor, Drone, and TravisCI it is possible to build and upload installable packages to the conda-forge anaconda.org channel for Linux, Windows and OSX respectively.
To manage the continuous integration and simplify feedstock maintenance conda-smithy has been developed. Using the
conda-forge.yml
within this repository, it is possible to re-render all of this feedstock’s supporting files (e.g. the CI configuration files) withconda smithy rerender
.For more information please check the conda-forge documentation.
Terminology
feedstock - the conda recipe (raw material), supporting scripts and CI configuration.
conda-smithy - the tool which helps orchestrate the feedstock. Its primary use is in the construction of the CI
.yml
files and simplify the management of many feedstocks.conda-forge - the place where the feedstock and smithy live and work to produce the finished article (built conda distributions)
Updating pytest-bdd-feedstock
If you would like to improve the pytest-bdd recipe or build a new package version, please fork this repository and submit a PR. Upon submission, your changes will be run on the appropriate platforms to give the reviewer an opportunity to confirm that the changes result in a successful build. Once merged, the recipe will be re-built and uploaded automatically to the
conda-forge
channel, whereupon the built conda packages will be available for everybody to install and use from theconda-forge
channel. Note that all branches in the conda-forge/pytest-bdd-feedstock are immediately built and any created packages are uploaded, so PRs should be based on branches in forks and branches in the main repository should only be used to build distinct package versions.In order to produce a uniquely identifiable distribution:
build/number
.build/number
back to 0.Feedstock Maintainers