We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We should consider using UI tests to the CI/tests ala snapbox or trycmd
snapbox
trycmd
this would help catch unexpected changes to output that don't necessarily cause the build to error.
The text was updated successfully, but these errors were encountered:
I think assert_cmd might be the proper tool for the job here: https://crates.io/crates/assert_cmd
Edit: trycmd is probably better, and I'll try to configure it entirely tomorrow.
Sorry, something went wrong.
I think some variant of this should be finished prior to 0.3.0, just to avoid any regressions during our next release.
Alexhuszagh
Successfully merging a pull request may close this issue.
We should consider using UI tests to the CI/tests ala
snapbox
ortrycmd
this would help catch unexpected changes to output that don't necessarily cause the build to error.
The text was updated successfully, but these errors were encountered: