Skip to content
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

Restore --nocapture as a no-op argument #18

Merged
merged 1 commit into from
Aug 14, 2022

Conversation

sunshowers
Copy link
Contributor

Nextest's custom test harness support requires that tests be run with
--nocapture. Since libtest-mimic doesn't capture output anyway, just
accept --nocapture as a no-op.

I verified that with this change, libtest-mimic becomes compatible
with nextest again.

Nextest's [custom test harness] support requires that tests be run with
`--nocapture`. Since libtest-mimic doesn't capture output anyway, just
accept `--nocapture` as a no-op.

I verified that with this change, libtest-mimic becomes compatible
with nextest again.

[custom test harness]: https://nexte.st/book/custom-test-harnesses.html
@LukasKalbertodt
Copy link
Owner

I removed all of the "unsupported" CLI options because it felt strange to me to have a flag that isn't implemented. But of course you have a good point about --nocapture being the default (and only) mode in libtest-mimic anyway. So I think it makes sense to just merge this as is.

@LukasKalbertodt LukasKalbertodt merged commit 90536df into LukasKalbertodt:master Aug 14, 2022
@sunshowers sunshowers deleted the nocapture branch September 6, 2024 18:34
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.

2 participants