-
Notifications
You must be signed in to change notification settings - Fork 34
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
Fine control over signals, stdin, etc #94
Labels
enhancement
Improve the expected
Comments
|
epage
pushed a commit
to epage/assert_cmd
that referenced
this issue
May 29, 2021
In the tree view, we already show the original and the current value, we shouldnt show an entire Diff that is only parseable by color. In changing this, we removed the more cosmetic atom selector. We also removed the edit distance, since there isn't a known case for it. Let us know if you needed this! Fixes assert-rs#94 Fixes assert-rs#105
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As food for thoughts, here's how I'm using
assert_cmd
.The guiding idea is that I build a struct describing programs to run/delay/kill, a set of input files, and a set of post-run checks that operate on created files (including the program's stdout/stderr). I can
run()
on that struct once it is set up, and it takes care of setting up the TempDir, scheduling program start, and running the checks.With that in place, I have a pretty powerful way to write a unittest, using my crate's
main
binary and a few ancillary processes:If there's enough interest, I could try to get this cleared for upstreaming. Currently there are a few extensions and API decisions that are specific to my project, and the code is a bit ad-hoc in places.
Originally posted by @vincentdephily in #74 (comment)
The text was updated successfully, but these errors were encountered: