Testing

Platform spec node

Testing

Back to Contracts and effects ◎ Open in platform map

Spec standingStandard

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

ADRs

No architecture decision records under adr/ for this feature yet. Standard features must publish at least one ADR or keep a ## Decisions summary on the hub.

Articles

• Contracts Structural contract declarations, conformance lists, and embedding. Distinct from compiler Mod SDK contracts and from runtime requires/ensures (not in v0.1 grammar). article Standard Reviewed Thu May 21
• Error handling Representing and propagating failures (`Result`, `try`, unwinding policy). Runtime lowering shares the ABI error envelope described in Execution. article Standard Reviewed Thu May 21
• Testing The language-level test harness, discovery, and assertions users rely on. Corelib testing helpers extend but do not redefine these semantics. article Standard Reviewed Thu May 21

History

0 revisions (git unavailable at build; counts may be empty)

Open full history on GitHub

No commits recorded for this path.

Completeness

OKarea · 2 SpecSection(s) · 0 H2 heading(s)

Section id	Required	Found
scope	yes	yes
features	yes	yes

Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).

Related spec docs

• Area
  Contracts and effects

  Parent area

• Domain
  Language meta

  Parent domain hub

• Domain
  Platform specification

  Cross-cutting index

• Domain
  Execution documentation

  Non-normative legacy execution bridge

Normative specification

Scope

Defines the test item, discovery metadata, and skip rules for language-level tests. Harness execution is realized by tooling and corelib helpers.

Syntax

test MyCase {
    meta { timeout = 30; }
    // statements
}

• test Name { body } declares a test entry point; the identifier is followed directly by the test body block (no parameter list).
• meta { key = expr; } sections attach metadata (timeouts, categories) parsed as TestMetaSection.
• skip { key = expr; } sections mark conditional skip predicates.

Static rules

• Test bodies must contain only statements and meta/skip sections allowed by TestBodyItem.
• Tests may appear in Test project kinds; placement in App/Lib projects should warn per manifest policy.
• Attributes on tests follow the general attribute rules (E1508–E1510).

Dynamic semantics

• The test runner must invoke each discovered test entrypoint in isolation unless meta specifies shared fixtures (future).
• Failed assertions must report as test failures without undefined behavior.
• Skipped tests must not count as failures when skip predicates evaluate true.

Diagnostics

Attribute and visibility issues use E15xx; test-specific codes may be added in the registry band reserved for tooling.

Conformance

beskid test (tooling) must discover all test items in Test projects matching this syntax.

Decisions

• D-LM-TST-001 — First-class test item: Tests are module items, not attributes on functions only.
• D-LM-TST-002 — meta/skip blocks: Structured sections replace ad hoc comment conventions.
• D-LM-TST-003 — Test project kind: Discovery should scope to Test projects unless manifest policy allows otherwise.
• D-LM-TST-004 — Corelib helpers are additive: Assertion helpers in corelib must not redefine language-level test syntax.

Platform view

The language-level test harness, discovery, and assertions users rely on. Corelib testing helpers extend but do not redefine these semantics.