q6-report for behave
The behave recorder of q6-report, a test report that keeps a project's history in one HTML file, with no server and no network.
The recorder writes each scenario's result while behave runs, and the q6-report command from npm adds the run to the history and writes the page.
Install
From the suite's root, npx --yes q6-report init does everything below once, with the tool the project uses, and says what it changed.
By hand:
Add it beside behave with the tool that keeps your project's dependencies, e.g: Poetry, which writes it into pyproject.toml:
poetry add --group dev q6-report
pip install q6-report installs it into the active environment only, so a project on pip also lists q6-report in its requirements file.
Turn it on in behave.ini, as a formatter under the first one, which stays on the format line:
[behave]
format = pretty
q6_report.behave_recorder:Recorder
The recorder writes into a q6-report folder in the folder behave runs from, or into the folder Q6_REPORT_DIR names.
A failed scenario shows its screenshot when the suite saves its screenshots as files into one folder, named once in behave.ini; for each attempt, the recorder takes the newest image saved there while it ran:
[behave.userdata]
q6_report.screenshots = screenshots
A suite with no such folder hands each file over with q6_report.attach_image(path) from its screenshot code.
The page
When behave ends, the recorder writes the page with the q6-report command from npm, of its own version, and behave prints where the page is.
That needs Node 22 or newer on the machine; without it, the recorder says what to run on a machine that has it, beside the folder.
In a CI, the page is written once, after every job, by npx --yes q6-report finish, so there the recorder leaves it.
A run stopped with Ctrl+C goes to a page of trial runs, which the report links to, and leaves the report's history as it was.
Screenshots, attachments, settings and the CI setups are in the README.
Metadata
Release files for q6-report 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| q6_report-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for q6_report-0.1.1-py3-none-any.whl |
Release files / q6_report-0.1.1-py3-none-any.whl
| Download URL | q6_report-0.1.1-py3-none-any.whl |
|---|---|
| Size | 13.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ad9efc05d6dea275e0053771052dffd77d7820890f0e03848cc018793bfe44a5
|
|
BLAKE2b-256 checksum How to use checksums |
1245f731e0d0bf6798794d7b46548496d955d21ae36d7ebee11624b5c7ebf13e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.
Transparency logSecurity for q6-report 0.1.1
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.
Full provenance
1 file in this release has been uploaded with provenance metadata.
Attestation for q6_report-0.1.1-py3-none-any.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.
Transparency logA 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.