trycmd
trycmd copied to clipboard
Snapshot testing for a herd of CLI tests
~~~md ``` $ stdout='Hello\nWorld' stderr='Goodbye' bin-fixture Hello Goodbye ``` ~~~ produces ~~~ Hello\nWorld Goodbye ~~~
This would offer some flexibility if it is obvious and doesn't complicate the syntax since we have to detect the end of one command's output from the start of the...
From https://github.com/assert-rs/assert_cmd/issues/139 > It would be nice to mention that when running tests in `cross`, one needs to prepend their command with the value contained in `CARGO_TARGET_*_RUNNER` i.e `qemu-aarch64 xh`...
I just started using this library for testing a cli that is used for manipulating files. I absolutely love how painless it's going to make testing, but I did notice...
Building on #92, it'd be great to have structured data handling in trycmd to allow irrelevant details to be glossed over and for smarter wildcards.
In some cases, CLIs cares the ordering of object entries in JSON or other structured data. It'd be great to have an option to check that the entry ordering are...
This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more. ## Open These updates have all been created already. Click a checkbox below to...
I'm working on upgrading to snapbox 0.5, and the new method of comparing an output to a file in the path seems to require more boilerplate. Instead of `.stdout_matches_path(my_path)`, I...
Maybe I'm missing something or using it wrong, please let me know. Current behaviour is that it just reports ok. Seems unexpected when one wants to prepare a snapshot.