This release is a pre-release and may not be stable for production use.
behave
behave is behavior-driven development, Python style.
Behavior-driven development (or BDD) is an agile software development technique that encourages collaboration between developers, QA and non-technical or business participants in a software project.
behave uses tests written in a natural language style, backed up by Python code.
First, install *behave*.
Now make a directory called “features/”. In that directory create a file called “example.feature” containing:
# -- FILE: features/example.feature
Feature: Showing off behave
Scenario: Run a simple test
Given we have behave installed
When we implement 5 tests
Then behave will test them for us!
Make a new directory called “features/steps/”. In that directory create a file called “example_steps.py” containing:
# -- FILE: features/steps/example_steps.py
from behave import given, when, then, step
@given('we have behave installed')
def step_impl(context):
pass
@when('we implement {number:d} tests')
def step_impl(context, number): # -- NOTE: number is converted into integer
assert number > 1 or number == 0
context.tests_count = number
@then('behave will test them for us!')
def step_impl(context):
assert context.failed is False
assert context.tests_count >= 0
Run behave:
$ behave
Feature: Showing off behave # features/example.feature:2
Scenario: Run a simple test # features/example.feature:4
Given we have behave installed # features/steps/example_steps.py:4
When we implement 5 tests # features/steps/example_steps.py:8
Then behave will test them for us! # features/steps/example_steps.py:13
1 feature passed, 0 failed, 0 skipped
1 scenario passed, 0 failed, 0 skipped
3 steps passed, 0 failed, 0 skipped, 0 undefined
Now, continue reading to learn how to get the most out of behave. To get started, we recommend the tutorial and then the feature testing language and api references.
More Information
behave.example: Behave Examples and Tutorials (docs, executable examples).
changelog (latest changes)
Metadata
Release files for behave-bse 1.2.7.dev5
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 | Actions |
|---|---|---|---|---|
| behave-bse-1.2.7.dev5.tar.gz | 772.5 kB | Without provenance | Details for behave-bse-1.2.7.dev5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| behave_bse-1.2.7.dev5-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for behave_bse-1.2.7.dev5-py2.py3-none-any.whl |
Total release size: 949.3 kB
Release files / behave-bse-1.2.7.dev5.tar.gz
| Download URL | behave-bse-1.2.7.dev5.tar.gz |
|---|---|
| Size | 772.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
78af152c3d3105863e277b444b9d51ccefe570848a895c6788b93faaba4e6e47
|
|
BLAKE2b-256 checksum How to use checksums |
18679045ac2ee5cabb3d233c13e6c78371130caec38c122b479288b92d842df0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.5
|
Release files / behave_bse-1.2.7.dev5-py2.py3-none-any.whl
| Download URL | behave_bse-1.2.7.dev5-py2.py3-none-any.whl |
|---|---|
| Size | 176.8 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
629a21f69f7cf4014a83eebe7b34c9fc1a3402620c7480ee173a742b6d29d03c
|
|
BLAKE2b-256 checksum How to use checksums |
7915a78fc0e771240c3595495ae08de59e76e6abc87b6513adbde5b71481fd2a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.5
|
Security for behave-bse 1.2.7.dev5
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.