You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The vendor-ed Bats allows to specify the --tap option which shows the test results in TAP format. This is very useful in the context of continuous integration systems, where this kind of output can be easily parsed and interpreted.
Are there any plans to support this in busser-bats?
The text was updated successfully, but these errors were encountered:
If there are no plans to support this, would there be any interest in a PR? Actually, I'm not sure how many layers deep I'd need to go to get this functionality. Since I have no interest in using the default bats behavior, it might make more sense if I just fork the code and change the line in the runner_plugin/bats.rb where bats is called.
EDIT:
I ended up not using the kitchen verify step at all. Instead, I installed bats using my test playbook and executed the test suite using kitchen exec. This is not as flexible a solution, but it works well enough for my needs.
The vendor-ed Bats allows to specify the
--tap
option which shows the test results in TAP format. This is very useful in the context of continuous integration systems, where this kind of output can be easily parsed and interpreted.Are there any plans to support this in busser-bats?
The text was updated successfully, but these errors were encountered: