The Test Crusade
If it is not tested, it does not function. Faith is for the Ecclesiarchy — we deal in PROOF.
/church:test-crusade
"Coverage is not a number — it is a SACRED COVENANT with the Machine God. And the Tech-Priests have come to COLLECT on every unfulfilled promise."
— Battle Cry of the Tech-Priests
The Test Crusade deploys four fanatical squads to ensure that every function, every branch, every edge case is covered by meaningful assertions. The Machine God does not accept faith — He demands PROOF through the sacred rites of automated testing.
How the Crusade Operates
The sacred operational sequence, as prescribed by the Fabricator-General.
Reconnaissance
The existing test coverage is scanned by sacred augurs.
Parallel Squad Deployment
All four squads deploy to their designated sectors.
Severity Classification
Untested code is ranked by criticality and blast radius.
Consolidated Battle Report
All findings merged into a single data-slate for the Fabricator-General.
Victory Declaration
Coverage targets met. The Machine God's proof-standard is satisfied.
Continuous Vigil
The test suite stands eternal guard. Regression is heresy.
The Sacred Laws
The holy laws this crusade enforces. Break them and face the Omnissiah's wrath.
Untested code is BROKEN code. It merely has not revealed its corruption yet. The Scrapcode lurks in every untested branch.
Meaningful assertions ONLY. expect(true).toBe(true) is a heretical prayer, not a test. Assert behavior, outcomes, and sacred contracts.
Property-based tests for entities. If a domain entity has invariants, they must be tested against the full space of possible inputs — not merely the ones the developer imagined.
No test debt shall accumulate. Every .skip and .todo is a wound in the Machine Spirit.
Lifecycle tests for factories. If it creates, it must be tested through creation, mutation, and destruction.
The Holy Squad
The specialist Tech-Priest agents deployed during this crusade. Each carries only the doctrine they need.