This repository has been archived by the owner on Apr 29, 2021. It is now read-only.
Add support for .bats.sh
convention tests
#200
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
IntelliJ IDEA highlights each end of a Bats test case with an error marker when using
.sh
syntax highlighting, which makes Bats adoption much harder in some teams. Thus the feature proposal for supporting.bats.sh
test files with a convention-based test discovery. From README.md:Bash-compatible convention syntax
If your tools don't have built-in support for
.bats
syntax, you canstill use Bats with its support for
.bats.sh
convention tests. Eachfunction declaration starting with the
funciton
keyword is going to beconverted to a Bats test. For example, running the following test file:
will output:
Test suites
You can invoke the
bats
interpreter with multiple test filearguments, or with a path to a directory containing multiple
.bats
and / or
.bats.sh
files. Bats will run each test file individually andaggregate the results. If any test case fails,
bats
exits with a1
status code.