Repository navigation

ENG-190: explicit test scenarios in the client - #349

Open

NejcS wants to merge 23 commits into

mainfrom

feat/explicit-test-scenarios

Open

ENG-190: explicit test scenarios in the client#349
NejcS wants to merge 23 commits into
mainfrom
feat/explicit-test-scenarios

Commits on Oct 29, 2026
- build: pin plain-parser to the explicit-test-scenarios branch
  NejcS
  committed
  c7e244d
- test: convert the .plain fixtures and examples to the current syntax
  NejcS
  committed
  9b58c03
- feat: read test scenarios from the test folders
  NejcS
  committed
  dbdc708
- feat: take func-ids in --render-range and --render-from
  NejcS
  committed
  61bc811
- feat: track the render state by func-id
  NejcS
  committed
  785b8ca
- test: use func-ids in the git and journal tests
  NejcS
  committed
  02ee1c3
- feat: send test scenarios to the backend in the spec tree
  NejcS
  committed
  092a931
- feat: warn when scenarios are found but conformance tests are off
  NejcS
  committed
  62412ec
- feat: name a functionality as module and func-id in the TUI, telemetry and logs
  NejcS
  committed
  d114c5a
- docs: regenerate the CLI reference from the checkout
  NejcS
  committed
  a4d18c4
- feat: render a functionality without scenarios, without its conformance tests
  NejcS
  committed
  73bce58
- feat: require an explicit test directory when conformance tests are on
  NejcS
  committed
  4926330
- fix: bind scenarios once per module and refuse a numbered build folder
  NejcS
  committed
  5b4cc01
- test: use func-ids in the render stop reason tests
  NejcS
  committed
  743413d
- fix: render the acceptance scenarios that remain after a code fix
  NejcS
  committed
  f021773
- feat: check that the acceptance tests implement the scenarios
  NejcS
  committed
  76dc422
- docs: add --job-tag to the CLI reference
  NejcS
  committed
  ec2a4fe
Commits on Oct 30, 2026
Commits on Oct 31, 2026
- feat: rename the test folder option to --tests-folder
  NejcS
  committed
  b1647ae
- feat: default the tests folder to "tests" next to the plain file
  NejcS
  committed
  b455488

Navigation Menu

Repository navigation

ENG-190: explicit test scenarios in the client - #349

ENG-190: explicit test scenarios in the client#349
NejcS wants to merge 23 commits into
mainfrom
feat/explicit-test-scenarios

Commits on Oct 29, 2026

build: pin plain-parser to the explicit-test-scenarios branch

test: convert the .plain fixtures and examples to the current syntax

feat: read test scenarios from the test folders

feat: take func-ids in --render-range and --render-from

feat: track the render state by func-id

test: use func-ids in the git and journal tests

feat: send test scenarios to the backend in the spec tree

feat: warn when scenarios are found but conformance tests are off

feat: name a functionality as module and func-id in the TUI, telemetry and logs

docs: regenerate the CLI reference from the checkout

feat: render a functionality without scenarios, without its conformance tests

feat: require an explicit test directory when conformance tests are on

fix: bind scenarios once per module and refuse a numbered build folder

test: use func-ids in the render stop reason tests

fix: render the acceptance scenarios that remain after a code fix

feat: check that the acceptance tests implement the scenarios

docs: add --job-tag to the CLI reference

Commits on Oct 30, 2026

fix: render an acceptance scenario once, whatever path asks for it

fix: write the acceptance tests again when the conformance tests are regenerated

fix: read the markdown of a required module functionality in the unit tests fixer

style: format the acceptance scenario test with black

Commits on Oct 31, 2026

feat: rename the test folder option to --tests-folder

feat: default the tests folder to "tests" next to the plain file