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.
When I see a test failing I can't see the outputs and the status provided by the tested scripts. It would be great when on each call of "run" the $output and the $status is written to a logfile that can be used in Jenkins to be archived so that a developer can check what was going on. Here the feature request in details:
Executing bats tool with option --log= (path must exist, file need not exist, append mode)
Logging name of related test
Logging a kind of message: "status of run was ..." (of related run)
Logging output of related run
The text was updated successfully, but these errors were encountered:
Getting feedback on failing tests. This has been discussed many times before. See Standard Library of Test Helpers #110 for a detailed discussion. The conculsion is that only the developer knows what information is relevant to any given failing assertion. This led to the development of helper libraries. See bats-docs, bats-assert and bats-file.
When I see a test failing I can't see the outputs and the status provided by the tested scripts. It would be great when on each call of "run" the $output and the $status is written to a logfile that can be used in Jenkins to be archived so that a developer can check what was going on. Here the feature request in details:
The text was updated successfully, but these errors were encountered: