Skip to content
Skills Library
Programming · Testing

test-behaviour

/test-behaviour

Pick the test shape that proves a behaviour. Use when you ask "how do I test this?", add a test, test a domain rule, a lifecycle, a retry, a session, a UI interaction, a timer, or a race, or review a test that might be tautological.

Repository
PAROL6 ↗
Licence
MIT
Last repository change
12.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
4
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Pick the test shape that proves a behaviour. Use when you ask "how do I test this?", add a test, test a domain rule, a lifecycle, a retry, a session, a UI interaction, a timer, or a race, or review a test that might be tautological.

Triggers from the description

how do I test this?
Original author description

Pick the test shape that proves a behaviour. Use when you ask "how do I test this?", add a test, test a domain rule, a lifecycle, a retry, a session, a UI interaction, a timer, or a race, or review a test that might be tautological.

How it works

  1. 1. A domain rule: a property
  2. 2. Anything with history: a model
  3. 3. UI behaviour: a Foldkit Scene
  4. 4. A seam: one example
  5. 5. Always: plant a bug
Original SKILL.md headings · 73 lines, 400 words
SKILL.md preview
---
name: test-behaviour
description: Pick the test shape that proves a behaviour. Use when you ask "how do I test this?", add a test, test a domain rule, a lifecycle, a retry, a session, a UI interaction, a timer, or a race, or review a test that might be tautological.
plain: "Name what the test proves, pick the shape for it, then plant a bug and watch the test fail."
diagram: |-
  what does it prove?
  ├ domain rule  → it.prop
  ├ history      → model test
  ├ UI behaviour → Scene
  └ one seam     → example
      │
  plant a bug → test fails
  restore     → test passes
---

# Test a behaviour

A test proves one behaviour. Name that behaviour before you write the test. Then pick the shape below that fits it.

Each shape returns a fixed, independent answer. A test that reruns the code under test cannot catch its mistakes. Read [tests that earn their place](https://github.com/joelhooks/rat-stack/blob/main/.brain/resources/lore/tests-that-earn-their-place.svx) first.

## 1. A domain rule: a property

A rule that holds for many inputs is an `it.prop` over Effect `Arbitrary` inputs. Use `it.effect.prop` when the check returns an Effect.

The core suite generates names and checks their length after trimming. The assertion states the accepted length without calling the validator:

```ts repo=rat-stack path=packages/core/test/join-identity.test.ts at=f1e24f7ee9f9b5f4a06574cb8c1646de001e4a3f lines=101-120

```

Read [property-based testing](https://github.com/joelhooks/rat-stack/blob/main/.brain/resources/lore/property-based-testing.svx).

## 2. Anything with history: a model

Sessions, retries, and lifecycles depend on earlier steps. Generate command sequences and check the real system against a small model after each step.

The inspection lifecycle replays generated histories against the real actor:

```ts repo=rat-stack path=packages/core/test/inspect-machine.model.test.ts at=1d4d3252326a216909ccec05e93312d1ab0eaf84 lines=214-219

```

Copy `skills/add-a-lifecycle-machine/templates/lifecycle.model.test.md` for a new machine. Read [model-based testing](https://github.com/joelhooks/rat-stack/blob/main/.brain/resources/lore/model-based-testing.svx).

## 3. UI behaviour: a Foldkit Scene

A Scene runs `update`, the view, and subscriptions together. Input and time are data:

- Input is a step: `pointerDown`, `click`, `type`, or `Subscription.emit`.
- Time is a Command. Resolve it with `Command.resolve(WaitX, CompletedWaitX(...))`.
- Do not use fake timers, a clock, or a DOM.

A race is a plain assertion. Resolve a stale timer after the state has moved on, then assert that nothing broke.

Assert on what the view shows: roles, text, and data attributes. Do not assert on Model fields.

The reader's copy button resolves the copy and then its reset wait:

```ts repo=rat-stack path=apps/web/test/reader.scene.test.ts at=1d4d3252326a216909ccec05e93312d1ab0eaf84 lines=51-69

```

Read [UI behaviour is a scene](https://github.com/joelhooks/rat-stack/blob/main/.brain/resources/lore/ui-behaviour-is-a-scene.svx) for the Foldkit UI Toast race.

## 4. A seam: one example

An example test fits one interface between parts, such as a service over the real filesystem. Keep one, and supply services through a Layer:

```ts repo=rat-stack path=packages/core/test/file-inspector.test.ts at=1d4d3252326a216909ccec05e93312d1ab0eaf84 lines=24-34

```

## 5. Always: plant a bug

1. Break the behaviour the test protects.
2. Run the test. It must fail.
3. Restore the code. The test must pass.

Reject these tests:

- A tautological test computes its expected answer with the code under test.
- A change-detector test fails on any edit and proves no rule.
- A regression test for a bug the suite already covers adds nothing.

Do not rewrite an expected result to match broken code.

Versions

The database has no other skills named test-behaviour.

Database snapshot: 13.11.2026 · package version 26bbadfec0d9 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100test-retry-config
    Test Retry Config - Auto-activating skill for Test Automation. Triggers on: test retry config, test retry config Part of the Test Automation skill category. Use when writing or running tests. Trigger with phrases like "test retry config", "test config", "test".
  • 100test-first
    Use when implementing a feature, fixing a bug, refactoring, or changing behaviour in any codebase, before writing the production code that does it.
  • 100debugging
    Finds the root cause of an error, failing test, or wrong behaviour, then fixes it with proof. Use when something is broken, a test fails, or output is unexpected.
  • 100spec-binding-review
    Judge whether a `/** @scenario */` bind proves its scenario: every Then step proven by an assertion; the test at the scenario's level (an @integration composition scenario is proven by booting the composition, not by a unit with fakes); a test of a library instance the test…
  • 100integration-e2e-testing
    Selects and designs the smallest integration/E2E test set that proves accepted behavior at an observable boundary. Use when writing or reviewing E2E or integration tests.
  • 100tester
    Prove behaviour in the RUNNING product, not in a diff: Test 0 reproduces a reported bug before any fix, Test 3 accepts a landed change by the same user path with before/after evidence. Use when the brief says tester or тестер and names Test 0 or Test 3.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.