Skip to content

Make .trycmd more cram like #19

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Nov 9, 2021
Merged

Make .trycmd more cram like #19

merged 5 commits into from
Nov 9, 2021

Conversation

epage
Copy link
Contributor

@epage epage commented Nov 9, 2021

This makes a .trycmd file look like:

$ ls
> -a
? success

with > being a line continuation and ? being optional exit status.

epage added 5 commits November 9, 2021 12:45
Pass is a test status, success if a program exit status.
BREAKING CHANGE: Renamed
- `fail` to `failed`
- `skip` to `skipped`
This will open us up to expanding the syntax in the future.
cram ignores exit codes (except code 80 being skipped).  We want to
support verifying the intended exit code to avoid the need for toml
files.
This also deviates from cram because cram ignores exit codes (except
`80` which is skip).
@epage epage merged commit fad7262 into assert-rs:main Nov 9, 2021
@epage epage deleted the cram branch November 9, 2021 19:50
epage added a commit to epage/snapbox that referenced this pull request May 14, 2024
chore(ci): Ensure CI job always runs
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