Skip to content

Use is assertion messages instead of testing blocks - #21

Merged
olecve merged 1 commit into
mainfrom
refactor/is-messages
Jul 16, 2026
Merged

Use is assertion messages instead of testing blocks#21
olecve merged 1 commit into
mainfrom
refactor/is-messages

Conversation

@olecve

@olecve olecve commented Jul 16, 2026

Copy link
Copy Markdown
Owner

Replaces (testing "…" …) wrappers with per-assertion messages passed as the is message argument (on its own line), across the library tests and both example projects.

  • deftests that had multiple testing blocks are flattened, with each assertion carrying its own descriptive message.
  • Dropped the now-unused testing from every test namespace's :refer.

No behavior change — same assertions, just sourced context from is messages. Verified: root suite (49 tests) and both examples' npm run ci pass; lint + fmt clean.

Replace (testing "…" …) wrappers with per-assertion messages passed as
the is message argument (on its own line), across the library tests and
the example projects. deftests with multiple testing blocks are
flattened, each assertion carrying its own descriptive message. Drop the
now-unused testing refer from every test namespace.
@olecve
olecve merged commit 8a866b8 into main Jul 16, 2026
4 checks passed
@olecve
olecve deleted the refactor/is-messages branch July 16, 2026 14:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant