qt5base-lts/tests/auto/testlib/selftests/expected_commandlinedata.tap

TAP version 13
# tst_DataTable
ok 1 - initTestCase()
# QVERIFY(test)
ok 2 - fiveTablePasses(fiveTablePasses_data1)
# QVERIFY(test)
ok 3 - fiveTablePasses(fiveTablePasses_data2)
# QVERIFY(test)
ok 4 - fiveTablePasses(fiveTablePasses_data3)
# QVERIFY(test)
ok 5 - fiveTablePasses(fiveTablePasses_data4)
# QVERIFY(test)
ok 6 - fiveTablePasses(fiveTablePasses_data5)
# QVERIFY(test)
ok 7 - fiveTablePasses(fiveTablePasses_data1)
ok 8 - cleanupTestCase()
1..8
# tests 8
# pass 8
# fail 0
testlib: Add Test Anything Protocol (TAP) reporter The Test Anything Protocol (TAP), was originally Perl's simple text-based interface between testing modules and test harnesses, but has since been adopted by a large number of producers and consumers in many different languages, which allows colorizing and summarizing test results. The format is very simple: TAP version 13 ok 1 - test description not ok 2 - test description --- message: 'Failure message' severity: fail expected: 123 actual: 456 ... ok 3 - test description # SKIP 1..3 The specification [1] is very brief, so the implementation has been based on how typical consumers behave, especially when it comes to the undefined diagnostics block. [1] http://testanything.org/tap-version-13-specification.html Change-Id: I616e802ea380165c678510e940ddc6607d39c92d Reviewed-by: Simon Hausmann <simon.hausmann@qt.io> 2018-03-01 16:06:23 +00:00			`TAP version 13`
			`# tst_DataTable`
			`ok 1 - initTestCase()`
			`# QVERIFY(test)`
			`ok 2 - fiveTablePasses(fiveTablePasses_data1)`
			`# QVERIFY(test)`
			`ok 3 - fiveTablePasses(fiveTablePasses_data2)`
			`# QVERIFY(test)`
			`ok 4 - fiveTablePasses(fiveTablePasses_data3)`
			`# QVERIFY(test)`
			`ok 5 - fiveTablePasses(fiveTablePasses_data4)`
			`# QVERIFY(test)`
			`ok 6 - fiveTablePasses(fiveTablePasses_data5)`
			`# QVERIFY(test)`
			`ok 7 - fiveTablePasses(fiveTablePasses_data1)`
			`ok 8 - cleanupTestCase()`
			`1..8`
			`# tests 8`
			`# pass 8`
			`# fail 0`