08. Green tests, red production
Beskid tests in source, the test CLI, and why CI still distrusts your optimism.
Green tests, red production
Green tests are a mood. Production is where the runtime remembers every optimistic return; you left in a harness.
This chapter is informative: how to write test items, run them with beskid test, and understand the difference between “my file passed” and “the platform still conforms.” Normative grammar and discovery rules live under Testing.
What you will find here
Section titled “What you will find here”| Section | Topic |
|---|---|
| Test items in source | test Name { }, meta, and skip. |
The beskid test CLI | Discovery, filters, JSON output. |
| Arrange, act, assert | Structure without a framework cult. |
| Conformance vs unit | beskid_tests vs your project’s tests. |
| CI and testing | What the compiler repo actually runs. |
By the end of this chapter
Section titled “By the end of this chapter”- Declare and tag tests beside the code they exercise.
- Filter runs by tag and group for fast local loops.
- Know when to read book/reference/testing/ vs compiler conformance.
Start here
Section titled “Start here”Test items in source — or jump to The beskid test CLI if you already copied a harness from a colleague.
Next chapter
Section titled “Next chapter”09. Contracts, effects, and other polite threats — structural contracts, Result, and why panic is not a design pattern.