Skip to content

WIP: ts.ts parity, eval-tester fixtures#339

Open
balupton wants to merge 14 commits intomasterfrom
dev/parity
Open

WIP: ts.ts parity, eval-tester fixtures#339
balupton wants to merge 14 commits intomasterfrom
dev/parity

Conversation

@balupton
Copy link
Copy Markdown
Member

@balupton balupton commented Apr 8, 2026

breaking changes:

  • eval-tester and __do no longer strip trailing newlines, and the ability to so so has been removed; tests expected outputs must be updated

balupton added 10 commits April 8, 2026 12:25
- adds comments
- consistent conventions
- help parity with bash
as `run` better implies the outputs are visible
it now outputs visible errors on mismatches

this was able to catch a mismatch in `stdinargs.bash`

the code has also been reworked to be more understandable and less redundant

finally it fixes a latent bug where the prior use of `segments[*]` produced invalid outputs as segment indexes are for segments, not for the concat string
adds a `EVAL_TESTER_ADD_TRAILING_NEWLINES_TO_SPECIFIED_EXPECTATIONS` env variable to make this easier, applied to all `is-fs-tests.bash` sourcers

also some minor linting and spellchecks
/ref 96e4a8f

STDIN should not have had `original_output_value` applied
elements are now inline, which creates intuitive output for exact mode - `expected` output now called `expect` for alignment with `actual`

this made it easier to fix `read-key` tests for exactness
this is better, as `expected` is better than `expect`

this mad it easier to resolve the `echo-min` exactness failures
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant