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)
Getting feedback on failing tests. This has been discussed many times before. See #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.
Logging. This has been a long awaited feature and a number of attempts have been made. See #123 and #173. None of them have been merged yet due to lack of time from the maintainer (see #150).
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: