Revision as of 22:52, 19 August 2020

External

How to troubleshoot tests - how do I get access to intermediate stderr and stdout?
bats vs. bats-core (https://github.com/bats-core/bats-core.git). Apparently bats-core supersedes bats, and it should be used instead. Research, and understand the difference. One is that bats error reports are included as comments, not part of tap output, and are not therefore propagated to the Xunit version of tap-xunit. In other words, bats-core includes builtin xunit output.

Revision as of 22:45, 19 August 2020 (view source) Ovidiu (talk \| contribs) (→‎TODO) ← Older edit		Revision as of 22:52, 19 August 2020 (view source) Ovidiu (talk \| contribs) (→‎TODO) Newer edit →
Line 18:		Line 18:

	* How to troubleshoot tests - how do I get access to intermediate stderr and stdout?		* How to troubleshoot tests - how do I get access to intermediate stderr and stdout?
	* bats vs. bats-core (https://github.com/bats-core/bats-core.git). Apparently bats-core supersedes bats, and it should be used instead. Research, and understand the difference. One is that bats error reports are included as comments, not part of tap output, and are not therefore propagated to the Xunit version of tap-xunit.		* bats vs. bats-core (https://github.com/bats-core/bats-core.git). Apparently bats-core supersedes bats, and it should be used instead. Research, and understand the difference. One is that bats error reports are included as comments, not part of tap output, and are not therefore propagated to the Xunit version of tap-xunit. In other words, bats-core includes builtin xunit output.