pytest-rulebearing

Each Rulebearing architecture rule as a test in the pytest run: one item per rule, failing with the rule's fix and its first violations. Source, documentation and releases: https://github.com/benbahrenburg/rulebearing

pip install pytest-rulebearing        # installs the rulebearing wheel for this platform too
pytest --rulebearing                  # or set rulebearing = true, below

[tool.pytest.ini_options]
rulebearing = true
rulebearing_config = "rulebearing.yaml"   # optional; the binary finds one by default
rulebearing_args = ["src"]                # optional; what to cruise

What it does

When --rulebearing is passed or rulebearing = true is set, the plugin runs rulebearing cruise --output-type json once, during collection, and adds one item per rule, named rulebearing::<rule> and marked rulebearing (so -m rulebearing and -k select them). It never evaluates a rule: the binary decides, the plugin reports (ADR-0010 rule 4).

The failure message is exactly the message the junit reporter writes for that rule (crates/rb-report/src/junit.rs, Wave 2 plan § 1.5):

A run that writes no result (the binary is missing, or the configuration is invalid) is one failing item, rulebearing::cruise, whose message is the command, its exit code and its stderr.

Paths on the command line are relative to the invocation directory; paths in the ini file are relative to the ini file, which is also where the binary runs.

Developing

The plugin is linted and type-checked by the root configuration through cargo xtask lint (ADR-0023) and holds the 70% line floor of ADR-0018. The tests run against the shared fixture adapters/fixture with the binary built from the checkout; tests/test_junit_equality.py is the proof that every message equals rulebearing cruise -T junit's.

cargo build --release -p rb-cli
pip install pytest pytest-cov hatchling packaging
pytest adapters/python --cov=adapters/python          # from the repository root

Plan: Wave 2, Step 14. Release: docs/release.md.