Reusable step library for behave with multi-technology support and i18n.
Project description
behave-steplib
Reusable step libraries for Behave BDD — share, discover and install step definitions across projects. Zero mandatory dependencies; each technology is an optional extra.
Why behave-steplib?
Writing BDD step definitions for HTTP APIs, web browsers, databases and Kafka is repetitive. Every project re-implements the same "send a request", "check the status code", "query the database" steps. behave-steplib provides a curated, typed, multilingual library of reusable steps that you install once and share across projects.
- Modular —
api,web,db,kafka,data,io,climodules activated via extras and lazy imports. Install only what you need. - Auto-registered —
autoload(context)discovers every installed step via Python entry points and registers it with behave in one line. - Multilingual — steps defined in English with
esandpttranslations; all patterns are registered with behave so matching works regardless of the language used in feature files. - Typed — full type hints,
mypy --strictclean,py.typedmarker included. - CLI —
steplib list / show / validate / initpowered by Typer for inspecting and validating your step library from the terminal. - Pluggable — third-party packages can register steps via the
steplib.pluginsentry point group;autoloaddiscovers them automatically. - Ecosystem — integrates with
behave-kit(soft assertions),behave-tables(table conversion) andbehave-data(test data loading) when installed. - Backends — each module supports multiple backends (e.g. stdlib/httpx/requests for API, selenium for web) selectable at autoload time.
Installation
pip install behave-steplib # core only (behave, parse, typer)
pip install behave-steplib[api] # + httpx HTTP client
pip install behave-steplib[requests] # + requests HTTP client
pip install "behave-steplib[api,requests,web,db,kafka,data,io]" # + all technology extras
pip install "behave-steplib[all]" # + every technology extra
pip install behave-steplib[dev] # + pytest, ruff, mypy, build, twine
| Extra | Packages | Description |
|---|---|---|
[api] |
httpx |
HTTP API testing with httpx |
[requests] |
requests |
HTTP API testing with requests |
[web] |
selenium |
Browser testing with Selenium |
[db] |
sqlalchemy |
Database testing with SQLAlchemy |
[kafka] |
kafka-python-ng |
Kafka producer/consumer testing |
[io] |
jsonschema |
File, JSON, CSV and directory operations |
[cli] |
— | Shell command execution and assertions |
[kit] |
behave-kit |
Soft assertions, typed context, fixtures |
[data] |
behave-data |
Test data loading (CSV, JSON, YAML, Excel) |
[tables] |
behave-tables |
Table conversion helpers |
[dev] |
pytest, ruff, mypy, build, twine | Development tools |
[docs] |
sphinx, furo, myst-parser, sphinx-autodoc-typehints | Documentation tools |
[all] |
api, requests, web, db, kafka, kit, data, tables, io | Everything except dev/docs |
Requirements
- Python 3.11+ (tested on CPython 3.11, 3.12, 3.13 and 3.14)
- behave — the only mandatory runtime dependency alongside
parseandtyper
Quickstart
Level 1 — Automatic wiring
Add three hooks to your environment.py and every installed step is wired automatically:
# features/environment.py
from steplib.behave import autoload
def before_all(context):
context.steplib = autoload(context)
def before_scenario(context, scenario):
context.steplib.reset()
def after_scenario(context, scenario):
context.steplib.cleanup()
Or generate it with the CLI:
steplib init
Level 2 — Explicit load
Load only the modules you need by dotted path:
from steplib.behave import load
def before_all(context):
context.steplib = load(context, "steplib.modules.api.steps")
Level 3 — Filtered autoload
When multiple extras are installed, narrow which steps are active:
from steplib.behave import autoload
def before_all(context):
context.steplib = autoload(
context,
categories=["api"],
backends={"api": "httpx"},
)
Example feature
Feature: API health check
Scenario: GET users returns 200
Given the API base url is "https://api.example.com"
When I send a GET request to "/users"
Then the response status is 200
And the response body is valid JSON
And the JSON path "$.users[0].name" equals "Ada"
Multilingual features
Steps are defined in English and translated to Spanish and Portuguese. All patterns are registered with behave — no language switch needed:
# es
Cuando envío una petición GET a "/users"
Entonces el estado de la respuesta es 200
# pt
Quando envio uma requisição GET para "/users"
Então o status da resposta é 200
Modules
API
HTTP API testing with stdlib (urllib), httpx or requests backends. 55 steps covering configuration, authentication, SSL/redirects, requests (body, form, JSON, query params, headers), status/body/JSON Path/header/response-time assertions, store/extract, variable reuse and table comparison.
Given the API base url is "https://api.example.com"
And I set the bearer token to "eyJhbGciOi..."
When I send a POST request to "/users" with JSON body
"""
{"name": "Ada", "email": "ada@example.com"}
"""
Then the response status is 201
And the JSON path "$.id" is not null
And the response time is less than 5 seconds
And I store the JSON path "$.id" as "user_id"
Web
Browser testing with Selenium (Chrome, Firefox, headless). 34 steps covering configuration, navigation, interactions (click, type, clear, select, screenshot), waits, assertions (title, URL, element presence/visibility/enabled/text/attribute, page content), cookies, frame switching and store/extract.
Given the web base url is "https://example.com"
When I navigate to "/login"
And I type "admin" into the element id "username"
And I type "secret" into the element id "password"
And I click the element id "submit"
Then the page title is "Dashboard"
And the element id "welcome" is visible
And I store the text of element id "username" as "displayed_name"
DB
Database testing with SQLAlchemy (SQLite, PostgreSQL, MySQL, ...). 22 steps covering connection management, query execution (with bind parameters), row count assertions, column assertions (equals, not equals, contains, null, not null), scalar queries, table assertions, transactions and store/extract.
Given the database connection string is "sqlite:///test.db"
When I connect to the database
And I execute the SQL query "SELECT * FROM users"
Then the query returns 3 rows
And the column "name" in the first row equals "Ada"
And the column "email" in the first row contains "@"
And I store the column "id" from the first row as "user_id"
Kafka
Kafka producer and consumer testing with kafka-python-ng. 20 steps covering bootstrap/group/offset configuration, producer/consumer config overrides, message production (single, JSON, batch from table), consumption (with optional timeout), assertions (count, contains, key/value by index, regex, order) and store/extract.
Given the Kafka bootstrap servers are "localhost:9092"
And the Kafka consumer group is "test-group"
When I produce a message to topic "events" with key "id" and value "hello"
And I consume messages from topic "events" with timeout 10000 ms
Then the consumed messages count is 1
And the message at index 0 has value "hello"
And I store the message count as "total_messages"
Data
Generic variable management and environment variable handling — cross-module variable store, file loading (JSON/YAML), dot-path extraction, scenario-safe env var modifications, regex/string assertions, numeric comparisons, and a wait utility. 32 steps covering variable set/assert/delete/copy/clear, JSON parsing, file loading, key-path extraction, regex match, starts/ends with, increment, greater/less than, full environment variable lifecycle, and sleep.
Given I set the variable "user_id" to "42"
Then the variable "user_id" equals "42"
And the variable "user_id" has length 2
When I load the JSON file "data/user.json" into the variable "user"
And I extract the key path "address.city" from the variable "user" as "city"
Then the variable "city" equals "Berlin"
And the variable "email" matches the pattern ".*@.*\..*"
When I increment the variable "counter" by 1
Then the variable "counter" is greater than 0
When I wait for 0.5 seconds
Given I set the environment variable "API_KEY" to "secret123"
Then the environment variable "API_KEY" exists
When I store the environment variable "API_KEY" as "api_key"
IO
File, JSON, CSV and directory operations with optional JSON Schema validation. 38 steps covering file CRUD (read, write, append, delete, copy, move, rename, create empty), file assertions (exists, not exists, same, size, extension), JSON operations (load, save, path get/set/delete, validity, schema match, diff, merge, type check), CSV operations (create, write row, save, header row), directory operations (create, exists, not exists, list, delete) and read file as lines.
Given I create the directory "output/logs"
When I write "hello" to the file "output/logs/test.txt"
Then the file "output/logs/test.txt" exists
And the file size of "output/logs/test.txt" is greater than 0 bytes
When I read the file "output/logs/test.txt" as lines into "lines"
Then the variable "lines" has length 1
Given I load the JSON file "data/config.json"
Then the JSON path "$.version" equals "1.0"
And the JSON matches the schema "schemas/config.json"
And the last JSON is valid
When I create the CSV file "output/data.csv" with header "name,age"
And I write the CSV row "Alice,30" to the file "output/data.csv"
And I save the CSV file
Then the directory "output" exists
When I delete the directory "output"
Then the directory "output" does not exist
CLI
Shell command execution with subprocess, capturing exit code, stdout and stderr. 10 steps covering command execution (with optional timeout), exit code assertions, stdout assertions (contains, not contains, equals, matches pattern), stderr assertions, and storing output (stdout and stderr) into variables.
When I run the command "echo hello"
Then the command exit code is 0
And the command output contains "hello"
And the command output does not contain "error"
And the command output matches the pattern "hell."
When I store the command output as "result"
Then the variable "result" contains "hello"
When I run the command "echo error 1>&2" with timeout 10 seconds
And I store the command error output as "errors"
Then the command stderr contains "error"
CLI
steplib list # list all registered steps
steplib list --category api # filter by category
steplib list --backend httpx # filter by backend
steplib list --json # output as JSON
steplib show "I send a {method} request to {url}"
steplib validate # validate step contracts
steplib init # generate features/environment.py
Writing custom steps
Use the @step decorator to define your own steps with full metadata:
from steplib import Param, step
@step(
"the invoice total is {total:f}",
category="invoice",
description="Assert the invoice total matches.",
parameters=[Param("total", type=float, required=True)],
example='Then the invoice total is 19.99',
i18n={
"es": "el total de la factura es {total:f}",
"pt": "o total da fatura é {total:f}",
},
tags=["invoice"],
version="1.0.0",
)
def step_invoice_total(context, total):
assert context.invoice.total == total
Register steps in a register(registry) function and declare an entry point:
# pyproject.toml
[project.entry-points."steplib.plugins"]
mycompany = "mycompany.steps:register"
Once installed, autoload(context) discovers your package automatically.
Development
make dev # install with api, requests, dev and docs extras
make lint # ruff + mypy --strict
make test-cov # pytest with >=80% coverage gate
make docs-build # build Sphinx documentation
make build # build sdist + wheel
Documentation
Full documentation is available at https://mathiaspaulenko.github.io/behave-steplib.
Acknowledgements
- Behave — the BDD framework this library extends.
- parse — pattern matching for step definitions.
- Typer — CLI framework.
- Sphinx + furo — documentation.
License
MIT — see LICENSE.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file behave_steplib-1.4.0.tar.gz.
File metadata
- Download URL: behave_steplib-1.4.0.tar.gz
- Upload date:
- Size: 154.3 kB
- Tags: Source
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.13.14
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
e77fc7552e5f947d1a1baafdb8e68f8a2de5f3f848a857ef525db54f0003de50
|
|
| MD5 |
37612ccaaa3df1f1aeeb4d4bfb92cbd4
|
|
| BLAKE2b-256 |
6fc1795f92f4e3ad0573563124ff95edf552699c0b849f76b9738e0375bc93d2
|
Provenance
The following attestation bundles were made for behave_steplib-1.4.0.tar.gz:
Publisher:
release.yml on MathiasPaulenko/behave-steplib
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
behave_steplib-1.4.0.tar.gz -
Subject digest:
e77fc7552e5f947d1a1baafdb8e68f8a2de5f3f848a857ef525db54f0003de50 - Sigstore transparency entry: 2273566820
- Sigstore integration time:
-
Permalink:
MathiasPaulenko/behave-steplib@fa1281d9c48651603c059f70520ec0872ede3c79 -
Branch / Tag:
refs/tags/v1.4.0 - Owner: https://github.com/MathiasPaulenko
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
release.yml@fa1281d9c48651603c059f70520ec0872ede3c79 -
Trigger Event:
push
-
Statement type:
File details
Details for the file behave_steplib-1.4.0-py3-none-any.whl.
File metadata
- Download URL: behave_steplib-1.4.0-py3-none-any.whl
- Upload date:
- Size: 94.7 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.13.14
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
db40c04a9019533ee67d2c1aedd1d78945d6fae73890209981c8123302e1d3f6
|
|
| MD5 |
b9894e6e7904e50c480904dbd9add469
|
|
| BLAKE2b-256 |
1131967b57e410a30fdfdcf547d80a5d5c56db1c7c0621117ac4fcbf9a813493
|
Provenance
The following attestation bundles were made for behave_steplib-1.4.0-py3-none-any.whl:
Publisher:
release.yml on MathiasPaulenko/behave-steplib
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
behave_steplib-1.4.0-py3-none-any.whl -
Subject digest:
db40c04a9019533ee67d2c1aedd1d78945d6fae73890209981c8123302e1d3f6 - Sigstore transparency entry: 2273567269
- Sigstore integration time:
-
Permalink:
MathiasPaulenko/behave-steplib@fa1281d9c48651603c059f70520ec0872ede3c79 -
Branch / Tag:
refs/tags/v1.4.0 - Owner: https://github.com/MathiasPaulenko
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
release.yml@fa1281d9c48651603c059f70520ec0872ede3c79 -
Trigger Event:
push
-
Statement type: