use Test::Builder::Tester tests => 1; use Test::More; test_out("not ok 1 - foo"); test_fail(+1); fail("foo"); test_test("fail works");
The testing system is designed to be used by performing a three step process for each test you wish to test. This process starts with using "test_out" and "test_err" in advance to declare what the testsuite you are testing will output with Test::Builder to stdout and stderr.
You then can run the test(s) from your test suite that call Test::Builder. At this point the output of Test::Builder is safely captured by Test::Builder::Tester rather than being interpreted as real test output.
The final stage is to call "test_test" that will simply compare what you predeclared to what Test::Builder actually outputted, and report the results back with a ``ok'' or ``not ok'' (with debugging) to the normal output.
test_out("ok 1","ok 2");
is the same as
test_out("ok 1\nok 2");
which is even the same as
test_out("ok 1"); test_out("ok 2");
Once "test_out" or "test_err" (or "test_fail" or "test_diag") have been called, all further output from Test::Builder will be captured by Test::Builder::Tester. This means that you will not be able perform further tests to the normal output in the normal way until you call "test_test" (well, unless you manually meddle with the output filehandles)
test_err("# Failed test ($0 at line ".line_num(+1).")");
"test_fail" exists as a convenience function that can be called instead. It takes one argument, the offset from the current line that the line that causes the fail is on.
This means that the example in the synopsis could be rewritten more simply as:
test_out("not ok 1 - foo"); test_fail(+1); fail("foo"); test_test("fail works");
The "test_diag" function prepends comment hashes and spacing to the start and newlines to the end of the expected output passed to it and adds it to the list of expected error output. So, instead of writing
test_err("# Couldn't open file");
you can write
test_diag("Couldn't open file");
Remember that Test::Builder's diag function will not add newlines to the end of output and test_diag will. So to check
You would do
without the newlines.
This takes name/value pairs that effect how the test is run.
As a convenience, if only one argument is passed then this argument is assumed to be the name of the test (as in the above examples.)
Once "test_test" has been run test output will be redirected back to the original filehandles that Test::Builder was connected to (probably STDOUT and STDERR,) meaning any further tests you run will function normally and cause success/errors for Test::Harness.
Essentially this is the same as the "__LINE__" macro, but the "line_num(+3)" idiom is arguably nicer.
In addition to the six exported functions there exists one function that can only be accessed with a fully qualified function call.
To assist you "test_test" can colour the background of the debug information to disambiguate the different types of output. The debug output will have its background coloured green and red. The green part represents the text which is the same between the executed and actual output, the red shows which part differs.
The "color" function determines if colouring should occur or not. Passing it a true or false value will enable or disable colouring respectively, and the function called with no argument will return the current setting.
To enable colouring from the command line, you can use the Text::Builder::Tester::Color module like so:
perl -Mlib=Text::Builder::Tester::Color test.t
Or by including the Test::Builder::Tester::Color module directly in the PERL5LIB.
Calls "Test::Builder->no_ending" turning off the ending tests. This is needed as otherwise it will trip out because we've run more tests than we strictly should have and it'll register any failures we had that we were testing for as real failures.
The color function doesn't work unless Term::ANSIColor is compatible with your terminal. Additionally, Win32::Console::ANSI must be installed on windows platforms for color output.
Bugs (and requests for new features) can be reported to the author though GitHub: <https://github.com/Test-More/test-more/issues>
Some code taken from Test::More and Test::Catch, written by Michael G Schwern <email@example.com>. Hence, those parts Copyright Micheal G Schwern 2001. Used and distributed with permission.