Conformance vs unit

Two different questions:

1. Does my package behave? — your test items, your CI job.
2. Does Beskid still mean what the spec says? — beskid_tests, beskid_e2e_tests, and the Conformance area.

Confusing them is how you ship a green app on a red language.

Your unit and integration tests

• Authored as test items in your repos.
• Run with beskid test and your tags/groups.
• Prove your contracts, parsers, and business rules.

Platform conformance harnesses

The reference compiler workspace (compiler/Cargo.toml) includes:

Crate	Role
beskid_tests	Fixture-heavy behavior locks, incremental/mod scheduling
beskid_e2e_tests	End-to-end CLI and pipeline scenarios

Normative policy: Conformance evidence, Test harnesses and fixtures.

flowchart TB
  userTests[Your test items in .bd files]
  cli[beskid test]
  conformance[beskid_tests / beskid_e2e_tests in compiler CI]
  spec[Platform spec contracts]
  userTests --> cli
  conformance --> spec
  cli -.->|does not replace| conformance

When to contribute upstream

If you found a language or compiler bug (diagnostic code wrong, spawn lowering changed, manifest resolution drift), add or extend a conformance fixture in compiler/ and update the spec in the same change set (spec leads code).

Next

CI and testing