bats-assert
bats-assert copied to clipboard
bats-core
Common assertions for Bats
Copy the arguments from the bats-core install.sh so that bats libraries can be packaged in the same manner as bats-core.
It's really hard to detect the difference between actual and expected output right from the bats message when the test fails. Because bats doesn't indicate what the difference between expectation...
When creating the release 2.1.0, you accidentally published a lightweight tag. As a result, `v2.1.0` shows up as `v2.0.0-79-g78fa631` when pulled in as a submodule. Not sure if fixing this...
The `run` command in `bats-core` has the ability to keep stderr-related output into separate variables: > Use `--separate-stderr` to split stdout and stderr into `$output`/`$stderr` and `${lines[@]}`/`${stderr_lines[@]}` as per https://bats-core.readthedocs.io/en/latest/writing-tests.html#run-test-other-commands...
Optional explanation on assertion result ======================================== Sometimes we write checks based not directly in the output but in some derived result. E.g. consider the case of checking for the nr...
nicely there is no typos. Nevertheless decided to submit a PR so it remains such. Sent similar ones for bats-core and bats-files
As already posted in https://github.com/bats-core/bats-support/issues/8, the use of CC0 for code is no longer allowed in Fedora (see https://lwn.net/Articles/902410/.) Would it be possible to relicense bats-assert to another, more widely...
Hi, thanks for your work on this package - incredibly helpful. Running into a small issue, when I `npm install` the package I get this warning: ``` npm WARN [email protected]...
