Using a Python BDD test runner like behave, create living documentation from your BDD feature files. This library will create documents that contain up-to-date information about your BDD specs and helps generate a static site for your living documentation.
Current supported document types:
*.mmark files (to be used by Hugo)
Installation
pip install livingdocs
You should also install the Hugo binaries in order to generate your static site: https://gohugo.io/overview/installing/
Quick Start
Use the CLI command livingdocs to configure your Hugo site:
$ livingdocs Your site's title: <enter title> Your site's description: <enter description> ....
This will create a livingdocs folder in your root directory which will have a Hugo skeleton to create a static site.
Using a test runner like behave, you can generate documents for each feature, scenario and step. In environment.py, you can use the DocsMaker to capture this information:
from livingdocs.maker import DocsMaker
def before_all(context):
context.docs = DocsMaker('feature')
def before_scenario(context, scenario):
context.docs.start_scenario(context, scenario)
def after_scenario(context, scenario):
context.docs.end_scenario(context, scenario)
def before_feature(context, feature):
context.docs.start_feature(context, feature)
def after_feature(context, feature):
context.docs.end_feature(context, feature)
def before_step(context, step):
context.docs.start_step(context, step)
def after_step(context, step):
"""
if context.browser is an instance
of Selenium Webdriver, then it will
take a snapshot of this step.
"""
context.docs.end_step(context, step)
Development
First create a virtual env, then to run the tests use:
tox -e py27
License
BSD License
Changelog
0.2.0 (2016-09-16)
Feature - added cli command to generate static site
0.1.3 (2016-09-13)
Bugfix - Feature filename path can be nested directories
0.1.2 (2016-08-21)
Don’t include Pillow (or PIL) in basic install setup.
0.1.1 (2016-08-21)
Requirements are installed during setup.
0.1.0 (2016-08-21)
First release on PyPI.
Metadata
Release files for livingdocs 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 | |
|---|---|---|---|---|
| livingdocs-0.2.0.tar.gz | 233.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| livingdocs-0.2.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 462.0 kB
Release files / livingdocs-0.2.0.tar.gz
| Download URL | livingdocs-0.2.0.tar.gz |
|---|---|
| Size | 233.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
54410503b44c514ae2c9dd84143aa54726f679dae9405972acafca99d93ba104
|
|
BLAKE2b-256 checksum How to use checksums |
cc35df7137f9fbe76df53d85ab2f007d167d7ea3005b1cc4fd824b6e12074c84
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / livingdocs-0.2.0-py2.py3-none-any.whl
| Download URL | livingdocs-0.2.0-py2.py3-none-any.whl |
|---|---|
| Size | 228.8 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
7772c6dde2eea6e5c925c82f046e710c8085f34d839119947843b290d103333c
|
|
BLAKE2b-256 checksum How to use checksums |
2c2b637c5cbeae30addaa76feedded97e1c6f8a761ddf65b78bd9740149c3804
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for livingdocs 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.