bind9/unit
Michal Nowak 9e6f6156f7
Omit spurious string from unit test debugging efforts
When both 'broken' and 'failed' test cases appear in unit test output

...
===> Broken tests
lib/isc/tests/socket_test:main  ->  broken: Test case timed out  [300.022s]
===> Failed tests
lib/isc/tests/time_test:main  ->  failed: 2 of 6 tests failed  [0.006s]
===> Summary
...

spurious '===>' string gets matched, that results in the following
error:

  Usage error for command debug: '===>' is not a test case identifier (missing ':'?).

Following change makes sure the string is omitted.

I checked on FreeBSD and OpenBSD that the AWK construct is supported.
2020-01-21 18:14:44 +01:00
..
.gitignore [master] update gitignore files; use rev-parse to get srcid 2014-06-17 13:49:30 -07:00
gdb Gather debug info on broken unit tests 2020-01-06 11:25:09 +00:00
README warn, rather than failing, if kyua is not present 2018-11-16 14:31:36 +01:00
unittest.sh.in Omit spurious string from unit test debugging efforts 2020-01-21 18:14:44 +01:00

Unit tests for BIND 9 are based on the CMocka testing framework and
the Kyua test execution engine.

If your distribution of choice doesn't include packages for kyua or cmocka, the
sources can be found here:

 * Kyua 0.13 - https://github.com/jmmv/kyua/releases
 * CMocka 1.0 - https://cmocka.org/files/