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
{{ message }}
This repository has been archived by the owner on Apr 29, 2021. It is now read-only.
So if any of the above fails, I only see that the test fails and need to debug the failing line by hand. In bash I can do a set -x to see the lines as they are executed. Is it possible to do something like this in bats?
Thanks
Sven
The text was updated successfully, but these errors were encountered:
Recently we wanted to conveniently enable debug out of the full output of run commands in tests. We did not find a really satisfying solution, but stumpled upon this issue immediately. So adding for all the lost souls with the same problem:
We worked around it by adding some debug code to the teardown() { } function, which has all necessary variables in scope.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi Sam,
I'm currently using bats but have no idea how to dig deeper in a test case when something goes wrong.
Example testcase:
So if any of the above fails, I only see that the test fails and need to debug the failing line by hand. In bash I can do a
set -x
to see the lines as they are executed. Is it possible to do something like this in bats?Thanks
Sven
The text was updated successfully, but these errors were encountered: