3rd-party/catch2
1
0
Fork 0
mirror of https://github.com/catchorg/Catch2.git synced 2024-11-22 21:36:11 +01:00
Code Issues Packages Projects Releases Wiki Activity
e260288807
catch2/tests/SelfTest/Baselines/console.sw.approved.txt

19018 lines
617 KiB
Plaintext
Raw Normal View History

Change reporters to report filters in round-trippable format
2022-10-27 20:43:00 +02:00
Filters: "*" ~[!nonportable] ~[!benchmark] ~[approvals]
Always report rng seed from builtin reporters Not all reporters use a format that supports this, so TeamCity and Automake reporters still do not report it. The console reporter now reports it even on successful runs, where before it only reported the rng seed in the header, which was showed either for failed run, or for run with `-s`. CLoses #2065
2022-04-19 10:32:13 +02:00
Randomness seeded to: 1
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Report Catch2's version in the xml reporter output
2022-05-03 19:44:55 +02:00
<exe-name> is a Catch2 v<version> host application.
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Run with -? for options
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
# A test name that starts with a #
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with message:
yay
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
Small cleanup of self tests
2019-08-04 13:50:25 +02:00
-------------------------------------------------------------------------------
#1027: Bitfields can be captured
-------------------------------------------------------------------------------
Compilation.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Compilation.tests.cpp:<line number>: PASSED:
Add compilation test for #1027
2017-11-13 10:07:06 +01:00
REQUIRE( y.v == 0 )
with expansion:
0 == 0
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Compilation.tests.cpp:<line number>: PASSED:
Add compilation test for #1027
2017-11-13 10:07:06 +01:00
REQUIRE( 0 == y.v )
with expansion:
0 == 0
Fix compilation for types where relops don't return bool Closes #1147
2018-01-12 15:43:56 +01:00
-------------------------------------------------------------------------------
#1147
-------------------------------------------------------------------------------
Compilation.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Compilation.tests.cpp:<line number>: PASSED:
Fix compilation for types where relops don't return bool Closes #1147
2018-01-12 15:43:56 +01:00
REQUIRE( t1 == t2 )
with expansion:
{?} == {?}
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Compilation.tests.cpp:<line number>: PASSED:
Fix compilation for types where relops don't return bool Closes #1147
2018-01-12 15:43:56 +01:00
REQUIRE( t1 != t2 )
with expansion:
{?} != {?}
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Compilation.tests.cpp:<line number>: PASSED:
Fix compilation for types where relops don't return bool Closes #1147
2018-01-12 15:43:56 +01:00
REQUIRE( t1 < t2 )
with expansion:
{?} < {?}
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Compilation.tests.cpp:<line number>: PASSED:
Fix compilation for types where relops don't return bool Closes #1147
2018-01-12 15:43:56 +01:00
REQUIRE( t1 > t2 )
with expansion:
{?} > {?}
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Compilation.tests.cpp:<line number>: PASSED:
Fix compilation for types where relops don't return bool Closes #1147
2018-01-12 15:43:56 +01:00
REQUIRE( t1 <= t2 )
with expansion:
{?} <= {?}
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Compilation.tests.cpp:<line number>: PASSED:
Fix compilation for types where relops don't return bool Closes #1147
2018-01-12 15:43:56 +01:00
REQUIRE( t1 >= t2 )
with expansion:
{?} >= {?}
https://github.com/catchorg/Catch2/issues/1175 - don't list hidden tests by default
2018-02-08 23:18:32 +01:00
-------------------------------------------------------------------------------
#1175 - Hidden Test
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
https://github.com/catchorg/Catch2/issues/1175 - don't list hidden tests by default
2018-02-08 23:18:32 +01:00
Fix stringifying static array of unsigned chars The fix leaves an open question: should we keep treating refs to static array of chars as strings, or should we instead use `strnlen` to check if it is null-terminated within the buffer Fixes #1238
2018-04-06 11:39:40 +02:00
-------------------------------------------------------------------------------
#1238
-------------------------------------------------------------------------------
Compilation.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Compilation.tests.cpp:<line number>: PASSED:
Fix stringifying static array of unsigned chars The fix leaves an open question: should we keep treating refs to static array of chars as strings, or should we instead use `strnlen` to check if it is null-terminated within the buffer Fixes #1238
2018-04-06 11:39:40 +02:00
REQUIRE( std::memcmp(uarr, "123", sizeof(uarr)) == 0 )
with expansion:
0 == 0
with messages:
uarr := "123"
sarr := "456"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Compilation.tests.cpp:<line number>: PASSED:
Fix stringifying static array of unsigned chars The fix leaves an open question: should we keep treating refs to static array of chars as strings, or should we instead use `strnlen` to check if it is null-terminated within the buffer Fixes #1238
2018-04-06 11:39:40 +02:00
REQUIRE( std::memcmp(sarr, "456", sizeof(sarr)) == 0 )
with expansion:
0 == 0
with messages:
uarr := "123"
sarr := "456"
Support for parenthesizing types with commas.
2018-04-10 04:41:44 +02:00
-------------------------------------------------------------------------------
#1245
-------------------------------------------------------------------------------
Compilation.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Compilation.tests.cpp:<line number>: PASSED:
Support for parenthesizing types with commas.
2018-04-10 04:41:44 +02:00
Refactor SectionInfo constructors
2019-11-16 21:53:32 +01:00
-------------------------------------------------------------------------------
#1319: Sections can have description (even if it is not saved
SectionName
-------------------------------------------------------------------------------
Compilation.tests.cpp:<line number>
...............................................................................
Compilation.tests.cpp:<line number>: PASSED:
Add tests for #1403
2018-10-13 14:43:58 +02:00
-------------------------------------------------------------------------------
#1403
-------------------------------------------------------------------------------
Compilation.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Compilation.tests.cpp:<line number>: PASSED:
Add tests for #1403
2018-10-13 14:43:58 +02:00
REQUIRE( h1 == h2 )
with expansion:
[1403 helper] == [1403 helper]
Fix vendored dep because upstream is non-responsive Eventually this needs to be fixed in the textflow project by Phil, but he has not done so in the half a year this bug has been known to be there, so... Closes #1470 Closes #1455
2019-04-10 20:15:42 +02:00
-------------------------------------------------------------------------------
#1455 - INFO and WARN can start with a linebreak
-------------------------------------------------------------------------------
Message.tests.cpp:<line number>
...............................................................................
Message.tests.cpp:<line number>: warning:
This info message starts with a linebreak
This warning message starts with a linebreak
No assertions in test case '#1455 - INFO and WARN can start with a linebreak'
Add tests for #1514 If the regression comes back, it will only be caught by approvals, but that's better than nothing.
2019-03-02 21:22:41 +01:00
This would not be caught previously
Force flush streams in tests for #1514 This avoids the problem where writes to stderr/stdout stop being line-buffered when stderr/stdout is redirected to a file, which led to different order of outputs between Linux and Windows in our tests.
2019-03-06 21:53:17 +01:00
Nor would this
Add tests for #1514 If the regression comes back, it will only be caught by approvals, but that's better than nothing.
2019-03-02 21:22:41 +01:00
-------------------------------------------------------------------------------
#1514: stderr/stdout is not captured in tests aborted by an exception
-------------------------------------------------------------------------------
Tricky.tests.cpp:<line number>
...............................................................................
Tricky.tests.cpp:<line number>: FAILED:
explicitly with message:
1514
Namespace our type traits in catch_meta Previously they could conflict with user-defined type traits that were in the global namespace. Fixes #1548
2019-02-23 21:06:16 +01:00
-------------------------------------------------------------------------------
#1548
-------------------------------------------------------------------------------
Compilation.tests.cpp:<line number>
...............................................................................
Compilation.tests.cpp:<line number>: PASSED:
REQUIRE( std::is_same<TypeList<int>, TypeList<int>>::value )
with expansion:
true
Fix bug in test spec parser handling of escaping in ORed patterns It did not clear out all of its internal state when switching from one pattern to another, so when it should've escaped `,`, it took its position from its position in the original user-provided string, rather than its position in the current pattern. Fixes #1905
2020-04-12 18:44:42 +02:00
-------------------------------------------------------------------------------
#1905 -- test spec parser properly clears internal state between compound tests
-------------------------------------------------------------------------------
Split tests for TestSpec into its own file They also got slapped with the `[approvals]` tag in the process, because we have too many approval tests and want less of them, and these particular tests don't bring much value. Related to #2090
2022-10-26 21:03:49 +02:00
TestSpec.tests.cpp:<line number>
Fix bug in test spec parser handling of escaping in ORed patterns It did not clear out all of its internal state when switching from one pattern to another, so when it should've escaped `,`, it took its position from its position in the original user-provided string, rather than its position in the current pattern. Fixes #1905
2020-04-12 18:44:42 +02:00
...............................................................................
Split tests for TestSpec into its own file They also got slapped with the `[approvals]` tag in the process, because we have too many approval tests and want less of them, and these particular tests don't bring much value. Related to #2090
2022-10-26 21:03:49 +02:00
TestSpec.tests.cpp:<line number>: PASSED:
Fix bug in test spec parser handling of escaping in ORed patterns It did not clear out all of its internal state when switching from one pattern to another, so when it should've escaped `,`, it took its position from its position in the original user-provided string, rather than its position in the current pattern. Fixes #1905
2020-04-12 18:44:42 +02:00
REQUIRE( spec.matches(*fakeTestCase("spec . char")) )
with expansion:
true
Split tests for TestSpec into its own file They also got slapped with the `[approvals]` tag in the process, because we have too many approval tests and want less of them, and these particular tests don't bring much value. Related to #2090
2022-10-26 21:03:49 +02:00
TestSpec.tests.cpp:<line number>: PASSED:
Fix bug in test spec parser handling of escaping in ORed patterns It did not clear out all of its internal state when switching from one pattern to another, so when it should've escaped `,`, it took its position from its position in the original user-provided string, rather than its position in the current pattern. Fixes #1905
2020-04-12 18:44:42 +02:00
REQUIRE( spec.matches(*fakeTestCase("spec , char")) )
with expansion:
true
Split tests for TestSpec into its own file They also got slapped with the `[approvals]` tag in the process, because we have too many approval tests and want less of them, and these particular tests don't bring much value. Related to #2090
2022-10-26 21:03:49 +02:00
TestSpec.tests.cpp:<line number>: PASSED:
Fix bug in test spec parser handling of escaping in ORed patterns It did not clear out all of its internal state when switching from one pattern to another, so when it should've escaped `,`, it took its position from its position in the original user-provided string, rather than its position in the current pattern. Fixes #1905
2020-04-12 18:44:42 +02:00
REQUIRE_FALSE( spec.matches(*fakeTestCase(R"(spec \, char)")) )
with expansion:
!false
Add more tests for test spec parser Originally the tests were from #1912, but as it turned out, the issue was somewhere else. Still, the inputs provided were interesting, so they are now part of our test suite.
2020-04-17 21:16:18 +02:00
-------------------------------------------------------------------------------
#1912 -- test spec parser handles escaping
Various parentheses
-------------------------------------------------------------------------------
Split tests for TestSpec into its own file They also got slapped with the `[approvals]` tag in the process, because we have too many approval tests and want less of them, and these particular tests don't bring much value. Related to #2090
2022-10-26 21:03:49 +02:00
TestSpec.tests.cpp:<line number>
Add more tests for test spec parser Originally the tests were from #1912, but as it turned out, the issue was somewhere else. Still, the inputs provided were interesting, so they are now part of our test suite.
2020-04-17 21:16:18 +02:00
...............................................................................
Split tests for TestSpec into its own file They also got slapped with the `[approvals]` tag in the process, because we have too many approval tests and want less of them, and these particular tests don't bring much value. Related to #2090
2022-10-26 21:03:49 +02:00
TestSpec.tests.cpp:<line number>: PASSED:
Add more tests for test spec parser Originally the tests were from #1912, but as it turned out, the issue was somewhere else. Still, the inputs provided were interesting, so they are now part of our test suite.
2020-04-17 21:16:18 +02:00
REQUIRE( spec.matches(*fakeTestCase(R"(spec {a} char)")) )
with expansion:
true
Split tests for TestSpec into its own file They also got slapped with the `[approvals]` tag in the process, because we have too many approval tests and want less of them, and these particular tests don't bring much value. Related to #2090
2022-10-26 21:03:49 +02:00
TestSpec.tests.cpp:<line number>: PASSED:
Add more tests for test spec parser Originally the tests were from #1912, but as it turned out, the issue was somewhere else. Still, the inputs provided were interesting, so they are now part of our test suite.
2020-04-17 21:16:18 +02:00
REQUIRE( spec.matches(*fakeTestCase(R"(spec [a] char)")) )
with expansion:
true
Split tests for TestSpec into its own file They also got slapped with the `[approvals]` tag in the process, because we have too many approval tests and want less of them, and these particular tests don't bring much value. Related to #2090
2022-10-26 21:03:49 +02:00
TestSpec.tests.cpp:<line number>: PASSED:
Add more tests for test spec parser Originally the tests were from #1912, but as it turned out, the issue was somewhere else. Still, the inputs provided were interesting, so they are now part of our test suite.
2020-04-17 21:16:18 +02:00
REQUIRE_FALSE( spec.matches(*fakeTestCase("differs but has similar tag", "[a]")) )
with expansion:
!false
-------------------------------------------------------------------------------
#1912 -- test spec parser handles escaping
backslash in test name
-------------------------------------------------------------------------------
Split tests for TestSpec into its own file They also got slapped with the `[approvals]` tag in the process, because we have too many approval tests and want less of them, and these particular tests don't bring much value. Related to #2090
2022-10-26 21:03:49 +02:00
TestSpec.tests.cpp:<line number>
Add more tests for test spec parser Originally the tests were from #1912, but as it turned out, the issue was somewhere else. Still, the inputs provided were interesting, so they are now part of our test suite.
2020-04-17 21:16:18 +02:00
...............................................................................
Split tests for TestSpec into its own file They also got slapped with the `[approvals]` tag in the process, because we have too many approval tests and want less of them, and these particular tests don't bring much value. Related to #2090
2022-10-26 21:03:49 +02:00
TestSpec.tests.cpp:<line number>: PASSED:
Add more tests for test spec parser Originally the tests were from #1912, but as it turned out, the issue was somewhere else. Still, the inputs provided were interesting, so they are now part of our test suite.
2020-04-17 21:16:18 +02:00
REQUIRE( spec.matches(*fakeTestCase(R"(spec \ char)")) )
with expansion:
true
Improved generator tracking * Successive executions of the same `GENERATE` macro (e.g. because of a for loop) no longer lead to multiple nested generators. * The same line can now contain multiple `GENERATE` macros without issues. Fixes #1913
2020-06-01 19:04:23 +02:00
-------------------------------------------------------------------------------
#1913 - GENERATE inside a for loop should not keep recreating the generator
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( counter < 7 )
with expansion:
3 < 7
-------------------------------------------------------------------------------
#1913 - GENERATE inside a for loop should not keep recreating the generator
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( counter < 7 )
with expansion:
6 < 7
-------------------------------------------------------------------------------
#1913 - GENERATEs can share a line
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( i != j )
with expansion:
1 != 3
-------------------------------------------------------------------------------
#1913 - GENERATEs can share a line
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( i != j )
with expansion:
1 != 4
-------------------------------------------------------------------------------
#1913 - GENERATEs can share a line
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( i != j )
with expansion:
2 != 3
-------------------------------------------------------------------------------
#1913 - GENERATEs can share a line
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( i != j )
with expansion:
2 != 4
Modify generator tracking to allow GENERATEs between SECTIONs This means that code such as ```cpp TEST_CASE() { SECTION("first") { SUCCEED(); } auto _ = GENERATE(1, 2); SECTION("second") { SUCCEED(); } } ``` will run and report 3 assertions, 1 from section "first" and 2 from section "second". This also applies for greater and potentially more confusing nesting, but fundamentally it is up to the user to avoid overly complex and confusing nestings, just as with `SECTION`s. The old behaviour of `GENERATE` as first thing in a `TEST_CASE`, `GENERATE` not followed by a `SECTION`, etc etc should be unchanged. Closes #1938
2020-07-04 17:45:30 +02:00
-------------------------------------------------------------------------------
#1938 - GENERATE after a section
A
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
with message:
A
-------------------------------------------------------------------------------
#1938 - GENERATE after a section
B
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
1
-------------------------------------------------------------------------------
#1938 - GENERATE after a section
B
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
2
-------------------------------------------------------------------------------
#1938 - GENERATE after a section
B
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
3
-------------------------------------------------------------------------------
#1938 - Section followed by flat generate
A
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( 1 )
-------------------------------------------------------------------------------
#1938 - Section followed by flat generate
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
2
-------------------------------------------------------------------------------
#1938 - Section followed by flat generate
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
3
-------------------------------------------------------------------------------
#1938 - flat generate
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
1
-------------------------------------------------------------------------------
#1938 - flat generate
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
2
-------------------------------------------------------------------------------
#1938 - flat generate
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
3
-------------------------------------------------------------------------------
#1938 - mixed sections and generates
A
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
with message:
A
-------------------------------------------------------------------------------
#1938 - mixed sections and generates
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
with messages:
i := 1
j := 3
k := 5
-------------------------------------------------------------------------------
#1938 - mixed sections and generates
B
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
with message:
B
-------------------------------------------------------------------------------
#1938 - mixed sections and generates
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
with messages:
i := 1
j := 3
k := 6
-------------------------------------------------------------------------------
#1938 - mixed sections and generates
B
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
with message:
B
-------------------------------------------------------------------------------
#1938 - mixed sections and generates
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
with messages:
i := 1
j := 4
k := 5
-------------------------------------------------------------------------------
#1938 - mixed sections and generates
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
with messages:
i := 1
j := 4
k := 6
-------------------------------------------------------------------------------
#1938 - mixed sections and generates
A
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
with message:
A
-------------------------------------------------------------------------------
#1938 - mixed sections and generates
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
with messages:
i := 2
j := 3
k := 5
-------------------------------------------------------------------------------
#1938 - mixed sections and generates
B
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
with message:
B
-------------------------------------------------------------------------------
#1938 - mixed sections and generates
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
with messages:
i := 2
j := 3
k := 6
-------------------------------------------------------------------------------
#1938 - mixed sections and generates
B
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
with message:
B
-------------------------------------------------------------------------------
#1938 - mixed sections and generates
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
with messages:
i := 2
j := 4
k := 5
-------------------------------------------------------------------------------
#1938 - mixed sections and generates
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
with messages:
i := 2
j := 4
k := 6
-------------------------------------------------------------------------------
#1938 - nested generate
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
1
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( n )
with expansion:
1
-------------------------------------------------------------------------------
#1938 - nested generate
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
1
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( n )
with expansion:
2
-------------------------------------------------------------------------------
#1938 - nested generate
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
1
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( n )
with expansion:
3
-------------------------------------------------------------------------------
#1938 - nested generate
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
2
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( n )
with expansion:
1
-------------------------------------------------------------------------------
#1938 - nested generate
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
2
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( n )
with expansion:
2
-------------------------------------------------------------------------------
#1938 - nested generate
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
2
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( n )
with expansion:
3
-------------------------------------------------------------------------------
#1938 - nested generate
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
3
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( n )
with expansion:
1
-------------------------------------------------------------------------------
#1938 - nested generate
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
3
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( n )
with expansion:
2
-------------------------------------------------------------------------------
#1938 - nested generate
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
3
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( n )
with expansion:
3
Fix copy paste error in 7-arg TEMPLATE_TEST_CASE_SIG implementation Closes #1954
2020-06-13 15:41:25 +02:00
-------------------------------------------------------------------------------
#1954 - 7 arg template test case sig compiles - 1, 1, 1, 1, 1, 0, 0
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
-------------------------------------------------------------------------------
#1954 - 7 arg template test case sig compiles - 5, 1, 1, 1, 1, 0, 0
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
-------------------------------------------------------------------------------
#1954 - 7 arg template test case sig compiles - 5, 3, 1, 1, 1, 0, 0
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
Fix ulp distance calculation for numbers with different signs This is a simplification of the fix proposed in #2152, with the critical function split out so that it can be tested directly, without having to go through the ULP matcher. Closes #2152
2021-07-26 22:01:04 +02:00
-------------------------------------------------------------------------------
#2152 - ULP checks between differently signed values were wrong - double
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: PASSED:
CHECK_THAT( smallest_non_zero, WithinULP( -smallest_non_zero, 2 ) )
with expansion:
0.0 is within 2 ULPs of -4.9406564584124654e-324 ([-1.4821969375237396e-323,
4.9406564584124654e-324])
Matchers.tests.cpp:<line number>: PASSED:
CHECK_THAT( smallest_non_zero, !WithinULP( -smallest_non_zero, 1 ) )
with expansion:
0.0 not is within 1 ULPs of -4.9406564584124654e-324 ([-9.8813129168249309e-
324, -0.0000000000000000e+00])
-------------------------------------------------------------------------------
#2152 - ULP checks between differently signed values were wrong - float
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: PASSED:
CHECK_THAT( smallest_non_zero, WithinULP( -smallest_non_zero, 2 ) )
with expansion:
0.0f is within 2 ULPs of -1.40129846e-45f ([-4.20389539e-45, 1.40129846e-45])
Matchers.tests.cpp:<line number>: PASSED:
CHECK_THAT( smallest_non_zero, !WithinULP( -smallest_non_zero, 1 ) )
with expansion:
0.0f not is within 1 ULPs of -1.40129846e-45f ([-2.80259693e-45, -0.
00000000e+00])
Stop exceptions in generator constructors from aborting the binary Fixes #2615
2023-01-17 11:04:49 +01:00
-------------------------------------------------------------------------------
#2615 - Throwing in constructor generator fails test case but does not abort
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: FAILED:
due to unexpected exception with message:
failure to init
approved tests that were correct the first time (previous approvals were erroneous)
2017-04-09 21:40:01 +02:00
-------------------------------------------------------------------------------
#748 - captures with unexpected exceptions
outside assertions
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Exception.tests.cpp:<line number>
approved tests that were correct the first time (previous approvals were erroneous)
2017-04-09 21:40:01 +02:00
...............................................................................
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Exception.tests.cpp:<line number>: FAILED:
approved tests that were correct the first time (previous approvals were erroneous)
2017-04-09 21:40:01 +02:00
due to unexpected exception with messages:
answer := 42
expected exception
Added compilation tests to approvals
2017-02-10 12:53:29 +01:00
-------------------------------------------------------------------------------
Added approvals for “failed as expected” tests
2017-04-07 10:33:19 +02:00
#748 - captures with unexpected exceptions
inside REQUIRE_NOTHROW
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Exception.tests.cpp:<line number>
Added approvals for “failed as expected” tests
2017-04-07 10:33:19 +02:00
...............................................................................
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Exception.tests.cpp:<line number>: FAILED:
Added approvals for “failed as expected” tests
2017-04-07 10:33:19 +02:00
REQUIRE_NOTHROW( thisThrows() )
due to unexpected exception with messages:
answer := 42
expected exception
-------------------------------------------------------------------------------
#748 - captures with unexpected exceptions
inside REQUIRE_THROWS
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Exception.tests.cpp:<line number>
Added approvals for “failed as expected” tests
2017-04-07 10:33:19 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Exception.tests.cpp:<line number>: PASSED:
Added approvals for “failed as expected” tests
2017-04-07 10:33:19 +02:00
REQUIRE_THROWS( thisThrows() )
with message:
answer := 42
-------------------------------------------------------------------------------
#809
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Compilation.tests.cpp:<line number>
Added approvals for “failed as expected” tests
2017-04-07 10:33:19 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Compilation.tests.cpp:<line number>: PASSED:
Added approvals for “failed as expected” tests
2017-04-07 10:33:19 +02:00
REQUIRE( 42 == f )
with expansion:
42 == {?}
-------------------------------------------------------------------------------
#833
Added compilation tests to approvals
2017-02-10 12:53:29 +01:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Compilation.tests.cpp:<line number>
Added compilation tests to approvals
2017-02-10 12:53:29 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Compilation.tests.cpp:<line number>: PASSED:
Added approvals for “failed as expected” tests
2017-04-07 10:33:19 +02:00
REQUIRE( a == t )
with expansion:
3 == 3
Added compilation tests to approvals
2017-02-10 12:53:29 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Compilation.tests.cpp:<line number>: PASSED:
Added approvals for “failed as expected” tests
2017-04-07 10:33:19 +02:00
CHECK( a == t )
with expansion:
3 == 3
Added compilation tests to approvals
2017-02-10 12:53:29 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Compilation.tests.cpp:<line number>: PASSED:
Added approvals for “failed as expected” tests
2017-04-07 10:33:19 +02:00
REQUIRE_THROWS( throws_int(true) )
Added compilation tests to approvals
2017-02-10 12:53:29 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Compilation.tests.cpp:<line number>: PASSED:
Update Baselines
2017-07-20 00:29:19 +02:00
CHECK_THROWS_AS( throws_int(true), int )
Added compilation tests to approvals
2017-02-10 12:53:29 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Compilation.tests.cpp:<line number>: PASSED:
Added approvals for “failed as expected” tests
2017-04-07 10:33:19 +02:00
REQUIRE_NOTHROW( throws_int(false) )
Added tests (single char pretty printing + op overload) Tests for issue #809 -- Potentional operator overload ambiguity -- and PR #646 -- Pretty print characters.
2017-02-07 13:32:48 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Compilation.tests.cpp:<line number>: PASSED:
Start fixing up Matchers: namespaces, composition ops This commit also forbids composing lvalues of composed matchers, as per previous deprecation notice. I do not expect this to be contentious in practice, because there was a bug in that usage for years, and nobody complained.
2020-02-18 23:31:16 +01:00
REQUIRE_THAT( "aaa", Catch::Matchers::EndsWith("aaa") )
Added tests (single char pretty printing + op overload) Tests for issue #809 -- Potentional operator overload ambiguity -- and PR #646 -- Pretty print characters.
2017-02-07 13:32:48 +01:00
with expansion:
Added approvals for “failed as expected” tests
2017-04-07 10:33:19 +02:00
"aaa" ends with: "aaa"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Compilation.tests.cpp:<line number>: PASSED:
Added approvals for “failed as expected” tests
2017-04-07 10:33:19 +02:00
REQUIRE( templated_tests<int>(3) )
with expansion:
true
Added tests (single char pretty printing + op overload) Tests for issue #809 -- Potentional operator overload ambiguity -- and PR #646 -- Pretty print characters.
2017-02-07 13:32:48 +01:00
Add tests for #835 Also add ErrnoGuard before `isatty` call, because apparently it can set errno to 25 (ENOTTY).
2017-03-06 22:07:33 +01:00
-------------------------------------------------------------------------------
Cleanups output normalization in ApprovalTests Removed: * NaN normalization * INFINITY normalization * errno normalization * Completely unused duration regex Tests using these macros should be tagged `[approvals]` so they are not run as part of approval tests. Also simplified regex for the test's executable filename, and hidden some tests relying on nullptr normalization.
2022-01-26 23:47:40 +01:00
#835 -- errno should not be touched by Catch2
Add tests for #835 Also add ErrnoGuard before `isatty` call, because apparently it can set errno to 25 (ENOTTY).
2017-03-06 22:07:33 +01:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Add tests for #835 Also add ErrnoGuard before `isatty` call, because apparently it can set errno to 25 (ENOTTY).
2017-03-06 22:07:33 +01:00
...............................................................................
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>: FAILED:
Add tests for #835 Also add ErrnoGuard before `isatty` call, because apparently it can set errno to 25 (ENOTTY).
2017-03-06 22:07:33 +01:00
CHECK( f() == 0 )
with expansion:
1 == 0
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Cleanups output normalization in ApprovalTests Removed: * NaN normalization * INFINITY normalization * errno normalization * Completely unused duration regex Tests using these macros should be tagged `[approvals]` so they are not run as part of approval tests. Also simplified regex for the test's executable filename, and hidden some tests relying on nullptr normalization.
2022-01-26 23:47:40 +01:00
REQUIRE( errno_after == 1 )
Add tests for #835 Also add ErrnoGuard before `isatty` call, because apparently it can set errno to 25 (ENOTTY).
2017-03-06 22:07:33 +01:00
with expansion:
1 == 1
Enabled SFINAE stream test
2017-04-25 15:57:58 +02:00
-------------------------------------------------------------------------------
#872
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Compilation.tests.cpp:<line number>
Enabled SFINAE stream test
2017-04-25 15:57:58 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Compilation.tests.cpp:<line number>: PASSED:
Enabled SFINAE stream test
2017-04-25 15:57:58 +02:00
REQUIRE( x == 4 )
with expansion:
{?} == 4
with message:
dummy := 0
Cherry picked 4f21bb72ff16f82b7fcf7362d683547f412641f4 (Add tests for #961) from master - had to redo the baselines
2017-08-10 21:38:07 +02:00
-------------------------------------------------------------------------------
#961 -- Dynamically created sections should all be reported
Looped section 0
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Cherry picked 4f21bb72ff16f82b7fcf7362d683547f412641f4 (Add tests for #961) from master - had to redo the baselines
2017-08-10 21:38:07 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Cherry picked 4f21bb72ff16f82b7fcf7362d683547f412641f4 (Add tests for #961) from master - had to redo the baselines
2017-08-10 21:38:07 +02:00
with message:
Everything is OK
-------------------------------------------------------------------------------
#961 -- Dynamically created sections should all be reported
Looped section 1
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Cherry picked 4f21bb72ff16f82b7fcf7362d683547f412641f4 (Add tests for #961) from master - had to redo the baselines
2017-08-10 21:38:07 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Cherry picked 4f21bb72ff16f82b7fcf7362d683547f412641f4 (Add tests for #961) from master - had to redo the baselines
2017-08-10 21:38:07 +02:00
with message:
Everything is OK
-------------------------------------------------------------------------------
#961 -- Dynamically created sections should all be reported
Looped section 2
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Cherry picked 4f21bb72ff16f82b7fcf7362d683547f412641f4 (Add tests for #961) from master - had to redo the baselines
2017-08-10 21:38:07 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Cherry picked 4f21bb72ff16f82b7fcf7362d683547f412641f4 (Add tests for #961) from master - had to redo the baselines
2017-08-10 21:38:07 +02:00
with message:
Everything is OK
-------------------------------------------------------------------------------
#961 -- Dynamically created sections should all be reported
Looped section 3
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Cherry picked 4f21bb72ff16f82b7fcf7362d683547f412641f4 (Add tests for #961) from master - had to redo the baselines
2017-08-10 21:38:07 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Cherry picked 4f21bb72ff16f82b7fcf7362d683547f412641f4 (Add tests for #961) from master - had to redo the baselines
2017-08-10 21:38:07 +02:00
with message:
Everything is OK
-------------------------------------------------------------------------------
#961 -- Dynamically created sections should all be reported
Looped section 4
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Cherry picked 4f21bb72ff16f82b7fcf7362d683547f412641f4 (Add tests for #961) from master - had to redo the baselines
2017-08-10 21:38:07 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Cherry picked 4f21bb72ff16f82b7fcf7362d683547f412641f4 (Add tests for #961) from master - had to redo the baselines
2017-08-10 21:38:07 +02:00
with message:
Everything is OK
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
'Not' checks that should fail
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
...............................................................................
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( false != false )
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( true != true )
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( !true )
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
false
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK_FALSE( true )
Fixed expansion of _FALSE binary expression - see #1051
2017-10-13 20:45:19 +02:00
with expansion:
!true
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( !trueValue )
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
false
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK_FALSE( trueValue )
with expansion:
!true
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( !(1 == 1) )
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
false
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK_FALSE( 1 == 1 )
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
'Not' checks that should succeed
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( false == false )
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( true == true )
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( !false )
Some minor tidy-up/ style alignment of recent toString merges
2014-09-04 08:27:09 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
true
Some minor tidy-up/ style alignment of recent toString merges
2014-09-04 08:27:09 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE_FALSE( false )
Fixed expansion of _FALSE binary expression - see #1051
2017-10-13 20:45:19 +02:00
with expansion:
!false
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( !falseValue )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
true
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE_FALSE( falseValue )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
!false
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( !(1 == 2) )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
true
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE_FALSE( 1 == 2 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
(unimplemented) static bools can be evaluated
compare to true
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Tricky.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( is_true<true>::value == true )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
true == true
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( true == is_true<true>::value )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
true == true
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
(unimplemented) static bools can be evaluated
compare to false
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Tricky.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( is_true<false>::value == false )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
false == false
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( false == is_true<false>::value )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
false == false
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
(unimplemented) static bools can be evaluated
negation
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Tricky.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( !is_true<false>::value )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
true
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
(unimplemented) static bools can be evaluated
double negation
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Tricky.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( !!is_true<true>::value )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
true
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
(unimplemented) static bools can be evaluated
direct
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Tricky.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( is_true<true>::value )
Changed Approx::toString() to be implemented in terms of toString( double ) (as proposed in #233)
2013-12-19 19:41:55 +01:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
true
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE_FALSE( is_true<false>::value )
Changed Approx::toString() to be implemented in terms of toString( double ) (as proposed in #233)
2013-12-19 19:41:55 +01:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
!false
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
3x3x3 ints
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Generators.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( x < y )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
1 < 4
Updated baselines
2017-02-27 16:27:43 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
CHECK( y < z )
Updated baselines
2017-02-27 16:27:43 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
4 < 7
Updated baselines
2017-02-27 16:27:43 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( x < z )
Make Approx::margin inclusive Fixes #952, related to #980
2017-10-30 15:25:48 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
1 < 7
Make Approx::margin inclusive Fixes #952, related to #980
2017-10-30 15:25:48 +01:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
3x3x3 ints
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Updated baselines
2017-02-27 16:27:43 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( x < y )
Updated baselines
2017-02-27 16:27:43 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
1 < 4
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
CHECK( y < z )
Updated baselines
2017-02-27 16:27:43 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
4 < 8
Fixed NoAssertions warning
2018-01-26 17:52:28 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( x < z )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
1 < 8
Fixed NoAssertions warning
2018-01-26 17:52:28 +01:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
3x3x3 ints
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Generators.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( x < y )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
1 < 4
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
CHECK( y < z )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
4 < 9
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( x < z )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
1 < 9
approved tests that were correct the first time (previous approvals were erroneous)
2017-04-09 21:40:01 +02:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
3x3x3 ints
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Generators.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( x < y )
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
1 < 5
Make Approx::margin inclusive Fixes #952, related to #980
2017-10-30 15:25:48 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
CHECK( y < z )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
5 < 7
Make Approx::margin inclusive Fixes #952, related to #980
2017-10-30 15:25:48 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( x < z )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
1 < 7
Make Approx::margin inclusive Fixes #952, related to #980
2017-10-30 15:25:48 +01:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
3x3x3 ints
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Approx cleanup: More tests, INFINITY handling, etc
2017-11-01 07:30:11 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( x < y )
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
1 < 5
Approx cleanup: More tests, INFINITY handling, etc
2017-11-01 07:30:11 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
CHECK( y < z )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
5 < 8
Make Approx::margin inclusive Fixes #952, related to #980
2017-10-30 15:25:48 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( x < z )
Make Approx::margin inclusive Fixes #952, related to #980
2017-10-30 15:25:48 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
1 < 8
Make Approx::margin inclusive Fixes #952, related to #980
2017-10-30 15:25:48 +01:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
3x3x3 ints
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( x < y )
Make Approx::margin inclusive Fixes #952, related to #980
2017-10-30 15:25:48 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
1 < 5
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
CHECK( y < z )
Make Approx::margin inclusive Fixes #952, related to #980
2017-10-30 15:25:48 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
5 < 9
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( x < z )
Make Approx::margin inclusive Fixes #952, related to #980
2017-10-30 15:25:48 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
1 < 9
Make Approx::margin inclusive Fixes #952, related to #980
2017-10-30 15:25:48 +01:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
3x3x3 ints
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( x < y )
Make Approx::margin inclusive Fixes #952, related to #980
2017-10-30 15:25:48 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
1 < 6
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
CHECK( y < z )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
6 < 7
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( x < z )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
1 < 7
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
3x3x3 ints
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Generators.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( x < y )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
1 < 6
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
CHECK( y < z )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
6 < 8
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( x < z )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
1 < 8
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
3x3x3 ints
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( x < y )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
1 < 6
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
CHECK( y < z )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
6 < 9
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( x < z )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
1 < 9
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
3x3x3 ints
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Generators.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( x < y )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
2 < 4
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
CHECK( y < z )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
4 < 7
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( x < z )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
2 < 7
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
3x3x3 ints
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( x < y )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
2 < 4
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
CHECK( y < z )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
4 < 8
Add PredicateMatcher that takes an arbitrary predicate functions Also adds `Predicate` helper function to create `PredicateMatcher`. Because of limitations in type inference it needs to be explicitly typed, like so `Predicate<std::string>([](std::string const& str) { ... })`. It also takes an optional second argument for description of the predicate. It is possible to infer the argument with sufficient TMP, see https://stackoverflow.com/questions/43560492/how-to-extract-lambdas-return-type-and-variadic-parameters-pack-back-from-gener/43561563#43561563 but I don't think that the magic is worth introducing ATM. Closes #1236
2018-04-03 23:28:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( x < z )
Added tests (single char pretty printing + op overload) Tests for issue #809 -- Potentional operator overload ambiguity -- and PR #646 -- Pretty print characters.
2017-02-07 13:32:48 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
2 < 8
Added tests (single char pretty printing + op overload) Tests for issue #809 -- Potentional operator overload ambiguity -- and PR #646 -- Pretty print characters.
2017-02-07 13:32:48 +01:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
3x3x3 ints
Added tests (single char pretty printing + op overload) Tests for issue #809 -- Potentional operator overload ambiguity -- and PR #646 -- Pretty print characters.
2017-02-07 13:32:48 +01:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Generators.tests.cpp:<line number>
Added tests (single char pretty printing + op overload) Tests for issue #809 -- Potentional operator overload ambiguity -- and PR #646 -- Pretty print characters.
2017-02-07 13:32:48 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( x < y )
Added tests (single char pretty printing + op overload) Tests for issue #809 -- Potentional operator overload ambiguity -- and PR #646 -- Pretty print characters.
2017-02-07 13:32:48 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
2 < 4
Added tests (single char pretty printing + op overload) Tests for issue #809 -- Potentional operator overload ambiguity -- and PR #646 -- Pretty print characters.
2017-02-07 13:32:48 +01:00
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators.tests.cpp:<line number>: PASSED:
CHECK( y < z )
with expansion:
4 < 9
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( x < z )
Added tests (single char pretty printing + op overload) Tests for issue #809 -- Potentional operator overload ambiguity -- and PR #646 -- Pretty print characters.
2017-02-07 13:32:48 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
2 < 9
Added tests (single char pretty printing + op overload) Tests for issue #809 -- Potentional operator overload ambiguity -- and PR #646 -- Pretty print characters.
2017-02-07 13:32:48 +01:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
3x3x3 ints
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( x < y )
Added tests (single char pretty printing + op overload) Tests for issue #809 -- Potentional operator overload ambiguity -- and PR #646 -- Pretty print characters.
2017-02-07 13:32:48 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
2 < 5
Added tests (single char pretty printing + op overload) Tests for issue #809 -- Potentional operator overload ambiguity -- and PR #646 -- Pretty print characters.
2017-02-07 13:32:48 +01:00
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators.tests.cpp:<line number>: PASSED:
CHECK( y < z )
with expansion:
5 < 7
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( x < z )
Added tests (single char pretty printing + op overload) Tests for issue #809 -- Potentional operator overload ambiguity -- and PR #646 -- Pretty print characters.
2017-02-07 13:32:48 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
2 < 7
Added tests (single char pretty printing + op overload) Tests for issue #809 -- Potentional operator overload ambiguity -- and PR #646 -- Pretty print characters.
2017-02-07 13:32:48 +01:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
3x3x3 ints
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( x < y )
Added tests (single char pretty printing + op overload) Tests for issue #809 -- Potentional operator overload ambiguity -- and PR #646 -- Pretty print characters.
2017-02-07 13:32:48 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
2 < 5
Added tests (single char pretty printing + op overload) Tests for issue #809 -- Potentional operator overload ambiguity -- and PR #646 -- Pretty print characters.
2017-02-07 13:32:48 +01:00
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators.tests.cpp:<line number>: PASSED:
CHECK( y < z )
with expansion:
5 < 8
More macros are now variadic Also added tests for them
2017-05-03 19:10:27 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( x < z )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
2 < 8
More macros are now variadic Also added tests for them
2017-05-03 19:10:27 +02:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
3x3x3 ints
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
More macros are now variadic Also added tests for them
2017-05-03 19:10:27 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( x < y )
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
2 < 5
More macros are now variadic Also added tests for them
2017-05-03 19:10:27 +02:00
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators.tests.cpp:<line number>: PASSED:
CHECK( y < z )
with expansion:
5 < 9
More macros are now variadic Also added tests for them
2017-05-03 19:10:27 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( x < z )
More macros are now variadic Also added tests for them
2017-05-03 19:10:27 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
2 < 9
More macros are now variadic Also added tests for them
2017-05-03 19:10:27 +02:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
3x3x3 ints
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( x < y )
More macros are now variadic Also added tests for them
2017-05-03 19:10:27 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
2 < 6
More macros are now variadic Also added tests for them
2017-05-03 19:10:27 +02:00
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators.tests.cpp:<line number>: PASSED:
CHECK( y < z )
with expansion:
6 < 7
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( x < z )
More macros are now variadic Also added tests for them
2017-05-03 19:10:27 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
2 < 7
More macros are now variadic Also added tests for them
2017-05-03 19:10:27 +02:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
3x3x3 ints
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( x < y )
More macros are now variadic Also added tests for them
2017-05-03 19:10:27 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
2 < 6
More macros are now variadic Also added tests for them
2017-05-03 19:10:27 +02:00
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators.tests.cpp:<line number>: PASSED:
CHECK( y < z )
with expansion:
6 < 8
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( x < z )
More macros are now variadic Also added tests for them
2017-05-03 19:10:27 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
2 < 8
More macros are now variadic Also added tests for them
2017-05-03 19:10:27 +02:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
3x3x3 ints
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( x < y )
More macros are now variadic Also added tests for them
2017-05-03 19:10:27 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
2 < 6
More macros are now variadic Also added tests for them
2017-05-03 19:10:27 +02:00
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators.tests.cpp:<line number>: PASSED:
CHECK( y < z )
with expansion:
6 < 9
More macros are now variadic Also added tests for them
2017-05-03 19:10:27 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( x < z )
More macros are now variadic Also added tests for them
2017-05-03 19:10:27 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
2 < 9
More macros are now variadic Also added tests for them
2017-05-03 19:10:27 +02:00
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
3x3x3 ints
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Generators.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( x < y )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
3 < 4
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators.tests.cpp:<line number>: PASSED:
CHECK( y < z )
with expansion:
4 < 7
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( x < z )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
3 < 7
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
3x3x3 ints
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Generators.tests.cpp:<line number>
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( x < y )
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
3 < 4
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators.tests.cpp:<line number>: PASSED:
CHECK( y < z )
with expansion:
4 < 8
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( x < z )
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
3 < 8
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
3x3x3 ints
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( x < y )
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
3 < 4
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators.tests.cpp:<line number>: PASSED:
CHECK( y < z )
with expansion:
4 < 9
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( x < z )
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
3 < 9
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
3x3x3 ints
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( x < y )
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
3 < 5
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators.tests.cpp:<line number>: PASSED:
CHECK( y < z )
with expansion:
5 < 7
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( x < z )
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
3 < 7
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
3x3x3 ints
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( x < y )
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
3 < 5
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators.tests.cpp:<line number>: PASSED:
CHECK( y < z )
with expansion:
5 < 8
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( x < z )
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
3 < 8
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
3x3x3 ints
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( x < y )
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
3 < 5
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators.tests.cpp:<line number>: PASSED:
CHECK( y < z )
with expansion:
5 < 9
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( x < z )
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
3 < 9
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
3x3x3 ints
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( x < y )
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
3 < 6
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators.tests.cpp:<line number>: PASSED:
CHECK( y < z )
with expansion:
6 < 7
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( x < z )
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
3 < 7
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
3x3x3 ints
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Generators.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( x < y )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
3 < 6
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators.tests.cpp:<line number>: PASSED:
CHECK( y < z )
with expansion:
6 < 8
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( x < z )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
3 < 8
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
3x3x3 ints
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( x < y )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
3 < 6
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators.tests.cpp:<line number>: PASSED:
CHECK( y < z )
with expansion:
6 < 9
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( x < z )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
3 < 9
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
A METHOD_AS_TEST_CASE based test run that fails
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: FAILED:
REQUIRE( s == "world" )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
"hello" == "world"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
A METHOD_AS_TEST_CASE based test run that succeeds
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Class.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( s == "hello" )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
"hello" == "hello"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Template tests: added TEMPLATE_PRODUCT_TEST_CASE support for generating test cases based on multiple template template types combined with template arguments for each of the template template types specified e.g. ``` TEMPLATE_PRODUCT_TEST_CASE("template product","[template]", (std::tuple, std::pair, std::map), ((int,float),(char,double),(int,char))) ``` will effectively create 9 test cases with types: std::tuple<int,float> std::tuple<char,double> std::tuple<int,char> std::pair<int,float> std::pair<char, double> std::pair<int,char> std::map<int,float> std::map<char,double> std::map<int,char> Tested type is accessible in test case body as TestType Unique name is created by appending ` - <index>` to test name since preprocessor has some limitations in recursions Closes #1454
2018-12-06 19:27:33 +01:00
-------------------------------------------------------------------------------
Use correct type name instead of index for TEMPLATE_PRODUCT_TEST_CASE (#1544) Previously, for a TEMPLATE_PRODUCT_TEST_CASE("Test" ..., T, (P1, P2)), the generated test case names were Test - 0 Test - 1 With this commit, the correct typename is used: Test - T<P1> Test - T<P2> ----------- MSVC needs another indirection to evaluate INTERNAL_CATCH_STRINGIZE and also inserts a space before theINTERNAL_CATCH_STRINGIZE_WITHOUT_PARENS parameter, which we can get rid of by pointer arithmetic.
2019-02-17 21:52:22 +01:00
A TEMPLATE_PRODUCT_TEST_CASE_METHOD based test run that fails - Template_Foo
<float>
Template tests: added TEMPLATE_PRODUCT_TEST_CASE support for generating test cases based on multiple template template types combined with template arguments for each of the template template types specified e.g. ``` TEMPLATE_PRODUCT_TEST_CASE("template product","[template]", (std::tuple, std::pair, std::map), ((int,float),(char,double),(int,char))) ``` will effectively create 9 test cases with types: std::tuple<int,float> std::tuple<char,double> std::tuple<int,char> std::pair<int,float> std::pair<char, double> std::pair<int,char> std::map<int,float> std::map<char,double> std::map<int,char> Tested type is accessible in test case body as TestType Unique name is created by appending ` - <index>` to test name since preprocessor has some limitations in recursions Closes #1454
2018-12-06 19:27:33 +01:00
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: FAILED:
REQUIRE( Template_Fixture_2<TestType>::m_a.size() == 1 )
with expansion:
0 == 1
-------------------------------------------------------------------------------
Use correct type name instead of index for TEMPLATE_PRODUCT_TEST_CASE (#1544) Previously, for a TEMPLATE_PRODUCT_TEST_CASE("Test" ..., T, (P1, P2)), the generated test case names were Test - 0 Test - 1 With this commit, the correct typename is used: Test - T<P1> Test - T<P2> ----------- MSVC needs another indirection to evaluate INTERNAL_CATCH_STRINGIZE and also inserts a space before theINTERNAL_CATCH_STRINGIZE_WITHOUT_PARENS parameter, which we can get rid of by pointer arithmetic.
2019-02-17 21:52:22 +01:00
A TEMPLATE_PRODUCT_TEST_CASE_METHOD based test run that fails - Template_Foo
<int>
Template tests: added TEMPLATE_PRODUCT_TEST_CASE support for generating test cases based on multiple template template types combined with template arguments for each of the template template types specified e.g. ``` TEMPLATE_PRODUCT_TEST_CASE("template product","[template]", (std::tuple, std::pair, std::map), ((int,float),(char,double),(int,char))) ``` will effectively create 9 test cases with types: std::tuple<int,float> std::tuple<char,double> std::tuple<int,char> std::pair<int,float> std::pair<char, double> std::pair<int,char> std::map<int,float> std::map<char,double> std::map<int,char> Tested type is accessible in test case body as TestType Unique name is created by appending ` - <index>` to test name since preprocessor has some limitations in recursions Closes #1454
2018-12-06 19:27:33 +01:00
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: FAILED:
REQUIRE( Template_Fixture_2<TestType>::m_a.size() == 1 )
with expansion:
0 == 1
-------------------------------------------------------------------------------
Use correct type name instead of index for TEMPLATE_PRODUCT_TEST_CASE (#1544) Previously, for a TEMPLATE_PRODUCT_TEST_CASE("Test" ..., T, (P1, P2)), the generated test case names were Test - 0 Test - 1 With this commit, the correct typename is used: Test - T<P1> Test - T<P2> ----------- MSVC needs another indirection to evaluate INTERNAL_CATCH_STRINGIZE and also inserts a space before theINTERNAL_CATCH_STRINGIZE_WITHOUT_PARENS parameter, which we can get rid of by pointer arithmetic.
2019-02-17 21:52:22 +01:00
A TEMPLATE_PRODUCT_TEST_CASE_METHOD based test run that fails - std::vector
<float>
Template tests: added TEMPLATE_PRODUCT_TEST_CASE support for generating test cases based on multiple template template types combined with template arguments for each of the template template types specified e.g. ``` TEMPLATE_PRODUCT_TEST_CASE("template product","[template]", (std::tuple, std::pair, std::map), ((int,float),(char,double),(int,char))) ``` will effectively create 9 test cases with types: std::tuple<int,float> std::tuple<char,double> std::tuple<int,char> std::pair<int,float> std::pair<char, double> std::pair<int,char> std::map<int,float> std::map<char,double> std::map<int,char> Tested type is accessible in test case body as TestType Unique name is created by appending ` - <index>` to test name since preprocessor has some limitations in recursions Closes #1454
2018-12-06 19:27:33 +01:00
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: FAILED:
REQUIRE( Template_Fixture_2<TestType>::m_a.size() == 1 )
with expansion:
0 == 1
-------------------------------------------------------------------------------
Use correct type name instead of index for TEMPLATE_PRODUCT_TEST_CASE (#1544) Previously, for a TEMPLATE_PRODUCT_TEST_CASE("Test" ..., T, (P1, P2)), the generated test case names were Test - 0 Test - 1 With this commit, the correct typename is used: Test - T<P1> Test - T<P2> ----------- MSVC needs another indirection to evaluate INTERNAL_CATCH_STRINGIZE and also inserts a space before theINTERNAL_CATCH_STRINGIZE_WITHOUT_PARENS parameter, which we can get rid of by pointer arithmetic.
2019-02-17 21:52:22 +01:00
A TEMPLATE_PRODUCT_TEST_CASE_METHOD based test run that fails - std::vector
<int>
Template tests: added TEMPLATE_PRODUCT_TEST_CASE support for generating test cases based on multiple template template types combined with template arguments for each of the template template types specified e.g. ``` TEMPLATE_PRODUCT_TEST_CASE("template product","[template]", (std::tuple, std::pair, std::map), ((int,float),(char,double),(int,char))) ``` will effectively create 9 test cases with types: std::tuple<int,float> std::tuple<char,double> std::tuple<int,char> std::pair<int,float> std::pair<char, double> std::pair<int,char> std::map<int,float> std::map<char,double> std::map<int,char> Tested type is accessible in test case body as TestType Unique name is created by appending ` - <index>` to test name since preprocessor has some limitations in recursions Closes #1454
2018-12-06 19:27:33 +01:00
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: FAILED:
REQUIRE( Template_Fixture_2<TestType>::m_a.size() == 1 )
with expansion:
0 == 1
-------------------------------------------------------------------------------
Use correct type name instead of index for TEMPLATE_PRODUCT_TEST_CASE (#1544) Previously, for a TEMPLATE_PRODUCT_TEST_CASE("Test" ..., T, (P1, P2)), the generated test case names were Test - 0 Test - 1 With this commit, the correct typename is used: Test - T<P1> Test - T<P2> ----------- MSVC needs another indirection to evaluate INTERNAL_CATCH_STRINGIZE and also inserts a space before theINTERNAL_CATCH_STRINGIZE_WITHOUT_PARENS parameter, which we can get rid of by pointer arithmetic.
2019-02-17 21:52:22 +01:00
A TEMPLATE_PRODUCT_TEST_CASE_METHOD based test run that succeeds - Template_Foo
<float>
Template tests: added TEMPLATE_PRODUCT_TEST_CASE support for generating test cases based on multiple template template types combined with template arguments for each of the template template types specified e.g. ``` TEMPLATE_PRODUCT_TEST_CASE("template product","[template]", (std::tuple, std::pair, std::map), ((int,float),(char,double),(int,char))) ``` will effectively create 9 test cases with types: std::tuple<int,float> std::tuple<char,double> std::tuple<int,char> std::pair<int,float> std::pair<char, double> std::pair<int,char> std::map<int,float> std::map<char,double> std::map<int,char> Tested type is accessible in test case body as TestType Unique name is created by appending ` - <index>` to test name since preprocessor has some limitations in recursions Closes #1454
2018-12-06 19:27:33 +01:00
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: PASSED:
REQUIRE( Template_Fixture_2<TestType>::m_a.size() == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
Use correct type name instead of index for TEMPLATE_PRODUCT_TEST_CASE (#1544) Previously, for a TEMPLATE_PRODUCT_TEST_CASE("Test" ..., T, (P1, P2)), the generated test case names were Test - 0 Test - 1 With this commit, the correct typename is used: Test - T<P1> Test - T<P2> ----------- MSVC needs another indirection to evaluate INTERNAL_CATCH_STRINGIZE and also inserts a space before theINTERNAL_CATCH_STRINGIZE_WITHOUT_PARENS parameter, which we can get rid of by pointer arithmetic.
2019-02-17 21:52:22 +01:00
A TEMPLATE_PRODUCT_TEST_CASE_METHOD based test run that succeeds - Template_Foo
<int>
Template tests: added TEMPLATE_PRODUCT_TEST_CASE support for generating test cases based on multiple template template types combined with template arguments for each of the template template types specified e.g. ``` TEMPLATE_PRODUCT_TEST_CASE("template product","[template]", (std::tuple, std::pair, std::map), ((int,float),(char,double),(int,char))) ``` will effectively create 9 test cases with types: std::tuple<int,float> std::tuple<char,double> std::tuple<int,char> std::pair<int,float> std::pair<char, double> std::pair<int,char> std::map<int,float> std::map<char,double> std::map<int,char> Tested type is accessible in test case body as TestType Unique name is created by appending ` - <index>` to test name since preprocessor has some limitations in recursions Closes #1454
2018-12-06 19:27:33 +01:00
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: PASSED:
REQUIRE( Template_Fixture_2<TestType>::m_a.size() == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
Use correct type name instead of index for TEMPLATE_PRODUCT_TEST_CASE (#1544) Previously, for a TEMPLATE_PRODUCT_TEST_CASE("Test" ..., T, (P1, P2)), the generated test case names were Test - 0 Test - 1 With this commit, the correct typename is used: Test - T<P1> Test - T<P2> ----------- MSVC needs another indirection to evaluate INTERNAL_CATCH_STRINGIZE and also inserts a space before theINTERNAL_CATCH_STRINGIZE_WITHOUT_PARENS parameter, which we can get rid of by pointer arithmetic.
2019-02-17 21:52:22 +01:00
A TEMPLATE_PRODUCT_TEST_CASE_METHOD based test run that succeeds - std::vector
<float>
Template tests: added TEMPLATE_PRODUCT_TEST_CASE support for generating test cases based on multiple template template types combined with template arguments for each of the template template types specified e.g. ``` TEMPLATE_PRODUCT_TEST_CASE("template product","[template]", (std::tuple, std::pair, std::map), ((int,float),(char,double),(int,char))) ``` will effectively create 9 test cases with types: std::tuple<int,float> std::tuple<char,double> std::tuple<int,char> std::pair<int,float> std::pair<char, double> std::pair<int,char> std::map<int,float> std::map<char,double> std::map<int,char> Tested type is accessible in test case body as TestType Unique name is created by appending ` - <index>` to test name since preprocessor has some limitations in recursions Closes #1454
2018-12-06 19:27:33 +01:00
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: PASSED:
REQUIRE( Template_Fixture_2<TestType>::m_a.size() == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
Use correct type name instead of index for TEMPLATE_PRODUCT_TEST_CASE (#1544) Previously, for a TEMPLATE_PRODUCT_TEST_CASE("Test" ..., T, (P1, P2)), the generated test case names were Test - 0 Test - 1 With this commit, the correct typename is used: Test - T<P1> Test - T<P2> ----------- MSVC needs another indirection to evaluate INTERNAL_CATCH_STRINGIZE and also inserts a space before theINTERNAL_CATCH_STRINGIZE_WITHOUT_PARENS parameter, which we can get rid of by pointer arithmetic.
2019-02-17 21:52:22 +01:00
A TEMPLATE_PRODUCT_TEST_CASE_METHOD based test run that succeeds - std::vector
<int>
Template tests: added TEMPLATE_PRODUCT_TEST_CASE support for generating test cases based on multiple template template types combined with template arguments for each of the template template types specified e.g. ``` TEMPLATE_PRODUCT_TEST_CASE("template product","[template]", (std::tuple, std::pair, std::map), ((int,float),(char,double),(int,char))) ``` will effectively create 9 test cases with types: std::tuple<int,float> std::tuple<char,double> std::tuple<int,char> std::pair<int,float> std::pair<char, double> std::pair<int,char> std::map<int,float> std::map<char,double> std::map<int,char> Tested type is accessible in test case body as TestType Unique name is created by appending ` - <index>` to test name since preprocessor has some limitations in recursions Closes #1454
2018-12-06 19:27:33 +01:00
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: PASSED:
REQUIRE( Template_Fixture_2<TestType>::m_a.size() == 0 )
with expansion:
0 == 0
Nttp support tests approvals
2019-05-23 19:29:18 +02:00
-------------------------------------------------------------------------------
A TEMPLATE_PRODUCT_TEST_CASE_METHOD_SIG based test run that fails -
Template_Foo_2<float, 6>
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: FAILED:
REQUIRE( Template_Fixture_2<TestType>{}.m_a.size() < 2 )
with expansion:
6 < 2
-------------------------------------------------------------------------------
A TEMPLATE_PRODUCT_TEST_CASE_METHOD_SIG based test run that fails -
Template_Foo_2<int, 2>
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: FAILED:
REQUIRE( Template_Fixture_2<TestType>{}.m_a.size() < 2 )
with expansion:
2 < 2
-------------------------------------------------------------------------------
A TEMPLATE_PRODUCT_TEST_CASE_METHOD_SIG based test run that fails - std::array
<float, 6>
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: FAILED:
REQUIRE( Template_Fixture_2<TestType>{}.m_a.size() < 2 )
with expansion:
6 < 2
-------------------------------------------------------------------------------
A TEMPLATE_PRODUCT_TEST_CASE_METHOD_SIG based test run that fails - std::array
<int, 2>
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: FAILED:
REQUIRE( Template_Fixture_2<TestType>{}.m_a.size() < 2 )
with expansion:
2 < 2
-------------------------------------------------------------------------------
A TEMPLATE_PRODUCT_TEST_CASE_METHOD_SIG based test run that succeeds -
Template_Foo_2<float,6>
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: PASSED:
REQUIRE( Template_Fixture_2<TestType>{}.m_a.size() >= 2 )
with expansion:
6 >= 2
-------------------------------------------------------------------------------
A TEMPLATE_PRODUCT_TEST_CASE_METHOD_SIG based test run that succeeds -
Template_Foo_2<int,2>
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: PASSED:
REQUIRE( Template_Fixture_2<TestType>{}.m_a.size() >= 2 )
with expansion:
2 >= 2
-------------------------------------------------------------------------------
A TEMPLATE_PRODUCT_TEST_CASE_METHOD_SIG based test run that succeeds - std::
array<float,6>
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: PASSED:
REQUIRE( Template_Fixture_2<TestType>{}.m_a.size() >= 2 )
with expansion:
6 >= 2
-------------------------------------------------------------------------------
A TEMPLATE_PRODUCT_TEST_CASE_METHOD_SIG based test run that succeeds - std::
array<int,2>
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: PASSED:
REQUIRE( Template_Fixture_2<TestType>{}.m_a.size() >= 2 )
with expansion:
2 >= 2
Add support for templated tests This adds support for templated tests and test methods via `TEMPLATE_TEST_CASE` and `TEMPLATE_TEST_CASE_METHOD` macros. These work mostly just like their regular counterparts*, but take an unlimited** number of types as their last arguments. * Unlike the plain `TEST_CASE*` macros, the `TEMPLATE*` variants require a tag string. ** In practice there is limit of about 300 types.
2018-11-08 07:26:39 +01:00
-------------------------------------------------------------------------------
A TEMPLATE_TEST_CASE_METHOD based test run that fails - double
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: FAILED:
REQUIRE( Template_Fixture<TestType>::m_a == 2 )
with expansion:
1.0 == 2
-------------------------------------------------------------------------------
A TEMPLATE_TEST_CASE_METHOD based test run that fails - float
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: FAILED:
REQUIRE( Template_Fixture<TestType>::m_a == 2 )
with expansion:
1.0f == 2
-------------------------------------------------------------------------------
A TEMPLATE_TEST_CASE_METHOD based test run that fails - int
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: FAILED:
REQUIRE( Template_Fixture<TestType>::m_a == 2 )
with expansion:
1 == 2
-------------------------------------------------------------------------------
A TEMPLATE_TEST_CASE_METHOD based test run that succeeds - double
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: PASSED:
REQUIRE( Template_Fixture<TestType>::m_a == 1 )
with expansion:
1.0 == 1
-------------------------------------------------------------------------------
A TEMPLATE_TEST_CASE_METHOD based test run that succeeds - float
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: PASSED:
REQUIRE( Template_Fixture<TestType>::m_a == 1 )
with expansion:
1.0f == 1
-------------------------------------------------------------------------------
A TEMPLATE_TEST_CASE_METHOD based test run that succeeds - int
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: PASSED:
REQUIRE( Template_Fixture<TestType>::m_a == 1 )
with expansion:
1 == 1
Nttp support tests approvals
2019-05-23 19:29:18 +02:00
-------------------------------------------------------------------------------
A TEMPLATE_TEST_CASE_METHOD_SIG based test run that fails - 1
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: FAILED:
REQUIRE( Nttp_Fixture<V>::value == 0 )
with expansion:
1 == 0
-------------------------------------------------------------------------------
A TEMPLATE_TEST_CASE_METHOD_SIG based test run that fails - 3
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: FAILED:
REQUIRE( Nttp_Fixture<V>::value == 0 )
with expansion:
3 == 0
-------------------------------------------------------------------------------
A TEMPLATE_TEST_CASE_METHOD_SIG based test run that fails - 6
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: FAILED:
REQUIRE( Nttp_Fixture<V>::value == 0 )
with expansion:
6 == 0
-------------------------------------------------------------------------------
A TEMPLATE_TEST_CASE_METHOD_SIG based test run that succeeds - 1
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: PASSED:
REQUIRE( Nttp_Fixture<V>::value > 0 )
with expansion:
1 > 0
-------------------------------------------------------------------------------
A TEMPLATE_TEST_CASE_METHOD_SIG based test run that succeeds - 3
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: PASSED:
REQUIRE( Nttp_Fixture<V>::value > 0 )
with expansion:
3 > 0
-------------------------------------------------------------------------------
A TEMPLATE_TEST_CASE_METHOD_SIG based test run that succeeds - 6
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: PASSED:
REQUIRE( Nttp_Fixture<V>::value > 0 )
with expansion:
6 > 0
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
A TEST_CASE_METHOD based test run that fails
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: FAILED:
REQUIRE( m_a == 2 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
1 == 2
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
A TEST_CASE_METHOD based test run that succeeds
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Class.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
TEST_CASE_PERSISTENT_FIXTURE: A new fixture macro for allowing persistent fixtures throughout a TEST_CASE (#2885) This PR introduces a new `TEST_CASE` macro called `TEST_CASE_PERSISTENT_FIXTURE`. `TEST_CASE_PERSISTENT_FIXTURE` offers the same functionality as `TEST_CASE_METHOD` except for one difference. The object on which the test method is invoked is only created once for all invocations of the test case. The object is created just after the `testCaseStarting` event is broadcast and the object is destroyed just before the `testCaseEnding` event is broadcast. The main motivation for this new functionality is to allow `TEST_CASE`s to do expensive setup and teardown once per `TEST_CASE`, without having to resort to abusing event listeners or static function variables with manual initialization. Implements #1602 --------- Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2024-08-05 17:01:41 +02:00
Class.tests.cpp:<line number>: PASSED:
REQUIRE( m_a == 1 )
with expansion:
1 == 1
-------------------------------------------------------------------------------
A TEST_CASE_PERSISTENT_FIXTURE based test run that fails
First partial run
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: PASSED:
REQUIRE( m_a++ == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
A TEST_CASE_PERSISTENT_FIXTURE based test run that fails
Second partial run
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: FAILED:
REQUIRE( m_a == 0 )
with expansion:
1 == 0
-------------------------------------------------------------------------------
A TEST_CASE_PERSISTENT_FIXTURE based test run that succeeds
First partial run
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: PASSED:
REQUIRE( m_a++ == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
A TEST_CASE_PERSISTENT_FIXTURE based test run that succeeds
Second partial run
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Class.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( m_a == 1 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
1 == 1
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Template tests: added TEMPLATE_PRODUCT_TEST_CASE support for generating test cases based on multiple template template types combined with template arguments for each of the template template types specified e.g. ``` TEMPLATE_PRODUCT_TEST_CASE("template product","[template]", (std::tuple, std::pair, std::map), ((int,float),(char,double),(int,char))) ``` will effectively create 9 test cases with types: std::tuple<int,float> std::tuple<char,double> std::tuple<int,char> std::pair<int,float> std::pair<char, double> std::pair<int,char> std::map<int,float> std::map<char,double> std::map<int,char> Tested type is accessible in test case body as TestType Unique name is created by appending ` - <index>` to test name since preprocessor has some limitations in recursions Closes #1454
2018-12-06 19:27:33 +01:00
-------------------------------------------------------------------------------
Use correct type name instead of index for TEMPLATE_PRODUCT_TEST_CASE (#1544) Previously, for a TEMPLATE_PRODUCT_TEST_CASE("Test" ..., T, (P1, P2)), the generated test case names were Test - 0 Test - 1 With this commit, the correct typename is used: Test - T<P1> Test - T<P2> ----------- MSVC needs another indirection to evaluate INTERNAL_CATCH_STRINGIZE and also inserts a space before theINTERNAL_CATCH_STRINGIZE_WITHOUT_PARENS parameter, which we can get rid of by pointer arithmetic.
2019-02-17 21:52:22 +01:00
A Template product test case - Foo<float>
Template tests: added TEMPLATE_PRODUCT_TEST_CASE support for generating test cases based on multiple template template types combined with template arguments for each of the template template types specified e.g. ``` TEMPLATE_PRODUCT_TEST_CASE("template product","[template]", (std::tuple, std::pair, std::map), ((int,float),(char,double),(int,char))) ``` will effectively create 9 test cases with types: std::tuple<int,float> std::tuple<char,double> std::tuple<int,char> std::pair<int,float> std::pair<char, double> std::pair<int,char> std::map<int,float> std::map<char,double> std::map<int,char> Tested type is accessible in test case body as TestType Unique name is created by appending ` - <index>` to test name since preprocessor has some limitations in recursions Closes #1454
2018-12-06 19:27:33 +01:00
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( x.size() == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
Use correct type name instead of index for TEMPLATE_PRODUCT_TEST_CASE (#1544) Previously, for a TEMPLATE_PRODUCT_TEST_CASE("Test" ..., T, (P1, P2)), the generated test case names were Test - 0 Test - 1 With this commit, the correct typename is used: Test - T<P1> Test - T<P2> ----------- MSVC needs another indirection to evaluate INTERNAL_CATCH_STRINGIZE and also inserts a space before theINTERNAL_CATCH_STRINGIZE_WITHOUT_PARENS parameter, which we can get rid of by pointer arithmetic.
2019-02-17 21:52:22 +01:00
A Template product test case - Foo<int>
Template tests: added TEMPLATE_PRODUCT_TEST_CASE support for generating test cases based on multiple template template types combined with template arguments for each of the template template types specified e.g. ``` TEMPLATE_PRODUCT_TEST_CASE("template product","[template]", (std::tuple, std::pair, std::map), ((int,float),(char,double),(int,char))) ``` will effectively create 9 test cases with types: std::tuple<int,float> std::tuple<char,double> std::tuple<int,char> std::pair<int,float> std::pair<char, double> std::pair<int,char> std::map<int,float> std::map<char,double> std::map<int,char> Tested type is accessible in test case body as TestType Unique name is created by appending ` - <index>` to test name since preprocessor has some limitations in recursions Closes #1454
2018-12-06 19:27:33 +01:00
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( x.size() == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
Use correct type name instead of index for TEMPLATE_PRODUCT_TEST_CASE (#1544) Previously, for a TEMPLATE_PRODUCT_TEST_CASE("Test" ..., T, (P1, P2)), the generated test case names were Test - 0 Test - 1 With this commit, the correct typename is used: Test - T<P1> Test - T<P2> ----------- MSVC needs another indirection to evaluate INTERNAL_CATCH_STRINGIZE and also inserts a space before theINTERNAL_CATCH_STRINGIZE_WITHOUT_PARENS parameter, which we can get rid of by pointer arithmetic.
2019-02-17 21:52:22 +01:00
A Template product test case - std::vector<float>
Template tests: added TEMPLATE_PRODUCT_TEST_CASE support for generating test cases based on multiple template template types combined with template arguments for each of the template template types specified e.g. ``` TEMPLATE_PRODUCT_TEST_CASE("template product","[template]", (std::tuple, std::pair, std::map), ((int,float),(char,double),(int,char))) ``` will effectively create 9 test cases with types: std::tuple<int,float> std::tuple<char,double> std::tuple<int,char> std::pair<int,float> std::pair<char, double> std::pair<int,char> std::map<int,float> std::map<char,double> std::map<int,char> Tested type is accessible in test case body as TestType Unique name is created by appending ` - <index>` to test name since preprocessor has some limitations in recursions Closes #1454
2018-12-06 19:27:33 +01:00
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( x.size() == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
Use correct type name instead of index for TEMPLATE_PRODUCT_TEST_CASE (#1544) Previously, for a TEMPLATE_PRODUCT_TEST_CASE("Test" ..., T, (P1, P2)), the generated test case names were Test - 0 Test - 1 With this commit, the correct typename is used: Test - T<P1> Test - T<P2> ----------- MSVC needs another indirection to evaluate INTERNAL_CATCH_STRINGIZE and also inserts a space before theINTERNAL_CATCH_STRINGIZE_WITHOUT_PARENS parameter, which we can get rid of by pointer arithmetic.
2019-02-17 21:52:22 +01:00
A Template product test case - std::vector<int>
Template tests: added TEMPLATE_PRODUCT_TEST_CASE support for generating test cases based on multiple template template types combined with template arguments for each of the template template types specified e.g. ``` TEMPLATE_PRODUCT_TEST_CASE("template product","[template]", (std::tuple, std::pair, std::map), ((int,float),(char,double),(int,char))) ``` will effectively create 9 test cases with types: std::tuple<int,float> std::tuple<char,double> std::tuple<int,char> std::pair<int,float> std::pair<char, double> std::pair<int,char> std::map<int,float> std::map<char,double> std::map<int,char> Tested type is accessible in test case body as TestType Unique name is created by appending ` - <index>` to test name since preprocessor has some limitations in recursions Closes #1454
2018-12-06 19:27:33 +01:00
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( x.size() == 0 )
with expansion:
0 == 0
Nttp support tests approvals
2019-05-23 19:29:18 +02:00
-------------------------------------------------------------------------------
A Template product test case with array signature - Bar<float, 42>
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( x.size() > 0 )
with expansion:
42 > 0
-------------------------------------------------------------------------------
A Template product test case with array signature - Bar<int, 9>
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( x.size() > 0 )
with expansion:
9 > 0
-------------------------------------------------------------------------------
A Template product test case with array signature - std::array<float, 42>
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( x.size() > 0 )
with expansion:
42 > 0
-------------------------------------------------------------------------------
A Template product test case with array signature - std::array<int, 9>
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( x.size() > 0 )
with expansion:
9 > 0
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
A comparison that uses literals instead of the normal constructor
-------------------------------------------------------------------------------
Approx.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( d == 1.23_a )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.22999999999999998
==
Approx( 1.22999999999999998 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( d != 1.22_a )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.22999999999999998
!=
Approx( 1.21999999999999997 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( -d == -1.23_a )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
-1.22999999999999998
==
Approx( -1.22999999999999998 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( d == 1.2_a .epsilon(.1) )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.22999999999999998
==
Approx( 1.19999999999999996 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( d != 1.2_a .epsilon(.001) )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.22999999999999998
!=
Approx( 1.19999999999999996 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( d == 1_a .epsilon(.3) )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.22999999999999998 == Approx( 1.0 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
A couple of nested sections followed by a failure
Outer
Inner
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
with message:
that's not flying - that's failing in style
-------------------------------------------------------------------------------
A couple of nested sections followed by a failure
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: FAILED:
explicitly with message:
to infinity and beyond
-------------------------------------------------------------------------------
A failing expression with a non streamable type is still captured
-------------------------------------------------------------------------------
Tricky.tests.cpp:<line number>
...............................................................................
Tricky.tests.cpp:<line number>: FAILED:
CHECK( &o1 == &o2 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
0x<hex digits> == 0x<hex digits>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Update baselines
2018-08-19 23:22:36 +02:00
Tricky.tests.cpp:<line number>: FAILED:
CHECK( o1 == o2 )
with expansion:
{?} == {?}
-------------------------------------------------------------------------------
Absolute margin
-------------------------------------------------------------------------------
Approx.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( 104.0 != Approx(100.0) )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
104.0 != Approx( 100.0 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( 104.0 == Approx(100.0).margin(5) )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
104.0 == Approx( 100.0 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( 104.0 == Approx(100.0).margin(4) )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
104.0 == Approx( 100.0 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( 104.0 != Approx(100.0).margin(3) )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
104.0 != Approx( 100.0 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( 100.3 != Approx(100.0) )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
100.29999999999999716 != Approx( 100.0 )
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( 100.3 == Approx(100.0).margin(0.5) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
100.29999999999999716 == Approx( 100.0 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
An empty test with no assertions
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Misc.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Update baselines
2018-08-19 23:22:36 +02:00
No assertions in test case 'An empty test with no assertions'
-------------------------------------------------------------------------------
An expression with side-effects should only be evaluated once
-------------------------------------------------------------------------------
Tricky.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( i++ == 7 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
7 == 7
Add tests for case insensitive string matching
2017-11-13 15:46:33 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( i++ == 8 )
Add tests for case insensitive string matching
2017-11-13 15:46:33 +01:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
8 == 8
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
An unchecked exception reports the line of the last assertion
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Exception.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Exception.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( 1 == 1 )
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Exception.tests.cpp:<line number>: FAILED:
Update baselines
2018-08-19 23:22:36 +02:00
{Unknown expression after the reported line}
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
due to unexpected exception with message:
Update baselines
2018-08-19 23:22:36 +02:00
unexpected exception
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Anonymous test case 1
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
VariadicMacros.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
VariadicMacros.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
with message:
anonymous test case
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
approved tests that were correct the first time (previous approvals were erroneous)
2017-04-09 21:40:01 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Approx setters validate their arguments
approved tests that were correct the first time (previous approvals were erroneous)
2017-04-09 21:40:01 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Approx.tests.cpp:<line number>
approved tests that were correct the first time (previous approvals were erroneous)
2017-04-09 21:40:01 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE_NOTHROW( Approx(0).margin(0) )
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE_NOTHROW( Approx(0).margin(1234656) )
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE_THROWS_AS( Approx(0).margin(-2), std::domain_error )
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE_NOTHROW( Approx(0).epsilon(0) )
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE_NOTHROW( Approx(0).epsilon(1) )
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE_THROWS_AS( Approx(0).epsilon(-0.001), std::domain_error )
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE_THROWS_AS( Approx(0).epsilon(1.0001), std::domain_error )
approved tests that were correct the first time (previous approvals were erroneous)
2017-04-09 21:40:01 +02:00
Approx cleanup: More tests, INFINITY handling, etc
2017-11-01 07:30:11 +01:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Approx with exactly-representable margin
Approx cleanup: More tests, INFINITY handling, etc
2017-11-01 07:30:11 +01:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Approx.tests.cpp:<line number>
Approx cleanup: More tests, INFINITY handling, etc
2017-11-01 07:30:11 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( 0.25f == Approx(0.0f).margin(0.25f) )
Approx cleanup: More tests, INFINITY handling, etc
2017-11-01 07:30:11 +01:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
0.25f == Approx( 0.0 )
Approx cleanup: More tests, INFINITY handling, etc
2017-11-01 07:30:11 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( 0.0f == Approx(0.25f).margin(0.25f) )
Approx cleanup: More tests, INFINITY handling, etc
2017-11-01 07:30:11 +01:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
0.0f == Approx( 0.25 )
Approx cleanup: More tests, INFINITY handling, etc
2017-11-01 07:30:11 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( 0.5f == Approx(0.25f).margin(0.25f) )
with expansion:
0.5f == Approx( 0.25 )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( 245.0f == Approx(245.25f).margin(0.25f) )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
245.0f == Approx( 245.25 )
Add tests for case insensitive string matching
2017-11-13 15:46:33 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( 245.5f == Approx(245.25f).margin(0.25f) )
Add tests for case insensitive string matching
2017-11-13 15:46:33 +01:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
245.5f == Approx( 245.25 )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Approx cleanup: More tests, INFINITY handling, etc
2017-11-01 07:30:11 +01:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Approximate PI
Approx cleanup: More tests, INFINITY handling, etc
2017-11-01 07:30:11 +01:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Approx.tests.cpp:<line number>
Approx cleanup: More tests, INFINITY handling, etc
2017-11-01 07:30:11 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( divide( 22, 7 ) == Approx( 3.141 ).epsilon( 0.001 ) )
Approx cleanup: More tests, INFINITY handling, etc
2017-11-01 07:30:11 +01:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
3.14285714285714279
==
Approx( 3.14100000000000001 )
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( divide( 22, 7 ) != Approx( 3.141 ).epsilon( 0.0001 ) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
3.14285714285714279
!=
Approx( 3.14100000000000001 )
Approx cleanup: More tests, INFINITY handling, etc
2017-11-01 07:30:11 +01:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Approximate comparisons with different epsilons
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Approx.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( d != Approx( 1.231 ) )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.22999999999999998
!=
Approx( 1.23100000000000009 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( d == Approx( 1.231 ).epsilon( 0.1 ) )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.22999999999999998
==
Approx( 1.23100000000000009 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Approximate comparisons with floats
-------------------------------------------------------------------------------
Approx.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( 1.23f == Approx( 1.23f ) )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.230000019f
==
Approx( 1.23000001907348633 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( 0.0f == Approx( 0.0f ) )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
0.0f == Approx( 0.0 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Approximate comparisons with ints
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Approx.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( 1 == Approx( 1 ) )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
1 == Approx( 1.0 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( 0 == Approx( 0 ) )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
0 == Approx( 0.0 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Approximate comparisons with mixed numeric types
-------------------------------------------------------------------------------
Approx.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( 1.0f == Approx( 1 ) )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
1.0f == Approx( 1.0 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( 0 == Approx( dZero) )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
0 == Approx( 0.0 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( 0 == Approx( dSmall ).margin( 0.001 ) )
Update baselines
2017-06-06 15:07:57 +02:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
0 == Approx( 0.00001 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( 1.234f == Approx( dMedium ) )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.233999968f
==
Approx( 1.23399999999999999 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( dMedium == Approx( 1.234f ) )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.23399999999999999
==
Approx( 1.23399996757507324 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Arbitrary predicate matcher
Function pointer
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 1, Predicate<int>( alwaysTrue, "always true" ) )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
1 matches predicate: "always true"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 1, !Predicate<int>( alwaysFalse, "always false" ) )
Add tests for case insensitive string matching
2017-11-13 15:46:33 +01:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
1 not matches predicate: "always false"
Add tests for case insensitive string matching
2017-11-13 15:46:33 +01:00
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Arbitrary predicate matcher
Lambdas + different type
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( "Hello olleH", Predicate<std::string>( []( std::string const& str ) -> bool { return str.front() == str.back(); }, "First and last character should be equal" ) )
Add tests for case insensitive string matching
2017-11-13 15:46:33 +01:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
"Hello olleH" matches predicate: "First and last character should be equal"
Add tests for case insensitive string matching
2017-11-13 15:46:33 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( "This wouldn't pass", !Predicate<std::string>( []( std::string const& str ) -> bool { return str.front() == str.back(); } ) )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
"This wouldn't pass" not matches undescribed predicate
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Support bitand and bitor in REQUIRE/CHECK This means that bit-flag-like types with conversion to bool can be asserted on, like so `REQUIRE(var & Flags::AddNewline)`.
2020-04-21 11:00:08 +02:00
-------------------------------------------------------------------------------
Assertion macros support bit operators and bool conversions
-------------------------------------------------------------------------------
Compilation.tests.cpp:<line number>
...............................................................................
Compilation.tests.cpp:<line number>: PASSED:
REQUIRE( lhs | rhs )
with expansion:
Val: 1 | Val: 2
Compilation.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( lhs & rhs )
with expansion:
!(Val: 1 & Val: 2)
Compilation.tests.cpp:<line number>: PASSED:
REQUIRE( HasBitOperators{ 1 } & HasBitOperators{ 1 } )
with expansion:
Val: 1 & Val: 1
Add support for bitwise xor to the decomposer
2020-04-21 19:27:12 +02:00
Compilation.tests.cpp:<line number>: PASSED:
REQUIRE( lhs ^ rhs )
with expansion:
Val: 1 ^ Val: 2
Compilation.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( lhs ^ lhs )
with expansion:
!(Val: 1 ^ Val: 1)
Add stringification support to std::exception and deriving classes This support is based on overriden `std::exception::what` method, so if an exception does not do so meaningfully, the message is still pointless. This is only used as a fallback, both `StringMaker` specialization and `operator<<` overload have priority..
2018-05-12 17:46:25 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Assertions then sections
Add stringification support to std::exception and deriving classes This support is based on overriden `std::exception::what` method, so if an exception does not do so meaningfully, the message is still pointless. This is only used as a fallback, both `StringMaker` specialization and `operator<<` overload have priority..
2018-05-12 17:46:25 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Tricky.tests.cpp:<line number>
Add stringification support to std::exception and deriving classes This support is based on overriden `std::exception::what` method, so if an exception does not do so meaningfully, the message is still pointless. This is only used as a fallback, both `StringMaker` specialization and `operator<<` overload have priority..
2018-05-12 17:46:25 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( true )
Add stringification support to std::exception and deriving classes This support is based on overriden `std::exception::what` method, so if an exception does not do so meaningfully, the message is still pointless. This is only used as a fallback, both `StringMaker` specialization and `operator<<` overload have priority..
2018-05-12 17:46:25 +02:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Assertions then sections
A section
-------------------------------------------------------------------------------
Tricky.tests.cpp:<line number>
...............................................................................
Add stringification support to std::exception and deriving classes This support is based on overriden `std::exception::what` method, so if an exception does not do so meaningfully, the message is still pointless. This is only used as a fallback, both `StringMaker` specialization and `operator<<` overload have priority..
2018-05-12 17:46:25 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( true )
Add stringification support to std::exception and deriving classes This support is based on overriden `std::exception::what` method, so if an exception does not do so meaningfully, the message is still pointless. This is only used as a fallback, both `StringMaker` specialization and `operator<<` overload have priority..
2018-05-12 17:46:25 +02:00
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Assertions then sections
A section
Another section
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Tricky.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( true )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Assertions then sections
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Tricky.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( true )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Assertions then sections
A section
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Tricky.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( true )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Assertions then sections
A section
Another other section
-------------------------------------------------------------------------------
Tricky.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( true )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Add generic Contains matcher It matches a range iff the range contains a specific element, or an element in the range matches the provided matcher.
2020-03-02 14:25:43 +01:00
-------------------------------------------------------------------------------
Basic use of the Contains range matcher
Different argument ranges, same element type, default comparison
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( a, Contains(1) )
with expansion:
{ 1, 2, 3 } contains element 1
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( b, Contains(1) )
with expansion:
{ 0, 1, 2 } contains element 1
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( c, !Contains(1) )
with expansion:
{ 4, 5, 6 } not contains element 1
-------------------------------------------------------------------------------
Basic use of the Contains range matcher
Different argument ranges, same element type, custom comparison
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( a, Contains(0, close_enough) )
with expansion:
{ 1, 2, 3 } contains element 0
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( b, Contains(0, close_enough) )
with expansion:
{ 0, 1, 2 } contains element 0
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( c, !Contains(0, close_enough) )
with expansion:
{ 4, 5, 6 } not contains element 0
-------------------------------------------------------------------------------
Basic use of the Contains range matcher
Different element type, custom comparisons
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( a, Contains(4, [](auto&& lhs, size_t sz) { return lhs.size() == sz; }) )
with expansion:
{ "abc", "abcd", "abcde" } contains element 4
-------------------------------------------------------------------------------
Basic use of the Contains range matcher
Can handle type that requires ADL-found free function begin and end
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( in, Contains(1) )
with expansion:
{ 1, 2, 3, 4, 5 } contains element 1
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( in, !Contains(8) )
with expansion:
{ 1, 2, 3, 4, 5 } not contains element 8
-------------------------------------------------------------------------------
Basic use of the Contains range matcher
Initialization with move only types
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( in, Contains(MoveOnlyTestElement{ 2 }) )
with expansion:
{ 1, 2, 3 } contains element 2
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( in, !Contains(MoveOnlyTestElement{ 9 }) )
with expansion:
{ 1, 2, 3 } not contains element 9
-------------------------------------------------------------------------------
Basic use of the Contains range matcher
Matching using matcher
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( in, Contains(Catch::Matchers::WithinAbs(0.5, 0.5)) )
with expansion:
{ 1.0, 2.0, 3.0, 0.0 } contains element matching is within 0.5 of 0.5
Add IsEmpty and SizeIs matchers for ranges/containers `SizeIs` can accept both `size_t` and a matcher. In the first case, it checks whether the size of the range is equal to specified size. In the second case, it checks whether the provided matcher accepts the size of the range.
2020-03-09 11:13:07 +01:00
-------------------------------------------------------------------------------
Basic use of the Empty range matcher
Simple, std-provided containers
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( empty_array, IsEmpty() )
with expansion:
{ } is empty
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( non_empty_array, !IsEmpty() )
with expansion:
{ 0.0 } not is empty
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( empty_vec, IsEmpty() )
with expansion:
{ } is empty
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( non_empty_vec, !IsEmpty() )
with expansion:
{ 'a', 'b', 'c' } not is empty
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( inner_lists_are_empty, !IsEmpty() )
with expansion:
{ { } } not is empty
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( inner_lists_are_empty.front(), IsEmpty() )
with expansion:
{ } is empty
-------------------------------------------------------------------------------
Basic use of the Empty range matcher
Type with empty
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( has_empty{}, !IsEmpty() )
with expansion:
{?} not is empty
-------------------------------------------------------------------------------
Basic use of the Empty range matcher
Type requires ADL found empty free function
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( unrelated::ADL_empty{}, IsEmpty() )
with expansion:
{?} is empty
Fix CAPTURE macro for nontrivial uses The previous implemetation was just plain broken for most of possible uses, the new one should work (even though it is ugly as all hell, and should be improved ASAP). Fixes #1436
2018-11-19 23:06:06 +01:00
-------------------------------------------------------------------------------
CAPTURE can deal with complex expressions
-------------------------------------------------------------------------------
Message.tests.cpp:<line number>
...............................................................................
Message.tests.cpp:<line number>: PASSED:
with messages:
a := 1
b := 2
c := 3
a + b := 3
a+b := 3
c > b := true
a == 1 := true
-------------------------------------------------------------------------------
CAPTURE can deal with complex expressions involving commas
-------------------------------------------------------------------------------
Message.tests.cpp:<line number>
...............................................................................
Message.tests.cpp:<line number>: PASSED:
with messages:
Fix tests for C++23's multi-arg index operator Closes #2744
2023-10-28 21:49:49 +02:00
custom_index_op<int>{1, 2, 3}[0, 1, 2] := 0
custom_index_op<int>{1, 2, 3}[(0, 1)] := 0
custom_index_op<int>{1, 2, 3}[0] := 0
Fix CAPTURE macro for nontrivial uses The previous implemetation was just plain broken for most of possible uses, the new one should work (even though it is ugly as all hell, and should be improved ASAP). Fixes #1436
2018-11-19 23:06:06 +01:00
(helper_1436<int, int>{12, -12}) := { 12, -12 }
(helper_1436<int, int>(-12, 12)) := { -12, 12 }
(1, 2) := 2
(2, 3) := 3
Allow quotes in CAPTURE arguments (#1608) * Allow quotes in CAPTURE arguments Fix CAPTURE to handle string and character literals properly
2019-05-01 19:12:44 +02:00
-------------------------------------------------------------------------------
CAPTURE parses string and character constants
-------------------------------------------------------------------------------
Message.tests.cpp:<line number>
...............................................................................
Message.tests.cpp:<line number>: PASSED:
with messages:
("comma, in string", "escaped, \", ") := "escaped, ", "
"single quote in string,'," := "single quote in string,',"
"some escapes, \\,\\\\" := "some escapes, \,\\"
"some, ), unmatched, } prenheses {[<" := "some, ), unmatched, } prenheses {[
<"
'"' := '"'
'\'' := '''
',' := ','
'}' := '}'
')' := ')'
'(' := '('
'{' := '{'
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Capture and info messages
Capture should stringify like assertions
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
ToStringGeneral.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringGeneral.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( true )
with message:
i := 2
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Capture and info messages
Info should NOT stringify the way assertions do
-------------------------------------------------------------------------------
ToStringGeneral.tests.cpp:<line number>
...............................................................................
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringGeneral.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( true )
with message:
3
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Add CaseInsensitiveEqualTo comparison type
2021-12-26 18:54:47 +01:00
-------------------------------------------------------------------------------
CaseInsensitiveEqualsTo is case insensitive
Degenerate cases
-------------------------------------------------------------------------------
Details.tests.cpp:<line number>
...............................................................................
Details.tests.cpp:<line number>: PASSED:
REQUIRE( eq( "", "" ) )
with expansion:
true
Details.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( eq( "", "a" ) )
with expansion:
!false
-------------------------------------------------------------------------------
CaseInsensitiveEqualsTo is case insensitive
Plain comparisons
-------------------------------------------------------------------------------
Details.tests.cpp:<line number>
...............................................................................
Details.tests.cpp:<line number>: PASSED:
REQUIRE( eq( "a", "a" ) )
with expansion:
true
Details.tests.cpp:<line number>: PASSED:
REQUIRE( eq( "a", "A" ) )
with expansion:
true
Details.tests.cpp:<line number>: PASSED:
REQUIRE( eq( "A", "a" ) )
with expansion:
true
Details.tests.cpp:<line number>: PASSED:
REQUIRE( eq( "A", "A" ) )
with expansion:
true
Details.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( eq( "a", "b" ) )
with expansion:
!false
Details.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( eq( "a", "B" ) )
with expansion:
!false
-------------------------------------------------------------------------------
CaseInsensitiveLess is case insensitive
Degenerate cases
-------------------------------------------------------------------------------
Details.tests.cpp:<line number>
...............................................................................
Details.tests.cpp:<line number>: PASSED:
REQUIRE( lt( "", "a" ) )
with expansion:
true
Details.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( lt( "a", "a" ) )
with expansion:
!false
Details.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( lt( "", "" ) )
with expansion:
!false
-------------------------------------------------------------------------------
CaseInsensitiveLess is case insensitive
Plain comparisons
-------------------------------------------------------------------------------
Details.tests.cpp:<line number>
...............................................................................
Details.tests.cpp:<line number>: PASSED:
REQUIRE( lt( "a", "b" ) )
with expansion:
true
Details.tests.cpp:<line number>: PASSED:
REQUIRE( lt( "a", "B" ) )
with expansion:
true
Details.tests.cpp:<line number>: PASSED:
REQUIRE( lt( "A", "b" ) )
with expansion:
true
Details.tests.cpp:<line number>: PASSED:
REQUIRE( lt( "A", "B" ) )
with expansion:
true
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Character pretty printing
Specifically escaped
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
ToStringGeneral.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringGeneral.tests.cpp:<line number>: PASSED:
Update outdated tests for stringifying characters Previously the tests relied purely on output changes in approvals. Now the stringification output is checked directly as part of the unit tests.
2024-03-01 15:09:06 +01:00
CHECK( ::Catch::Detail::stringify('\t') == "'\\t'" )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Update outdated tests for stringifying characters Previously the tests relied purely on output changes in approvals. Now the stringification output is checked directly as part of the unit tests.
2024-03-01 15:09:06 +01:00
"'\t'" == "'\t'"
Update baselines
2017-06-06 15:07:57 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringGeneral.tests.cpp:<line number>: PASSED:
Update outdated tests for stringifying characters Previously the tests relied purely on output changes in approvals. Now the stringification output is checked directly as part of the unit tests.
2024-03-01 15:09:06 +01:00
CHECK( ::Catch::Detail::stringify('\n') == "'\\n'" )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Update outdated tests for stringifying characters Previously the tests relied purely on output changes in approvals. Now the stringification output is checked directly as part of the unit tests.
2024-03-01 15:09:06 +01:00
"'\n'" == "'\n'"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringGeneral.tests.cpp:<line number>: PASSED:
Update outdated tests for stringifying characters Previously the tests relied purely on output changes in approvals. Now the stringification output is checked directly as part of the unit tests.
2024-03-01 15:09:06 +01:00
CHECK( ::Catch::Detail::stringify('\r') == "'\\r'" )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Update outdated tests for stringifying characters Previously the tests relied purely on output changes in approvals. Now the stringification output is checked directly as part of the unit tests.
2024-03-01 15:09:06 +01:00
"'\r'" == "'\r'"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringGeneral.tests.cpp:<line number>: PASSED:
Update outdated tests for stringifying characters Previously the tests relied purely on output changes in approvals. Now the stringification output is checked directly as part of the unit tests.
2024-03-01 15:09:06 +01:00
CHECK( ::Catch::Detail::stringify('\f') == "'\\f'" )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Update outdated tests for stringifying characters Previously the tests relied purely on output changes in approvals. Now the stringification output is checked directly as part of the unit tests.
2024-03-01 15:09:06 +01:00
"'\f'" == "'\f'"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Character pretty printing
General chars
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
ToStringGeneral.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringGeneral.tests.cpp:<line number>: PASSED:
Update outdated tests for stringifying characters Previously the tests relied purely on output changes in approvals. Now the stringification output is checked directly as part of the unit tests.
2024-03-01 15:09:06 +01:00
CHECK( ::Catch::Detail::stringify( ' ' ) == "' '" )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Update outdated tests for stringifying characters Previously the tests relied purely on output changes in approvals. Now the stringification output is checked directly as part of the unit tests.
2024-03-01 15:09:06 +01:00
"' '" == "' '"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringGeneral.tests.cpp:<line number>: PASSED:
Update outdated tests for stringifying characters Previously the tests relied purely on output changes in approvals. Now the stringification output is checked directly as part of the unit tests.
2024-03-01 15:09:06 +01:00
CHECK( ::Catch::Detail::stringify( 'A' ) == "'A'" )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Update outdated tests for stringifying characters Previously the tests relied purely on output changes in approvals. Now the stringification output is checked directly as part of the unit tests.
2024-03-01 15:09:06 +01:00
"'A'" == "'A'"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringGeneral.tests.cpp:<line number>: PASSED:
Update outdated tests for stringifying characters Previously the tests relied purely on output changes in approvals. Now the stringification output is checked directly as part of the unit tests.
2024-03-01 15:09:06 +01:00
CHECK( ::Catch::Detail::stringify( 'z' ) == "'z'" )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Update outdated tests for stringifying characters Previously the tests relied purely on output changes in approvals. Now the stringification output is checked directly as part of the unit tests.
2024-03-01 15:09:06 +01:00
"'z'" == "'z'"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Character pretty printing
Low ASCII
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
ToStringGeneral.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringGeneral.tests.cpp:<line number>: PASSED:
Update outdated tests for stringifying characters Previously the tests relied purely on output changes in approvals. Now the stringification output is checked directly as part of the unit tests.
2024-03-01 15:09:06 +01:00
CHECK( ::Catch::Detail::stringify( '\0' ) == "0" )
Update baselines
2017-06-06 15:07:57 +02:00
with expansion:
Update outdated tests for stringifying characters Previously the tests relied purely on output changes in approvals. Now the stringification output is checked directly as part of the unit tests.
2024-03-01 15:09:06 +01:00
"0" == "0"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringGeneral.tests.cpp:<line number>: PASSED:
Update outdated tests for stringifying characters Previously the tests relied purely on output changes in approvals. Now the stringification output is checked directly as part of the unit tests.
2024-03-01 15:09:06 +01:00
CHECK( ::Catch::Detail::stringify( static_cast<char>(2) ) == "2" )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Update outdated tests for stringifying characters Previously the tests relied purely on output changes in approvals. Now the stringification output is checked directly as part of the unit tests.
2024-03-01 15:09:06 +01:00
"2" == "2"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringGeneral.tests.cpp:<line number>: PASSED:
Update outdated tests for stringifying characters Previously the tests relied purely on output changes in approvals. Now the stringification output is checked directly as part of the unit tests.
2024-03-01 15:09:06 +01:00
CHECK( ::Catch::Detail::stringify( static_cast<char>(5) ) == "5" )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Update outdated tests for stringifying characters Previously the tests relied purely on output changes in approvals. Now the stringification output is checked directly as part of the unit tests.
2024-03-01 15:09:06 +01:00
"5" == "5"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Fix bug in TokenStream parser When presented with just '-' it would access the string at position [1]
2024-09-05 23:06:32 +02:00
-------------------------------------------------------------------------------
Clara::Arg does not crash on incomplete input
-------------------------------------------------------------------------------
Clara.tests.cpp:<line number>
...............................................................................
Clara.tests.cpp:<line number>: PASSED:
CHECK( name.empty() )
with expansion:
true
Clara.tests.cpp:<line number>: PASSED:
CHECK( result )
with expansion:
{?}
Clara.tests.cpp:<line number>: PASSED:
CHECK( result.type() == Catch::Clara::Detail::ResultType::Ok )
with expansion:
0 == 0
Clara.tests.cpp:<line number>: PASSED:
CHECK( parsed.type() == Catch::Clara::ParseResultType::NoMatch )
with expansion:
1 == 1
Clara.tests.cpp:<line number>: PASSED:
CHECK( parsed.remainingTokens().count() == 2 )
with expansion:
2 == 2
Clara.tests.cpp:<line number>: PASSED:
CHECK( name.empty() )
with expansion:
true
Arg::parse accepts plain Args as argument
2020-11-07 17:51:50 +01:00
-------------------------------------------------------------------------------
Clara::Arg supports single-arg parse the way Opt does
-------------------------------------------------------------------------------
Clara.tests.cpp:<line number>
...............................................................................
Clara.tests.cpp:<line number>: PASSED:
CHECK( name.empty() )
with expansion:
true
Clara.tests.cpp:<line number>: PASSED:
REQUIRE( name == "foo" )
with expansion:
"foo" == "foo"
Add support for multiply calling lambda parsers in Clara Previously a lambda parser in Clara could only be invoked once, even if it internally was ok with being invoked multiple times. With this change, a lambda parser can mark itself as `accept_many`, in which case it will be invoked multiple times if the appropriate flag was supplied multiple times by the user.
2021-10-27 18:57:56 +02:00
-------------------------------------------------------------------------------
Clara::Opt supports accept-many lambdas
Parsing fails on multiple options without accept_many
-------------------------------------------------------------------------------
Clara.tests.cpp:<line number>
...............................................................................
Clara.tests.cpp:<line number>: PASSED:
CHECK_FALSE( parse_result )
with expansion:
!{?}
-------------------------------------------------------------------------------
Clara::Opt supports accept-many lambdas
Parsing succeeds on multiple options with accept_many
-------------------------------------------------------------------------------
Clara.tests.cpp:<line number>
...............................................................................
Clara.tests.cpp:<line number>: PASSED:
CHECK( parse_result )
with expansion:
{?}
Clara.tests.cpp:<line number>: PASSED:
CHECK( res == std::vector<std::string>{ "aaa", "bbb" } )
with expansion:
{ "aaa", "bbb" } == { "aaa", "bbb" }
Add tests for ColourGuard
2022-03-24 00:09:27 +01:00
-------------------------------------------------------------------------------
ColourGuard behaviour
ColourGuard is disengaged by default
-------------------------------------------------------------------------------
ColourImpl.tests.cpp:<line number>
...............................................................................
ColourImpl.tests.cpp:<line number>: PASSED:
REQUIRE( streamWrapper.str().empty() )
with expansion:
true
-------------------------------------------------------------------------------
ColourGuard behaviour
ColourGuard is engaged by op<<
-------------------------------------------------------------------------------
ColourImpl.tests.cpp:<line number>
...............................................................................
ColourImpl.tests.cpp:<line number>: PASSED:
REQUIRE( streamWrapper.str() == "1\nUsing code: 2\n2\nUsing code: 0\n3\n" )
with expansion:
"1
Using code: 2
2
Using code: 0
3
"
==
"1
Using code: 2
2
Using code: 0
3
"
-------------------------------------------------------------------------------
ColourGuard behaviour
ColourGuard can be engaged explicitly
-------------------------------------------------------------------------------
ColourImpl.tests.cpp:<line number>
...............................................................................
ColourImpl.tests.cpp:<line number>: PASSED:
REQUIRE( streamWrapper.str() == "Using code: 2\nA\nB\nUsing code: 0\nC\n" )
with expansion:
"Using code: 2
A
B
Using code: 0
C
"
==
"Using code: 2
A
B
Using code: 0
C
"
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
-------------------------------------------------------------------------------
Combining MatchAllOfGeneric does not nest
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: PASSED:
with message:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
std::is_same< decltype( ( MatcherA() && MatcherB() ) && MatcherC() ), Catch::
Matchers::Detail:: MatchAllOfGeneric<MatcherA, MatcherB, MatcherC>>::value
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 1, ( MatcherA() && MatcherB() ) && MatcherC() )
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
with expansion:
Add Wfloat-equal to default-enabled warnings This is kinda messy, because there is no good way to signal to the compiler that some code uses direct comparison of floating point numbers intentionally, so instead we have to use diagnostic pragmas. We also have to over-suppress the test files, because Clang (and possibly GCC) still issue warnings from template instantiation even if the instantion site is under warning suppression, so the template definition has to be under warning suppression as well. Closes #2406
2022-05-14 15:37:39 +02:00
1 ( equals: (int) 1 or (string) "1" and equals: (long long) 1 and equals: (T)
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
1 )
Matchers.tests.cpp:<line number>: PASSED:
with message:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
std::is_same< decltype( MatcherA() && ( MatcherB() && MatcherC() ) ), Catch::
Matchers::Detail:: MatchAllOfGeneric<MatcherA, MatcherB, MatcherC>>::value
Fix and extend tests for composing generic matchers
2020-03-28 22:01:17 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 1, MatcherA() && ( MatcherB() && MatcherC() ) )
Fix and extend tests for composing generic matchers
2020-03-28 22:01:17 +01:00
with expansion:
Add Wfloat-equal to default-enabled warnings This is kinda messy, because there is no good way to signal to the compiler that some code uses direct comparison of floating point numbers intentionally, so instead we have to use diagnostic pragmas. We also have to over-suppress the test files, because Clang (and possibly GCC) still issue warnings from template instantiation even if the instantion site is under warning suppression, so the template definition has to be under warning suppression as well. Closes #2406
2022-05-14 15:37:39 +02:00
1 ( equals: (int) 1 or (string) "1" and equals: (long long) 1 and equals: (T)
Fix and extend tests for composing generic matchers
2020-03-28 22:01:17 +01:00
1 )
Matchers.tests.cpp:<line number>: PASSED:
with message:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
std::is_same< decltype( ( MatcherA() && MatcherB() ) && ( MatcherC() &&
MatcherD() ) ), Catch::Matchers::Detail:: MatchAllOfGeneric<MatcherA,
MatcherB, MatcherC, MatcherD>>:: value
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 1, ( MatcherA() && MatcherB() ) && ( MatcherC() && MatcherD() ) )
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
with expansion:
Add Wfloat-equal to default-enabled warnings This is kinda messy, because there is no good way to signal to the compiler that some code uses direct comparison of floating point numbers intentionally, so instead we have to use diagnostic pragmas. We also have to over-suppress the test files, because Clang (and possibly GCC) still issue warnings from template instantiation even if the instantion site is under warning suppression, so the template definition has to be under warning suppression as well. Closes #2406
2022-05-14 15:37:39 +02:00
1 ( equals: (int) 1 or (string) "1" and equals: (long long) 1 and equals: (T)
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
1 and equals: true )
-------------------------------------------------------------------------------
Combining MatchAnyOfGeneric does not nest
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: PASSED:
with message:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
std::is_same< decltype( ( MatcherA() || MatcherB() ) || MatcherC() ), Catch::
Matchers::Detail:: MatchAnyOfGeneric<MatcherA, MatcherB, MatcherC>>::value
Fix and extend tests for composing generic matchers
2020-03-28 22:01:17 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 1, ( MatcherA() || MatcherB() ) || MatcherC() )
Fix and extend tests for composing generic matchers
2020-03-28 22:01:17 +01:00
with expansion:
Add Wfloat-equal to default-enabled warnings This is kinda messy, because there is no good way to signal to the compiler that some code uses direct comparison of floating point numbers intentionally, so instead we have to use diagnostic pragmas. We also have to over-suppress the test files, because Clang (and possibly GCC) still issue warnings from template instantiation even if the instantion site is under warning suppression, so the template definition has to be under warning suppression as well. Closes #2406
2022-05-14 15:37:39 +02:00
1 ( equals: (int) 1 or (string) "1" or equals: (long long) 1 or equals: (T) 1
Fix and extend tests for composing generic matchers
2020-03-28 22:01:17 +01:00
)
Matchers.tests.cpp:<line number>: PASSED:
with message:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
std::is_same< decltype( MatcherA() || ( MatcherB() || MatcherC() ) ), Catch::
Matchers::Detail:: MatchAnyOfGeneric<MatcherA, MatcherB, MatcherC>>::value
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 1, MatcherA() || ( MatcherB() || MatcherC() ) )
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
with expansion:
Add Wfloat-equal to default-enabled warnings This is kinda messy, because there is no good way to signal to the compiler that some code uses direct comparison of floating point numbers intentionally, so instead we have to use diagnostic pragmas. We also have to over-suppress the test files, because Clang (and possibly GCC) still issue warnings from template instantiation even if the instantion site is under warning suppression, so the template definition has to be under warning suppression as well. Closes #2406
2022-05-14 15:37:39 +02:00
1 ( equals: (int) 1 or (string) "1" or equals: (long long) 1 or equals: (T) 1
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
)
Matchers.tests.cpp:<line number>: PASSED:
with message:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
std::is_same< decltype( ( MatcherA() || MatcherB() ) || ( MatcherC() ||
MatcherD() ) ), Catch::Matchers::Detail:: MatchAnyOfGeneric<MatcherA,
MatcherB, MatcherC, MatcherD>>:: value
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 1, ( MatcherA() || MatcherB() ) || ( MatcherC() || MatcherD() ) )
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
with expansion:
Add Wfloat-equal to default-enabled warnings This is kinda messy, because there is no good way to signal to the compiler that some code uses direct comparison of floating point numbers intentionally, so instead we have to use diagnostic pragmas. We also have to over-suppress the test files, because Clang (and possibly GCC) still issue warnings from template instantiation even if the instantion site is under warning suppression, so the template definition has to be under warning suppression as well. Closes #2406
2022-05-14 15:37:39 +02:00
1 ( equals: (int) 1 or (string) "1" or equals: (long long) 1 or equals: (T) 1
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
or equals: true )
-------------------------------------------------------------------------------
Combining MatchNotOfGeneric does not nest
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: PASSED:
with message:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
std::is_same< decltype( !MatcherA() ), Catch::Matchers::Detail::
MatchNotOfGeneric<MatcherA>>::value
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
Matchers.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( 0, !MatcherA() )
with expansion:
Add Wfloat-equal to default-enabled warnings This is kinda messy, because there is no good way to signal to the compiler that some code uses direct comparison of floating point numbers intentionally, so instead we have to use diagnostic pragmas. We also have to over-suppress the test files, because Clang (and possibly GCC) still issue warnings from template instantiation even if the instantion site is under warning suppression, so the template definition has to be under warning suppression as well. Closes #2406
2022-05-14 15:37:39 +02:00
0 not equals: (int) 1 or (string) "1"
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
Matchers.tests.cpp:<line number>: PASSED:
with message:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
std::is_same<decltype( !!MatcherA() ), MatcherA const&>::value
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
Matchers.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( 1, !!MatcherA() )
with expansion:
Add Wfloat-equal to default-enabled warnings This is kinda messy, because there is no good way to signal to the compiler that some code uses direct comparison of floating point numbers intentionally, so instead we have to use diagnostic pragmas. We also have to over-suppress the test files, because Clang (and possibly GCC) still issue warnings from template instantiation even if the instantion site is under warning suppression, so the template definition has to be under warning suppression as well. Closes #2406
2022-05-14 15:37:39 +02:00
1 equals: (int) 1 or (string) "1"
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
Matchers.tests.cpp:<line number>: PASSED:
with message:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
std::is_same< decltype( !!!MatcherA() ), Catch::Matchers::Detail::
MatchNotOfGeneric<MatcherA>>::value
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
Matchers.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( 0, !!!MatcherA() )
with expansion:
Add Wfloat-equal to default-enabled warnings This is kinda messy, because there is no good way to signal to the compiler that some code uses direct comparison of floating point numbers intentionally, so instead we have to use diagnostic pragmas. We also have to over-suppress the test files, because Clang (and possibly GCC) still issue warnings from template instantiation even if the instantion site is under warning suppression, so the template definition has to be under warning suppression as well. Closes #2406
2022-05-14 15:37:39 +02:00
0 not equals: (int) 1 or (string) "1"
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
Matchers.tests.cpp:<line number>: PASSED:
with message:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
std::is_same<decltype( !!!!MatcherA() ), MatcherA const&>::value
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
Matchers.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( 1, !!!!MatcherA() )
with expansion:
Add Wfloat-equal to default-enabled warnings This is kinda messy, because there is no good way to signal to the compiler that some code uses direct comparison of floating point numbers intentionally, so instead we have to use diagnostic pragmas. We also have to over-suppress the test files, because Clang (and possibly GCC) still issue warnings from template instantiation even if the instantion site is under warning suppression, so the template definition has to be under warning suppression as well. Closes #2406
2022-05-14 15:37:39 +02:00
1 equals: (int) 1 or (string) "1"
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
-------------------------------------------------------------------------------
Combining concrete matchers does not use templated matchers
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: PASSED:
with message:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
std::is_same<decltype( StartsWith( "foo" ) || ( StartsWith( "bar" ) &&
EndsWith( "bar" ) && !EndsWith( "foo" ) ) ), Catch::Matchers::Detail::
MatchAnyOf<std::string>>::value
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
-------------------------------------------------------------------------------
Combining only templated matchers
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: PASSED:
with message:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
std::is_same<decltype( MatcherA() || MatcherB() ), Catch::Matchers::Detail::
MatchAnyOfGeneric<MatcherA, MatcherB>>::value
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
Matchers.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( 1, MatcherA() || MatcherB() )
with expansion:
Add Wfloat-equal to default-enabled warnings This is kinda messy, because there is no good way to signal to the compiler that some code uses direct comparison of floating point numbers intentionally, so instead we have to use diagnostic pragmas. We also have to over-suppress the test files, because Clang (and possibly GCC) still issue warnings from template instantiation even if the instantion site is under warning suppression, so the template definition has to be under warning suppression as well. Closes #2406
2022-05-14 15:37:39 +02:00
1 ( equals: (int) 1 or (string) "1" or equals: (long long) 1 )
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
Matchers.tests.cpp:<line number>: PASSED:
with message:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
std::is_same<decltype( MatcherA() && MatcherB() ), Catch::Matchers::Detail::
MatchAllOfGeneric<MatcherA, MatcherB>>::value
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
Matchers.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( 1, MatcherA() && MatcherB() )
with expansion:
Add Wfloat-equal to default-enabled warnings This is kinda messy, because there is no good way to signal to the compiler that some code uses direct comparison of floating point numbers intentionally, so instead we have to use diagnostic pragmas. We also have to over-suppress the test files, because Clang (and possibly GCC) still issue warnings from template instantiation even if the instantion site is under warning suppression, so the template definition has to be under warning suppression as well. Closes #2406
2022-05-14 15:37:39 +02:00
1 ( equals: (int) 1 or (string) "1" and equals: (long long) 1 )
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
Matchers.tests.cpp:<line number>: PASSED:
with message:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
std::is_same< decltype( MatcherA() || !MatcherB() ), Catch::Matchers::Detail:
:MatchAnyOfGeneric< MatcherA, Catch::Matchers::Detail::MatchNotOfGeneric
<MatcherB>>>::value
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
Matchers.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( 1, MatcherA() || !MatcherB() )
with expansion:
Add Wfloat-equal to default-enabled warnings This is kinda messy, because there is no good way to signal to the compiler that some code uses direct comparison of floating point numbers intentionally, so instead we have to use diagnostic pragmas. We also have to over-suppress the test files, because Clang (and possibly GCC) still issue warnings from template instantiation even if the instantion site is under warning suppression, so the template definition has to be under warning suppression as well. Closes #2406
2022-05-14 15:37:39 +02:00
1 ( equals: (int) 1 or (string) "1" or not equals: (long long) 1 )
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
-------------------------------------------------------------------------------
Combining templated and concrete matchers
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( vec, Predicate<std::vector<int>>( []( auto const& v ) { return std::all_of( v.begin(), v.end(), []( int elem ) { return elem % 2 == 1; } ); }, "All elements are odd" ) && !EqualsRange( a ) )
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
with expansion:
{ 1, 3, 5 } ( matches predicate: "All elements are odd" and not Equals: { 5,
3, 1 } )
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( str, StartsWith( "foo" ) && EqualsRange( arr ) && EndsWith( "bar" ) )
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
with expansion:
"foobar" ( starts with: "foo" and Equals: { 'f', 'o', 'o', 'b', 'a', 'r' }
and ends with: "bar" )
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( str, StartsWith( "foo" ) && !EqualsRange( bad_arr ) && EndsWith( "bar" ) )
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
with expansion:
"foobar" ( starts with: "foo" and not Equals: { 'o', 'o', 'f', 'b', 'a', 'r'
} and ends with: "bar" )
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( str, EqualsRange( arr ) && StartsWith( "foo" ) && EndsWith( "bar" ) )
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
with expansion:
"foobar" ( Equals: { 'f', 'o', 'o', 'b', 'a', 'r' } and starts with: "foo"
and ends with: "bar" )
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( str, !EqualsRange( bad_arr ) && StartsWith( "foo" ) && EndsWith( "bar" ) )
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
with expansion:
"foobar" ( not Equals: { 'o', 'o', 'f', 'b', 'a', 'r' } and starts with:
"foo" and ends with: "bar" )
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( str, EqualsRange( bad_arr ) || ( StartsWith( "foo" ) && EndsWith( "bar" ) ) )
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
with expansion:
"foobar" ( Equals: { 'o', 'o', 'f', 'b', 'a', 'r' } or ( starts with: "foo"
and ends with: "bar" ) )
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( str, ( StartsWith( "foo" ) && EndsWith( "bar" ) ) || EqualsRange( bad_arr ) )
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
with expansion:
"foobar" ( ( starts with: "foo" and ends with: "bar" ) or Equals: { 'o', 'o',
'f', 'b', 'a', 'r' } )
-------------------------------------------------------------------------------
Combining templated matchers
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( container, EqualsRange( a ) || EqualsRange( b ) || EqualsRange( c ) )
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
with expansion:
{ 1, 2, 3 } ( Equals: { 1, 2, 3 } or Equals: { 0, 1, 2 } or Equals: { 4, 5, 6
} )
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Commas in various macros are allowed
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Tricky.tests.cpp:<line number>
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE_THROWS( std::vector<constructor_throws>{constructor_throws{}, constructor_throws{}} )
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK_THROWS( std::vector<constructor_throws>{constructor_throws{}, constructor_throws{}} )
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE_NOTHROW( std::vector<int>{1, 2, 3} == std::vector<int>{1, 2, 3} )
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK_NOTHROW( std::vector<int>{1, 2, 3} == std::vector<int>{1, 2, 3} )
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( std::vector<int>{1, 2} == std::vector<int>{1, 2} )
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
{ 1, 2 } == { 1, 2 }
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( std::vector<int>{1, 2} == std::vector<int>{1, 2} )
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
{ 1, 2 } == { 1, 2 }
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE_FALSE( std::vector<int>{1, 2} == std::vector<int>{1, 2, 3} )
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
!({ 1, 2 } == { 1, 2, 3 })
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK_FALSE( std::vector<int>{1, 2} == std::vector<int>{1, 2, 3} )
Fix bug in WithinAbs::match() and add tests for it
2018-03-19 20:36:07 +01:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
!({ 1, 2 } == { 1, 2, 3 })
Fix bug in WithinAbs::match() and add tests for it
2018-03-19 20:36:07 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK_NOFAIL( std::vector<int>{1, 2} == std::vector<int>{1, 2} )
Fix bug in WithinAbs::match() and add tests for it
2018-03-19 20:36:07 +01:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
{ 1, 2 } == { 1, 2 }
Fix bug in WithinAbs::match() and add tests for it
2018-03-19 20:36:07 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECKED_IF( std::vector<int>{1, 2} == std::vector<int>{1, 2} )
Fix bug in WithinAbs::match() and add tests for it
2018-03-19 20:36:07 +01:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
{ 1, 2 } == { 1, 2 }
Fix bug in WithinAbs::match() and add tests for it
2018-03-19 20:36:07 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( true )
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECKED_ELSE( std::vector<int>{1, 2} == std::vector<int>{1, 2} )
Fix bug in WithinAbs::match() and add tests for it
2018-03-19 20:36:07 +01:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
{ 1, 2 } == { 1, 2 }
Fix bug in WithinAbs::match() and add tests for it
2018-03-19 20:36:07 +01:00
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Comparing function pointers
-------------------------------------------------------------------------------
Tricky.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( a )
with expansion:
0x<hex digits>
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( a == &foo )
with expansion:
0x<hex digits> == 0x<hex digits>
Introduce Catch's own RNG based on the PCG family of RNGs In the future, we will also want to introduce our own `uniform_int_distribution` and `uniform_real_distribution` to get repeatable test runs across different platforms.
2019-10-06 21:47:54 +02:00
-------------------------------------------------------------------------------
Comparison ops
-------------------------------------------------------------------------------
RandomNumberGeneration.tests.cpp:<line number>
...............................................................................
RandomNumberGeneration.tests.cpp:<line number>: PASSED:
REQUIRE( SimplePcg32{} == SimplePcg32{} )
with expansion:
{?} == {?}
RandomNumberGeneration.tests.cpp:<line number>: PASSED:
REQUIRE( SimplePcg32{ 0 } != SimplePcg32{} )
with expansion:
{?} != {?}
RandomNumberGeneration.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( SimplePcg32{ 1 } == SimplePcg32{ 2 } )
with expansion:
!({?} == {?})
RandomNumberGeneration.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( SimplePcg32{ 1 } != SimplePcg32{ 1 } )
with expansion:
!({?} != {?})
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Comparison with explicitly convertible types
-------------------------------------------------------------------------------
Approx.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( td == Approx(10.0) )
with expansion:
StrongDoubleTypedef(10) == Approx( 10.0 )
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( Approx(10.0) == td )
with expansion:
Approx( 10.0 ) == StrongDoubleTypedef(10)
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( td != Approx(11.0) )
with expansion:
StrongDoubleTypedef(10) != Approx( 11.0 )
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( Approx(11.0) != td )
with expansion:
Approx( 11.0 ) != StrongDoubleTypedef(10)
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( td <= Approx(10.0) )
with expansion:
StrongDoubleTypedef(10) <= Approx( 10.0 )
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( td <= Approx(11.0) )
with expansion:
StrongDoubleTypedef(10) <= Approx( 11.0 )
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( Approx(10.0) <= td )
with expansion:
Approx( 10.0 ) <= StrongDoubleTypedef(10)
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( Approx(9.0) <= td )
with expansion:
Approx( 9.0 ) <= StrongDoubleTypedef(10)
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( td >= Approx(9.0) )
with expansion:
StrongDoubleTypedef(10) >= Approx( 9.0 )
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( td >= Approx(td) )
with expansion:
StrongDoubleTypedef(10) >= Approx( 10.0 )
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( Approx(td) >= td )
with expansion:
Approx( 10.0 ) >= StrongDoubleTypedef(10)
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( Approx(11.0) >= td )
with expansion:
Approx( 11.0 ) >= StrongDoubleTypedef(10)
-------------------------------------------------------------------------------
Comparisons between ints where one side is computed
-------------------------------------------------------------------------------
Condition.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( 54 == 6*9 )
with expansion:
54 == 54
-------------------------------------------------------------------------------
Comparisons between unsigned ints and negative signed ints match c++ standard
behaviour
-------------------------------------------------------------------------------
Condition.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( ( -1 > 2u ) )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( -1 > 2u )
with expansion:
-1 > 2
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( ( 2u < -1 ) )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( 2u < -1 )
with expansion:
2 < -1
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( ( minInt > 2u ) )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
CHECK( minInt > 2u )
with expansion:
-2147483648 > 2
-------------------------------------------------------------------------------
Comparisons with int literals don't warn when mixing signed/ unsigned
-------------------------------------------------------------------------------
Condition.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( i == 1 )
with expansion:
1 == 1
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( ui == 2 )
with expansion:
2 == 2
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( l == 3 )
with expansion:
3 == 3
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( ul == 4 )
with expansion:
4 == 4
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( c == 5 )
with expansion:
5 == 5
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( uc == 6 )
with expansion:
6 == 6
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( 1 == i )
with expansion:
1 == 1
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( 2 == ui )
with expansion:
2 == 2
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( 3 == l )
with expansion:
3 == 3
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( 4 == ul )
with expansion:
4 == 4
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( 5 == c )
with expansion:
5 == 5
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( 6 == uc )
with expansion:
6 == 6
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( (std::numeric_limits<uint32_t>::max)() > ul )
with expansion:
4294967295 (0x<hex digits>) > 4
Add test for shortcircuiting behaviour of generic matcher combinators
2020-07-26 21:22:13 +02:00
-------------------------------------------------------------------------------
Composed generic matchers shortcircuit
MatchAllOf
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: PASSED:
CHECK_FALSE( matcher.match( 1 ) )
with expansion:
!false
Matchers.tests.cpp:<line number>: PASSED:
REQUIRE( first.matchCalled )
with expansion:
true
Matchers.tests.cpp:<line number>: PASSED:
REQUIRE( !second.matchCalled )
with expansion:
true
-------------------------------------------------------------------------------
Composed generic matchers shortcircuit
MatchAnyOf
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK( matcher.match( 1 ) )
Add test for shortcircuiting behaviour of generic matcher combinators
2020-07-26 21:22:13 +02:00
with expansion:
true
Matchers.tests.cpp:<line number>: PASSED:
REQUIRE( first.matchCalled )
with expansion:
true
Matchers.tests.cpp:<line number>: PASSED:
REQUIRE( !second.matchCalled )
with expansion:
true
Add explicit test for shortcircuiting behaviour of combined matchers
2020-06-14 21:48:08 +02:00
-------------------------------------------------------------------------------
Composed matchers shortcircuit
Refactor how shortcircuiting of old style matchers is tested
2020-07-26 21:31:29 +02:00
MatchAllOf
Add explicit test for shortcircuiting behaviour of combined matchers
2020-06-14 21:48:08 +02:00
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: PASSED:
Refactor how shortcircuiting of old style matchers is tested
2020-07-26 21:31:29 +02:00
CHECK_FALSE( matcher.match( 1 ) )
Add explicit test for shortcircuiting behaviour of combined matchers
2020-06-14 21:48:08 +02:00
with expansion:
Refactor how shortcircuiting of old style matchers is tested
2020-07-26 21:31:29 +02:00
!false
Add explicit test for shortcircuiting behaviour of combined matchers
2020-06-14 21:48:08 +02:00
Matchers.tests.cpp:<line number>: PASSED:
REQUIRE( first.matchCalled )
with expansion:
true
Matchers.tests.cpp:<line number>: PASSED:
REQUIRE( !second.matchCalled )
with expansion:
true
-------------------------------------------------------------------------------
Composed matchers shortcircuit
Refactor how shortcircuiting of old style matchers is tested
2020-07-26 21:31:29 +02:00
MatchAnyOf
Add explicit test for shortcircuiting behaviour of combined matchers
2020-06-14 21:48:08 +02:00
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: PASSED:
Refactor how shortcircuiting of old style matchers is tested
2020-07-26 21:31:29 +02:00
CHECK( matcher.match( 1 ) )
Add explicit test for shortcircuiting behaviour of combined matchers
2020-06-14 21:48:08 +02:00
with expansion:
Refactor how shortcircuiting of old style matchers is tested
2020-07-26 21:31:29 +02:00
true
Add explicit test for shortcircuiting behaviour of combined matchers
2020-06-14 21:48:08 +02:00
Matchers.tests.cpp:<line number>: PASSED:
REQUIRE( first.matchCalled )
with expansion:
true
Matchers.tests.cpp:<line number>: PASSED:
REQUIRE( !second.matchCalled )
with expansion:
true
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Contains string matcher
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: FAILED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
CHECK_THAT( testStringForMatching(), ContainsSubstring( "not there", Catch::CaseSensitive::No ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
"this string contains 'abc' as a substring" contains: "not there" (case
insensitive)
Matchers.tests.cpp:<line number>: FAILED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
CHECK_THAT( testStringForMatching(), ContainsSubstring( "STRING" ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
"this string contains 'abc' as a substring" contains: "STRING"
Add a generator that takes an iterator pair
2019-10-06 13:49:50 +02:00
-------------------------------------------------------------------------------
Copy and then generate a range
Add a from_range(Container) overload to the generator helpers
2019-10-09 14:51:24 +02:00
from var and iterators
Add a generator that takes an iterator pair
2019-10-06 13:49:50 +02:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( elem % 2 == 1 )
with expansion:
1 == 1
-------------------------------------------------------------------------------
Copy and then generate a range
Add a from_range(Container) overload to the generator helpers
2019-10-09 14:51:24 +02:00
from var and iterators
Add a generator that takes an iterator pair
2019-10-06 13:49:50 +02:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( elem % 2 == 1 )
with expansion:
1 == 1
-------------------------------------------------------------------------------
Copy and then generate a range
Add a from_range(Container) overload to the generator helpers
2019-10-09 14:51:24 +02:00
from var and iterators
Add a generator that takes an iterator pair
2019-10-06 13:49:50 +02:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( elem % 2 == 1 )
with expansion:
1 == 1
-------------------------------------------------------------------------------
Copy and then generate a range
Add a from_range(Container) overload to the generator helpers
2019-10-09 14:51:24 +02:00
from var and iterators
Add a generator that takes an iterator pair
2019-10-06 13:49:50 +02:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( elem % 2 == 1 )
with expansion:
1 == 1
-------------------------------------------------------------------------------
Copy and then generate a range
Add a from_range(Container) overload to the generator helpers
2019-10-09 14:51:24 +02:00
from var and iterators
Add a generator that takes an iterator pair
2019-10-06 13:49:50 +02:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( elem % 2 == 1 )
with expansion:
1 == 1
-------------------------------------------------------------------------------
Copy and then generate a range
Add a from_range(Container) overload to the generator helpers
2019-10-09 14:51:24 +02:00
from var and iterators
Add a generator that takes an iterator pair
2019-10-06 13:49:50 +02:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( elem % 2 == 1 )
with expansion:
1 == 1
Add a from_range(Container) overload to the generator helpers
2019-10-09 14:51:24 +02:00
-------------------------------------------------------------------------------
Copy and then generate a range
From a temporary container
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( elem % 2 == 1 )
with expansion:
1 == 1
-------------------------------------------------------------------------------
Copy and then generate a range
From a temporary container
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( elem % 2 == 1 )
with expansion:
1 == 1
-------------------------------------------------------------------------------
Copy and then generate a range
From a temporary container
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( elem % 2 == 1 )
with expansion:
1 == 1
-------------------------------------------------------------------------------
Copy and then generate a range
From a temporary container
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( elem % 2 == 1 )
with expansion:
1 == 1
-------------------------------------------------------------------------------
Copy and then generate a range
From a temporary container
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( elem % 2 == 1 )
with expansion:
1 == 1
-------------------------------------------------------------------------------
Copy and then generate a range
From a temporary container
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( elem % 2 == 1 )
with expansion:
1 == 1
-------------------------------------------------------------------------------
Copy and then generate a range
Final validation
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( call_count == 1 )
with expansion:
1 == 1
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( make_data().size() == test_count )
with expansion:
6 == 6
Add IStream::isStdOut
2022-02-21 23:48:15 +01:00
-------------------------------------------------------------------------------
Cout stream properly declares it writes to stdout
-------------------------------------------------------------------------------
Stream.tests.cpp:<line number>
...............................................................................
Stream.tests.cpp:<line number>: PASSED:
Rename isStdout => isConsole and add doccomment
2022-03-21 00:22:54 +01:00
REQUIRE( Catch::makeStream( "-" )->isConsole() )
Add IStream::isStdOut
2022-02-21 23:48:15 +01:00
with expansion:
true
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Custom exceptions can be translated when testing for nothrow
-------------------------------------------------------------------------------
Exception.tests.cpp:<line number>
...............................................................................
Exception.tests.cpp:<line number>: FAILED:
REQUIRE_NOTHROW( throwCustom() )
due to unexpected exception with message:
custom exception - not std
-------------------------------------------------------------------------------
Custom exceptions can be translated when testing for throwing as something else
-------------------------------------------------------------------------------
Exception.tests.cpp:<line number>
...............................................................................
Exception.tests.cpp:<line number>: FAILED:
REQUIRE_THROWS_AS( throwCustom(), std::exception )
due to unexpected exception with message:
custom exception - not std
-------------------------------------------------------------------------------
Custom std-exceptions can be custom translated
-------------------------------------------------------------------------------
Exception.tests.cpp:<line number>
...............................................................................
Exception.tests.cpp:<line number>: FAILED:
due to unexpected exception with message:
custom std exception
-------------------------------------------------------------------------------
Default scale is invisible to comparison
-------------------------------------------------------------------------------
Approx.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( 101.000001 != Approx(100).epsilon(0.01) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
101.00000099999999748 != Approx( 100.0 )
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( std::pow(10, -5) != Approx(std::pow(10, -7)) )
with expansion:
0.00001 != Approx( 0.0000001 )
Rebased approvals for stringified enum tests
2019-04-26 12:30:19 +02:00
-------------------------------------------------------------------------------
Directly creating an EnumInfo
-------------------------------------------------------------------------------
ToString.tests.cpp:<line number>
...............................................................................
ToString.tests.cpp:<line number>: PASSED:
CHECK( enumInfo->lookup(0) == "Value1" )
with expansion:
Value1 == "Value1"
ToString.tests.cpp:<line number>: PASSED:
CHECK( enumInfo->lookup(1) == "Value2" )
with expansion:
Value2 == "Value2"
ToString.tests.cpp:<line number>: PASSED:
CHECK( enumInfo->lookup(3) == "{** unexpected enum value **}" )
with expansion:
{** unexpected enum value **}
==
"{** unexpected enum value **}"
Test & document SKIP in generator constructor Closes #1593
2023-05-31 15:12:23 +02:00
-------------------------------------------------------------------------------
Empty generators can SKIP in constructor
-------------------------------------------------------------------------------
Skip.tests.cpp:<line number>
...............................................................................
Skip.tests.cpp:<line number>: SKIPPED:
explicitly with message:
This generator is empty
Add IStream::isStdOut
2022-02-21 23:48:15 +01:00
-------------------------------------------------------------------------------
Empty stream name opens cout stream
-------------------------------------------------------------------------------
Stream.tests.cpp:<line number>
...............................................................................
Stream.tests.cpp:<line number>: PASSED:
Rename isStdout => isConsole and add doccomment
2022-03-21 00:22:54 +01:00
REQUIRE( Catch::makeStream( "" )->isConsole() )
Add IStream::isStdOut
2022-02-21 23:48:15 +01:00
with expansion:
true
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
EndsWith string matcher
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( testStringForMatching(), EndsWith( "Substring" ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
"this string contains 'abc' as a substring" ends with: "Substring"
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( testStringForMatching(), EndsWith( "this", Catch::CaseSensitive::No ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
"this string contains 'abc' as a substring" ends with: "this" (case
insensitive)
Rebased approvals for stringified enum tests
2019-04-26 12:30:19 +02:00
-------------------------------------------------------------------------------
Enums can quickly have stringification enabled using REGISTER_ENUM
-------------------------------------------------------------------------------
EnumToString.tests.cpp:<line number>
...............................................................................
EnumToString.tests.cpp:<line number>: PASSED:
REQUIRE( stringify( EnumClass3::Value1 ) == "Value1" )
with expansion:
"Value1" == "Value1"
EnumToString.tests.cpp:<line number>: PASSED:
REQUIRE( stringify( EnumClass3::Value2 ) == "Value2" )
with expansion:
"Value2" == "Value2"
EnumToString.tests.cpp:<line number>: PASSED:
REQUIRE( stringify( EnumClass3::Value3 ) == "Value3" )
with expansion:
"Value3" == "Value3"
EnumToString.tests.cpp:<line number>: PASSED:
REQUIRE( stringify( EnumClass3::Value4 ) == "{** unexpected enum value **}" )
with expansion:
"{** unexpected enum value **}"
==
"{** unexpected enum value **}"
EnumToString.tests.cpp:<line number>: PASSED:
REQUIRE( stringify( ec3 ) == "Value2" )
with expansion:
"Value2" == "Value2"
-------------------------------------------------------------------------------
Enums in namespaces can quickly have stringification enabled using
REGISTER_ENUM
-------------------------------------------------------------------------------
EnumToString.tests.cpp:<line number>
...............................................................................
EnumToString.tests.cpp:<line number>: PASSED:
REQUIRE( stringify( Bikeshed::Colours::Red ) == "Red" )
with expansion:
"Red" == "Red"
EnumToString.tests.cpp:<line number>: PASSED:
REQUIRE( stringify( Bikeshed::Colours::Blue ) == "Blue" )
with expansion:
"Blue" == "Blue"
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Epsilon only applies to Approx's value
-------------------------------------------------------------------------------
Approx.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( 101.01 != Approx(100).epsilon(0.01) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
101.01000000000000512 != Approx( 100.0 )
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Equality checks that should fail
-------------------------------------------------------------------------------
Condition.tests.cpp:<line number>
...............................................................................
Condition.tests.cpp:<line number>: FAILED:
CHECK( data.int_seven == 6 )
with expansion:
7 == 6
Condition.tests.cpp:<line number>: FAILED:
CHECK( data.int_seven == 8 )
with expansion:
7 == 8
Condition.tests.cpp:<line number>: FAILED:
CHECK( data.int_seven == 0 )
with expansion:
7 == 0
Condition.tests.cpp:<line number>: FAILED:
CHECK( data.float_nine_point_one == Approx( 9.11f ) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
9.100000381f
==
Approx( 9.10999965667724609 )
Update baselines
2018-08-19 23:22:36 +02:00
Condition.tests.cpp:<line number>: FAILED:
CHECK( data.float_nine_point_one == Approx( 9.0f ) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
9.100000381f == Approx( 9.0 )
Update baselines
2018-08-19 23:22:36 +02:00
Condition.tests.cpp:<line number>: FAILED:
CHECK( data.float_nine_point_one == Approx( 1 ) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
9.100000381f == Approx( 1.0 )
Update baselines
2018-08-19 23:22:36 +02:00
Condition.tests.cpp:<line number>: FAILED:
CHECK( data.float_nine_point_one == Approx( 0 ) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
9.100000381f == Approx( 0.0 )
Update baselines
2018-08-19 23:22:36 +02:00
Condition.tests.cpp:<line number>: FAILED:
CHECK( data.double_pi == Approx( 3.1415 ) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
3.14159265350000005
==
Approx( 3.14150000000000018 )
Update baselines
2018-08-19 23:22:36 +02:00
Condition.tests.cpp:<line number>: FAILED:
CHECK( data.str_hello == "goodbye" )
with expansion:
"hello" == "goodbye"
Condition.tests.cpp:<line number>: FAILED:
CHECK( data.str_hello == "hell" )
with expansion:
"hello" == "hell"
Condition.tests.cpp:<line number>: FAILED:
CHECK( data.str_hello == "hello1" )
with expansion:
"hello" == "hello1"
Condition.tests.cpp:<line number>: FAILED:
CHECK( data.str_hello.size() == 6 )
with expansion:
5 == 6
Condition.tests.cpp:<line number>: FAILED:
CHECK( x == Approx( 1.301 ) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.30000000000000027
==
Approx( 1.30099999999999993 )
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Equality checks that should succeed
-------------------------------------------------------------------------------
Condition.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( data.int_seven == 7 )
with expansion:
7 == 7
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( data.float_nine_point_one == Approx( 9.1f ) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
9.100000381f
==
Approx( 9.10000038146972656 )
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( data.double_pi == Approx( 3.1415926535 ) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
3.14159265350000005
==
Approx( 3.14159265350000005 )
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( data.str_hello == "hello" )
with expansion:
"hello" == "hello"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( "hello" == data.str_hello )
with expansion:
"hello" == "hello"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( data.str_hello.size() == 5 )
with expansion:
5 == 5
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( x == Approx( 1.3 ) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.30000000000000027
==
Approx( 1.30000000000000004 )
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Equals
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( testStringForMatching(), Equals( "this string contains 'abc' as a substring" ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
"this string contains 'abc' as a substring" equals: "this string contains
'abc' as a substring"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( testStringForMatching(), Equals( "this string contains 'ABC' as a substring", Catch::CaseSensitive::No ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
"this string contains 'abc' as a substring" equals: "this string contains
'abc' as a substring" (case insensitive)
-------------------------------------------------------------------------------
Equals string matcher
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( testStringForMatching(), Equals( "this string contains 'ABC' as a substring" ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
"this string contains 'abc' as a substring" equals: "this string contains
'ABC' as a substring"
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( testStringForMatching(), Equals( "something else", Catch::CaseSensitive::No ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
"this string contains 'abc' as a substring" equals: "something else" (case
insensitive)
-------------------------------------------------------------------------------
Exception as a value (e.g. in REQUIRE_THROWS_MATCHES) can be stringified
-------------------------------------------------------------------------------
ToStringGeneral.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringGeneral.tests.cpp:<line number>: PASSED:
Fix typos identified by codespell. Self test baselines also modified accordingly, due to one typo found in a string in test code.
2019-04-08 23:30:28 +02:00
REQUIRE( ::Catch::Detail::stringify(WhatException{}) == "This exception has overridden what() method" )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Fix typos identified by codespell. Self test baselines also modified accordingly, due to one typo found in a string in test code.
2019-04-08 23:30:28 +02:00
"This exception has overridden what() method"
Update baselines
2018-08-19 23:22:36 +02:00
==
Fix typos identified by codespell. Self test baselines also modified accordingly, due to one typo found in a string in test code.
2019-04-08 23:30:28 +02:00
"This exception has overridden what() method"
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringGeneral.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( ::Catch::Detail::stringify(OperatorException{}) == "OperatorException" )
with expansion:
"OperatorException" == "OperatorException"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringGeneral.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( ::Catch::Detail::stringify(StringMakerException{}) == "StringMakerException" )
with expansion:
"StringMakerException"
==
"StringMakerException"
-------------------------------------------------------------------------------
Exception matchers that fail
No exception
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THROWS_MATCHES( doesNotThrow(), SpecialException, ExceptionMatcher{ 1 } )
Update baselines
2018-08-19 23:22:36 +02:00
because no exception was thrown where one was expected:
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THROWS_MATCHES( doesNotThrow(), SpecialException, ExceptionMatcher{ 1 } )
Update baselines
2018-08-19 23:22:36 +02:00
because no exception was thrown where one was expected:
-------------------------------------------------------------------------------
Exception matchers that fail
Type mismatch
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THROWS_MATCHES( throwsAsInt( 1 ), SpecialException, ExceptionMatcher{ 1 } )
Update baselines
2018-08-19 23:22:36 +02:00
due to unexpected exception with message:
Unknown exception
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THROWS_MATCHES( throwsAsInt( 1 ), SpecialException, ExceptionMatcher{ 1 } )
Update baselines
2018-08-19 23:22:36 +02:00
due to unexpected exception with message:
Unknown exception
-------------------------------------------------------------------------------
Exception matchers that fail
Contents are wrong
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THROWS_MATCHES( throwsSpecialException( 3 ), SpecialException, ExceptionMatcher{ 1 } )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
SpecialException::what special exception has value of 1
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THROWS_MATCHES( throwsSpecialException( 4 ), SpecialException, ExceptionMatcher{ 1 } )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
SpecialException::what special exception has value of 1
-------------------------------------------------------------------------------
Exception matchers that succeed
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THROWS_MATCHES( throwsSpecialException( 1 ), SpecialException, ExceptionMatcher{ 1 } )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
SpecialException::what special exception has value of 1
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THROWS_MATCHES( throwsSpecialException( 2 ), SpecialException, ExceptionMatcher{ 2 } )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
SpecialException::what special exception has value of 2
Add MessageMatches matcher for exception (#2570)
2022-12-12 00:40:47 +01:00
-------------------------------------------------------------------------------
Exception message can be matched
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: PASSED:
REQUIRE_THROWS_MATCHES( throwsDerivedException(), DerivedException, MessageMatches( StartsWith( "Derived" ) ) )
with expansion:
DerivedException::what matches "starts with: "Derived""
Matchers.tests.cpp:<line number>: PASSED:
REQUIRE_THROWS_MATCHES( throwsDerivedException(), DerivedException, MessageMatches( EndsWith( "::what" ) ) )
with expansion:
DerivedException::what matches "ends with: "::what""
Matchers.tests.cpp:<line number>: PASSED:
REQUIRE_THROWS_MATCHES( throwsDerivedException(), DerivedException, MessageMatches( !StartsWith( "::what" ) ) )
with expansion:
DerivedException::what matches "not starts with: "::what""
Matchers.tests.cpp:<line number>: PASSED:
REQUIRE_THROWS_MATCHES( throwsSpecialException( 2 ), SpecialException, MessageMatches( StartsWith( "Special" ) ) )
with expansion:
SpecialException::what matches "starts with: "Special""
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Exception messages can be tested for
exact match
-------------------------------------------------------------------------------
Exception.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Exception.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE_THROWS_WITH( thisThrows(), "expected exception" )
with expansion:
"expected exception" equals: "expected exception"
-------------------------------------------------------------------------------
Exception messages can be tested for
different case
-------------------------------------------------------------------------------
Exception.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Exception.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE_THROWS_WITH( thisThrows(), Equals( "expecteD Exception", Catch::CaseSensitive::No ) )
with expansion:
"expected exception" equals: "expected exception" (case insensitive)
-------------------------------------------------------------------------------
Exception messages can be tested for
wildcarded
-------------------------------------------------------------------------------
Exception.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Exception.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE_THROWS_WITH( thisThrows(), StartsWith( "expected" ) )
with expansion:
"expected exception" starts with: "expected"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Exception.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE_THROWS_WITH( thisThrows(), EndsWith( "exception" ) )
with expansion:
"expected exception" ends with: "exception"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Exception.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THROWS_WITH( thisThrows(), ContainsSubstring( "except" ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
"expected exception" contains: "except"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Exception.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THROWS_WITH( thisThrows(), ContainsSubstring( "exCept", Catch::CaseSensitive::No ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
"expected exception" contains: "except" (case insensitive)
Add a matcher that checks exception's message Only works for exceptions that publicly derive from `std::exception` and the matching is done exactly, including case and whitespace. Closes #1649 Closes #1728 # Please enter the commit message for your changes. Lines starting # with '#' will be ignored, and an empty message aborts the commit. # On branch master # Your branch is up-to-date with 'origin/master'. # # Changes to be committed: # modified: ../docs/matchers.md # modified: ../include/internal/catch_capture_matchers.h # modified: ../projects/CMakeLists.txt # modified: ../projects/SelfTest/Baselines/compact.sw.approved.txt # modified: ../projects/SelfTest/Baselines/console.std.approved.txt # modified: ../projects/SelfTest/Baselines/console.sw.approved.txt # modified: ../projects/SelfTest/Baselines/junit.sw.approved.txt # modified: ../projects/SelfTest/Baselines/xml.sw.approved.txt # modified: ../projects/SelfTest/UsageTests/Matchers.tests.cpp # # Untracked files: # ./ # ../clang-full/ # ../clang-test/ # ../clang10-build/ # ../coverage-build/ # ../gcc-build/ # ../gcc-full/ # ../include/internal/catch_matchers_exception.cpp # ../include/internal/catch_matchers_exception.hpp # ../misc-build/ # ../msvc-sln/ # ../notes.txt # ../test-install/ #
2019-10-13 20:37:07 +02:00
-------------------------------------------------------------------------------
Exceptions matchers
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THROWS_MATCHES( throwsDerivedException(), DerivedException, Message( "DerivedException::what" ) )
Add a matcher that checks exception's message Only works for exceptions that publicly derive from `std::exception` and the matching is done exactly, including case and whitespace. Closes #1649 Closes #1728 # Please enter the commit message for your changes. Lines starting # with '#' will be ignored, and an empty message aborts the commit. # On branch master # Your branch is up-to-date with 'origin/master'. # # Changes to be committed: # modified: ../docs/matchers.md # modified: ../include/internal/catch_capture_matchers.h # modified: ../projects/CMakeLists.txt # modified: ../projects/SelfTest/Baselines/compact.sw.approved.txt # modified: ../projects/SelfTest/Baselines/console.std.approved.txt # modified: ../projects/SelfTest/Baselines/console.sw.approved.txt # modified: ../projects/SelfTest/Baselines/junit.sw.approved.txt # modified: ../projects/SelfTest/Baselines/xml.sw.approved.txt # modified: ../projects/SelfTest/UsageTests/Matchers.tests.cpp # # Untracked files: # ./ # ../clang-full/ # ../clang-test/ # ../clang10-build/ # ../coverage-build/ # ../gcc-build/ # ../gcc-full/ # ../include/internal/catch_matchers_exception.cpp # ../include/internal/catch_matchers_exception.hpp # ../misc-build/ # ../msvc-sln/ # ../notes.txt # ../test-install/ #
2019-10-13 20:37:07 +02:00
with expansion:
Fix baselines
2019-10-13 21:26:51 +02:00
DerivedException::what exception message matches "DerivedException::what"
Add a matcher that checks exception's message Only works for exceptions that publicly derive from `std::exception` and the matching is done exactly, including case and whitespace. Closes #1649 Closes #1728 # Please enter the commit message for your changes. Lines starting # with '#' will be ignored, and an empty message aborts the commit. # On branch master # Your branch is up-to-date with 'origin/master'. # # Changes to be committed: # modified: ../docs/matchers.md # modified: ../include/internal/catch_capture_matchers.h # modified: ../projects/CMakeLists.txt # modified: ../projects/SelfTest/Baselines/compact.sw.approved.txt # modified: ../projects/SelfTest/Baselines/console.std.approved.txt # modified: ../projects/SelfTest/Baselines/console.sw.approved.txt # modified: ../projects/SelfTest/Baselines/junit.sw.approved.txt # modified: ../projects/SelfTest/Baselines/xml.sw.approved.txt # modified: ../projects/SelfTest/UsageTests/Matchers.tests.cpp # # Untracked files: # ./ # ../clang-full/ # ../clang-test/ # ../clang10-build/ # ../coverage-build/ # ../gcc-build/ # ../gcc-full/ # ../include/internal/catch_matchers_exception.cpp # ../include/internal/catch_matchers_exception.hpp # ../misc-build/ # ../msvc-sln/ # ../notes.txt # ../test-install/ #
2019-10-13 20:37:07 +02:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THROWS_MATCHES( throwsDerivedException(), DerivedException, !Message( "derivedexception::what" ) )
Add a matcher that checks exception's message Only works for exceptions that publicly derive from `std::exception` and the matching is done exactly, including case and whitespace. Closes #1649 Closes #1728 # Please enter the commit message for your changes. Lines starting # with '#' will be ignored, and an empty message aborts the commit. # On branch master # Your branch is up-to-date with 'origin/master'. # # Changes to be committed: # modified: ../docs/matchers.md # modified: ../include/internal/catch_capture_matchers.h # modified: ../projects/CMakeLists.txt # modified: ../projects/SelfTest/Baselines/compact.sw.approved.txt # modified: ../projects/SelfTest/Baselines/console.std.approved.txt # modified: ../projects/SelfTest/Baselines/console.sw.approved.txt # modified: ../projects/SelfTest/Baselines/junit.sw.approved.txt # modified: ../projects/SelfTest/Baselines/xml.sw.approved.txt # modified: ../projects/SelfTest/UsageTests/Matchers.tests.cpp # # Untracked files: # ./ # ../clang-full/ # ../clang-test/ # ../clang10-build/ # ../coverage-build/ # ../gcc-build/ # ../gcc-full/ # ../include/internal/catch_matchers_exception.cpp # ../include/internal/catch_matchers_exception.hpp # ../misc-build/ # ../msvc-sln/ # ../notes.txt # ../test-install/ #
2019-10-13 20:37:07 +02:00
with expansion:
Fix baselines
2019-10-13 21:26:51 +02:00
DerivedException::what not exception message matches "derivedexception::what"
Add a matcher that checks exception's message Only works for exceptions that publicly derive from `std::exception` and the matching is done exactly, including case and whitespace. Closes #1649 Closes #1728 # Please enter the commit message for your changes. Lines starting # with '#' will be ignored, and an empty message aborts the commit. # On branch master # Your branch is up-to-date with 'origin/master'. # # Changes to be committed: # modified: ../docs/matchers.md # modified: ../include/internal/catch_capture_matchers.h # modified: ../projects/CMakeLists.txt # modified: ../projects/SelfTest/Baselines/compact.sw.approved.txt # modified: ../projects/SelfTest/Baselines/console.std.approved.txt # modified: ../projects/SelfTest/Baselines/console.sw.approved.txt # modified: ../projects/SelfTest/Baselines/junit.sw.approved.txt # modified: ../projects/SelfTest/Baselines/xml.sw.approved.txt # modified: ../projects/SelfTest/UsageTests/Matchers.tests.cpp # # Untracked files: # ./ # ../clang-full/ # ../clang-test/ # ../clang10-build/ # ../coverage-build/ # ../gcc-build/ # ../gcc-full/ # ../include/internal/catch_matchers_exception.cpp # ../include/internal/catch_matchers_exception.hpp # ../misc-build/ # ../msvc-sln/ # ../notes.txt # ../test-install/ #
2019-10-13 20:37:07 +02:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THROWS_MATCHES( throwsSpecialException( 2 ), SpecialException, !Message( "DerivedException::what" ) )
Add a matcher that checks exception's message Only works for exceptions that publicly derive from `std::exception` and the matching is done exactly, including case and whitespace. Closes #1649 Closes #1728 # Please enter the commit message for your changes. Lines starting # with '#' will be ignored, and an empty message aborts the commit. # On branch master # Your branch is up-to-date with 'origin/master'. # # Changes to be committed: # modified: ../docs/matchers.md # modified: ../include/internal/catch_capture_matchers.h # modified: ../projects/CMakeLists.txt # modified: ../projects/SelfTest/Baselines/compact.sw.approved.txt # modified: ../projects/SelfTest/Baselines/console.std.approved.txt # modified: ../projects/SelfTest/Baselines/console.sw.approved.txt # modified: ../projects/SelfTest/Baselines/junit.sw.approved.txt # modified: ../projects/SelfTest/Baselines/xml.sw.approved.txt # modified: ../projects/SelfTest/UsageTests/Matchers.tests.cpp # # Untracked files: # ./ # ../clang-full/ # ../clang-test/ # ../clang10-build/ # ../coverage-build/ # ../gcc-build/ # ../gcc-full/ # ../include/internal/catch_matchers_exception.cpp # ../include/internal/catch_matchers_exception.hpp # ../misc-build/ # ../msvc-sln/ # ../notes.txt # ../test-install/ #
2019-10-13 20:37:07 +02:00
with expansion:
Fix baselines
2019-10-13 21:26:51 +02:00
SpecialException::what not exception message matches "DerivedException::what"
Add a matcher that checks exception's message Only works for exceptions that publicly derive from `std::exception` and the matching is done exactly, including case and whitespace. Closes #1649 Closes #1728 # Please enter the commit message for your changes. Lines starting # with '#' will be ignored, and an empty message aborts the commit. # On branch master # Your branch is up-to-date with 'origin/master'. # # Changes to be committed: # modified: ../docs/matchers.md # modified: ../include/internal/catch_capture_matchers.h # modified: ../projects/CMakeLists.txt # modified: ../projects/SelfTest/Baselines/compact.sw.approved.txt # modified: ../projects/SelfTest/Baselines/console.std.approved.txt # modified: ../projects/SelfTest/Baselines/console.sw.approved.txt # modified: ../projects/SelfTest/Baselines/junit.sw.approved.txt # modified: ../projects/SelfTest/Baselines/xml.sw.approved.txt # modified: ../projects/SelfTest/UsageTests/Matchers.tests.cpp # # Untracked files: # ./ # ../clang-full/ # ../clang-test/ # ../clang10-build/ # ../coverage-build/ # ../gcc-build/ # ../gcc-full/ # ../include/internal/catch_matchers_exception.cpp # ../include/internal/catch_matchers_exception.hpp # ../misc-build/ # ../msvc-sln/ # ../notes.txt # ../test-install/ #
2019-10-13 20:37:07 +02:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THROWS_MATCHES( throwsSpecialException( 2 ), SpecialException, Message( "SpecialException::what" ) )
Add a matcher that checks exception's message Only works for exceptions that publicly derive from `std::exception` and the matching is done exactly, including case and whitespace. Closes #1649 Closes #1728 # Please enter the commit message for your changes. Lines starting # with '#' will be ignored, and an empty message aborts the commit. # On branch master # Your branch is up-to-date with 'origin/master'. # # Changes to be committed: # modified: ../docs/matchers.md # modified: ../include/internal/catch_capture_matchers.h # modified: ../projects/CMakeLists.txt # modified: ../projects/SelfTest/Baselines/compact.sw.approved.txt # modified: ../projects/SelfTest/Baselines/console.std.approved.txt # modified: ../projects/SelfTest/Baselines/console.sw.approved.txt # modified: ../projects/SelfTest/Baselines/junit.sw.approved.txt # modified: ../projects/SelfTest/Baselines/xml.sw.approved.txt # modified: ../projects/SelfTest/UsageTests/Matchers.tests.cpp # # Untracked files: # ./ # ../clang-full/ # ../clang-test/ # ../clang10-build/ # ../coverage-build/ # ../gcc-build/ # ../gcc-full/ # ../include/internal/catch_matchers_exception.cpp # ../include/internal/catch_matchers_exception.hpp # ../misc-build/ # ../msvc-sln/ # ../notes.txt # ../test-install/ #
2019-10-13 20:37:07 +02:00
with expansion:
Fix baselines
2019-10-13 21:26:51 +02:00
SpecialException::what exception message matches "SpecialException::what"
Add a matcher that checks exception's message Only works for exceptions that publicly derive from `std::exception` and the matching is done exactly, including case and whitespace. Closes #1649 Closes #1728 # Please enter the commit message for your changes. Lines starting # with '#' will be ignored, and an empty message aborts the commit. # On branch master # Your branch is up-to-date with 'origin/master'. # # Changes to be committed: # modified: ../docs/matchers.md # modified: ../include/internal/catch_capture_matchers.h # modified: ../projects/CMakeLists.txt # modified: ../projects/SelfTest/Baselines/compact.sw.approved.txt # modified: ../projects/SelfTest/Baselines/console.std.approved.txt # modified: ../projects/SelfTest/Baselines/console.sw.approved.txt # modified: ../projects/SelfTest/Baselines/junit.sw.approved.txt # modified: ../projects/SelfTest/Baselines/xml.sw.approved.txt # modified: ../projects/SelfTest/UsageTests/Matchers.tests.cpp # # Untracked files: # ./ # ../clang-full/ # ../clang-test/ # ../clang10-build/ # ../coverage-build/ # ../gcc-build/ # ../gcc-full/ # ../include/internal/catch_matchers_exception.cpp # ../include/internal/catch_matchers_exception.hpp # ../misc-build/ # ../msvc-sln/ # ../notes.txt # ../test-install/ #
2019-10-13 20:37:07 +02:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Expected exceptions that don't throw or unexpected exceptions fail the test
-------------------------------------------------------------------------------
Exception.tests.cpp:<line number>
...............................................................................
Exception.tests.cpp:<line number>: FAILED:
CHECK_THROWS_AS( thisThrows(), std::string )
due to unexpected exception with message:
expected exception
Exception.tests.cpp:<line number>: FAILED:
CHECK_THROWS_AS( thisDoesntThrow(), std::domain_error )
because no exception was thrown where one was expected:
Exception.tests.cpp:<line number>: FAILED:
CHECK_NOTHROW( thisThrows() )
due to unexpected exception with message:
expected exception
-------------------------------------------------------------------------------
FAIL aborts the test
-------------------------------------------------------------------------------
Message.tests.cpp:<line number>
...............................................................................
Message.tests.cpp:<line number>: FAILED:
explicitly with message:
This is a failure
-------------------------------------------------------------------------------
FAIL does not require an argument
-------------------------------------------------------------------------------
Message.tests.cpp:<line number>
...............................................................................
Message.tests.cpp:<line number>: FAILED:
-------------------------------------------------------------------------------
FAIL_CHECK does not abort the test
-------------------------------------------------------------------------------
Message.tests.cpp:<line number>
...............................................................................
Message.tests.cpp:<line number>: FAILED:
explicitly with message:
This is a failure
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Message.tests.cpp:<line number>: warning:
Update baselines
2018-08-19 23:22:36 +02:00
This message appears in the output
-------------------------------------------------------------------------------
Factorials are computed
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( Factorial(0) == 1 )
with expansion:
1 == 1
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( Factorial(1) == 1 )
with expansion:
1 == 1
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( Factorial(2) == 2 )
with expansion:
2 == 2
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( Factorial(3) == 6 )
with expansion:
6 == 6
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( Factorial(10) == 3628800 )
with expansion:
3628800 (0x<hex digits>) == 3628800 (0x<hex digits>)
Add test for empty result of filter generator
2023-02-01 18:27:41 +01:00
-------------------------------------------------------------------------------
Filter generator throws exception for empty generator
-------------------------------------------------------------------------------
GeneratorsImpl.tests.cpp:<line number>
...............................................................................
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE_THROWS_AS( filter( []( int ) { return false; }, value( 3 ) ), Catch::GeneratorException )
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
-------------------------------------------------------------------------------
Floating point matchers: double
Relative
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 10., WithinRel( 11.1, 0.1 ) )
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
10.0 and 11.09999999999999964 are within 10% of each other
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 10., !WithinRel( 11.2, 0.1 ) )
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
10.0 not and 11.19999999999999929 are within 10% of each other
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 1., !WithinRel( 0., 0.99 ) )
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
with expansion:
Use Catch::StringMaker for output in WithinRelMatcher (#2846) The WithinRelMatcher does not listen to the precision specification; it just naively pipes to stringstream. If you specify the precision, that has no impact on the outputted values when the match fails. This fix makes the WithinRelMatcher listen to the precision (https://github.com/catchorg/Catch2/blob/devel/docs/tostring.md#floating-point-precision) specified by: Catch::StringMaker<float>::precision
2024-04-15 13:35:39 +02:00
1.0 not and 0.0 are within 99% of each other
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( -0., WithinRel( 0. ) )
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
with expansion:
Use Catch::StringMaker for output in WithinRelMatcher (#2846) The WithinRelMatcher does not listen to the precision specification; it just naively pipes to stringstream. If you specify the precision, that has no impact on the outputted values when the match fails. This fix makes the WithinRelMatcher listen to the precision (https://github.com/catchorg/Catch2/blob/devel/docs/tostring.md#floating-point-precision) specified by: Catch::StringMaker<float>::precision
2024-04-15 13:35:39 +02:00
-0.0 and 0.0 are within 2.22045e-12% of each other
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
-------------------------------------------------------------------------------
Floating point matchers: double
Relative
Some subnormal values
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( v1, WithinRel( v2 ) )
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
with expansion:
Use Catch::StringMaker for output in WithinRelMatcher (#2846) The WithinRelMatcher does not listen to the precision specification; it just naively pipes to stringstream. If you specify the precision, that has no impact on the outputted values when the match fails. This fix makes the WithinRelMatcher listen to the precision (https://github.com/catchorg/Catch2/blob/devel/docs/tostring.md#floating-point-precision) specified by: Catch::StringMaker<float>::precision
2024-04-15 13:35:39 +02:00
0.0 and 0.0 are within 2.22045e-12% of each other
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Floating point matchers: double
Margin
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 1., WithinAbs( 1., 0 ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
1.0 is within 0.0 of 1.0
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 0., WithinAbs( 1., 1 ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
0.0 is within 1.0 of 1.0
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 0., !WithinAbs( 1., 0.99 ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
0.0 not is within 0.98999999999999999 of 1.0
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 0., !WithinAbs( 1., 0.99 ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
0.0 not is within 0.98999999999999999 of 1.0
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 11., !WithinAbs( 10., 0.5 ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
11.0 not is within 0.5 of 10.0
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 10., !WithinAbs( 11., 0.5 ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
10.0 not is within 0.5 of 11.0
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( -10., WithinAbs( -10., 0.5 ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
-10.0 is within 0.5 of -10.0
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( -10., WithinAbs( -9.6, 0.5 ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
-10.0 is within 0.5 of -9.59999999999999964
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Floating point matchers: double
ULPs
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 1., WithinULP( 1., 0 ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Use scientific notation for the WithinULP matcher This should now properly handle small numbers which would previously output something like `[0.00000000000000019, 0.00000000000000019]`, which does not allow user to read the numbers properly. Closes #1760
2019-10-20 12:30:21 +02:00
1.0 is within 0 ULPs of 1.0000000000000000e+00 ([1.0000000000000000e+00, 1.
0000000000000000e+00])
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( nextafter( 1., 2. ), WithinULP( 1., 1 ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.00000000000000022 is within 1 ULPs of 1.0000000000000000e+00 ([9.
9999999999999989e-01, 1.0000000000000002e+00])
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 0., WithinULP( nextafter( 0., 1. ), 1 ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Use scientific notation for the WithinULP matcher This should now properly handle small numbers which would previously output something like `[0.00000000000000019, 0.00000000000000019]`, which does not allow user to read the numbers properly. Closes #1760
2019-10-20 12:30:21 +02:00
0.0 is within 1 ULPs of 4.9406564584124654e-324 ([0.0000000000000000e+00, 9.
8813129168249309e-324])
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 1., WithinULP( nextafter( 1., 0. ), 1 ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Use scientific notation for the WithinULP matcher This should now properly handle small numbers which would previously output something like `[0.00000000000000019, 0.00000000000000019]`, which does not allow user to read the numbers properly. Closes #1760
2019-10-20 12:30:21 +02:00
1.0 is within 1 ULPs of 9.9999999999999989e-01 ([9.9999999999999978e-01, 1.
0000000000000000e+00])
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 1., !WithinULP( nextafter( 1., 2. ), 0 ) )
Use scientific notation for the WithinULP matcher This should now properly handle small numbers which would previously output something like `[0.00000000000000019, 0.00000000000000019]`, which does not allow user to read the numbers properly. Closes #1760
2019-10-20 12:30:21 +02:00
with expansion:
1.0 not is within 0 ULPs of 1.0000000000000002e+00 ([1.0000000000000002e+00,
1.0000000000000002e+00])
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 1., WithinULP( 1., 0 ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Use scientific notation for the WithinULP matcher This should now properly handle small numbers which would previously output something like `[0.00000000000000019, 0.00000000000000019]`, which does not allow user to read the numbers properly. Closes #1760
2019-10-20 12:30:21 +02:00
1.0 is within 0 ULPs of 1.0000000000000000e+00 ([1.0000000000000000e+00, 1.
0000000000000000e+00])
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( -0., WithinULP( 0., 0 ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Use scientific notation for the WithinULP matcher This should now properly handle small numbers which would previously output something like `[0.00000000000000019, 0.00000000000000019]`, which does not allow user to read the numbers properly. Closes #1760
2019-10-20 12:30:21 +02:00
-0.0 is within 0 ULPs of 0.0000000000000000e+00 ([0.0000000000000000e+00, 0.
0000000000000000e+00])
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Floating point matchers: double
Composed
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 1., WithinAbs( 1., 0.5 ) || WithinULP( 2., 1 ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Use scientific notation for the WithinULP matcher This should now properly handle small numbers which would previously output something like `[0.00000000000000019, 0.00000000000000019]`, which does not allow user to read the numbers properly. Closes #1760
2019-10-20 12:30:21 +02:00
1.0 ( is within 0.5 of 1.0 or is within 1 ULPs of 2.0000000000000000e+00 ([1.
9999999999999998e+00, 2.0000000000000004e+00]) )
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 1., WithinAbs( 2., 0.5 ) || WithinULP( 1., 0 ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Use scientific notation for the WithinULP matcher This should now properly handle small numbers which would previously output something like `[0.00000000000000019, 0.00000000000000019]`, which does not allow user to read the numbers properly. Closes #1760
2019-10-20 12:30:21 +02:00
1.0 ( is within 0.5 of 2.0 or is within 0 ULPs of 1.0000000000000000e+00 ([1.
0000000000000000e+00, 1.0000000000000000e+00]) )
Update baselines
2018-08-19 23:22:36 +02:00
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 0.0001, WithinAbs( 0., 0.001 ) || WithinRel( 0., 0.1 ) )
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
with expansion:
Use Catch::StringMaker for output in WithinRelMatcher (#2846) The WithinRelMatcher does not listen to the precision specification; it just naively pipes to stringstream. If you specify the precision, that has no impact on the outputted values when the match fails. This fix makes the WithinRelMatcher listen to the precision (https://github.com/catchorg/Catch2/blob/devel/docs/tostring.md#floating-point-precision) specified by: Catch::StringMaker<float>::precision
2024-04-15 13:35:39 +02:00
0.0001 ( is within 0.001 of 0.0 or and 0.0 are within 10% of each other )
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Floating point matchers: double
Constructor validation
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_NOTHROW( WithinAbs( 1., 0. ) )
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THROWS_AS( WithinAbs( 1., -1. ), std::domain_error )
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_NOTHROW( WithinULP( 1., 0 ) )
Update baselines
2018-08-19 23:22:36 +02:00
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_NOTHROW( WithinRel( 1., 0. ) )
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THROWS_AS( WithinRel( 1., -0.2 ), std::domain_error )
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THROWS_AS( WithinRel( 1., 1. ), std::domain_error )
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
Add IsNaN matcher
2023-02-26 00:14:32 +01:00
-------------------------------------------------------------------------------
Floating point matchers: double
IsNaN
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( 1., !IsNaN() )
with expansion:
1.0 not is NaN
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
-------------------------------------------------------------------------------
Floating point matchers: float
Relative
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 10.f, WithinRel( 11.1f, 0.1f ) )
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
10.0f and 11.10000038146972656 are within 10% of each other
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 10.f, !WithinRel( 11.2f, 0.1f ) )
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
10.0f not and 11.19999980926513672 are within 10% of each other
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 1.f, !WithinRel( 0.f, 0.99f ) )
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
with expansion:
Use Catch::StringMaker for output in WithinRelMatcher (#2846) The WithinRelMatcher does not listen to the precision specification; it just naively pipes to stringstream. If you specify the precision, that has no impact on the outputted values when the match fails. This fix makes the WithinRelMatcher listen to the precision (https://github.com/catchorg/Catch2/blob/devel/docs/tostring.md#floating-point-precision) specified by: Catch::StringMaker<float>::precision
2024-04-15 13:35:39 +02:00
1.0f not and 0.0 are within 99% of each other
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( -0.f, WithinRel( 0.f ) )
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
with expansion:
Use Catch::StringMaker for output in WithinRelMatcher (#2846) The WithinRelMatcher does not listen to the precision specification; it just naively pipes to stringstream. If you specify the precision, that has no impact on the outputted values when the match fails. This fix makes the WithinRelMatcher listen to the precision (https://github.com/catchorg/Catch2/blob/devel/docs/tostring.md#floating-point-precision) specified by: Catch::StringMaker<float>::precision
2024-04-15 13:35:39 +02:00
-0.0f and 0.0 are within 0.00119209% of each other
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
-------------------------------------------------------------------------------
Floating point matchers: float
Relative
Some subnormal values
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( v1, WithinRel( v2 ) )
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
with expansion:
Use Catch::StringMaker for output in WithinRelMatcher (#2846) The WithinRelMatcher does not listen to the precision specification; it just naively pipes to stringstream. If you specify the precision, that has no impact on the outputted values when the match fails. This fix makes the WithinRelMatcher listen to the precision (https://github.com/catchorg/Catch2/blob/devel/docs/tostring.md#floating-point-precision) specified by: Catch::StringMaker<float>::precision
2024-04-15 13:35:39 +02:00
0.0f and 0.0 are within 0.00119209% of each other
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Floating point matchers: float
Margin
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 1.f, WithinAbs( 1.f, 0 ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
1.0f is within 0.0 of 1.0
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 0.f, WithinAbs( 1.f, 1 ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
0.0f is within 1.0 of 1.0
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 0.f, !WithinAbs( 1.f, 0.99f ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
0.0f not is within 0.99000000953674316 of 1.0
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 0.f, !WithinAbs( 1.f, 0.99f ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
0.0f not is within 0.99000000953674316 of 1.0
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 0.f, WithinAbs( -0.f, 0 ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
0.0f is within 0.0 of -0.0
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 11.f, !WithinAbs( 10.f, 0.5f ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
11.0f not is within 0.5 of 10.0
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 10.f, !WithinAbs( 11.f, 0.5f ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
10.0f not is within 0.5 of 11.0
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( -10.f, WithinAbs( -10.f, 0.5f ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
-10.0f is within 0.5 of -10.0
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( -10.f, WithinAbs( -9.6f, 0.5f ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
-10.0f is within 0.5 of -9.60000038146972656
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Floating point matchers: float
ULPs
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 1.f, WithinULP( 1.f, 0 ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Use scientific notation for the WithinULP matcher This should now properly handle small numbers which would previously output something like `[0.00000000000000019, 0.00000000000000019]`, which does not allow user to read the numbers properly. Closes #1760
2019-10-20 12:30:21 +02:00
1.0f is within 0 ULPs of 1.00000000e+00f ([1.00000000e+00, 1.00000000e+00])
Update baselines
2018-08-19 23:22:36 +02:00
Fix ulp distance calculation for numbers with different signs This is a simplification of the fix proposed in #2152, with the critical function split out so that it can be tested directly, without having to go through the ULP matcher. Closes #2152
2021-07-26 22:01:04 +02:00
Matchers.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( -1.f, WithinULP( -1.f, 0 ) )
with expansion:
-1.0f is within 0 ULPs of -1.00000000e+00f ([-1.00000000e+00, -1.00000000e+
00])
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( nextafter( 1.f, 2.f ), WithinULP( 1.f, 1 ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.000000119f is within 1 ULPs of 1.00000000e+00f ([9.99999940e-01, 1.
00000012e+00])
Use scientific notation for the WithinULP matcher This should now properly handle small numbers which would previously output something like `[0.00000000000000019, 0.00000000000000019]`, which does not allow user to read the numbers properly. Closes #1760
2019-10-20 12:30:21 +02:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 0.f, WithinULP( nextafter( 0.f, 1.f ), 1 ) )
Use scientific notation for the WithinULP matcher This should now properly handle small numbers which would previously output something like `[0.00000000000000019, 0.00000000000000019]`, which does not allow user to read the numbers properly. Closes #1760
2019-10-20 12:30:21 +02:00
with expansion:
0.0f is within 1 ULPs of 1.40129846e-45f ([0.00000000e+00, 2.80259693e-45])
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 1.f, WithinULP( nextafter( 1.f, 0.f ), 1 ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Use scientific notation for the WithinULP matcher This should now properly handle small numbers which would previously output something like `[0.00000000000000019, 0.00000000000000019]`, which does not allow user to read the numbers properly. Closes #1760
2019-10-20 12:30:21 +02:00
1.0f is within 1 ULPs of 9.99999940e-01f ([9.99999881e-01, 1.00000000e+00])
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 1.f, !WithinULP( nextafter( 1.f, 2.f ), 0 ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Use scientific notation for the WithinULP matcher This should now properly handle small numbers which would previously output something like `[0.00000000000000019, 0.00000000000000019]`, which does not allow user to read the numbers properly. Closes #1760
2019-10-20 12:30:21 +02:00
1.0f not is within 0 ULPs of 1.00000012e+00f ([1.00000012e+00, 1.00000012e+
00])
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 1.f, WithinULP( 1.f, 0 ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Use scientific notation for the WithinULP matcher This should now properly handle small numbers which would previously output something like `[0.00000000000000019, 0.00000000000000019]`, which does not allow user to read the numbers properly. Closes #1760
2019-10-20 12:30:21 +02:00
1.0f is within 0 ULPs of 1.00000000e+00f ([1.00000000e+00, 1.00000000e+00])
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( -0.f, WithinULP( 0.f, 0 ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Use scientific notation for the WithinULP matcher This should now properly handle small numbers which would previously output something like `[0.00000000000000019, 0.00000000000000019]`, which does not allow user to read the numbers properly. Closes #1760
2019-10-20 12:30:21 +02:00
-0.0f is within 0 ULPs of 0.00000000e+00f ([0.00000000e+00, 0.00000000e+00])
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Floating point matchers: float
Composed
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 1.f, WithinAbs( 1.f, 0.5 ) || WithinULP( 1.f, 1 ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Use scientific notation for the WithinULP matcher This should now properly handle small numbers which would previously output something like `[0.00000000000000019, 0.00000000000000019]`, which does not allow user to read the numbers properly. Closes #1760
2019-10-20 12:30:21 +02:00
1.0f ( is within 0.5 of 1.0 or is within 1 ULPs of 1.00000000e+00f ([9.
99999940e-01, 1.00000012e+00]) )
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 1.f, WithinAbs( 2.f, 0.5 ) || WithinULP( 1.f, 0 ) )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Use scientific notation for the WithinULP matcher This should now properly handle small numbers which would previously output something like `[0.00000000000000019, 0.00000000000000019]`, which does not allow user to read the numbers properly. Closes #1760
2019-10-20 12:30:21 +02:00
1.0f ( is within 0.5 of 2.0 or is within 0 ULPs of 1.00000000e+00f ([1.
00000000e+00, 1.00000000e+00]) )
Update baselines
2018-08-19 23:22:36 +02:00
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( 0.0001f, WithinAbs( 0.f, 0.001f ) || WithinRel( 0.f, 0.1f ) )
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
0.0001f ( is within 0.00100000004749745 of 0.0 or and 0.0 are within 10% of
each other )
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Floating point matchers: float
Constructor validation
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_NOTHROW( WithinAbs( 1.f, 0.f ) )
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THROWS_AS( WithinAbs( 1.f, -1.f ), std::domain_error )
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_NOTHROW( WithinULP( 1.f, 0 ) )
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THROWS_AS( WithinULP( 1.f, static_cast<uint64_t>( -1 ) ), std::domain_error )
Update baselines
2018-08-19 23:22:36 +02:00
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_NOTHROW( WithinRel( 1.f, 0.f ) )
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THROWS_AS( WithinRel( 1.f, -0.2f ), std::domain_error )
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THROWS_AS( WithinRel( 1.f, 1.f ), std::domain_error )
Add a Relative Comparison matcher for floating point numbers It checks Knuth's _close enough with tolerance_ relationship, that is `|lhs - rhs| <= epsilon * max(|lhs|, |rhs|)`, rather then the _very close with tolerance_ relationship that can be written down as `|lhs - rhs| <= epsilon * min(|lhs|, |rhs|)`. This is because it is the more common model around the internet, and as such is likely to be less surprising to the users. In the future we might want to provide the other model as well. Closes #1746
2019-10-13 11:56:50 +02:00
Add IsNaN matcher
2023-02-26 00:14:32 +01:00
-------------------------------------------------------------------------------
Floating point matchers: float
IsNaN
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( 1., !IsNaN() )
with expansion:
1.0 not is NaN
Add test showing literals and complex generators in one GENERATE
2023-12-10 16:38:48 +01:00
-------------------------------------------------------------------------------
GENERATE can combine literals and generators
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( i % 2 == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
GENERATE can combine literals and generators
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( i % 2 == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
GENERATE can combine literals and generators
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( i % 2 == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
GENERATE can combine literals and generators
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( i % 2 == 0 )
with expansion:
0 == 0
Add generic generator modifiers This means mutiple generic generators and some inference helper * take(n, generator) * filter(predicate, generator) * map(func, generator) * repeat(generator, repeats)
2019-01-27 23:50:43 +01:00
-------------------------------------------------------------------------------
Generators -- adapters
Filtering by predicate
Add another test for FilterGenerator
2019-02-23 20:37:30 +01:00
Basic usage
Add generic generator modifiers This means mutiple generic generators and some inference helper * take(n, generator) * filter(predicate, generator) * map(func, generator) * repeat(generator, repeats)
2019-01-27 23:50:43 +01:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( i % 2 == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
Generators -- adapters
Filtering by predicate
Add another test for FilterGenerator
2019-02-23 20:37:30 +01:00
Basic usage
Add generic generator modifiers This means mutiple generic generators and some inference helper * take(n, generator) * filter(predicate, generator) * map(func, generator) * repeat(generator, repeats)
2019-01-27 23:50:43 +01:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( i % 2 == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
Generators -- adapters
Filtering by predicate
Add another test for FilterGenerator
2019-02-23 20:37:30 +01:00
Basic usage
Add generic generator modifiers This means mutiple generic generators and some inference helper * take(n, generator) * filter(predicate, generator) * map(func, generator) * repeat(generator, repeats)
2019-01-27 23:50:43 +01:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( i % 2 == 0 )
with expansion:
0 == 0
Add another test for FilterGenerator
2019-02-23 20:37:30 +01:00
-------------------------------------------------------------------------------
Generators -- adapters
Filtering by predicate
Throws if there are no matching values
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE_THROWS_AS( filter([] (int) {return false; }, value(1)), Catch::GeneratorException )
Add generic generator modifiers This means mutiple generic generators and some inference helper * take(n, generator) * filter(predicate, generator) * map(func, generator) * repeat(generator, repeats)
2019-01-27 23:50:43 +01:00
-------------------------------------------------------------------------------
Generators -- adapters
Shortening a range
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( i < 4 )
with expansion:
1 < 4
-------------------------------------------------------------------------------
Generators -- adapters
Shortening a range
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( i < 4 )
with expansion:
2 < 4
-------------------------------------------------------------------------------
Generators -- adapters
Shortening a range
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( i < 4 )
with expansion:
3 < 4
-------------------------------------------------------------------------------
Generators -- adapters
Transforming elements
Same type
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( i % 2 == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
Generators -- adapters
Transforming elements
Same type
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( i % 2 == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
Generators -- adapters
Transforming elements
Same type
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( i % 2 == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
Generators -- adapters
Transforming elements
Different type
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( i.size() == 1 )
with expansion:
1 == 1
-------------------------------------------------------------------------------
Generators -- adapters
Transforming elements
Different type
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( i.size() == 1 )
with expansion:
1 == 1
-------------------------------------------------------------------------------
Generators -- adapters
Transforming elements
Different type
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Deducing return type of map generator helper (#1576) * Deduce map return type implicitly Giving the first template argument to map generator function to deduce return type is now optional even if the return type is different from the type generated by mapped generator.
2019-03-24 15:44:22 +01:00
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( i.size() == 1 )
with expansion:
1 == 1
-------------------------------------------------------------------------------
Generators -- adapters
Transforming elements
Different deduced type
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( i.size() == 1 )
with expansion:
1 == 1
-------------------------------------------------------------------------------
Generators -- adapters
Transforming elements
Different deduced type
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( i.size() == 1 )
with expansion:
1 == 1
-------------------------------------------------------------------------------
Generators -- adapters
Transforming elements
Different deduced type
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Add generic generator modifiers This means mutiple generic generators and some inference helper * take(n, generator) * filter(predicate, generator) * map(func, generator) * repeat(generator, repeats)
2019-01-27 23:50:43 +01:00
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( i.size() == 1 )
with expansion:
1 == 1
-------------------------------------------------------------------------------
Generators -- adapters
Repeating a generator
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( j > 0 )
with expansion:
1 > 0
-------------------------------------------------------------------------------
Generators -- adapters
Repeating a generator
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( j > 0 )
with expansion:
2 > 0
-------------------------------------------------------------------------------
Generators -- adapters
Repeating a generator
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( j > 0 )
with expansion:
3 > 0
-------------------------------------------------------------------------------
Generators -- adapters
Repeating a generator
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( j > 0 )
with expansion:
1 > 0
-------------------------------------------------------------------------------
Generators -- adapters
Repeating a generator
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( j > 0 )
with expansion:
2 > 0
-------------------------------------------------------------------------------
Generators -- adapters
Repeating a generator
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( j > 0 )
with expansion:
3 > 0
Add ChunkGenerator This generator collects values from the underlying generator until it has a specified amount of them, and then returns them in one "chunk". In case the underlying generator does not have enough elements for a specific chunk, the left-over elements are discarded. Closes #1538
2019-02-23 20:22:46 +01:00
-------------------------------------------------------------------------------
Generators -- adapters
Chunking a generator into sized pieces
Number of elements in source is divisible by chunk size
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( chunk2.size() == 2 )
with expansion:
2 == 2
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( chunk2.front() == chunk2.back() )
with expansion:
1 == 1
-------------------------------------------------------------------------------
Generators -- adapters
Chunking a generator into sized pieces
Number of elements in source is divisible by chunk size
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( chunk2.size() == 2 )
with expansion:
2 == 2
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( chunk2.front() == chunk2.back() )
with expansion:
2 == 2
-------------------------------------------------------------------------------
Generators -- adapters
Chunking a generator into sized pieces
Number of elements in source is divisible by chunk size
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( chunk2.size() == 2 )
with expansion:
2 == 2
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( chunk2.front() == chunk2.back() )
with expansion:
3 == 3
-------------------------------------------------------------------------------
Generators -- adapters
Chunking a generator into sized pieces
Number of elements in source is not divisible by chunk size
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( chunk2.size() == 2 )
with expansion:
2 == 2
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( chunk2.front() == chunk2.back() )
with expansion:
1 == 1
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( chunk2.front() < 3 )
with expansion:
1 < 3
-------------------------------------------------------------------------------
Generators -- adapters
Chunking a generator into sized pieces
Number of elements in source is not divisible by chunk size
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( chunk2.size() == 2 )
with expansion:
2 == 2
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( chunk2.front() == chunk2.back() )
with expansion:
2 == 2
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( chunk2.front() < 3 )
with expansion:
2 < 3
Fix ChunkGenerator with chunk-size 0 Fixes #1671
2019-06-29 15:48:30 +02:00
-------------------------------------------------------------------------------
Generators -- adapters
Chunking a generator into sized pieces
Chunk size of zero
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( chunk2.size() == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
Generators -- adapters
Chunking a generator into sized pieces
Chunk size of zero
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( chunk2.size() == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
Generators -- adapters
Chunking a generator into sized pieces
Chunk size of zero
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( chunk2.size() == 0 )
with expansion:
0 == 0
Add ChunkGenerator This generator collects values from the underlying generator until it has a specified amount of them, and then returns them in one "chunk". In case the underlying generator does not have enough elements for a specific chunk, the left-over elements are discarded. Closes #1538
2019-02-23 20:22:46 +01:00
-------------------------------------------------------------------------------
Generators -- adapters
Chunking a generator into sized pieces
Throws on too small generators
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE_THROWS_AS( chunk(2, value(1)), Catch::GeneratorException )
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators -- simple
Update baselines
2018-08-19 23:22:36 +02:00
one
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( j < i )
with expansion:
-3 < 1
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators -- simple
Update baselines
2018-08-19 23:22:36 +02:00
one
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( j < i )
with expansion:
-2 < 1
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators -- simple
Update baselines
2018-08-19 23:22:36 +02:00
one
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( j < i )
with expansion:
-1 < 1
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators -- simple
two
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( 4u * i > str.size() )
with expansion:
4 > 1
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators -- simple
Update baselines
2018-08-19 23:22:36 +02:00
two
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( 4u * i > str.size() )
with expansion:
4 > 2
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators -- simple
Update baselines
2018-08-19 23:22:36 +02:00
two
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( 4u * i > str.size() )
with expansion:
4 > 3
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators -- simple
Update baselines
2018-08-19 23:22:36 +02:00
one
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( j < i )
with expansion:
-3 < 2
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators -- simple
Update baselines
2018-08-19 23:22:36 +02:00
one
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( j < i )
with expansion:
-2 < 2
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators -- simple
Update baselines
2018-08-19 23:22:36 +02:00
one
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( j < i )
with expansion:
-1 < 2
Update baselines
2018-08-19 23:22:36 +02:00
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators -- simple
two
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( 4u * i > str.size() )
with expansion:
8 > 1
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators -- simple
Update baselines
2018-08-19 23:22:36 +02:00
two
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( 4u * i > str.size() )
with expansion:
8 > 2
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators -- simple
Update baselines
2018-08-19 23:22:36 +02:00
two
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( 4u * i > str.size() )
with expansion:
8 > 3
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators -- simple
Update baselines
2018-08-19 23:22:36 +02:00
one
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( j < i )
with expansion:
-3 < 3
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators -- simple
Update baselines
2018-08-19 23:22:36 +02:00
one
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Generators.tests.cpp:<line number>
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( j < i )
with expansion:
-2 < 3
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators -- simple
Update baselines
2018-08-19 23:22:36 +02:00
one
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( j < i )
with expansion:
-1 < 3
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
Add constructor arg checking to WithinAbsMatcher Also tests :-)
2017-12-06 15:37:13 +01:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators -- simple
two
Add constructor arg checking to WithinAbsMatcher Also tests :-)
2017-12-06 15:37:13 +01:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Generators.tests.cpp:<line number>
Add constructor arg checking to WithinAbsMatcher Also tests :-)
2017-12-06 15:37:13 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( 4u * i > str.size() )
with expansion:
12 > 1
Add constructor arg checking to WithinAbsMatcher Also tests :-)
2017-12-06 15:37:13 +01:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators -- simple
Update baselines
2018-08-19 23:22:36 +02:00
two
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Add constructor arg checking to WithinAbsMatcher Also tests :-)
2017-12-06 15:37:13 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( 4u * i > str.size() )
with expansion:
12 > 2
Add constructor arg checking to WithinAbsMatcher Also tests :-)
2017-12-06 15:37:13 +01:00
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators -- simple
Update baselines
2018-08-19 23:22:36 +02:00
two
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
Generators.tests.cpp:<line number>
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( 4u * i > str.size() )
with expansion:
12 > 3
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators internals
Single value
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
GeneratorsImpl.tests.cpp:<line number>
...............................................................................
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
GeneratorsImpl.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( gen.get() == 123 )
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
123 == 123
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
GeneratorsImpl.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE_FALSE( gen.next() )
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
!false
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators internals
Preset values
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
GeneratorsImpl.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
GeneratorsImpl.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( gen.get() == 1 )
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
1 == 1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
GeneratorsImpl.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( gen.get() == 3 )
Fix bug in WithinAbs::match() and add tests for it
2018-03-19 20:36:07 +01:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
3 == 3
Fix bug in WithinAbs::match() and add tests for it
2018-03-19 20:36:07 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
GeneratorsImpl.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( gen.next() )
Fix bug in WithinAbs::match() and add tests for it
2018-03-19 20:36:07 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
true
Fix bug in WithinAbs::match() and add tests for it
2018-03-19 20:36:07 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
GeneratorsImpl.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( gen.get() == 5 )
Fix bug in WithinAbs::match() and add tests for it
2018-03-19 20:36:07 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
5 == 5
Fix bug in WithinAbs::match() and add tests for it
2018-03-19 20:36:07 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
GeneratorsImpl.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE_FALSE( gen.next() )
Fix bug in WithinAbs::match() and add tests for it
2018-03-19 20:36:07 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
!false
Fix bug in WithinAbs::match() and add tests for it
2018-03-19 20:36:07 +01:00
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators internals
Generator combinator
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
GeneratorsImpl.tests.cpp:<line number>
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
GeneratorsImpl.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( gen.get() == 1 )
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
1 == 1
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
GeneratorsImpl.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( gen.next() )
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
true
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
GeneratorsImpl.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( gen.get() == 5 )
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
5 == 5
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
GeneratorsImpl.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( gen.next() )
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
true
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
GeneratorsImpl.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( gen.get() == 2 )
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
with expansion:
Update baselines
2018-08-19 23:22:36 +02:00
2 == 2
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
GeneratorsImpl.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( gen.next() )
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
true
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
GeneratorsImpl.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( gen.get() == 4 )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
4 == 4
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
GeneratorsImpl.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( gen.next() )
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
true
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
GeneratorsImpl.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( gen.get() == 0 )
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
0 == 0
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
GeneratorsImpl.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE_FALSE( gen.next() )
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
!false
Add ULP and margin matcher Closes #1074
2017-11-10 18:14:42 +01:00
Add constructor arg checking to WithinAbsMatcher Also tests :-)
2017-12-06 15:37:13 +01:00
-------------------------------------------------------------------------------
Redo generator interface
2019-01-27 19:46:28 +01:00
Generators internals
Explicitly typed generator sequence
Add constructor arg checking to WithinAbsMatcher Also tests :-)
2017-12-06 15:37:13 +01:00
-------------------------------------------------------------------------------
Update baselines
2018-08-19 23:22:36 +02:00
GeneratorsImpl.tests.cpp:<line number>
Add constructor arg checking to WithinAbsMatcher Also tests :-)
2017-12-06 15:37:13 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
GeneratorsImpl.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( gen.get().size() == 2 )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
2 == 2
Add constructor arg checking to WithinAbsMatcher Also tests :-)
2017-12-06 15:37:13 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
GeneratorsImpl.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( gen.get() == "aa" )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
"aa" == "aa"
Add constructor arg checking to WithinAbsMatcher Also tests :-)
2017-12-06 15:37:13 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
GeneratorsImpl.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( gen.next() )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
true
Add constructor arg checking to WithinAbsMatcher Also tests :-)
2017-12-06 15:37:13 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
GeneratorsImpl.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( gen.get() == "bb" )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
"bb" == "bb"
Update baselines
2018-08-19 23:22:36 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
GeneratorsImpl.tests.cpp:<line number>: PASSED:
Redo generator interface
2019-01-27 19:46:28 +01:00
REQUIRE( gen.next() )
Update baselines
2018-08-19 23:22:36 +02:00
with expansion:
Redo generator interface
2019-01-27 19:46:28 +01:00
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == "cc" )
with expansion:
"cc" == "cc"
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( gen.next() )
with expansion:
!false
Add constructor arg checking to WithinAbsMatcher Also tests :-)
2017-12-06 15:37:13 +01:00
Add generic generator modifiers This means mutiple generic generators and some inference helper * take(n, generator) * filter(predicate, generator) * map(func, generator) * repeat(generator, repeats)
2019-01-27 23:50:43 +01:00
-------------------------------------------------------------------------------
Generators internals
Filter generator
Add test for filtering out multiple initial values in filter gen
2021-10-28 11:26:34 +02:00
Simple filtering
Add generic generator modifiers This means mutiple generic generators and some inference helper * take(n, generator) * filter(predicate, generator) * map(func, generator) * repeat(generator, repeats)
2019-01-27 23:50:43 +01:00
-------------------------------------------------------------------------------
GeneratorsImpl.tests.cpp:<line number>
...............................................................................
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 1 )
with expansion:
1 == 1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 3 )
with expansion:
3 == 3
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( gen.next() )
with expansion:
!false
Add test for filtering out multiple initial values in filter gen
2021-10-28 11:26:34 +02:00
-------------------------------------------------------------------------------
Generators internals
Filter generator
Filter out multiple elements at the start and end
-------------------------------------------------------------------------------
GeneratorsImpl.tests.cpp:<line number>
...............................................................................
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 1 )
with expansion:
1 == 1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 3 )
with expansion:
3 == 3
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( gen.next() )
with expansion:
!false
-------------------------------------------------------------------------------
Generators internals
Filter generator
Throws on construction if it can't get initial element
-------------------------------------------------------------------------------
GeneratorsImpl.tests.cpp:<line number>
...............................................................................
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE_THROWS_AS( filter([](int) { return false; }, value(1)), Catch::GeneratorException )
Add generic generator modifiers This means mutiple generic generators and some inference helper * take(n, generator) * filter(predicate, generator) * map(func, generator) * repeat(generator, repeats)
2019-01-27 23:50:43 +01:00
GeneratorsImpl.tests.cpp:<line number>: PASSED:
Add test for filtering out multiple initial values in filter gen
2021-10-28 11:26:34 +02:00
REQUIRE_THROWS_AS( filter([](int) { return false; }, values({ 1, 2, 3 })), Catch::GeneratorException )
Add generic generator modifiers This means mutiple generic generators and some inference helper * take(n, generator) * filter(predicate, generator) * map(func, generator) * repeat(generator, repeats)
2019-01-27 23:50:43 +01:00
-------------------------------------------------------------------------------
Generators internals
Take generator
Take less
-------------------------------------------------------------------------------
GeneratorsImpl.tests.cpp:<line number>
...............................................................................
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 1 )
with expansion:
1 == 1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 2 )
with expansion:
2 == 2
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( gen.next() )
with expansion:
!false
-------------------------------------------------------------------------------
Generators internals
Take generator
Take more
-------------------------------------------------------------------------------
GeneratorsImpl.tests.cpp:<line number>
...............................................................................
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 1 )
with expansion:
1 == 1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( gen.next() )
with expansion:
!false
-------------------------------------------------------------------------------
Generators internals
Deducing return type of map generator helper (#1576) * Deduce map return type implicitly Giving the first template argument to map generator function to deduce return type is now optional even if the return type is different from the type generated by mapped generator.
2019-03-24 15:44:22 +01:00
Map with explicit return type
-------------------------------------------------------------------------------
GeneratorsImpl.tests.cpp:<line number>
...............................................................................
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 2.0 )
with expansion:
2.0 == 2.0
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 4.0 )
with expansion:
4.0 == 4.0
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 6.0 )
with expansion:
6.0 == 6.0
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( gen.next() )
with expansion:
!false
-------------------------------------------------------------------------------
Generators internals
Map with deduced return type
Add generic generator modifiers This means mutiple generic generators and some inference helper * take(n, generator) * filter(predicate, generator) * map(func, generator) * repeat(generator, repeats)
2019-01-27 23:50:43 +01:00
-------------------------------------------------------------------------------
GeneratorsImpl.tests.cpp:<line number>
...............................................................................
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 2.0 )
with expansion:
2.0 == 2.0
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 4.0 )
with expansion:
4.0 == 4.0
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 6.0 )
with expansion:
6.0 == 6.0
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( gen.next() )
with expansion:
!false
-------------------------------------------------------------------------------
Generators internals
Repeat
Singular repeat
-------------------------------------------------------------------------------
GeneratorsImpl.tests.cpp:<line number>
...............................................................................
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 3 )
with expansion:
3 == 3
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( gen.next() )
with expansion:
!false
-------------------------------------------------------------------------------
Generators internals
Repeat
Actual repeat
-------------------------------------------------------------------------------
GeneratorsImpl.tests.cpp:<line number>
...............................................................................
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 1 )
with expansion:
1 == 1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 2 )
with expansion:
2 == 2
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 3 )
with expansion:
3 == 3
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 1 )
with expansion:
1 == 1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 2 )
with expansion:
2 == 2
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 3 )
with expansion:
3 == 3
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( gen.next() )
with expansion:
!false
Add RangeGenerator
2019-02-03 16:42:24 +01:00
-------------------------------------------------------------------------------
Generators internals
Range
Positive auto step
Integer
-------------------------------------------------------------------------------
GeneratorsImpl.tests.cpp:<line number>
...............................................................................
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == -2 )
with expansion:
-2 == -2
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == -1 )
with expansion:
-1 == -1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 0 )
with expansion:
0 == 0
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 1 )
with expansion:
1 == 1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( gen.next() )
with expansion:
!false
-------------------------------------------------------------------------------
Generators internals
Range
Negative auto step
Integer
-------------------------------------------------------------------------------
GeneratorsImpl.tests.cpp:<line number>
...............................................................................
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 2 )
with expansion:
2 == 2
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 1 )
with expansion:
1 == 1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 0 )
with expansion:
0 == 0
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == -1 )
with expansion:
-1 == -1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( gen.next() )
with expansion:
!false
-------------------------------------------------------------------------------
Generators internals
Range
Positive manual step
Integer
Exact
-------------------------------------------------------------------------------
GeneratorsImpl.tests.cpp:<line number>
...............................................................................
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == -7 )
with expansion:
-7 == -7
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == -4 )
with expansion:
-4 == -4
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == -1 )
with expansion:
-1 == -1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 2 )
with expansion:
2 == 2
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( gen.next() )
with expansion:
!false
-------------------------------------------------------------------------------
Generators internals
Range
Positive manual step
Integer
Slightly over end
-------------------------------------------------------------------------------
GeneratorsImpl.tests.cpp:<line number>
...............................................................................
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == -7 )
with expansion:
-7 == -7
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == -4 )
with expansion:
-4 == -4
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == -1 )
with expansion:
-1 == -1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 2 )
with expansion:
2 == 2
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( gen.next() )
with expansion:
!false
-------------------------------------------------------------------------------
Generators internals
Range
Positive manual step
Integer
Slightly under end
-------------------------------------------------------------------------------
GeneratorsImpl.tests.cpp:<line number>
...............................................................................
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == -7 )
with expansion:
-7 == -7
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == -4 )
with expansion:
-4 == -4
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == -1 )
with expansion:
-1 == -1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 2 )
with expansion:
2 == 2
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 5 )
with expansion:
5 == 5
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( gen.next() )
with expansion:
!false
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
-------------------------------------------------------------------------------
Generators internals
Range
Positive manual step
Floating Point
Exact
-------------------------------------------------------------------------------
GeneratorsImpl.tests.cpp:<line number>
...............................................................................
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
-1.0 == Approx( -1.0 )
with message:
Current expected value is -1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is -1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
-0.90000000000000002
==
Approx( -0.90000000000000002 )
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
with message:
Current expected value is -0.9
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is -0.9
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
-0.80000000000000004
==
Approx( -0.80000000000000004 )
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
with message:
Current expected value is -0.8
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is -0.8
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
-0.70000000000000007
==
Approx( -0.70000000000000007 )
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
with message:
Current expected value is -0.7
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is -0.7
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
-0.60000000000000009
==
Approx( -0.60000000000000009 )
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
with message:
Current expected value is -0.6
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is -0.6
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
-0.50000000000000011
==
Approx( -0.50000000000000011 )
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
with message:
Current expected value is -0.5
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is -0.5
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
-0.40000000000000013
==
Approx( -0.40000000000000013 )
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
with message:
Current expected value is -0.4
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is -0.4
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
-0.30000000000000016
==
Approx( -0.30000000000000016 )
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
with message:
Current expected value is -0.3
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is -0.3
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
-0.20000000000000015
==
Approx( -0.20000000000000015 )
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
with message:
Current expected value is -0.2
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is -0.2
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
-0.10000000000000014
==
Approx( -0.10000000000000014 )
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
with message:
Current expected value is -0.1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is -0.1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
-0.00000000000000014
==
Approx( -0.00000000000000014 )
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
with message:
Current expected value is -1.38778e-16
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is -1.38778e-16
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
0.09999999999999987
==
Approx( 0.09999999999999987 )
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
with message:
Current expected value is 0.1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is 0.1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
0.19999999999999987
==
Approx( 0.19999999999999987 )
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
with message:
Current expected value is 0.2
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is 0.2
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
0.29999999999999988
==
Approx( 0.29999999999999988 )
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
with message:
Current expected value is 0.3
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is 0.3
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
0.39999999999999991
==
Approx( 0.39999999999999991 )
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
with message:
Current expected value is 0.4
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is 0.4
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
0.49999999999999989
==
Approx( 0.49999999999999989 )
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
with message:
Current expected value is 0.5
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is 0.5
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
0.59999999999999987
==
Approx( 0.59999999999999987 )
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
with message:
Current expected value is 0.6
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is 0.6
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
0.69999999999999984
==
Approx( 0.69999999999999984 )
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
with message:
Current expected value is 0.7
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is 0.7
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
0.79999999999999982
==
Approx( 0.79999999999999982 )
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
with message:
Current expected value is 0.8
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is 0.8
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
0.8999999999999998
==
Approx( 0.8999999999999998 )
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
with message:
Current expected value is 0.9
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is 0.9
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx( rangeEnd ) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
0.99999999999999978 == Approx( 1.0 )
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( gen.next() )
with expansion:
!false
-------------------------------------------------------------------------------
Generators internals
Range
Positive manual step
Floating Point
Slightly over end
-------------------------------------------------------------------------------
GeneratorsImpl.tests.cpp:<line number>
...............................................................................
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
-1.0 == Approx( -1.0 )
with message:
Current expected value is -1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is -1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
-0.69999999999999996
==
Approx( -0.69999999999999996 )
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
with message:
Current expected value is -0.7
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is -0.7
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
-0.39999999999999997
==
Approx( -0.39999999999999997 )
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
with message:
Current expected value is -0.4
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is -0.4
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
-0.09999999999999998
==
Approx( -0.09999999999999998 )
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
with message:
Current expected value is -0.1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is -0.1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
0.20000000000000001
==
Approx( 0.20000000000000001 )
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
with message:
Current expected value is 0.2
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is 0.2
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
0.5 == Approx( 0.5 )
with message:
Current expected value is 0.5
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is 0.5
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( gen.next() )
with expansion:
!false
-------------------------------------------------------------------------------
Generators internals
Range
Positive manual step
Floating Point
Slightly under end
-------------------------------------------------------------------------------
GeneratorsImpl.tests.cpp:<line number>
...............................................................................
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
-1.0 == Approx( -1.0 )
with message:
Current expected value is -1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is -1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
-0.69999999999999996
==
Approx( -0.69999999999999996 )
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
with message:
Current expected value is -0.7
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is -0.7
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
-0.39999999999999997
==
Approx( -0.39999999999999997 )
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
with message:
Current expected value is -0.4
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is -0.4
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
-0.09999999999999998
==
Approx( -0.09999999999999998 )
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
with message:
Current expected value is -0.1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is -0.1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
0.20000000000000001
==
Approx( 0.20000000000000001 )
Enable `range` generator for floating point types
2019-10-16 16:03:42 +02:00
with message:
Current expected value is 0.2
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is 0.2
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == Approx(expected) )
with expansion:
0.5 == Approx( 0.5 )
with message:
Current expected value is 0.5
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
with message:
Current expected value is 0.5
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( gen.next() )
with expansion:
!false
Add RangeGenerator
2019-02-03 16:42:24 +01:00
-------------------------------------------------------------------------------
Generators internals
Range
Negative manual step
Integer
Exact
-------------------------------------------------------------------------------
GeneratorsImpl.tests.cpp:<line number>
...............................................................................
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 5 )
with expansion:
5 == 5
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 2 )
with expansion:
2 == 2
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == -1 )
with expansion:
-1 == -1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == -4 )
with expansion:
-4 == -4
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( gen.next() )
with expansion:
!false
-------------------------------------------------------------------------------
Generators internals
Range
Negative manual step
Integer
Slightly over end
-------------------------------------------------------------------------------
GeneratorsImpl.tests.cpp:<line number>
...............................................................................
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 5 )
with expansion:
5 == 5
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 2 )
with expansion:
2 == 2
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == -1 )
with expansion:
-1 == -1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == -4 )
with expansion:
-4 == -4
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( gen.next() )
with expansion:
!false
-------------------------------------------------------------------------------
Generators internals
Range
Negative manual step
Integer
Slightly under end
-------------------------------------------------------------------------------
GeneratorsImpl.tests.cpp:<line number>
...............................................................................
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 5 )
with expansion:
5 == 5
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == 2 )
with expansion:
2 == 2
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == -1 )
with expansion:
-1 == -1
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == -4 )
with expansion:
-4 == -4
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.next() )
with expansion:
true
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE( gen.get() == -7 )
with expansion:
-7 == -7
GeneratorsImpl.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( gen.next() )
with expansion:
!false
Added approvals for “Greater-than inequalities with different epsilons” test
2017-01-09 15:40:09 +01:00
-------------------------------------------------------------------------------
Greater-than inequalities with different epsilons
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Approx.tests.cpp:<line number>
Added approvals for “Greater-than inequalities with different epsilons” test
2017-01-09 15:40:09 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Added approvals for “Greater-than inequalities with different epsilons” test
2017-01-09 15:40:09 +01:00
REQUIRE( d >= Approx( 1.22 ) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.22999999999999998
>=
Approx( 1.21999999999999997 )
Added approvals for “Greater-than inequalities with different epsilons” test
2017-01-09 15:40:09 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Added approvals for “Greater-than inequalities with different epsilons” test
2017-01-09 15:40:09 +01:00
REQUIRE( d >= Approx( 1.23 ) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.22999999999999998
>=
Approx( 1.22999999999999998 )
Added approvals for “Greater-than inequalities with different epsilons” test
2017-01-09 15:40:09 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Added approvals for “Greater-than inequalities with different epsilons” test
2017-01-09 15:40:09 +01:00
REQUIRE_FALSE( d >= Approx( 1.24 ) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
!(1.22999999999999998
>=
Approx( 1.23999999999999999 ))
Added approvals for “Greater-than inequalities with different epsilons” test
2017-01-09 15:40:09 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Added approvals for “Greater-than inequalities with different epsilons” test
2017-01-09 15:40:09 +01:00
REQUIRE( d >= Approx( 1.24 ).epsilon(0.1) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.22999999999999998
>=
Approx( 1.23999999999999999 )
Added approvals for “Greater-than inequalities with different epsilons” test
2017-01-09 15:40:09 +01:00
Refactor tests
2022-03-31 22:30:38 +02:00
-------------------------------------------------------------------------------
Hashers with different seed produce different hash with same test case
-------------------------------------------------------------------------------
TestCaseInfoHasher.tests.cpp:<line number>
...............................................................................
TestCaseInfoHasher.tests.cpp:<line number>: PASSED:
REQUIRE( h1( dummy ) != h2( dummy ) )
with expansion:
3422778688 (0x<hex digits>)
!=
130711275 (0x<hex digits>)
-------------------------------------------------------------------------------
Hashers with same seed produce same hash
-------------------------------------------------------------------------------
TestCaseInfoHasher.tests.cpp:<line number>
...............................................................................
TestCaseInfoHasher.tests.cpp:<line number>: PASSED:
REQUIRE( h1( dummy ) == h2( dummy ) )
with expansion:
3422778688 (0x<hex digits>)
==
3422778688 (0x<hex digits>)
-------------------------------------------------------------------------------
Hashing different test cases produces different result
Different test name
-------------------------------------------------------------------------------
TestCaseInfoHasher.tests.cpp:<line number>
...............................................................................
TestCaseInfoHasher.tests.cpp:<line number>: PASSED:
REQUIRE( h( dummy1 ) != h( dummy2 ) )
with expansion:
2903002874 (0x<hex digits>)
!=
2668622104 (0x<hex digits>)
-------------------------------------------------------------------------------
Hashing different test cases produces different result
Different classname
-------------------------------------------------------------------------------
TestCaseInfoHasher.tests.cpp:<line number>
...............................................................................
TestCaseInfoHasher.tests.cpp:<line number>: PASSED:
REQUIRE( h( dummy1 ) != h( dummy2 ) )
with expansion:
2673152918 (0x<hex digits>)
!=
3916075712 (0x<hex digits>)
-------------------------------------------------------------------------------
Hashing different test cases produces different result
Different tags
-------------------------------------------------------------------------------
TestCaseInfoHasher.tests.cpp:<line number>
...............................................................................
TestCaseInfoHasher.tests.cpp:<line number>: PASSED:
REQUIRE( h( dummy1 ) != h( dummy2 ) )
with expansion:
2074929312 (0x<hex digits>)
!=
3429949824 (0x<hex digits>)
-------------------------------------------------------------------------------
Hashing test case produces same hash across multiple calls
-------------------------------------------------------------------------------
TestCaseInfoHasher.tests.cpp:<line number>
...............................................................................
TestCaseInfoHasher.tests.cpp:<line number>: PASSED:
REQUIRE( h( dummy ) == h( dummy ) )
with expansion:
3422778688 (0x<hex digits>)
==
3422778688 (0x<hex digits>)
Add test for multiple streaming parts in UNSCOPED_INFO
2023-09-17 10:44:31 +02:00
-------------------------------------------------------------------------------
INFO and UNSCOPED_INFO can stream multiple arguments
-------------------------------------------------------------------------------
Message.tests.cpp:<line number>
...............................................................................
Message.tests.cpp:<line number>: FAILED:
explicitly with messages:
This info has multiple parts.
This unscoped info has multiple parts.
Show infos!
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
INFO and WARN do not abort tests
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Message.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Message.tests.cpp:<line number>: warning:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
this is a message
this is a warning
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Fixed NoAssertions warning
2018-01-26 17:52:28 +01:00
No assertions in test case 'INFO and WARN do not abort tests'
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
INFO gets logged on failure
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Message.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Message.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( a == 1 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
2 == 1
with messages:
this message should be logged
so should this
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
INFO gets logged on failure, even if captured before successful assertions
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Message.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Message.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( a == 2 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
2 == 2
with message:
this message may be logged later
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Message.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( a == 1 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
2 == 1
Update baselines
2017-06-06 15:07:57 +02:00
with messages:
this message may be logged later
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
this message should be logged
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Message.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( a == 0 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
2 == 0
Update baselines
2017-06-06 15:07:57 +02:00
with messages:
this message may be logged later
this message should be logged
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
and this, but later
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Message.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( a == 2 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
2 == 2
Update baselines
2017-06-06 15:07:57 +02:00
with messages:
this message may be logged later
this message should be logged
and this, but later
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
but not this
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Remove obsoleted `SCOPED_MSG` and `SCOPED_CAPTURE` Standard `MSG` and `CAPTURE` behave the same way these used to, and are recommended instead.
2017-08-10 17:06:32 +02:00
-------------------------------------------------------------------------------
INFO is reset for each loop
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Message.tests.cpp:<line number>
Remove obsoleted `SCOPED_MSG` and `SCOPED_CAPTURE` Standard `MSG` and `CAPTURE` behave the same way these used to, and are recommended instead.
2017-08-10 17:06:32 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Message.tests.cpp:<line number>: PASSED:
Remove obsoleted `SCOPED_MSG` and `SCOPED_CAPTURE` Standard `MSG` and `CAPTURE` behave the same way these used to, and are recommended instead.
2017-08-10 17:06:32 +02:00
REQUIRE( i < 10 )
with expansion:
0 < 10
with messages:
current counter 0
i := 0
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Message.tests.cpp:<line number>: PASSED:
Remove obsoleted `SCOPED_MSG` and `SCOPED_CAPTURE` Standard `MSG` and `CAPTURE` behave the same way these used to, and are recommended instead.
2017-08-10 17:06:32 +02:00
REQUIRE( i < 10 )
with expansion:
1 < 10
with messages:
current counter 1
i := 1
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Message.tests.cpp:<line number>: PASSED:
Remove obsoleted `SCOPED_MSG` and `SCOPED_CAPTURE` Standard `MSG` and `CAPTURE` behave the same way these used to, and are recommended instead.
2017-08-10 17:06:32 +02:00
REQUIRE( i < 10 )
with expansion:
2 < 10
with messages:
current counter 2
i := 2
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Message.tests.cpp:<line number>: PASSED:
Remove obsoleted `SCOPED_MSG` and `SCOPED_CAPTURE` Standard `MSG` and `CAPTURE` behave the same way these used to, and are recommended instead.
2017-08-10 17:06:32 +02:00
REQUIRE( i < 10 )
with expansion:
3 < 10
with messages:
current counter 3
i := 3
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Message.tests.cpp:<line number>: PASSED:
Remove obsoleted `SCOPED_MSG` and `SCOPED_CAPTURE` Standard `MSG` and `CAPTURE` behave the same way these used to, and are recommended instead.
2017-08-10 17:06:32 +02:00
REQUIRE( i < 10 )
with expansion:
4 < 10
with messages:
current counter 4
i := 4
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Message.tests.cpp:<line number>: PASSED:
Remove obsoleted `SCOPED_MSG` and `SCOPED_CAPTURE` Standard `MSG` and `CAPTURE` behave the same way these used to, and are recommended instead.
2017-08-10 17:06:32 +02:00
REQUIRE( i < 10 )
with expansion:
5 < 10
with messages:
current counter 5
i := 5
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Message.tests.cpp:<line number>: PASSED:
Remove obsoleted `SCOPED_MSG` and `SCOPED_CAPTURE` Standard `MSG` and `CAPTURE` behave the same way these used to, and are recommended instead.
2017-08-10 17:06:32 +02:00
REQUIRE( i < 10 )
with expansion:
6 < 10
with messages:
current counter 6
i := 6
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Message.tests.cpp:<line number>: PASSED:
Remove obsoleted `SCOPED_MSG` and `SCOPED_CAPTURE` Standard `MSG` and `CAPTURE` behave the same way these used to, and are recommended instead.
2017-08-10 17:06:32 +02:00
REQUIRE( i < 10 )
with expansion:
7 < 10
with messages:
current counter 7
i := 7
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Message.tests.cpp:<line number>: PASSED:
Remove obsoleted `SCOPED_MSG` and `SCOPED_CAPTURE` Standard `MSG` and `CAPTURE` behave the same way these used to, and are recommended instead.
2017-08-10 17:06:32 +02:00
REQUIRE( i < 10 )
with expansion:
8 < 10
with messages:
current counter 8
i := 8
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Message.tests.cpp:<line number>: PASSED:
Remove obsoleted `SCOPED_MSG` and `SCOPED_CAPTURE` Standard `MSG` and `CAPTURE` behave the same way these used to, and are recommended instead.
2017-08-10 17:06:32 +02:00
REQUIRE( i < 10 )
with expansion:
9 < 10
with messages:
current counter 9
i := 9
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Message.tests.cpp:<line number>: FAILED:
Remove obsoleted `SCOPED_MSG` and `SCOPED_CAPTURE` Standard `MSG` and `CAPTURE` behave the same way these used to, and are recommended instead.
2017-08-10 17:06:32 +02:00
REQUIRE( i < 10 )
with expansion:
10 < 10
with messages:
current counter 10
i := 10
Assert Info reset need to also reset result disposition to normal to handle uncaught exception correctly (#2723) * AssertionEnd does not reset the assertion info yet. That is done after populateReaction. And reset assertion info would also reset the result disposition to normal, so that any uncaught exception would be reported as failure * Approving test output changes due to added unit tests * Unit tests to throw std::runtime_error instead of std::exception * Add a unit test to test incomplete assertion handler --------- Co-authored-by: Ross <ross.tang@gfo-x.com>
2023-08-07 22:07:31 +02:00
-------------------------------------------------------------------------------
Incomplete AssertionHandler
-------------------------------------------------------------------------------
AssertionHandler.tests.cpp:<line number>
...............................................................................
AssertionHandler.tests.cpp:<line number>: FAILED:
REQUIRE( Dummy )
due to unexpected exception with message:
Exception translation was disabled by CATCH_CONFIG_FAST_COMPILE
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Inequality checks that should fail
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( data.int_seven != 7 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
7 != 7
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( data.float_nine_point_one != Approx( 9.1f ) )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
9.100000381f
!=
Approx( 9.10000038146972656 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( data.double_pi != Approx( 3.1415926535 ) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
3.14159265350000005
!=
Approx( 3.14159265350000005 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( data.str_hello != "hello" )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"hello" != "hello"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( data.str_hello.size() != 5 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
5 != 5
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Inequality checks that should succeed
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( data.int_seven != 6 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
7 != 6
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( data.int_seven != 8 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
7 != 8
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( data.float_nine_point_one != Approx( 9.11f ) )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
9.100000381f
!=
Approx( 9.10999965667724609 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( data.float_nine_point_one != Approx( 9.0f ) )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
9.100000381f != Approx( 9.0 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( data.float_nine_point_one != Approx( 1 ) )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
9.100000381f != Approx( 1.0 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( data.float_nine_point_one != Approx( 0 ) )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
9.100000381f != Approx( 0.0 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( data.double_pi != Approx( 3.1415 ) )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
3.14159265350000005
!=
Approx( 3.14150000000000018 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( data.str_hello != "goodbye" )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"hello" != "goodbye"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( data.str_hello != "hell" )
with expansion:
"hello" != "hell"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( data.str_hello != "hello1" )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"hello" != "hello1"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( data.str_hello.size() != 6 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
5 != 6
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Add JSON reporter (#2706) Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2023-11-14 22:52:15 +01:00
-------------------------------------------------------------------------------
JsonWriter
Newly constructed JsonWriter does nothing
-------------------------------------------------------------------------------
Json.tests.cpp:<line number>
...............................................................................
Json.tests.cpp:<line number>: PASSED:
REQUIRE( stream.str() == "" )
with expansion:
"" == ""
-------------------------------------------------------------------------------
JsonWriter
Calling writeObject will create an empty pair of braces
-------------------------------------------------------------------------------
Json.tests.cpp:<line number>
...............................................................................
Json.tests.cpp:<line number>: PASSED:
REQUIRE( stream.str() == "{\n}" )
with expansion:
"{
}"
==
"{
}"
-------------------------------------------------------------------------------
JsonWriter
Calling writeObject with key will create an object to write the value
-------------------------------------------------------------------------------
Json.tests.cpp:<line number>
...............................................................................
Json.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( stream.str(), ContainsSubstring( "\"int\": 1," ) && ContainsSubstring( "\"double\": 1.5," ) && ContainsSubstring( "\"true\": true," ) && ContainsSubstring( "\"false\": false," ) && ContainsSubstring( "\"string\": \"this is a string\"," ) && ContainsSubstring( "\"array\": [\n 1,\n 2\n ]\n}" ) )
with expansion:
"{
"int": 1,
"double": 1.5,
"true": true,
"false": false,
"string": "this is a string",
"array": [
1,
2
]
}" ( contains: ""int": 1," and contains: ""double": 1.5," and contains:
""true": true," and contains: ""false": false," and contains: ""string":
"this is a string"," and contains: ""array": [
1,
2
]
}" )
-------------------------------------------------------------------------------
JsonWriter
nesting objects
-------------------------------------------------------------------------------
Json.tests.cpp:<line number>
...............................................................................
Json.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( stream.str(), ContainsSubstring( "\"empty_object\": {\n }," ) && ContainsSubstring( "\"fully_object\": {\n \"key\": 1\n }" ) )
with expansion:
"{
"empty_object": {
},
"fully_object": {
"key": 1
}
}" ( contains: ""empty_object": {
}," and contains: ""fully_object": {
"key": 1
}" )
-------------------------------------------------------------------------------
JsonWriter
Calling writeArray will create an empty pair of braces
-------------------------------------------------------------------------------
Json.tests.cpp:<line number>
...............................................................................
Json.tests.cpp:<line number>: PASSED:
REQUIRE( stream.str() == "[\n]" )
with expansion:
"[
]"
==
"[
]"
-------------------------------------------------------------------------------
JsonWriter
Calling writeArray creates array to write the values to
-------------------------------------------------------------------------------
Json.tests.cpp:<line number>
...............................................................................
Json.tests.cpp:<line number>: PASSED:
REQUIRE( stream.str() == "[\n 1,\n 1.5,\n true,\n false,\n \"this is a string\",\n {\n \"object\": 42\n },\n [\n \"array\",\n 42.5\n ]\n]" )
with expansion:
"[
1,
1.5,
true,
false,
"this is a string",
{
"object": 42
},
[
"array",
42.5
]
]"
==
"[
1,
1.5,
true,
false,
"this is a string",
{
"object": 42
},
[
"array",
42.5
]
]"
-------------------------------------------------------------------------------
JsonWriter
Moved from JsonObjectWriter shall not insert superfluous brace
-------------------------------------------------------------------------------
Json.tests.cpp:<line number>
...............................................................................
Json.tests.cpp:<line number>: PASSED:
REQUIRE( stream.str() == "{\n}" )
with expansion:
"{
}"
==
"{
}"
-------------------------------------------------------------------------------
JsonWriter
Moved from JsonArrayWriter shall not insert superfluous bracket
-------------------------------------------------------------------------------
Json.tests.cpp:<line number>
...............................................................................
Json.tests.cpp:<line number>: PASSED:
REQUIRE( stream.str() == "[\n]" )
with expansion:
"[
]"
==
"[
]"
-------------------------------------------------------------------------------
JsonWriter
Custom class shall be quoted
-------------------------------------------------------------------------------
Json.tests.cpp:<line number>
...............................................................................
Json.tests.cpp:<line number>: PASSED:
REQUIRE( stream.str() == "\"custom\"" )
with expansion:
""custom"" == ""custom""
-------------------------------------------------------------------------------
Fix special character escaping in JsonWriter
2023-11-14 23:35:22 +01:00
JsonWriter escapes charaters in strings properly
Quote in a string is escaped
Add JSON reporter (#2706) Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2023-11-14 22:52:15 +01:00
-------------------------------------------------------------------------------
Json.tests.cpp:<line number>
...............................................................................
Json.tests.cpp:<line number>: PASSED:
Fix special character escaping in JsonWriter
2023-11-14 23:35:22 +01:00
REQUIRE( sstream.str() == "\"\\\"\"" )
Add JSON reporter (#2706) Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2023-11-14 22:52:15 +01:00
with expansion:
""\""" == ""\"""
Fix special character escaping in JsonWriter
2023-11-14 23:35:22 +01:00
-------------------------------------------------------------------------------
JsonWriter escapes charaters in strings properly
Backslash in a string is escaped
-------------------------------------------------------------------------------
Json.tests.cpp:<line number>
...............................................................................
Json.tests.cpp:<line number>: PASSED:
REQUIRE( sstream.str() == "\"\\\\\"" )
with expansion:
""\\"" == ""\\""
-------------------------------------------------------------------------------
JsonWriter escapes charaters in strings properly
Forward slash in a string is **not** escaped
-------------------------------------------------------------------------------
Json.tests.cpp:<line number>
...............................................................................
Json.tests.cpp:<line number>: PASSED:
REQUIRE( sstream.str() == "\"/\"" )
with expansion:
""/"" == ""/""
-------------------------------------------------------------------------------
JsonWriter escapes charaters in strings properly
Backspace in a string is escaped
-------------------------------------------------------------------------------
Json.tests.cpp:<line number>
...............................................................................
Json.tests.cpp:<line number>: PASSED:
REQUIRE( sstream.str() == "\"\\b\"" )
with expansion:
""\b"" == ""\b""
-------------------------------------------------------------------------------
JsonWriter escapes charaters in strings properly
Formfeed in a string is escaped
-------------------------------------------------------------------------------
Json.tests.cpp:<line number>
...............................................................................
Json.tests.cpp:<line number>: PASSED:
REQUIRE( sstream.str() == "\"\\f\"" )
with expansion:
""\f"" == ""\f""
-------------------------------------------------------------------------------
JsonWriter escapes charaters in strings properly
linefeed in a string is escaped
-------------------------------------------------------------------------------
Json.tests.cpp:<line number>
...............................................................................
Json.tests.cpp:<line number>: PASSED:
REQUIRE( sstream.str() == "\"\\n\"" )
with expansion:
""\n"" == ""\n""
-------------------------------------------------------------------------------
JsonWriter escapes charaters in strings properly
carriage return in a string is escaped
-------------------------------------------------------------------------------
Json.tests.cpp:<line number>
...............................................................................
Json.tests.cpp:<line number>: PASSED:
REQUIRE( sstream.str() == "\"\\r\"" )
with expansion:
""\r"" == ""\r""
-------------------------------------------------------------------------------
JsonWriter escapes charaters in strings properly
tab in a string is escaped
-------------------------------------------------------------------------------
Json.tests.cpp:<line number>
...............................................................................
Json.tests.cpp:<line number>: PASSED:
REQUIRE( sstream.str() == "\"\\t\"" )
with expansion:
""\t"" == ""\t""
-------------------------------------------------------------------------------
JsonWriter escapes charaters in strings properly
combination of characters is escaped
-------------------------------------------------------------------------------
Json.tests.cpp:<line number>
...............................................................................
Json.tests.cpp:<line number>: PASSED:
REQUIRE( sstream.str() == "\"\\\\/\\t\\r\\n\"" )
with expansion:
""\\/\t\r\n"" == ""\\/\t\r\n""
Fix compilation error when lambdas are used in assertions This is a partial revert of b7b346c3e5603.
2020-03-19 13:32:45 +01:00
-------------------------------------------------------------------------------
Lambdas in assertions
-------------------------------------------------------------------------------
Compilation.tests.cpp:<line number>
...............................................................................
Compilation.tests.cpp:<line number>: PASSED:
REQUIRE( []() { return true; }() )
with expansion:
true
Added approvals for “Greater-than inequalities with different epsilons” test
2017-01-09 15:40:09 +01:00
-------------------------------------------------------------------------------
Less-than inequalities with different epsilons
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Approx.tests.cpp:<line number>
Added approvals for “Greater-than inequalities with different epsilons” test
2017-01-09 15:40:09 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Added approvals for “Greater-than inequalities with different epsilons” test
2017-01-09 15:40:09 +01:00
REQUIRE( d <= Approx( 1.24 ) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.22999999999999998
<=
Approx( 1.23999999999999999 )
Added approvals for “Greater-than inequalities with different epsilons” test
2017-01-09 15:40:09 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Added approvals for “Greater-than inequalities with different epsilons” test
2017-01-09 15:40:09 +01:00
REQUIRE( d <= Approx( 1.23 ) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.22999999999999998
<=
Approx( 1.22999999999999998 )
Added approvals for “Greater-than inequalities with different epsilons” test
2017-01-09 15:40:09 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Added approvals for “Greater-than inequalities with different epsilons” test
2017-01-09 15:40:09 +01:00
REQUIRE_FALSE( d <= Approx( 1.22 ) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
!(1.22999999999999998
<=
Approx( 1.21999999999999997 ))
Added approvals for “Greater-than inequalities with different epsilons” test
2017-01-09 15:40:09 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Added approvals for “Greater-than inequalities with different epsilons” test
2017-01-09 15:40:09 +01:00
REQUIRE( d <= Approx( 1.22 ).epsilon(0.1) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.22999999999999998
<=
Approx( 1.21999999999999997 )
Added approvals for “Greater-than inequalities with different epsilons” test
2017-01-09 15:40:09 +01:00
Added support for manually registering test functions. As discussed in #421
2015-11-20 17:54:07 +01:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ManuallyRegistered
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with message:
was called
-------------------------------------------------------------------------------
Matchers can be (AllOf) composed with the && operator
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
CHECK_THAT( testStringForMatching(), ContainsSubstring( "string" ) && ContainsSubstring( "abc" ) && ContainsSubstring( "substring" ) && ContainsSubstring( "contains" ) )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
"this string contains 'abc' as a substring" ( contains: "string" and
contains: "abc" and contains: "substring" and contains: "contains" )
-------------------------------------------------------------------------------
Matchers can be (AnyOf) composed with the || operator
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
CHECK_THAT( testStringForMatching(), ContainsSubstring( "string" ) || ContainsSubstring( "different" ) || ContainsSubstring( "random" ) )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
"this string contains 'abc' as a substring" ( contains: "string" or contains:
"different" or contains: "random" )
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
CHECK_THAT( testStringForMatching2(), ContainsSubstring( "string" ) || ContainsSubstring( "different" ) || ContainsSubstring( "random" ) )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
"some completely different text that contains one common word" ( contains:
"string" or contains: "different" or contains: "random" )
-------------------------------------------------------------------------------
Matchers can be composed with both && and ||
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
CHECK_THAT( testStringForMatching(), ( ContainsSubstring( "string" ) || ContainsSubstring( "different" ) ) && ContainsSubstring( "substring" ) )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
"this string contains 'abc' as a substring" ( ( contains: "string" or
contains: "different" ) and contains: "substring" )
-------------------------------------------------------------------------------
Matchers can be composed with both && and || - failing
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>: FAILED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
CHECK_THAT( testStringForMatching(), ( ContainsSubstring( "string" ) || ContainsSubstring( "different" ) ) && ContainsSubstring( "random" ) )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
"this string contains 'abc' as a substring" ( ( contains: "string" or
contains: "different" ) and contains: "random" )
-------------------------------------------------------------------------------
Matchers can be negated (Not) with the ! operator
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
CHECK_THAT( testStringForMatching(), !ContainsSubstring( "different" ) )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
"this string contains 'abc' as a substring" not contains: "different"
-------------------------------------------------------------------------------
Matchers can be negated (Not) with the ! operator - failing
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>: FAILED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
CHECK_THAT( testStringForMatching(), !ContainsSubstring( "substring" ) )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
"this string contains 'abc' as a substring" not contains: "substring"
Mark !mayfail tests as skipped in the JUnit reporter Should fix #2116
2021-06-07 19:53:34 +02:00
-------------------------------------------------------------------------------
Mayfail test case with nested sections
A
1
-------------------------------------------------------------------------------
Condition.tests.cpp:<line number>
...............................................................................
Condition.tests.cpp:<line number>: FAILED:
-------------------------------------------------------------------------------
Mayfail test case with nested sections
A
2
-------------------------------------------------------------------------------
Condition.tests.cpp:<line number>
...............................................................................
Condition.tests.cpp:<line number>: FAILED:
-------------------------------------------------------------------------------
Mayfail test case with nested sections
B
1
-------------------------------------------------------------------------------
Condition.tests.cpp:<line number>
...............................................................................
Condition.tests.cpp:<line number>: FAILED:
-------------------------------------------------------------------------------
Mayfail test case with nested sections
B
2
-------------------------------------------------------------------------------
Condition.tests.cpp:<line number>
...............................................................................
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Mismatching exception messages failing the test
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Exception.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Exception.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE_THROWS_WITH( thisThrows(), "expected exception" )
Integrated INTERNAL_CATCH_THROWS_STR_MATCHES with new AssertionHandler
2017-08-09 01:44:30 +02:00
with expansion:
"expected exception" equals: "expected exception"
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Exception.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE_THROWS_WITH( thisThrows(), "should fail" )
with expansion:
Integrated INTERNAL_CATCH_THROWS_STR_MATCHES with new AssertionHandler
2017-08-09 01:44:30 +02:00
"expected exception" equals: "should fail"
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Add more unit tests * Call order of listeners/reporters in multireporter * Adding listeners/reporters properly updates reporter preferences
2021-12-19 15:16:56 +01:00
-------------------------------------------------------------------------------
Multireporter calls reporters and listeners in correct order
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE( records == expected )
with expansion:
{ "Hello", "world", "Goodbye", "world" }
==
{ "Hello", "world", "Goodbye", "world" }
-------------------------------------------------------------------------------
Multireporter updates ReporterPreferences properly
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE( multiReporter.getPreferences().shouldRedirectStdOut == false )
with expansion:
false == false
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE( multiReporter.getPreferences().shouldReportAllAssertions == false )
with expansion:
false == false
-------------------------------------------------------------------------------
Multireporter updates ReporterPreferences properly
Adding listeners
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE( multiReporter.getPreferences().shouldRedirectStdOut == true )
with expansion:
true == true
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE( multiReporter.getPreferences().shouldReportAllAssertions == false )
with expansion:
false == false
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE( multiReporter.getPreferences().shouldRedirectStdOut == true )
with expansion:
true == true
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE( multiReporter.getPreferences().shouldReportAllAssertions == true )
with expansion:
true == true
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE( multiReporter.getPreferences().shouldRedirectStdOut == true )
with expansion:
true == true
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE( multiReporter.getPreferences().shouldReportAllAssertions == true )
with expansion:
true == true
-------------------------------------------------------------------------------
Multireporter updates ReporterPreferences properly
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE( multiReporter.getPreferences().shouldRedirectStdOut == false )
with expansion:
false == false
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE( multiReporter.getPreferences().shouldReportAllAssertions == false )
with expansion:
false == false
-------------------------------------------------------------------------------
Multireporter updates ReporterPreferences properly
Adding reporters
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE( multiReporter.getPreferences().shouldRedirectStdOut == true )
with expansion:
true == true
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE( multiReporter.getPreferences().shouldReportAllAssertions == false )
with expansion:
false == false
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE( multiReporter.getPreferences().shouldRedirectStdOut == true )
with expansion:
true == true
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE( multiReporter.getPreferences().shouldReportAllAssertions == true )
with expansion:
true == true
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE( multiReporter.getPreferences().shouldRedirectStdOut == true )
with expansion:
true == true
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE( multiReporter.getPreferences().shouldReportAllAssertions == true )
with expansion:
true == true
Add GENERATE_COPY and GENERATE_VAR capturing generator macros
2019-03-31 14:11:10 +02:00
-------------------------------------------------------------------------------
Nested generators and captured variables
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( values > -6 )
with expansion:
3 > -6
-------------------------------------------------------------------------------
Nested generators and captured variables
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( values > -6 )
with expansion:
4 > -6
-------------------------------------------------------------------------------
Nested generators and captured variables
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( values > -6 )
with expansion:
5 > -6
-------------------------------------------------------------------------------
Nested generators and captured variables
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( values > -6 )
with expansion:
6 > -6
-------------------------------------------------------------------------------
Nested generators and captured variables
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( values > -6 )
with expansion:
-5 > -6
-------------------------------------------------------------------------------
Nested generators and captured variables
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( values > -6 )
with expansion:
-4 > -6
-------------------------------------------------------------------------------
Nested generators and captured variables
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( values > -6 )
with expansion:
90 > -6
-------------------------------------------------------------------------------
Nested generators and captured variables
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( values > -6 )
with expansion:
91 > -6
-------------------------------------------------------------------------------
Nested generators and captured variables
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( values > -6 )
with expansion:
92 > -6
-------------------------------------------------------------------------------
Nested generators and captured variables
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( values > -6 )
with expansion:
93 > -6
-------------------------------------------------------------------------------
Nested generators and captured variables
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( values > -6 )
with expansion:
94 > -6
-------------------------------------------------------------------------------
Nested generators and captured variables
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( values > -6 )
with expansion:
95 > -6
-------------------------------------------------------------------------------
Nested generators and captured variables
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( values > -6 )
with expansion:
96 > -6
-------------------------------------------------------------------------------
Nested generators and captured variables
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( values > -6 )
with expansion:
97 > -6
-------------------------------------------------------------------------------
Nested generators and captured variables
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( values > -6 )
with expansion:
98 > -6
-------------------------------------------------------------------------------
Nested generators and captured variables
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( values > -6 )
with expansion:
99 > -6
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Nice descriptive name
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: warning:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
This one ran
Fixed NoAssertions warning
2018-01-26 17:52:28 +01:00
No assertions in test case 'Nice descriptive name'
approved tests that were correct the first time (previous approvals were erroneous)
2017-04-09 21:40:01 +02:00
-------------------------------------------------------------------------------
Non-std exceptions can be translated
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Exception.tests.cpp:<line number>
approved tests that were correct the first time (previous approvals were erroneous)
2017-04-09 21:40:01 +02:00
...............................................................................
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Exception.tests.cpp:<line number>: FAILED:
approved tests that were correct the first time (previous approvals were erroneous)
2017-04-09 21:40:01 +02:00
due to unexpected exception with message:
custom exception
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Objects that evaluated in boolean contexts can be checked
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Tricky.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( True )
with expansion:
Update baselines
2017-06-06 15:07:57 +02:00
{?}
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( !False )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK_FALSE( False )
with expansion:
Update baselines
2017-06-06 15:07:57 +02:00
!{?}
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Add STATIC_REQUIRE assertion By default, it expands into a `static_assert` + `SUCCEED` pair, but it can also be deferred to runtime by defining `CATCH_CONFIG_RUNTIME_STATIC_REQUIRE`, which causes it to expand into plain old `REQUIRE`. Closes #1362 Closes #1356
2018-10-13 21:29:59 +02:00
-------------------------------------------------------------------------------
Optionally static assertions
-------------------------------------------------------------------------------
Compilation.tests.cpp:<line number>
...............................................................................
Add STATIC_CHECK and STATIC_CHECK_FALSE (#2318)
2021-11-15 00:28:27 +01:00
Compilation.tests.cpp:<line number>: PASSED:
with message:
std::is_void<void>::value
Compilation.tests.cpp:<line number>: PASSED:
with message:
!(std::is_void<int>::value)
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Compilation.tests.cpp:<line number>: PASSED:
Add STATIC_REQUIRE assertion By default, it expands into a `static_assert` + `SUCCEED` pair, but it can also be deferred to runtime by defining `CATCH_CONFIG_RUNTIME_STATIC_REQUIRE`, which causes it to expand into plain old `REQUIRE`. Closes #1362 Closes #1356
2018-10-13 21:29:59 +02:00
with message:
std::is_void<void>::value
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Compilation.tests.cpp:<line number>: PASSED:
Add STATIC_REQUIRE assertion By default, it expands into a `static_assert` + `SUCCEED` pair, but it can also be deferred to runtime by defining `CATCH_CONFIG_RUNTIME_STATIC_REQUIRE`, which causes it to expand into plain old `REQUIRE`. Closes #1362 Closes #1356
2018-10-13 21:29:59 +02:00
with message:
!(std::is_void<int>::value)
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Ordering comparison checks that should fail
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( data.int_seven > 7 )
with expansion:
7 > 7
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( data.int_seven < 7 )
with expansion:
7 < 7
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( data.int_seven > 8 )
with expansion:
7 > 8
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( data.int_seven < 6 )
with expansion:
7 < 6
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( data.int_seven < 0 )
with expansion:
7 < 0
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( data.int_seven < -1 )
with expansion:
7 < -1
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( data.int_seven >= 8 )
with expansion:
7 >= 8
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( data.int_seven <= 6 )
with expansion:
7 <= 6
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( data.float_nine_point_one < 9 )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
9.100000381f < 9
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( data.float_nine_point_one > 10 )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
9.100000381f > 10
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( data.float_nine_point_one > 9.2 )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
9.100000381f > 9.19999999999999929
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( data.str_hello > "hello" )
with expansion:
"hello" > "hello"
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( data.str_hello < "hello" )
with expansion:
"hello" < "hello"
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( data.str_hello > "hellp" )
with expansion:
"hello" > "hellp"
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( data.str_hello > "z" )
with expansion:
"hello" > "z"
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( data.str_hello < "hellm" )
with expansion:
"hello" < "hellm"
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( data.str_hello < "a" )
with expansion:
"hello" < "a"
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( data.str_hello >= "z" )
with expansion:
"hello" >= "z"
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( data.str_hello <= "a" )
with expansion:
"hello" <= "a"
-------------------------------------------------------------------------------
Ordering comparison checks that should succeed
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( data.int_seven < 8 )
with expansion:
7 < 8
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( data.int_seven > 6 )
with expansion:
7 > 6
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( data.int_seven > 0 )
with expansion:
7 > 0
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( data.int_seven > -1 )
with expansion:
7 > -1
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( data.int_seven >= 7 )
with expansion:
7 >= 7
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( data.int_seven >= 6 )
with expansion:
7 >= 6
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( data.int_seven <= 7 )
with expansion:
7 <= 7
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( data.int_seven <= 8 )
with expansion:
7 <= 8
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( data.float_nine_point_one > 9 )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
9.100000381f > 9
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( data.float_nine_point_one < 10 )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
9.100000381f < 10
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( data.float_nine_point_one < 9.2 )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
9.100000381f < 9.19999999999999929
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( data.str_hello <= "hello" )
with expansion:
"hello" <= "hello"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( data.str_hello >= "hello" )
with expansion:
"hello" >= "hello"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( data.str_hello < "hellp" )
with expansion:
"hello" < "hellp"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( data.str_hello < "zebra" )
with expansion:
"hello" < "zebra"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( data.str_hello > "hellm" )
with expansion:
"hello" > "hellm"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( data.str_hello > "a" )
with expansion:
"hello" > "a"
Introduce Catch's own RNG based on the PCG family of RNGs In the future, we will also want to introduce our own `uniform_int_distribution` and `uniform_real_distribution` to get repeatable test runs across different platforms.
2019-10-06 21:47:54 +02:00
-------------------------------------------------------------------------------
Our PCG implementation provides expected results for known seeds
Default seeded
-------------------------------------------------------------------------------
RandomNumberGeneration.tests.cpp:<line number>
...............................................................................
RandomNumberGeneration.tests.cpp:<line number>: PASSED:
REQUIRE( rng() == 0x<hex digits> )
with expansion:
4242248763 (0x<hex digits>)
==
4242248763 (0x<hex digits>)
RandomNumberGeneration.tests.cpp:<line number>: PASSED:
REQUIRE( rng() == 0x<hex digits> )
with expansion:
1867888929 (0x<hex digits>)
==
1867888929 (0x<hex digits>)
RandomNumberGeneration.tests.cpp:<line number>: PASSED:
REQUIRE( rng() == 0x<hex digits> )
with expansion:
1276619030 (0x<hex digits>)
==
1276619030 (0x<hex digits>)
RandomNumberGeneration.tests.cpp:<line number>: PASSED:
REQUIRE( rng() == 0x<hex digits> )
with expansion:
1911218783 (0x<hex digits>)
==
1911218783 (0x<hex digits>)
RandomNumberGeneration.tests.cpp:<line number>: PASSED:
REQUIRE( rng() == 0x<hex digits> )
with expansion:
1827115164 (0x<hex digits>)
==
1827115164 (0x<hex digits>)
-------------------------------------------------------------------------------
Our PCG implementation provides expected results for known seeds
Specific seed
-------------------------------------------------------------------------------
RandomNumberGeneration.tests.cpp:<line number>
...............................................................................
RandomNumberGeneration.tests.cpp:<line number>: PASSED:
REQUIRE( rng() == 0x<hex digits> )
with expansion:
1472234645 (0x<hex digits>)
==
1472234645 (0x<hex digits>)
RandomNumberGeneration.tests.cpp:<line number>: PASSED:
REQUIRE( rng() == 0x<hex digits> )
with expansion:
868832940 (0x<hex digits>)
==
868832940 (0x<hex digits>)
RandomNumberGeneration.tests.cpp:<line number>: PASSED:
REQUIRE( rng() == 0x<hex digits> )
with expansion:
570883446 (0x<hex digits>)
==
570883446 (0x<hex digits>)
RandomNumberGeneration.tests.cpp:<line number>: PASSED:
REQUIRE( rng() == 0x<hex digits> )
with expansion:
889299803 (0x<hex digits>)
==
889299803 (0x<hex digits>)
RandomNumberGeneration.tests.cpp:<line number>: PASSED:
REQUIRE( rng() == 0x<hex digits> )
with expansion:
4261393167 (0x<hex digits>)
==
4261393167 (0x<hex digits>)
RandomNumberGeneration.tests.cpp:<line number>: PASSED:
REQUIRE( rng() == 0x<hex digits> )
with expansion:
1472234645 (0x<hex digits>)
==
1472234645 (0x<hex digits>)
RandomNumberGeneration.tests.cpp:<line number>: PASSED:
REQUIRE( rng() == 0x<hex digits> )
with expansion:
868832940 (0x<hex digits>)
==
868832940 (0x<hex digits>)
RandomNumberGeneration.tests.cpp:<line number>: PASSED:
REQUIRE( rng() == 0x<hex digits> )
with expansion:
570883446 (0x<hex digits>)
==
570883446 (0x<hex digits>)
RandomNumberGeneration.tests.cpp:<line number>: PASSED:
REQUIRE( rng() == 0x<hex digits> )
with expansion:
889299803 (0x<hex digits>)
==
889299803 (0x<hex digits>)
RandomNumberGeneration.tests.cpp:<line number>: PASSED:
REQUIRE( rng() == 0x<hex digits> )
with expansion:
4261393167 (0x<hex digits>)
==
4261393167 (0x<hex digits>)
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Output from all sections is reported
one
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Message.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Message.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
explicitly with message:
Message from section one
-------------------------------------------------------------------------------
Output from all sections is reported
two
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Message.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Message.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
explicitly with message:
Message from section two
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
-------------------------------------------------------------------------------
Overloaded comma or address-of operators are not used
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THROWS_AS( ( EvilMatcher(), EvilMatcher() ), EvilCommaOperatorUsed )
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
Matchers.tests.cpp:<line number>: PASSED:
REQUIRE_THROWS_AS( &EvilMatcher(), EvilAddressOfOperatorUsed )
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_NOTHROW( EvilMatcher() || ( EvilMatcher() && !EvilMatcher() ) )
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_NOTHROW( ( EvilMatcher() && EvilMatcher() ) || !EvilMatcher() )
Feature: generic matchers (#1843) This commit extends the Matchers feature with the ability to have type-independent (e.g. templated) matchers. This is done by adding a new base type that Matchers can extend, `MatcherGenericBase`, and overloads of operators `!`, `&&` and `||` that handle matchers extending `MatcherGenericBase` in a special manner. These new matchers can also take their arguments as values and non-const references. Closes #1307 Closes #1553 Closes #1554 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-16 11:19:10 +01:00
Add parseUInt utility function There is an increasing number of places where Catch2 wants to parse strings into numbers, but being stuck in C++14 world, we do not have good stdlib facilities to do this (`strtoul` and `stoul` are both bad).
2022-10-20 15:06:26 +02:00
-------------------------------------------------------------------------------
Parse uints
proper inputs
-------------------------------------------------------------------------------
Parse.tests.cpp:<line number>
...............................................................................
Parse.tests.cpp:<line number>: PASSED:
REQUIRE( parseUInt( "0" ) == Optional<unsigned int>{ 0 } )
with expansion:
{?} == {?}
Parse.tests.cpp:<line number>: PASSED:
REQUIRE( parseUInt( "100" ) == Optional<unsigned int>{ 100 } )
with expansion:
{?} == {?}
Parse.tests.cpp:<line number>: PASSED:
REQUIRE( parseUInt( "4294967295" ) == Optional<unsigned int>{ 4294967295 } )
with expansion:
{?} == {?}
Parse.tests.cpp:<line number>: PASSED:
REQUIRE( parseUInt( "0x<hex digits>", 16 ) == Optional<unsigned int>{ 255 } )
with expansion:
{?} == {?}
-------------------------------------------------------------------------------
Parse uints
Bad inputs
-------------------------------------------------------------------------------
Parse.tests.cpp:<line number>
...............................................................................
Parse.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( parseUInt( "" ) )
with expansion:
!{?}
Parse.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( parseUInt( "!!KJHF*#" ) )
with expansion:
!{?}
Parse.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( parseUInt( "-1" ) )
with expansion:
!{?}
Parse.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( parseUInt( "4294967296" ) )
with expansion:
!{?}
Parse.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( parseUInt( "42949672964294967296429496729642949672964294967296" ) )
with expansion:
!{?}
Parse.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( parseUInt( "2 4" ) )
with expansion:
!{?}
Parse.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( parseUInt( "0x<hex digits>", 10 ) )
with expansion:
!{?}
Add more tests for various less common tag-related cases
2021-12-27 10:04:48 +01:00
-------------------------------------------------------------------------------
Parsed tags are matched case insensitive
-------------------------------------------------------------------------------
TestSpecParser.tests.cpp:<line number>
...............................................................................
TestSpecParser.tests.cpp:<line number>: PASSED:
REQUIRE( spec.hasFilters() )
with expansion:
true
TestSpecParser.tests.cpp:<line number>: PASSED:
REQUIRE( spec.getInvalidSpecs().empty() )
with expansion:
true
TestSpecParser.tests.cpp:<line number>: PASSED:
REQUIRE( spec.matches( testCase ) )
with expansion:
true
Improve shardIndex/Count cli argument parsing
2021-10-26 23:26:07 +02:00
-------------------------------------------------------------------------------
Parsing sharding-related cli flags
shard-count
-------------------------------------------------------------------------------
CmdLine.tests.cpp:<line number>
...............................................................................
CmdLine.tests.cpp:<line number>: PASSED:
CHECK( cli.parse({ "test", "--shard-count=8" }) )
with expansion:
{?}
CmdLine.tests.cpp:<line number>: PASSED:
REQUIRE( config.shardCount == 8 )
with expansion:
8 == 8
-------------------------------------------------------------------------------
Parsing sharding-related cli flags
Negative shard count reports error
-------------------------------------------------------------------------------
CmdLine.tests.cpp:<line number>
...............................................................................
CmdLine.tests.cpp:<line number>: PASSED:
CHECK_FALSE( result )
with expansion:
!{?}
CmdLine.tests.cpp:<line number>: PASSED:
Refactor parsing of shard index/count in cmdline handling This worsens the message for negative numbers a bit, but simplifies the code enough that this is still a win.
2022-10-23 00:09:17 +02:00
REQUIRE_THAT( result.errorMessage(), ContainsSubstring( "Could not parse '-1' as shard count" ) )
Improve shardIndex/Count cli argument parsing
2021-10-26 23:26:07 +02:00
with expansion:
Refactor parsing of shard index/count in cmdline handling This worsens the message for negative numbers a bit, but simplifies the code enough that this is still a win.
2022-10-23 00:09:17 +02:00
"Could not parse '-1' as shard count" contains: "Could not parse '-1' as
shard count"
Improve shardIndex/Count cli argument parsing
2021-10-26 23:26:07 +02:00
-------------------------------------------------------------------------------
Parsing sharding-related cli flags
Zero shard count reports error
-------------------------------------------------------------------------------
CmdLine.tests.cpp:<line number>
...............................................................................
CmdLine.tests.cpp:<line number>: PASSED:
CHECK_FALSE( result )
with expansion:
!{?}
CmdLine.tests.cpp:<line number>: PASSED:
Refactor parsing of shard index/count in cmdline handling This worsens the message for negative numbers a bit, but simplifies the code enough that this is still a win.
2022-10-23 00:09:17 +02:00
REQUIRE_THAT( result.errorMessage(), ContainsSubstring( "Shard count must be positive" ) )
Improve shardIndex/Count cli argument parsing
2021-10-26 23:26:07 +02:00
with expansion:
Refactor parsing of shard index/count in cmdline handling This worsens the message for negative numbers a bit, but simplifies the code enough that this is still a win.
2022-10-23 00:09:17 +02:00
"Shard count must be positive" contains: "Shard count must be positive"
Improve shardIndex/Count cli argument parsing
2021-10-26 23:26:07 +02:00
-------------------------------------------------------------------------------
Parsing sharding-related cli flags
shard-index
-------------------------------------------------------------------------------
CmdLine.tests.cpp:<line number>
...............................................................................
CmdLine.tests.cpp:<line number>: PASSED:
CHECK( cli.parse({ "test", "--shard-index=2" }) )
with expansion:
{?}
CmdLine.tests.cpp:<line number>: PASSED:
REQUIRE( config.shardIndex == 2 )
with expansion:
2 == 2
-------------------------------------------------------------------------------
Parsing sharding-related cli flags
Negative shard index reports error
-------------------------------------------------------------------------------
CmdLine.tests.cpp:<line number>
...............................................................................
CmdLine.tests.cpp:<line number>: PASSED:
CHECK_FALSE( result )
with expansion:
!{?}
CmdLine.tests.cpp:<line number>: PASSED:
Refactor parsing of shard index/count in cmdline handling This worsens the message for negative numbers a bit, but simplifies the code enough that this is still a win.
2022-10-23 00:09:17 +02:00
REQUIRE_THAT( result.errorMessage(), ContainsSubstring( "Could not parse '-12' as shard index" ) )
Improve shardIndex/Count cli argument parsing
2021-10-26 23:26:07 +02:00
with expansion:
Refactor parsing of shard index/count in cmdline handling This worsens the message for negative numbers a bit, but simplifies the code enough that this is still a win.
2022-10-23 00:09:17 +02:00
"Could not parse '-12' as shard index" contains: "Could not parse '-12' as
shard index"
Improve shardIndex/Count cli argument parsing
2021-10-26 23:26:07 +02:00
-------------------------------------------------------------------------------
Parsing sharding-related cli flags
Shard index 0 is accepted
-------------------------------------------------------------------------------
CmdLine.tests.cpp:<line number>
...............................................................................
CmdLine.tests.cpp:<line number>: PASSED:
CHECK( cli.parse({ "test", "--shard-index=0" }) )
with expansion:
{?}
CmdLine.tests.cpp:<line number>: PASSED:
REQUIRE( config.shardIndex == 0 )
with expansion:
0 == 0
Add more tests for various less common tag-related cases
2021-12-27 10:04:48 +01:00
-------------------------------------------------------------------------------
Parsing tags with non-alphabetical characters is pass-through
-------------------------------------------------------------------------------
TestSpecParser.tests.cpp:<line number>
...............................................................................
TestSpecParser.tests.cpp:<line number>: PASSED:
REQUIRE( spec.hasFilters() )
with expansion:
true
with message:
tagString := "[tag with spaces]"
TestSpecParser.tests.cpp:<line number>: PASSED:
REQUIRE( spec.getInvalidSpecs().empty() )
with expansion:
true
with message:
tagString := "[tag with spaces]"
TestSpecParser.tests.cpp:<line number>: PASSED:
REQUIRE( spec.matches( testCase ) )
with expansion:
true
with message:
tagString := "[tag with spaces]"
-------------------------------------------------------------------------------
Parsing tags with non-alphabetical characters is pass-through
-------------------------------------------------------------------------------
TestSpecParser.tests.cpp:<line number>
...............................................................................
TestSpecParser.tests.cpp:<line number>: PASSED:
REQUIRE( spec.hasFilters() )
with expansion:
true
with message:
tagString := "[I said "good day" sir!]"
TestSpecParser.tests.cpp:<line number>: PASSED:
REQUIRE( spec.getInvalidSpecs().empty() )
with expansion:
true
with message:
tagString := "[I said "good day" sir!]"
TestSpecParser.tests.cpp:<line number>: PASSED:
REQUIRE( spec.matches( testCase ) )
with expansion:
true
with message:
tagString := "[I said "good day" sir!]"
Allow enabling multiple warnings in one invocation
2021-12-18 20:48:43 +01:00
-------------------------------------------------------------------------------
Parsing warnings
NoAssertions
-------------------------------------------------------------------------------
CmdLine.tests.cpp:<line number>
...............................................................................
CmdLine.tests.cpp:<line number>: PASSED:
REQUIRE( cli.parse( { "test", "-w", "NoAssertions" } ) )
with expansion:
{?}
CmdLine.tests.cpp:<line number>: PASSED:
REQUIRE( config.warnings == WarnAbout::NoAssertions )
with expansion:
1 == 1
-------------------------------------------------------------------------------
Parsing warnings
NoTests is no longer supported
-------------------------------------------------------------------------------
CmdLine.tests.cpp:<line number>
...............................................................................
CmdLine.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( cli.parse( { "test", "-w", "NoTests" } ) )
with expansion:
!{?}
-------------------------------------------------------------------------------
Parsing warnings
Combining multiple warnings
-------------------------------------------------------------------------------
CmdLine.tests.cpp:<line number>
...............................................................................
CmdLine.tests.cpp:<line number>: PASSED:
REQUIRE( cli.parse( { "test", "--warn", "NoAssertions", "--warn", "UnmatchedTestSpec" } ) )
with expansion:
{?}
CmdLine.tests.cpp:<line number>: PASSED:
REQUIRE( config.warnings == ( WarnAbout::NoAssertions | WarnAbout::UnmatchedTestSpec ) )
with expansion:
3 == 3
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Pointers can be compared to null
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Approval tests can use Catch path fixed in env. var, and convert nullptr and __null to 0 for comparison
2017-01-09 15:12:12 +01:00
REQUIRE( p == 0 )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
Reworked stringification layer, removed Catch::toString Now the order of stringification checks is 1) StringMaker specialization 2) operator<< toString overloads and specializations have been removed.
2017-05-02 23:51:03 +02:00
0 == 0
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( p == pNULL )
with expansion:
Reworked stringification layer, removed Catch::toString Now the order of stringification checks is 1) StringMaker specialization 2) operator<< toString overloads and specializations have been removed.
2017-05-02 23:51:03 +02:00
0 == 0
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Approval tests can use Catch path fixed in env. var, and convert nullptr and __null to 0 for comparison
2017-01-09 15:12:12 +01:00
REQUIRE( p != 0 )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
Approval tests can use Catch path fixed in env. var, and convert nullptr and __null to 0 for comparison
2017-01-09 15:12:12 +01:00
0x<hex digits> != 0
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Approval tests can use Catch path fixed in env. var, and convert nullptr and __null to 0 for comparison
2017-01-09 15:12:12 +01:00
REQUIRE( cp != 0 )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
Approval tests can use Catch path fixed in env. var, and convert nullptr and __null to 0 for comparison
2017-01-09 15:12:12 +01:00
0x<hex digits> != 0
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Approval tests can use Catch path fixed in env. var, and convert nullptr and __null to 0 for comparison
2017-01-09 15:12:12 +01:00
REQUIRE( cpc != 0 )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
Approval tests can use Catch path fixed in env. var, and convert nullptr and __null to 0 for comparison
2017-01-09 15:12:12 +01:00
0x<hex digits> != 0
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Approval tests can use Catch path fixed in env. var, and convert nullptr and __null to 0 for comparison
2017-01-09 15:12:12 +01:00
REQUIRE( returnsNull() == 0 )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
Approval tests can use Catch path fixed in env. var, and convert nullptr and __null to 0 for comparison
2017-01-09 15:12:12 +01:00
{null string} == 0
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Approval tests can use Catch path fixed in env. var, and convert nullptr and __null to 0 for comparison
2017-01-09 15:12:12 +01:00
REQUIRE( returnsConstNull() == 0 )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
Approval tests can use Catch path fixed in env. var, and convert nullptr and __null to 0 for comparison
2017-01-09 15:12:12 +01:00
{null string} == 0
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Approval tests can use Catch path fixed in env. var, and convert nullptr and __null to 0 for comparison
2017-01-09 15:12:12 +01:00
REQUIRE( 0 != p )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
Approval tests can use Catch path fixed in env. var, and convert nullptr and __null to 0 for comparison
2017-01-09 15:12:12 +01:00
0 != 0x<hex digits>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Refactor custom precision in floating point stringification Also fixup tests.
2019-05-02 21:32:54 +02:00
-------------------------------------------------------------------------------
Precision of floating point stringification can be set
Floats
-------------------------------------------------------------------------------
ToStringGeneral.tests.cpp:<line number>
...............................................................................
ToStringGeneral.tests.cpp:<line number>: PASSED:
CHECK( str1.size() == 3 + 5 )
with expansion:
8 == 8
ToStringGeneral.tests.cpp:<line number>: PASSED:
REQUIRE( str2.size() == 3 + 10 )
with expansion:
13 == 13
-------------------------------------------------------------------------------
Precision of floating point stringification can be set
Double
-------------------------------------------------------------------------------
ToStringGeneral.tests.cpp:<line number>
...............................................................................
ToStringGeneral.tests.cpp:<line number>: PASSED:
CHECK( str1.size() == 2 + 5 )
with expansion:
7 == 7
ToStringGeneral.tests.cpp:<line number>: PASSED:
REQUIRE( str2.size() == 2 + 15 )
with expansion:
17 == 17
Remove unused partial specialization for MatcherMethod<T> No matcher actually uses it, and there is no good reason for it, as the best it can do for user is removing a single indirection when using the pointer inside the matcher. Given the overhead of other code that will be running during such time, it is completely meaningless. This also fixes compilation for PredicateMatcher<const char*>.
2018-11-04 00:00:36 +01:00
-------------------------------------------------------------------------------
Predicate matcher can accept const char*
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( "foo", Predicate<const char*>( []( const char* const& ) { return true; } ) )
Remove unused partial specialization for MatcherMethod<T> No matcher actually uses it, and there is no good reason for it, as the best it can do for user is removing a single indirection when using the pointer inside the matcher. Given the overhead of other code that will be running during such time, it is completely meaningless. This also fixes compilation for PredicateMatcher<const char*>.
2018-11-04 00:00:36 +01:00
with expansion:
"foo" matches undescribed predicate
Don’t assume first CL arg (exe name) is present Fixes #729
2017-03-13 12:00:58 +01:00
-------------------------------------------------------------------------------
Process can be configured on command line
empty args don't cause a crash
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
CmdLine.tests.cpp:<line number>
Don’t assume first CL arg (exe name) is present Fixes #729
2017-03-13 12:00:58 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
CHECK( result )
with expansion:
{?}
Don’t assume first CL arg (exe name) is present Fixes #729
2017-03-13 12:00:58 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Don’t assume first CL arg (exe name) is present Fixes #729
2017-03-13 12:00:58 +01:00
CHECK( config.processName == "" )
with expansion:
"" == ""
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Process can be configured on command line
default - no arguments
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
CmdLine.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
CHECK( result )
with expansion:
{?}
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Don’t assume first CL arg (exe name) is present Fixes #729
2017-03-13 12:00:58 +01:00
CHECK( config.processName == "test" )
with expansion:
"test" == "test"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( config.shouldDebugBreak == false )
with expansion:
false == false
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( config.abortAfter == -1 )
with expansion:
-1 == -1
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( config.noThrow == false )
with expansion:
false == false
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Push down handling of default reporter to Config's constructor This simplifies the handling of default reporter in console parsing, at the cost of making `Config`'s constructor responsible for more things.
2022-02-17 20:44:27 +01:00
CHECK( config.reporterSpecifications.empty() )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
Push down handling of default reporter to Config's constructor This simplifies the handling of default reporter in console parsing, at the cost of making `Config`'s constructor responsible for more things.
2022-02-17 20:44:27 +01:00
true
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
https://github.com/catchorg/Catch2/issues/1175 - don't list hidden tests by default
2018-02-08 23:18:32 +01:00
CHECK_FALSE( cfg.hasTestFilters() )
with expansion:
!false
Push down handling of default reporter to Config's constructor This simplifies the handling of default reporter in console parsing, at the cost of making `Config`'s constructor responsible for more things.
2022-02-17 20:44:27 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Integrate the new reporter specs into Catch2 This means that the CLI interface now uses the new key-value oriented reporter spec, the common reporter base creates the colour implementation based on the reporter-specific configuration, and it also stores the custom configuration options for each reporter instance. Closes #339 as it allows per-reporter forcing of ansi colour codes.
2022-04-04 21:07:04 +02:00
CHECK( cfg.getReporterSpecs().size() == 1 )
Push down handling of default reporter to Config's constructor This simplifies the handling of default reporter in console parsing, at the cost of making `Config`'s constructor responsible for more things.
2022-02-17 20:44:27 +01:00
with expansion:
1 == 1
CmdLine.tests.cpp:<line number>: PASSED:
Introduce type to handle reporter specs with defaults filled-in
2022-04-13 14:55:05 +02:00
CHECK( cfg.getReporterSpecs()[0] == Catch::ReporterSpec{ expectedReporter, {}, {}, {} } )
with expansion:
{?} == {?}
CmdLine.tests.cpp:<line number>: PASSED:
CHECK( cfg.getProcessedReporterSpecs().size() == 1 )
with expansion:
1 == 1
CmdLine.tests.cpp:<line number>: PASSED:
CHECK( cfg.getProcessedReporterSpecs()[0] == Catch::ProcessedReporterSpec{ expectedReporter, std::string{}, Catch::ColourMode::PlatformDefault, {} } )
Push down handling of default reporter to Config's constructor This simplifies the handling of default reporter in console parsing, at the cost of making `Config`'s constructor responsible for more things.
2022-02-17 20:44:27 +01:00
with expansion:
Integrate the new reporter specs into Catch2 This means that the CLI interface now uses the new key-value oriented reporter spec, the common reporter base creates the colour implementation based on the reporter-specific configuration, and it also stores the custom configuration options for each reporter instance. Closes #339 as it allows per-reporter forcing of ansi colour codes.
2022-04-04 21:07:04 +02:00
{?} == {?}
Push down handling of default reporter to Config's constructor This simplifies the handling of default reporter in console parsing, at the cost of making `Config`'s constructor responsible for more things.
2022-02-17 20:44:27 +01:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Process can be configured on command line
test lists
Deprecated description in SECTION (still accepts it, for now, but doesn't use it anywhere)
2018-06-25 20:04:29 +02:00
Specify one test case using
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
CmdLine.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
CHECK( result )
with expansion:
{?}
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
https://github.com/catchorg/Catch2/issues/1175 - don't list hidden tests by default
2018-02-08 23:18:32 +01:00
REQUIRE( cfg.hasTestFilters() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Do not copy around TestCaseInfo Now a `TEST_CASE` macro should create a single TestCaseInfo and then it should never be copied around. This, together with latter changes, should significantly decrease the number of allocations made before `main` is even entered.
2019-11-04 21:35:57 +01:00
REQUIRE( cfg.testSpec().matches(*fakeTestCase("notIncluded")) == false )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
false == false
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Do not copy around TestCaseInfo Now a `TEST_CASE` macro should create a single TestCaseInfo and then it should never be copied around. This, together with latter changes, should significantly decrease the number of allocations made before `main` is even entered.
2019-11-04 21:35:57 +01:00
REQUIRE( cfg.testSpec().matches(*fakeTestCase("test1")) )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
true
-------------------------------------------------------------------------------
Process can be configured on command line
test lists
Specify one test case exclusion using exclude:
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
CmdLine.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
CHECK( result )
with expansion:
{?}
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
https://github.com/catchorg/Catch2/issues/1175 - don't list hidden tests by default
2018-02-08 23:18:32 +01:00
REQUIRE( cfg.hasTestFilters() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Do not copy around TestCaseInfo Now a `TEST_CASE` macro should create a single TestCaseInfo and then it should never be copied around. This, together with latter changes, should significantly decrease the number of allocations made before `main` is even entered.
2019-11-04 21:35:57 +01:00
REQUIRE( cfg.testSpec().matches(*fakeTestCase("test1")) == false )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
false == false
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Do not copy around TestCaseInfo Now a `TEST_CASE` macro should create a single TestCaseInfo and then it should never be copied around. This, together with latter changes, should significantly decrease the number of allocations made before `main` is even entered.
2019-11-04 21:35:57 +01:00
REQUIRE( cfg.testSpec().matches(*fakeTestCase("alwaysIncluded")) )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
true
-------------------------------------------------------------------------------
Process can be configured on command line
test lists
Specify one test case exclusion using ~
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
CmdLine.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
CHECK( result )
with expansion:
{?}
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
https://github.com/catchorg/Catch2/issues/1175 - don't list hidden tests by default
2018-02-08 23:18:32 +01:00
REQUIRE( cfg.hasTestFilters() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Do not copy around TestCaseInfo Now a `TEST_CASE` macro should create a single TestCaseInfo and then it should never be copied around. This, together with latter changes, should significantly decrease the number of allocations made before `main` is even entered.
2019-11-04 21:35:57 +01:00
REQUIRE( cfg.testSpec().matches(*fakeTestCase("test1")) == false )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
false == false
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Do not copy around TestCaseInfo Now a `TEST_CASE` macro should create a single TestCaseInfo and then it should never be copied around. This, together with latter changes, should significantly decrease the number of allocations made before `main` is even entered.
2019-11-04 21:35:57 +01:00
REQUIRE( cfg.testSpec().matches(*fakeTestCase("alwaysIncluded")) )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
true
-------------------------------------------------------------------------------
Process can be configured on command line
reporter
-r/console
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
CmdLine.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Add support for multiple parallel reporters This requires a bunch of different changes across the reporter subsystem. * We need to handle multiple reporters and their differing preferences in `ListeningReporter`, e.g. what to do when we mix reporters that capture and don't capture stdout. * We need to change how the reporter is given output and how we parse reporter's output destination from CLI. * Approval tests need to handle multireporter option
2021-02-06 20:12:07 +01:00
CHECK( result )
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
with expansion:
{?}
Add support for multiple parallel reporters This requires a bunch of different changes across the reporter subsystem. * We need to handle multiple reporters and their differing preferences in `ListeningReporter`, e.g. what to do when we mix reporters that capture and don't capture stdout. * We need to change how the reporter is given output and how we parse reporter's output destination from CLI. * Approval tests need to handle multireporter option
2021-02-06 20:12:07 +01:00
with message:
result.errorMessage() := ""
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Integrate the new reporter specs into Catch2 This means that the CLI interface now uses the new key-value oriented reporter spec, the common reporter base creates the colour implementation based on the reporter-specific configuration, and it also stores the custom configuration options for each reporter instance. Closes #339 as it allows per-reporter forcing of ansi colour codes.
2022-04-04 21:07:04 +02:00
REQUIRE( config.reporterSpecifications == vec_Specs{ { "console", {}, {}, {} } } )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
Integrate the new reporter specs into Catch2 This means that the CLI interface now uses the new key-value oriented reporter spec, the common reporter base creates the colour implementation based on the reporter-specific configuration, and it also stores the custom configuration options for each reporter instance. Closes #339 as it allows per-reporter forcing of ansi colour codes.
2022-04-04 21:07:04 +02:00
{ {?} } == { {?} }
Add support for multiple parallel reporters This requires a bunch of different changes across the reporter subsystem. * We need to handle multiple reporters and their differing preferences in `ListeningReporter`, e.g. what to do when we mix reporters that capture and don't capture stdout. * We need to change how the reporter is given output and how we parse reporter's output destination from CLI. * Approval tests need to handle multireporter option
2021-02-06 20:12:07 +01:00
with message:
result.errorMessage() := ""
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Process can be configured on command line
reporter
-r/xml
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
CmdLine.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Add support for multiple parallel reporters This requires a bunch of different changes across the reporter subsystem. * We need to handle multiple reporters and their differing preferences in `ListeningReporter`, e.g. what to do when we mix reporters that capture and don't capture stdout. * We need to change how the reporter is given output and how we parse reporter's output destination from CLI. * Approval tests need to handle multireporter option
2021-02-06 20:12:07 +01:00
CHECK( result )
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
with expansion:
{?}
Add support for multiple parallel reporters This requires a bunch of different changes across the reporter subsystem. * We need to handle multiple reporters and their differing preferences in `ListeningReporter`, e.g. what to do when we mix reporters that capture and don't capture stdout. * We need to change how the reporter is given output and how we parse reporter's output destination from CLI. * Approval tests need to handle multireporter option
2021-02-06 20:12:07 +01:00
with message:
result.errorMessage() := ""
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Integrate the new reporter specs into Catch2 This means that the CLI interface now uses the new key-value oriented reporter spec, the common reporter base creates the colour implementation based on the reporter-specific configuration, and it also stores the custom configuration options for each reporter instance. Closes #339 as it allows per-reporter forcing of ansi colour codes.
2022-04-04 21:07:04 +02:00
REQUIRE( config.reporterSpecifications == vec_Specs{ { "xml", {}, {}, {} } } )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
Integrate the new reporter specs into Catch2 This means that the CLI interface now uses the new key-value oriented reporter spec, the common reporter base creates the colour implementation based on the reporter-specific configuration, and it also stores the custom configuration options for each reporter instance. Closes #339 as it allows per-reporter forcing of ansi colour codes.
2022-04-04 21:07:04 +02:00
{ {?} } == { {?} }
Add support for multiple parallel reporters This requires a bunch of different changes across the reporter subsystem. * We need to handle multiple reporters and their differing preferences in `ListeningReporter`, e.g. what to do when we mix reporters that capture and don't capture stdout. * We need to change how the reporter is given output and how we parse reporter's output destination from CLI. * Approval tests need to handle multireporter option
2021-02-06 20:12:07 +01:00
with message:
result.errorMessage() := ""
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Process can be configured on command line
reporter
Allow only 1 reporter at a time
2018-04-07 12:05:29 +02:00
--reporter/junit
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
CmdLine.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Add support for multiple parallel reporters This requires a bunch of different changes across the reporter subsystem. * We need to handle multiple reporters and their differing preferences in `ListeningReporter`, e.g. what to do when we mix reporters that capture and don't capture stdout. * We need to change how the reporter is given output and how we parse reporter's output destination from CLI. * Approval tests need to handle multireporter option
2021-02-06 20:12:07 +01:00
CHECK( result )
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
with expansion:
{?}
Add support for multiple parallel reporters This requires a bunch of different changes across the reporter subsystem. * We need to handle multiple reporters and their differing preferences in `ListeningReporter`, e.g. what to do when we mix reporters that capture and don't capture stdout. * We need to change how the reporter is given output and how we parse reporter's output destination from CLI. * Approval tests need to handle multireporter option
2021-02-06 20:12:07 +01:00
with message:
result.errorMessage() := ""
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Integrate the new reporter specs into Catch2 This means that the CLI interface now uses the new key-value oriented reporter spec, the common reporter base creates the colour implementation based on the reporter-specific configuration, and it also stores the custom configuration options for each reporter instance. Closes #339 as it allows per-reporter forcing of ansi colour codes.
2022-04-04 21:07:04 +02:00
REQUIRE( config.reporterSpecifications == vec_Specs{ { "junit", {}, {}, {} } } )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
Integrate the new reporter specs into Catch2 This means that the CLI interface now uses the new key-value oriented reporter spec, the common reporter base creates the colour implementation based on the reporter-specific configuration, and it also stores the custom configuration options for each reporter instance. Closes #339 as it allows per-reporter forcing of ansi colour codes.
2022-04-04 21:07:04 +02:00
{ {?} } == { {?} }
Add support for multiple parallel reporters This requires a bunch of different changes across the reporter subsystem. * We need to handle multiple reporters and their differing preferences in `ListeningReporter`, e.g. what to do when we mix reporters that capture and don't capture stdout. * We need to change how the reporter is given output and how we parse reporter's output destination from CLI. * Approval tests need to handle multireporter option
2021-02-06 20:12:07 +01:00
with message:
result.errorMessage() := ""
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Process can be configured on command line
reporter
Add support for multiple parallel reporters This requires a bunch of different changes across the reporter subsystem. * We need to handle multiple reporters and their differing preferences in `ListeningReporter`, e.g. what to do when we mix reporters that capture and don't capture stdout. * We need to change how the reporter is given output and how we parse reporter's output destination from CLI. * Approval tests need to handle multireporter option
2021-02-06 20:12:07 +01:00
must match one of the available ones
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
CmdLine.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Add support for multiple parallel reporters This requires a bunch of different changes across the reporter subsystem. * We need to handle multiple reporters and their differing preferences in `ListeningReporter`, e.g. what to do when we mix reporters that capture and don't capture stdout. * We need to change how the reporter is given output and how we parse reporter's output destination from CLI. * Approval tests need to handle multireporter option
2021-02-06 20:12:07 +01:00
CHECK( !result )
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
with expansion:
Add support for multiple parallel reporters This requires a bunch of different changes across the reporter subsystem. * We need to handle multiple reporters and their differing preferences in `ListeningReporter`, e.g. what to do when we mix reporters that capture and don't capture stdout. * We need to change how the reporter is given output and how we parse reporter's output destination from CLI. * Approval tests need to handle multireporter option
2021-02-06 20:12:07 +01:00
true
CmdLine.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( result.errorMessage(), ContainsSubstring("Unrecognized reporter") )
with expansion:
"Unrecognized reporter, 'unsupported'. Check available with --list-reporters"
contains: "Unrecognized reporter"
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Catch's CLI now checks whether requested reporter exists Fixes #1351
2018-10-22 15:59:01 +02:00
-------------------------------------------------------------------------------
Process can be configured on command line
reporter
Add support for multiple parallel reporters This requires a bunch of different changes across the reporter subsystem. * We need to handle multiple reporters and their differing preferences in `ListeningReporter`, e.g. what to do when we mix reporters that capture and don't capture stdout. * We need to change how the reporter is given output and how we parse reporter's output destination from CLI. * Approval tests need to handle multireporter option
2021-02-06 20:12:07 +01:00
With output file
-------------------------------------------------------------------------------
CmdLine.tests.cpp:<line number>
...............................................................................
CmdLine.tests.cpp:<line number>: PASSED:
CHECK( result )
with expansion:
{?}
with message:
result.errorMessage() := ""
CmdLine.tests.cpp:<line number>: PASSED:
Integrate the new reporter specs into Catch2 This means that the CLI interface now uses the new key-value oriented reporter spec, the common reporter base creates the colour implementation based on the reporter-specific configuration, and it also stores the custom configuration options for each reporter instance. Closes #339 as it allows per-reporter forcing of ansi colour codes.
2022-04-04 21:07:04 +02:00
REQUIRE( config.reporterSpecifications == vec_Specs{ { "console", "out.txt"s, {}, {} } } )
Add support for multiple parallel reporters This requires a bunch of different changes across the reporter subsystem. * We need to handle multiple reporters and their differing preferences in `ListeningReporter`, e.g. what to do when we mix reporters that capture and don't capture stdout. * We need to change how the reporter is given output and how we parse reporter's output destination from CLI. * Approval tests need to handle multireporter option
2021-02-06 20:12:07 +01:00
with expansion:
Integrate the new reporter specs into Catch2 This means that the CLI interface now uses the new key-value oriented reporter spec, the common reporter base creates the colour implementation based on the reporter-specific configuration, and it also stores the custom configuration options for each reporter instance. Closes #339 as it allows per-reporter forcing of ansi colour codes.
2022-04-04 21:07:04 +02:00
{ {?} } == { {?} }
Add support for multiple parallel reporters This requires a bunch of different changes across the reporter subsystem. * We need to handle multiple reporters and their differing preferences in `ListeningReporter`, e.g. what to do when we mix reporters that capture and don't capture stdout. * We need to change how the reporter is given output and how we parse reporter's output destination from CLI. * Approval tests need to handle multireporter option
2021-02-06 20:12:07 +01:00
with message:
result.errorMessage() := ""
-------------------------------------------------------------------------------
Process can be configured on command line
reporter
With Windows-like absolute path as output file
-------------------------------------------------------------------------------
CmdLine.tests.cpp:<line number>
...............................................................................
CmdLine.tests.cpp:<line number>: PASSED:
CHECK( result )
with expansion:
{?}
with message:
result.errorMessage() := ""
CmdLine.tests.cpp:<line number>: PASSED:
Integrate the new reporter specs into Catch2 This means that the CLI interface now uses the new key-value oriented reporter spec, the common reporter base creates the colour implementation based on the reporter-specific configuration, and it also stores the custom configuration options for each reporter instance. Closes #339 as it allows per-reporter forcing of ansi colour codes.
2022-04-04 21:07:04 +02:00
REQUIRE( config.reporterSpecifications == vec_Specs{ { "console", "C:\\Temp\\out.txt"s, {}, {} } } )
Add support for multiple parallel reporters This requires a bunch of different changes across the reporter subsystem. * We need to handle multiple reporters and their differing preferences in `ListeningReporter`, e.g. what to do when we mix reporters that capture and don't capture stdout. * We need to change how the reporter is given output and how we parse reporter's output destination from CLI. * Approval tests need to handle multireporter option
2021-02-06 20:12:07 +01:00
with expansion:
Integrate the new reporter specs into Catch2 This means that the CLI interface now uses the new key-value oriented reporter spec, the common reporter base creates the colour implementation based on the reporter-specific configuration, and it also stores the custom configuration options for each reporter instance. Closes #339 as it allows per-reporter forcing of ansi colour codes.
2022-04-04 21:07:04 +02:00
{ {?} } == { {?} }
Add support for multiple parallel reporters This requires a bunch of different changes across the reporter subsystem. * We need to handle multiple reporters and their differing preferences in `ListeningReporter`, e.g. what to do when we mix reporters that capture and don't capture stdout. * We need to change how the reporter is given output and how we parse reporter's output destination from CLI. * Approval tests need to handle multireporter option
2021-02-06 20:12:07 +01:00
with message:
result.errorMessage() := ""
-------------------------------------------------------------------------------
Process can be configured on command line
reporter
Multiple reporters
All with output files
-------------------------------------------------------------------------------
CmdLine.tests.cpp:<line number>
...............................................................................
CmdLine.tests.cpp:<line number>: PASSED:
Integrate the new reporter specs into Catch2 This means that the CLI interface now uses the new key-value oriented reporter spec, the common reporter base creates the colour implementation based on the reporter-specific configuration, and it also stores the custom configuration options for each reporter instance. Closes #339 as it allows per-reporter forcing of ansi colour codes.
2022-04-04 21:07:04 +02:00
CHECK( cli.parse({ "test", "-r", "xml::out=output.xml", "-r", "junit::out=output-junit.xml" }) )
Add support for multiple parallel reporters This requires a bunch of different changes across the reporter subsystem. * We need to handle multiple reporters and their differing preferences in `ListeningReporter`, e.g. what to do when we mix reporters that capture and don't capture stdout. * We need to change how the reporter is given output and how we parse reporter's output destination from CLI. * Approval tests need to handle multireporter option
2021-02-06 20:12:07 +01:00
with expansion:
{?}
CmdLine.tests.cpp:<line number>: PASSED:
Integrate the new reporter specs into Catch2 This means that the CLI interface now uses the new key-value oriented reporter spec, the common reporter base creates the colour implementation based on the reporter-specific configuration, and it also stores the custom configuration options for each reporter instance. Closes #339 as it allows per-reporter forcing of ansi colour codes.
2022-04-04 21:07:04 +02:00
REQUIRE( config.reporterSpecifications == vec_Specs{ { "xml", "output.xml"s, {}, {} }, { "junit", "output-junit.xml"s, {}, {} } } )
Add support for multiple parallel reporters This requires a bunch of different changes across the reporter subsystem. * We need to handle multiple reporters and their differing preferences in `ListeningReporter`, e.g. what to do when we mix reporters that capture and don't capture stdout. * We need to change how the reporter is given output and how we parse reporter's output destination from CLI. * Approval tests need to handle multireporter option
2021-02-06 20:12:07 +01:00
with expansion:
Integrate the new reporter specs into Catch2 This means that the CLI interface now uses the new key-value oriented reporter spec, the common reporter base creates the colour implementation based on the reporter-specific configuration, and it also stores the custom configuration options for each reporter instance. Closes #339 as it allows per-reporter forcing of ansi colour codes.
2022-04-04 21:07:04 +02:00
{ {?}, {?} } == { {?}, {?} }
Add support for multiple parallel reporters This requires a bunch of different changes across the reporter subsystem. * We need to handle multiple reporters and their differing preferences in `ListeningReporter`, e.g. what to do when we mix reporters that capture and don't capture stdout. * We need to change how the reporter is given output and how we parse reporter's output destination from CLI. * Approval tests need to handle multireporter option
2021-02-06 20:12:07 +01:00
-------------------------------------------------------------------------------
Process can be configured on command line
reporter
Multiple reporters
Mixed output files and default output
-------------------------------------------------------------------------------
CmdLine.tests.cpp:<line number>
...............................................................................
CmdLine.tests.cpp:<line number>: PASSED:
Integrate the new reporter specs into Catch2 This means that the CLI interface now uses the new key-value oriented reporter spec, the common reporter base creates the colour implementation based on the reporter-specific configuration, and it also stores the custom configuration options for each reporter instance. Closes #339 as it allows per-reporter forcing of ansi colour codes.
2022-04-04 21:07:04 +02:00
CHECK( cli.parse({ "test", "-r", "xml::out=output.xml", "-r", "console" }) )
Add support for multiple parallel reporters This requires a bunch of different changes across the reporter subsystem. * We need to handle multiple reporters and their differing preferences in `ListeningReporter`, e.g. what to do when we mix reporters that capture and don't capture stdout. * We need to change how the reporter is given output and how we parse reporter's output destination from CLI. * Approval tests need to handle multireporter option
2021-02-06 20:12:07 +01:00
with expansion:
{?}
CmdLine.tests.cpp:<line number>: PASSED:
Integrate the new reporter specs into Catch2 This means that the CLI interface now uses the new key-value oriented reporter spec, the common reporter base creates the colour implementation based on the reporter-specific configuration, and it also stores the custom configuration options for each reporter instance. Closes #339 as it allows per-reporter forcing of ansi colour codes.
2022-04-04 21:07:04 +02:00
REQUIRE( config.reporterSpecifications == vec_Specs{ { "xml", "output.xml"s, {}, {} }, { "console", {}, {}, {} } } )
Add support for multiple parallel reporters This requires a bunch of different changes across the reporter subsystem. * We need to handle multiple reporters and their differing preferences in `ListeningReporter`, e.g. what to do when we mix reporters that capture and don't capture stdout. * We need to change how the reporter is given output and how we parse reporter's output destination from CLI. * Approval tests need to handle multireporter option
2021-02-06 20:12:07 +01:00
with expansion:
Integrate the new reporter specs into Catch2 This means that the CLI interface now uses the new key-value oriented reporter spec, the common reporter base creates the colour implementation based on the reporter-specific configuration, and it also stores the custom configuration options for each reporter instance. Closes #339 as it allows per-reporter forcing of ansi colour codes.
2022-04-04 21:07:04 +02:00
{ {?}, {?} } == { {?}, {?} }
Add support for multiple parallel reporters This requires a bunch of different changes across the reporter subsystem. * We need to handle multiple reporters and their differing preferences in `ListeningReporter`, e.g. what to do when we mix reporters that capture and don't capture stdout. * We need to change how the reporter is given output and how we parse reporter's output destination from CLI. * Approval tests need to handle multireporter option
2021-02-06 20:12:07 +01:00
-------------------------------------------------------------------------------
Process can be configured on command line
reporter
Multiple reporters
cannot have multiple reporters with default output
-------------------------------------------------------------------------------
CmdLine.tests.cpp:<line number>
...............................................................................
CmdLine.tests.cpp:<line number>: PASSED:
CHECK( !result )
with expansion:
true
CmdLine.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( result.errorMessage(), ContainsSubstring("Only one reporter may have unspecified output file.") )
with expansion:
"Only one reporter may have unspecified output file." contains: "Only one
reporter may have unspecified output file."
Catch's CLI now checks whether requested reporter exists Fixes #1351
2018-10-22 15:59:01 +02:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Process can be configured on command line
debugger
-b
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
CmdLine.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
CHECK( cli.parse({"test", "-b"}) )
with expansion:
{?}
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( config.shouldDebugBreak == true )
with expansion:
true == true
-------------------------------------------------------------------------------
Process can be configured on command line
debugger
--break
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
CmdLine.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
CHECK( cli.parse({"test", "--break"}) )
with expansion:
{?}
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( config.shouldDebugBreak )
with expansion:
true
-------------------------------------------------------------------------------
Process can be configured on command line
abort
-a aborts after first failure
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
CmdLine.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
CHECK( cli.parse({"test", "-a"}) )
with expansion:
{?}
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( config.abortAfter == 1 )
with expansion:
1 == 1
-------------------------------------------------------------------------------
Process can be configured on command line
abort
-x 2 aborts after two failures
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
CmdLine.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
CHECK( cli.parse({"test", "-x", "2"}) )
with expansion:
{?}
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( config.abortAfter == 2 )
with expansion:
2 == 2
-------------------------------------------------------------------------------
Process can be configured on command line
abort
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
-x must be numeric
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
CmdLine.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
CHECK( !result )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
true
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( result.errorMessage(), ContainsSubstring("convert") && ContainsSubstring("oops") )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
"Unable to convert 'oops' to destination type" ( contains: "convert" and
contains: "oops" )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Add command line option 'never' to --wait-for-keypress (#1866) Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-15 20:42:57 +01:00
-------------------------------------------------------------------------------
Process can be configured on command line
abort
wait-for-keypress
Accepted options
-------------------------------------------------------------------------------
CmdLine.tests.cpp:<line number>
...............................................................................
CmdLine.tests.cpp:<line number>: PASSED:
CHECK( cli.parse({"test", "--wait-for-keypress", std::get<0>(input)}) )
with expansion:
{?}
CmdLine.tests.cpp:<line number>: PASSED:
REQUIRE( config.waitForKeypress == std::get<1>(input) )
with expansion:
0 == 0
-------------------------------------------------------------------------------
Process can be configured on command line
abort
wait-for-keypress
Accepted options
-------------------------------------------------------------------------------
CmdLine.tests.cpp:<line number>
...............................................................................
CmdLine.tests.cpp:<line number>: PASSED:
CHECK( cli.parse({"test", "--wait-for-keypress", std::get<0>(input)}) )
with expansion:
{?}
CmdLine.tests.cpp:<line number>: PASSED:
REQUIRE( config.waitForKeypress == std::get<1>(input) )
with expansion:
1 == 1
-------------------------------------------------------------------------------
Process can be configured on command line
abort
wait-for-keypress
Accepted options
-------------------------------------------------------------------------------
CmdLine.tests.cpp:<line number>
...............................................................................
CmdLine.tests.cpp:<line number>: PASSED:
CHECK( cli.parse({"test", "--wait-for-keypress", std::get<0>(input)}) )
with expansion:
{?}
CmdLine.tests.cpp:<line number>: PASSED:
REQUIRE( config.waitForKeypress == std::get<1>(input) )
with expansion:
2 == 2
-------------------------------------------------------------------------------
Process can be configured on command line
abort
wait-for-keypress
Accepted options
-------------------------------------------------------------------------------
CmdLine.tests.cpp:<line number>
...............................................................................
CmdLine.tests.cpp:<line number>: PASSED:
CHECK( cli.parse({"test", "--wait-for-keypress", std::get<0>(input)}) )
with expansion:
{?}
CmdLine.tests.cpp:<line number>: PASSED:
REQUIRE( config.waitForKeypress == std::get<1>(input) )
with expansion:
3 == 3
-------------------------------------------------------------------------------
Process can be configured on command line
abort
wait-for-keypress
invalid options are reported
-------------------------------------------------------------------------------
CmdLine.tests.cpp:<line number>
...............................................................................
CmdLine.tests.cpp:<line number>: PASSED:
CHECK( !result )
with expansion:
true
CmdLine.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( result.errorMessage(), ContainsSubstring("never") && ContainsSubstring("both") )
Add command line option 'never' to --wait-for-keypress (#1866) Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2020-02-15 20:42:57 +01:00
with expansion:
"keypress argument must be one of: never, start, exit or both. 'sometimes'
not recognised" ( contains: "never" and contains: "both" )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Process can be configured on command line
nothrow
-e
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
CmdLine.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
CHECK( cli.parse({"test", "-e"}) )
with expansion:
{?}
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
REQUIRE( config.noThrow )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
true
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Process can be configured on command line
nothrow
--nothrow
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
CmdLine.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
CHECK( cli.parse({"test", "--nothrow"}) )
with expansion:
{?}
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
REQUIRE( config.noThrow )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
true
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Process can be configured on command line
output filename
-o filename
Added support for manually registering test functions. As discussed in #421
2015-11-20 17:54:07 +01:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
CmdLine.tests.cpp:<line number>
Added support for manually registering test functions. As discussed in #421
2015-11-20 17:54:07 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
CHECK( cli.parse({"test", "-o", "filename.ext"}) )
with expansion:
{?}
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Add support for multiple parallel reporters This requires a bunch of different changes across the reporter subsystem. * We need to handle multiple reporters and their differing preferences in `ListeningReporter`, e.g. what to do when we mix reporters that capture and don't capture stdout. * We need to change how the reporter is given output and how we parse reporter's output destination from CLI. * Approval tests need to handle multireporter option
2021-02-06 20:12:07 +01:00
REQUIRE( config.defaultOutputFilename == "filename.ext" )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
"filename.ext" == "filename.ext"
Added support for manually registering test functions. As discussed in #421
2015-11-20 17:54:07 +01:00
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Process can be configured on command line
output filename
--out
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
CmdLine.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
CHECK( cli.parse({"test", "--out", "filename.ext"}) )
with expansion:
{?}
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Add support for multiple parallel reporters This requires a bunch of different changes across the reporter subsystem. * We need to handle multiple reporters and their differing preferences in `ListeningReporter`, e.g. what to do when we mix reporters that capture and don't capture stdout. * We need to change how the reporter is given output and how we parse reporter's output destination from CLI. * Approval tests need to handle multireporter option
2021-02-06 20:12:07 +01:00
REQUIRE( config.defaultOutputFilename == "filename.ext" )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"filename.ext" == "filename.ext"
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Process can be configured on command line
combinations
Single character flags can be combined
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
CmdLine.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
CHECK( cli.parse({"test", "-abe"}) )
with expansion:
{?}
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( config.abortAfter == 1 )
with expansion:
1 == 1
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( config.shouldDebugBreak )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( config.noThrow == true )
with expansion:
true == true
-------------------------------------------------------------------------------
Process can be configured on command line
use-colour
without option
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
CmdLine.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
CHECK( cli.parse({"test"}) )
with expansion:
{?}
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Rename config::colourMode to config::defaultConfigMode This describes the actual intention much better.
2022-04-06 21:56:29 +02:00
REQUIRE( config.defaultColourMode == ColourMode::PlatformDefault )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
0 == 0
-------------------------------------------------------------------------------
Process can be configured on command line
use-colour
auto
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
CmdLine.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Refactor colour handling to prepare for per-reporter colour modes This includes always compiling the ANSI and None colour implementations, as they don't need to touch any platform specific APIs, and removing their respective compile-time configuration options. Because the Win32 colour implementation requires Win32-specific APIs, it is still hidden behind a compile-time toggle, `CATCH_CONFIG_COLOUR_WIN32` (renamed from `..._COLOUR_WINDOWS`). The commandline options for colours were also changed. The option now uses different name, and allows to select between different implementations, rather than changing whether the compiled-in colour implementation is used through "yes/no/default" options.
2022-03-27 23:35:41 +02:00
CHECK( cli.parse( { "test", "--colour-mode", "default" } ) )
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
with expansion:
{?}
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Rename config::colourMode to config::defaultConfigMode This describes the actual intention much better.
2022-04-06 21:56:29 +02:00
REQUIRE( config.defaultColourMode == ColourMode::PlatformDefault )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
0 == 0
-------------------------------------------------------------------------------
Process can be configured on command line
use-colour
yes
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
CmdLine.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Refactor colour handling to prepare for per-reporter colour modes This includes always compiling the ANSI and None colour implementations, as they don't need to touch any platform specific APIs, and removing their respective compile-time configuration options. Because the Win32 colour implementation requires Win32-specific APIs, it is still hidden behind a compile-time toggle, `CATCH_CONFIG_COLOUR_WIN32` (renamed from `..._COLOUR_WINDOWS`). The commandline options for colours were also changed. The option now uses different name, and allows to select between different implementations, rather than changing whether the compiled-in colour implementation is used through "yes/no/default" options.
2022-03-27 23:35:41 +02:00
CHECK( cli.parse({"test", "--colour-mode", "ansi"}) )
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
with expansion:
{?}
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Rename config::colourMode to config::defaultConfigMode This describes the actual intention much better.
2022-04-06 21:56:29 +02:00
REQUIRE( config.defaultColourMode == ColourMode::ANSI )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
1 == 1
-------------------------------------------------------------------------------
Process can be configured on command line
use-colour
no
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
CmdLine.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Refactor colour handling to prepare for per-reporter colour modes This includes always compiling the ANSI and None colour implementations, as they don't need to touch any platform specific APIs, and removing their respective compile-time configuration options. Because the Win32 colour implementation requires Win32-specific APIs, it is still hidden behind a compile-time toggle, `CATCH_CONFIG_COLOUR_WIN32` (renamed from `..._COLOUR_WINDOWS`). The commandline options for colours were also changed. The option now uses different name, and allows to select between different implementations, rather than changing whether the compiled-in colour implementation is used through "yes/no/default" options.
2022-03-27 23:35:41 +02:00
CHECK( cli.parse({"test", "--colour-mode", "none"}) )
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
with expansion:
{?}
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Rename config::colourMode to config::defaultConfigMode This describes the actual intention much better.
2022-04-06 21:56:29 +02:00
REQUIRE( config.defaultColourMode == ColourMode::None )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
Refactor colour handling to prepare for per-reporter colour modes This includes always compiling the ANSI and None colour implementations, as they don't need to touch any platform specific APIs, and removing their respective compile-time configuration options. Because the Win32 colour implementation requires Win32-specific APIs, it is still hidden behind a compile-time toggle, `CATCH_CONFIG_COLOUR_WIN32` (renamed from `..._COLOUR_WINDOWS`). The commandline options for colours were also changed. The option now uses different name, and allows to select between different implementations, rather than changing whether the compiled-in colour implementation is used through "yes/no/default" options.
2022-03-27 23:35:41 +02:00
3 == 3
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Process can be configured on command line
use-colour
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
error
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
CmdLine.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
CHECK( !result )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
CmdLine.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
CHECK_THAT( result.errorMessage(), ContainsSubstring( "colour mode must be one of" ) )
Rebased following Clara changes
2017-06-13 00:13:27 +02:00
with expansion:
Cleanup ColourMode parsing in CLI
2022-04-04 15:38:25 +02:00
"colour mode must be one of: default, ansi, win32, or none. 'wrong' is not
Refactor colour handling to prepare for per-reporter colour modes This includes always compiling the ANSI and None colour implementations, as they don't need to touch any platform specific APIs, and removing their respective compile-time configuration options. Because the Win32 colour implementation requires Win32-specific APIs, it is still hidden behind a compile-time toggle, `CATCH_CONFIG_COLOUR_WIN32` (renamed from `..._COLOUR_WINDOWS`). The commandline options for colours were also changed. The option now uses different name, and allows to select between different implementations, rather than changing whether the compiled-in colour implementation is used through "yes/no/default" options.
2022-03-27 23:35:41 +02:00
recognised" contains: "colour mode must be one of"
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Add an extra test for benchmarking macros Also updated baselines
2019-06-02 13:19:09 +02:00
-------------------------------------------------------------------------------
Process can be configured on command line
Benchmark options
samples
-------------------------------------------------------------------------------
CmdLine.tests.cpp:<line number>
...............................................................................
CmdLine.tests.cpp:<line number>: PASSED:
CHECK( cli.parse({ "test", "--benchmark-samples=200" }) )
with expansion:
{?}
CmdLine.tests.cpp:<line number>: PASSED:
REQUIRE( config.benchmarkSamples == 200 )
with expansion:
200 == 200
-------------------------------------------------------------------------------
Process can be configured on command line
Benchmark options
resamples
-------------------------------------------------------------------------------
CmdLine.tests.cpp:<line number>
...............................................................................
CmdLine.tests.cpp:<line number>: PASSED:
CHECK( cli.parse({ "test", "--benchmark-resamples=20000" }) )
with expansion:
{?}
CmdLine.tests.cpp:<line number>: PASSED:
REQUIRE( config.benchmarkResamples == 20000 )
with expansion:
20000 (0x<hex digits>) == 20000 (0x<hex digits>)
-------------------------------------------------------------------------------
Process can be configured on command line
Benchmark options
Allow configuring of benchmark warmup time
2020-01-27 15:43:27 +01:00
confidence-interval
Add an extra test for benchmarking macros Also updated baselines
2019-06-02 13:19:09 +02:00
-------------------------------------------------------------------------------
CmdLine.tests.cpp:<line number>
...............................................................................
CmdLine.tests.cpp:<line number>: PASSED:
CHECK( cli.parse({ "test", "--benchmark-confidence-interval=0.99" }) )
with expansion:
{?}
CmdLine.tests.cpp:<line number>: PASSED:
Move Approx out of the Detail namespace
2020-02-03 15:07:59 +01:00
REQUIRE( config.benchmarkConfidenceInterval == Catch::Approx(0.99) )
Add an extra test for benchmarking macros Also updated baselines
2019-06-02 13:19:09 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
0.98999999999999999
==
Approx( 0.98999999999999999 )
Add an extra test for benchmarking macros Also updated baselines
2019-06-02 13:19:09 +02:00
-------------------------------------------------------------------------------
Process can be configured on command line
Benchmark options
Allow configuring of benchmark warmup time
2020-01-27 15:43:27 +01:00
no-analysis
Add an extra test for benchmarking macros Also updated baselines
2019-06-02 13:19:09 +02:00
-------------------------------------------------------------------------------
CmdLine.tests.cpp:<line number>
...............................................................................
CmdLine.tests.cpp:<line number>: PASSED:
CHECK( cli.parse({ "test", "--benchmark-no-analysis" }) )
with expansion:
{?}
CmdLine.tests.cpp:<line number>: PASSED:
REQUIRE( config.benchmarkNoAnalysis )
with expansion:
true
Allow configuring of benchmark warmup time
2020-01-27 15:43:27 +01:00
-------------------------------------------------------------------------------
Process can be configured on command line
Benchmark options
warmup-time
-------------------------------------------------------------------------------
CmdLine.tests.cpp:<line number>
...............................................................................
CmdLine.tests.cpp:<line number>: PASSED:
CHECK( cli.parse({ "test", "--benchmark-warmup-time=10" }) )
with expansion:
{?}
CmdLine.tests.cpp:<line number>: PASSED:
REQUIRE( config.benchmarkWarmupTime == 10 )
with expansion:
10 == 10
Template tests: added TEMPLATE_PRODUCT_TEST_CASE support for generating test cases based on multiple template template types combined with template arguments for each of the template template types specified e.g. ``` TEMPLATE_PRODUCT_TEST_CASE("template product","[template]", (std::tuple, std::pair, std::map), ((int,float),(char,double),(int,char))) ``` will effectively create 9 test cases with types: std::tuple<int,float> std::tuple<char,double> std::tuple<int,char> std::pair<int,float> std::pair<char, double> std::pair<int,char> std::map<int,float> std::map<char,double> std::map<int,char> Tested type is accessible in test case body as TestType Unique name is created by appending ` - <index>` to test name since preprocessor has some limitations in recursions Closes #1454
2018-12-06 19:27:33 +01:00
-------------------------------------------------------------------------------
Use correct type name instead of index for TEMPLATE_PRODUCT_TEST_CASE (#1544) Previously, for a TEMPLATE_PRODUCT_TEST_CASE("Test" ..., T, (P1, P2)), the generated test case names were Test - 0 Test - 1 With this commit, the correct typename is used: Test - T<P1> Test - T<P2> ----------- MSVC needs another indirection to evaluate INTERNAL_CATCH_STRINGIZE and also inserts a space before theINTERNAL_CATCH_STRINGIZE_WITHOUT_PARENS parameter, which we can get rid of by pointer arithmetic.
2019-02-17 21:52:22 +01:00
Product with differing arities - std::tuple<int, double, float>
Template tests: added TEMPLATE_PRODUCT_TEST_CASE support for generating test cases based on multiple template template types combined with template arguments for each of the template template types specified e.g. ``` TEMPLATE_PRODUCT_TEST_CASE("template product","[template]", (std::tuple, std::pair, std::map), ((int,float),(char,double),(int,char))) ``` will effectively create 9 test cases with types: std::tuple<int,float> std::tuple<char,double> std::tuple<int,char> std::pair<int,float> std::pair<char, double> std::pair<int,char> std::map<int,float> std::map<char,double> std::map<int,char> Tested type is accessible in test case body as TestType Unique name is created by appending ` - <index>` to test name since preprocessor has some limitations in recursions Closes #1454
2018-12-06 19:27:33 +01:00
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( std::tuple_size<TestType>::value >= 1 )
with expansion:
Use correct type name instead of index for TEMPLATE_PRODUCT_TEST_CASE (#1544) Previously, for a TEMPLATE_PRODUCT_TEST_CASE("Test" ..., T, (P1, P2)), the generated test case names were Test - 0 Test - 1 With this commit, the correct typename is used: Test - T<P1> Test - T<P2> ----------- MSVC needs another indirection to evaluate INTERNAL_CATCH_STRINGIZE and also inserts a space before theINTERNAL_CATCH_STRINGIZE_WITHOUT_PARENS parameter, which we can get rid of by pointer arithmetic.
2019-02-17 21:52:22 +01:00
3 >= 1
Template tests: added TEMPLATE_PRODUCT_TEST_CASE support for generating test cases based on multiple template template types combined with template arguments for each of the template template types specified e.g. ``` TEMPLATE_PRODUCT_TEST_CASE("template product","[template]", (std::tuple, std::pair, std::map), ((int,float),(char,double),(int,char))) ``` will effectively create 9 test cases with types: std::tuple<int,float> std::tuple<char,double> std::tuple<int,char> std::pair<int,float> std::pair<char, double> std::pair<int,char> std::map<int,float> std::map<char,double> std::map<int,char> Tested type is accessible in test case body as TestType Unique name is created by appending ` - <index>` to test name since preprocessor has some limitations in recursions Closes #1454
2018-12-06 19:27:33 +01:00
-------------------------------------------------------------------------------
Use correct type name instead of index for TEMPLATE_PRODUCT_TEST_CASE (#1544) Previously, for a TEMPLATE_PRODUCT_TEST_CASE("Test" ..., T, (P1, P2)), the generated test case names were Test - 0 Test - 1 With this commit, the correct typename is used: Test - T<P1> Test - T<P2> ----------- MSVC needs another indirection to evaluate INTERNAL_CATCH_STRINGIZE and also inserts a space before theINTERNAL_CATCH_STRINGIZE_WITHOUT_PARENS parameter, which we can get rid of by pointer arithmetic.
2019-02-17 21:52:22 +01:00
Product with differing arities - std::tuple<int, double>
Template tests: added TEMPLATE_PRODUCT_TEST_CASE support for generating test cases based on multiple template template types combined with template arguments for each of the template template types specified e.g. ``` TEMPLATE_PRODUCT_TEST_CASE("template product","[template]", (std::tuple, std::pair, std::map), ((int,float),(char,double),(int,char))) ``` will effectively create 9 test cases with types: std::tuple<int,float> std::tuple<char,double> std::tuple<int,char> std::pair<int,float> std::pair<char, double> std::pair<int,char> std::map<int,float> std::map<char,double> std::map<int,char> Tested type is accessible in test case body as TestType Unique name is created by appending ` - <index>` to test name since preprocessor has some limitations in recursions Closes #1454
2018-12-06 19:27:33 +01:00
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( std::tuple_size<TestType>::value >= 1 )
with expansion:
2 >= 1
-------------------------------------------------------------------------------
Use correct type name instead of index for TEMPLATE_PRODUCT_TEST_CASE (#1544) Previously, for a TEMPLATE_PRODUCT_TEST_CASE("Test" ..., T, (P1, P2)), the generated test case names were Test - 0 Test - 1 With this commit, the correct typename is used: Test - T<P1> Test - T<P2> ----------- MSVC needs another indirection to evaluate INTERNAL_CATCH_STRINGIZE and also inserts a space before theINTERNAL_CATCH_STRINGIZE_WITHOUT_PARENS parameter, which we can get rid of by pointer arithmetic.
2019-02-17 21:52:22 +01:00
Product with differing arities - std::tuple<int>
Template tests: added TEMPLATE_PRODUCT_TEST_CASE support for generating test cases based on multiple template template types combined with template arguments for each of the template template types specified e.g. ``` TEMPLATE_PRODUCT_TEST_CASE("template product","[template]", (std::tuple, std::pair, std::map), ((int,float),(char,double),(int,char))) ``` will effectively create 9 test cases with types: std::tuple<int,float> std::tuple<char,double> std::tuple<int,char> std::pair<int,float> std::pair<char, double> std::pair<int,char> std::map<int,float> std::map<char,double> std::map<int,char> Tested type is accessible in test case body as TestType Unique name is created by appending ` - <index>` to test name since preprocessor has some limitations in recursions Closes #1454
2018-12-06 19:27:33 +01:00
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( std::tuple_size<TestType>::value >= 1 )
with expansion:
Use correct type name instead of index for TEMPLATE_PRODUCT_TEST_CASE (#1544) Previously, for a TEMPLATE_PRODUCT_TEST_CASE("Test" ..., T, (P1, P2)), the generated test case names were Test - 0 Test - 1 With this commit, the correct typename is used: Test - T<P1> Test - T<P2> ----------- MSVC needs another indirection to evaluate INTERNAL_CATCH_STRINGIZE and also inserts a space before theINTERNAL_CATCH_STRINGIZE_WITHOUT_PARENS parameter, which we can get rid of by pointer arithmetic.
2019-02-17 21:52:22 +01:00
1 >= 1
Template tests: added TEMPLATE_PRODUCT_TEST_CASE support for generating test cases based on multiple template template types combined with template arguments for each of the template template types specified e.g. ``` TEMPLATE_PRODUCT_TEST_CASE("template product","[template]", (std::tuple, std::pair, std::map), ((int,float),(char,double),(int,char))) ``` will effectively create 9 test cases with types: std::tuple<int,float> std::tuple<char,double> std::tuple<int,char> std::pair<int,float> std::pair<char, double> std::pair<int,char> std::map<int,float> std::map<char,double> std::map<int,char> Tested type is accessible in test case body as TestType Unique name is created by appending ` - <index>` to test name since preprocessor has some limitations in recursions Closes #1454
2018-12-06 19:27:33 +01:00
Add generateRandomSeed utility to generate randomness seed
2021-10-08 20:02:24 +02:00
-------------------------------------------------------------------------------
Random seed generation accepts known methods
-------------------------------------------------------------------------------
RandomNumberGeneration.tests.cpp:<line number>
...............................................................................
RandomNumberGeneration.tests.cpp:<line number>: PASSED:
REQUIRE_NOTHROW( Catch::generateRandomSeed(method) )
-------------------------------------------------------------------------------
Random seed generation accepts known methods
-------------------------------------------------------------------------------
RandomNumberGeneration.tests.cpp:<line number>
...............................................................................
RandomNumberGeneration.tests.cpp:<line number>: PASSED:
REQUIRE_NOTHROW( Catch::generateRandomSeed(method) )
-------------------------------------------------------------------------------
Random seed generation accepts known methods
-------------------------------------------------------------------------------
RandomNumberGeneration.tests.cpp:<line number>
...............................................................................
RandomNumberGeneration.tests.cpp:<line number>: PASSED:
REQUIRE_NOTHROW( Catch::generateRandomSeed(method) )
-------------------------------------------------------------------------------
Random seed generation reports unknown methods
-------------------------------------------------------------------------------
RandomNumberGeneration.tests.cpp:<line number>
...............................................................................
RandomNumberGeneration.tests.cpp:<line number>: PASSED:
REQUIRE_THROWS( Catch::generateRandomSeed(static_cast<Catch::GenerateFrom>(77)) )
Support sentinel-based ranges in default stringify (#2004)
2020-08-18 10:34:47 +02:00
-------------------------------------------------------------------------------
Range type with sentinel
-------------------------------------------------------------------------------
ToString.tests.cpp:<line number>
...............................................................................
ToString.tests.cpp:<line number>: PASSED:
CHECK( Catch::Detail::stringify(UsesSentinel{}) == "{ }" )
with expansion:
"{ }" == "{ }"
Update baselines
2017-06-06 15:07:57 +02:00
-------------------------------------------------------------------------------
Reconstruction should be based on stringification: #914
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Decomposition.tests.cpp:<line number>
Update baselines
2017-06-06 15:07:57 +02:00
...............................................................................
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Decomposition.tests.cpp:<line number>: FAILED:
Update baselines
2017-06-06 15:07:57 +02:00
CHECK( truthy(false) )
with expansion:
Hey, its truthy!
Provide a regex matcher against std::string Related to #1040
2017-11-13 15:35:31 +01:00
-------------------------------------------------------------------------------
Regex string matcher
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>
Provide a regex matcher against std::string Related to #1040
2017-11-13 15:35:31 +01:00
...............................................................................
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( testStringForMatching(), Matches( "this STRING contains 'abc' as a substring" ) )
Provide a regex matcher against std::string Related to #1040
2017-11-13 15:35:31 +01:00
with expansion:
"this string contains 'abc' as a substring" matches "this STRING contains
'abc' as a substring" case sensitively
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( testStringForMatching(), Matches( "contains 'abc' as a substring" ) )
Provide a regex matcher against std::string Related to #1040
2017-11-13 15:35:31 +01:00
with expansion:
"this string contains 'abc' as a substring" matches "contains 'abc' as a
substring" case sensitively
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( testStringForMatching(), Matches( "this string contains 'abc' as a" ) )
Provide a regex matcher against std::string Related to #1040
2017-11-13 15:35:31 +01:00
with expansion:
"this string contains 'abc' as a substring" matches "this string contains
'abc' as a" case sensitively
Error out reporter registration for reporter names with '::'
2022-01-09 19:01:14 +01:00
-------------------------------------------------------------------------------
Registering reporter with '::' in name fails
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_THROWS_WITH( registry.registerReporter( "with::doublecolons", Catch::Detail::make_unique<TestReporterFactory>() ), "'::' is not allowed in reporter name: 'with::doublecolons'" )
with expansion:
"'::' is not allowed in reporter name: 'with::doublecolons'" equals: "'::' is
not allowed in reporter name: 'with::doublecolons'"
Fix a bug in UnorderedEqualsMatcher Previously a mismatched prefix would be skipped before the actual comparison would be performed. Obviously, it is supposed to be _matching_ prefix that is skipped.
2018-09-28 15:30:00 +02:00
-------------------------------------------------------------------------------
Regression test #1
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( actual, !UnorderedEquals( expected ) )
Fix a bug in UnorderedEqualsMatcher Previously a mismatched prefix would be skipped before the actual comparison would be performed. Obviously, it is supposed to be _matching_ prefix that is skipped.
2018-09-28 15:30:00 +02:00
with expansion:
{ 'a', 'b' } not UnorderedEquals: { 'c', 'b' }
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( factories.empty() )
with expansion:
!false
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
Automake reporter lists tags
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( listingString, ContainsSubstring("fakeTag"s) )
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
with expansion:
"All available tags:
1 [fakeTag]
1 tag
" contains: "fakeTag"
with message:
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
Tested reporter: Automake
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( factories.empty() )
with expansion:
!false
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
Automake reporter lists reporters
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( listingString, ContainsSubstring("fake reporter"s) )
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
with expansion:
"Available reporters:
fake reporter: fake description
" contains: "fake reporter"
with message:
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
Tested reporter: Automake
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( factories.empty() )
with expansion:
!false
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
Automake reporter lists tests
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( listingString, ContainsSubstring( "fake test name"s ) && ContainsSubstring( "fakeTestTag"s ) )
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
with expansion:
"All available test cases:
fake test name
[fakeTestTag]
1 test case
" ( contains: "fake test name" and contains: "fakeTestTag" )
with message:
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
Tested reporter: Automake
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( factories.empty() )
with expansion:
!false
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
compact reporter lists tags
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( listingString, ContainsSubstring("fakeTag"s) )
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
with expansion:
"All available tags:
1 [fakeTag]
1 tag
" contains: "fakeTag"
with message:
Tested reporter: compact
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( factories.empty() )
with expansion:
!false
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
compact reporter lists reporters
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( listingString, ContainsSubstring("fake reporter"s) )
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
with expansion:
"Available reporters:
fake reporter: fake description
" contains: "fake reporter"
with message:
Tested reporter: compact
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( factories.empty() )
with expansion:
!false
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
compact reporter lists tests
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( listingString, ContainsSubstring( "fake test name"s ) && ContainsSubstring( "fakeTestTag"s ) )
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
with expansion:
"All available test cases:
fake test name
[fakeTestTag]
1 test case
" ( contains: "fake test name" and contains: "fakeTestTag" )
with message:
Tested reporter: compact
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( factories.empty() )
with expansion:
!false
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
console reporter lists tags
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( listingString, ContainsSubstring("fakeTag"s) )
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
with expansion:
"All available tags:
1 [fakeTag]
1 tag
" contains: "fakeTag"
with message:
Tested reporter: console
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( factories.empty() )
with expansion:
!false
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
console reporter lists reporters
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( listingString, ContainsSubstring("fake reporter"s) )
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
with expansion:
"Available reporters:
fake reporter: fake description
" contains: "fake reporter"
with message:
Tested reporter: console
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( factories.empty() )
with expansion:
!false
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
console reporter lists tests
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( listingString, ContainsSubstring( "fake test name"s ) && ContainsSubstring( "fakeTestTag"s ) )
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
with expansion:
"All available test cases:
fake test name
[fakeTestTag]
1 test case
" ( contains: "fake test name" and contains: "fakeTestTag" )
with message:
Tested reporter: console
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Add JSON reporter (#2706) Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2023-11-14 22:52:15 +01:00
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( factories.empty() )
with expansion:
!false
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
JSON reporter lists tags
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( listingString, ContainsSubstring("fakeTag"s) )
with expansion:
"{
"version": 1,
"metadata": {
"name": "",
"rng-seed": 1234,
"catch2-version": "<version>"
},
"listings": {
"tags": [
{
"aliases": [
"fakeTag"
],
"count": 1
}
]" contains: "fakeTag"
with message:
Tested reporter: JSON
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( factories.empty() )
with expansion:
!false
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
JSON reporter lists reporters
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( listingString, ContainsSubstring("fake reporter"s) )
with expansion:
"{
"version": 1,
"metadata": {
"name": "",
"rng-seed": 1234,
"catch2-version": "<version>"
},
"listings": {
"reporters": [
{
"name": "fake reporter",
"description": "fake description"
}
]" contains: "fake reporter"
with message:
Tested reporter: JSON
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( factories.empty() )
with expansion:
!false
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
JSON reporter lists tests
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( listingString, ContainsSubstring( "fake test name"s ) && ContainsSubstring( "fakeTestTag"s ) )
with expansion:
"{
"version": 1,
"metadata": {
"name": "",
"rng-seed": 1234,
"catch2-version": "<version>"
},
"listings": {
"tests": [
{
"name": "fake test name",
"class-name": "",
"tags": [
"fakeTestTag"
],
"source-location": {
"filename": "fake-file.cpp",
"line": 123456789
}
}
]" ( contains: "fake test name" and contains: "fakeTestTag" )
with message:
Tested reporter: JSON
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( factories.empty() )
with expansion:
!false
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
JUnit reporter lists tags
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( listingString, ContainsSubstring("fakeTag"s) )
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
with expansion:
"<?xml version="1.0" encoding="UTF-8"?>
All available tags:
1 [fakeTag]
1 tag
" contains: "fakeTag"
with message:
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
Tested reporter: JUnit
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( factories.empty() )
with expansion:
!false
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
JUnit reporter lists reporters
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( listingString, ContainsSubstring("fake reporter"s) )
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
with expansion:
"<?xml version="1.0" encoding="UTF-8"?>
Available reporters:
fake reporter: fake description
" contains: "fake reporter"
with message:
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
Tested reporter: JUnit
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( factories.empty() )
with expansion:
!false
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
JUnit reporter lists tests
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( listingString, ContainsSubstring( "fake test name"s ) && ContainsSubstring( "fakeTestTag"s ) )
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
with expansion:
"<?xml version="1.0" encoding="UTF-8"?>
All available test cases:
fake test name
[fakeTestTag]
1 test case
" ( contains: "fake test name" and contains: "fakeTestTag" )
with message:
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
Tested reporter: JUnit
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( factories.empty() )
with expansion:
!false
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
SonarQube reporter lists tags
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( listingString, ContainsSubstring("fakeTag"s) )
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
with expansion:
"<?xml version="1.0" encoding="UTF-8"?>
All available tags:
1 [fakeTag]
1 tag
" contains: "fakeTag"
with message:
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
Tested reporter: SonarQube
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( factories.empty() )
with expansion:
!false
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
SonarQube reporter lists reporters
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( listingString, ContainsSubstring("fake reporter"s) )
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
with expansion:
"<?xml version="1.0" encoding="UTF-8"?>
Available reporters:
fake reporter: fake description
" contains: "fake reporter"
with message:
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
Tested reporter: SonarQube
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( factories.empty() )
with expansion:
!false
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
SonarQube reporter lists tests
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( listingString, ContainsSubstring( "fake test name"s ) && ContainsSubstring( "fakeTestTag"s ) )
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
with expansion:
"<?xml version="1.0" encoding="UTF-8"?>
All available test cases:
fake test name
[fakeTestTag]
1 test case
" ( contains: "fake test name" and contains: "fakeTestTag" )
with message:
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
Tested reporter: SonarQube
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( factories.empty() )
with expansion:
!false
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
TAP reporter lists tags
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( listingString, ContainsSubstring("fakeTag"s) )
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
with expansion:
"All available tags:
1 [fakeTag]
1 tag
" contains: "fakeTag"
with message:
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
Tested reporter: TAP
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( factories.empty() )
with expansion:
!false
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
TAP reporter lists reporters
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( listingString, ContainsSubstring("fake reporter"s) )
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
with expansion:
"Available reporters:
fake reporter: fake description
" contains: "fake reporter"
with message:
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
Tested reporter: TAP
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( factories.empty() )
with expansion:
!false
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
TAP reporter lists tests
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( listingString, ContainsSubstring( "fake test name"s ) && ContainsSubstring( "fakeTestTag"s ) )
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
with expansion:
"All available test cases:
fake test name
[fakeTestTag]
1 test case
" ( contains: "fake test name" and contains: "fakeTestTag" )
with message:
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
Tested reporter: TAP
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( factories.empty() )
with expansion:
!false
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
TeamCity reporter lists tags
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( listingString, ContainsSubstring("fakeTag"s) )
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
with expansion:
"All available tags:
1 [fakeTag]
1 tag
" contains: "fakeTag"
with message:
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
Tested reporter: TeamCity
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( factories.empty() )
with expansion:
!false
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
TeamCity reporter lists reporters
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( listingString, ContainsSubstring("fake reporter"s) )
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
with expansion:
"Available reporters:
fake reporter: fake description
" contains: "fake reporter"
with message:
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
Tested reporter: TeamCity
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( factories.empty() )
with expansion:
!false
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
TeamCity reporter lists tests
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( listingString, ContainsSubstring( "fake test name"s ) && ContainsSubstring( "fakeTestTag"s ) )
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
with expansion:
"All available test cases:
fake test name
[fakeTestTag]
1 test case
" ( contains: "fake test name" and contains: "fakeTestTag" )
with message:
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
Tested reporter: TeamCity
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( factories.empty() )
with expansion:
!false
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
XML reporter lists tags
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( listingString, ContainsSubstring("fakeTag"s) )
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
with expansion:
"<?xml version="1.0" encoding="UTF-8"?>
<TagsFromMatchingTests>
<Tag>
<Count>1</Count>
<Aliases>
<Alias>fakeTag</Alias>
</Aliases>
</Tag>
</TagsFromMatchingTests>" contains: "fakeTag"
with message:
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
Tested reporter: XML
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( factories.empty() )
with expansion:
!false
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
XML reporter lists reporters
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( listingString, ContainsSubstring("fake reporter"s) )
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
with expansion:
"<?xml version="1.0" encoding="UTF-8"?>
<AvailableReporters>
<Reporter>
<Name>fake reporter</Name>
<Description>fake description</Description>
</Reporter>
</AvailableReporters>" contains: "fake reporter"
with message:
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
Tested reporter: XML
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( factories.empty() )
with expansion:
!false
-------------------------------------------------------------------------------
Reporter's write listings to provided stream
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
XML reporter lists tests
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( listingString, ContainsSubstring( "fake test name"s ) && ContainsSubstring( "fakeTestTag"s ) )
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
with expansion:
"<?xml version="1.0" encoding="UTF-8"?>
<MatchingTests>
<TestCase>
<Name>fake test name</Name>
<ClassName/>
<Tags>[fakeTestTag]</Tags>
<SourceInfo>
<File>fake-file.cpp</File>
<Line>123456789</Line>
</SourceInfo>
</TestCase>
</MatchingTests>" ( contains: "fake test name" and contains: "fakeTestTag" )
with message:
Use case in names of default reporters
2021-11-10 23:32:01 +01:00
Tested reporter: XML
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
Fix bad indentation calculation in the console reporter The problem came from the console reporter trying to provide a fancy linebreaking (primarily for things like `SCENARIO` or the BDD macros), so that new lines start with extra indentation if the text being line broken starts as "{text}: ". The console reporter did not properly take into account cases where the ": " part would already be in a later line, in which case it would ask for non-sensical level of indentation (larger than single line length). We fixed this by also enforcing that the special indentation case only triggers if the ": " is found early enough in the line, so that we also avoid degenerate cases like this: ``` blablabla: F a n c y . . . ``` Fixes #2309
2021-10-25 15:10:35 +02:00
-------------------------------------------------------------------------------
Reproducer for #2309 - a very long description past 80 chars (default console
width) with a late colon : blablabla
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
SUCCEED counts as a test pass
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Message.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Message.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with message:
this is a success
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Update MessageTests.cpp typo corrected
2017-11-30 16:17:23 +01:00
SUCCEED does not require an argument
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Message.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Message.tests.cpp:<line number>: PASSED:
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Scenario: BDD tests requiring Fixtures to provide commonly-accessed data or
methods
Add test for AND_GIVEN and update the baselines
2018-09-02 15:38:33 +02:00
Given: No operations precede me
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
BDD.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
BDD.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( before == 0 )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
0 == 0
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Scenario: BDD tests requiring Fixtures to provide commonly-accessed data or
methods
Add test for AND_GIVEN and update the baselines
2018-09-02 15:38:33 +02:00
Given: No operations precede me
When: We get the count
Then: Subsequently values are higher
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
BDD.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
BDD.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( after > before )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
1 > 0
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Scenario: Do that thing with the thing
Add test for AND_GIVEN and update the baselines
2018-09-02 15:38:33 +02:00
Given: This stuff exists
And given: And some assumption
When: I do this
Then: it should do this
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
BDD.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
BDD.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( itDoesThis() )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
true
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Scenario: Do that thing with the thing
Add test for AND_GIVEN and update the baselines
2018-09-02 15:38:33 +02:00
Given: This stuff exists
And given: And some assumption
When: I do this
Then: it should do this
And: do that
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
BDD.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
BDD.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( itDoesThat() )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
true
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Scenario: This is a really long scenario name to see how the list command deals
with wrapping
Add test for AND_GIVEN and update the baselines
2018-09-02 15:38:33 +02:00
Given: A section name that is so long that it cannot fit in a single
console width
When: The test headers are printed as part of the normal running of the
scenario
Then: The, deliberately very long and overly verbose (you see what I did
there?) section names must wrap, along with an indent
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
BDD.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
BDD.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with message:
boo!
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Scenario: Vector resizing affects size and capacity
Add test for AND_GIVEN and update the baselines
2018-09-02 15:38:33 +02:00
Given: an empty vector
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
BDD.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
BDD.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( v.size() == 0 )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
0 == 0
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Scenario: Vector resizing affects size and capacity
Add test for AND_GIVEN and update the baselines
2018-09-02 15:38:33 +02:00
Given: an empty vector
When: it is made larger
Then: the size and capacity go up
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
BDD.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
BDD.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( v.size() == 10 )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
10 == 10
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
BDD.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( v.capacity() >= 10 )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
10 >= 10
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Scenario: Vector resizing affects size and capacity
Add test for AND_GIVEN and update the baselines
2018-09-02 15:38:33 +02:00
Given: an empty vector
When: it is made larger
Then: the size and capacity go up
And when: it is made smaller again
Then: the size goes down but the capacity stays the same
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
BDD.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
BDD.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( v.size() == 5 )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
5 == 5
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
BDD.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( v.capacity() >= 10 )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
10 >= 10
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Scenario: Vector resizing affects size and capacity
Add test for AND_GIVEN and update the baselines
2018-09-02 15:38:33 +02:00
Given: an empty vector
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
BDD.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
BDD.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( v.size() == 0 )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
0 == 0
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Scenario: Vector resizing affects size and capacity
Add test for AND_GIVEN and update the baselines
2018-09-02 15:38:33 +02:00
Given: an empty vector
When: we reserve more space
Then: The capacity is increased but the size remains the same
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
BDD.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
BDD.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( v.capacity() >= 10 )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
10 >= 10
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
BDD.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( v.size() == 0 )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
0 == 0
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
A string sent directly to stdout
A string sent directly to stderr
Added clog test
2017-12-05 18:48:15 +01:00
A string sent to stderr via clog
Fixed NoAssertions warning
2018-01-26 17:52:28 +01:00
-------------------------------------------------------------------------------
Sends stuff to stdout and stderr
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
No assertions in test case 'Sends stuff to stdout and stderr'
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Some simple comparisons between doubles
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Approx.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( d == Approx( 1.23 ) )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.22999999999999998
==
Approx( 1.22999999999999998 )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( d != Approx( 1.22 ) )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.22999999999999998
!=
Approx( 1.21999999999999997 )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( d != Approx( 1.24 ) )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.22999999999999998
!=
Approx( 1.23999999999999999 )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Add float/int literal for Approx
2018-05-21 15:42:40 +02:00
REQUIRE( d == 1.23_a )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.22999999999999998
==
Approx( 1.22999999999999998 )
Add float/int literal for Approx
2018-05-21 15:42:40 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Add float/int literal for Approx
2018-05-21 15:42:40 +02:00
REQUIRE( d != 1.22_a )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.22999999999999998
!=
Approx( 1.21999999999999997 )
Add float/int literal for Approx
2018-05-21 15:42:40 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( Approx( d ) == 1.23 )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
Approx( 1.22999999999999998 )
==
1.22999999999999998
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( Approx( d ) != 1.22 )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
Approx( 1.22999999999999998 )
!=
1.21999999999999997
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( Approx( d ) != 1.24 )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
Approx( 1.22999999999999998 )
!=
1.23999999999999999
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Message from section one
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Standard output from all sections is reported
one
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Message.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
No assertions in section 'one'
Message from section two
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Standard output from all sections is reported
two
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Message.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
No assertions in section 'two'
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
StartsWith string matcher
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( testStringForMatching(), StartsWith( "This String" ) )
Add tests for case insensitive string matching
2017-11-13 15:46:33 +01:00
with expansion:
"this string contains 'abc' as a substring" starts with: "This String"
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( testStringForMatching(), StartsWith( "string", Catch::CaseSensitive::No ) )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Add tests for case insensitive string matching
2017-11-13 15:46:33 +01:00
"this string contains 'abc' as a substring" starts with: "string" (case
insensitive)
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Provide useful and unambigous stringification for static arrays
2018-01-14 18:06:21 +01:00
-------------------------------------------------------------------------------
Static arrays are convertible to string
Single item
-------------------------------------------------------------------------------
ToStringGeneral.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringGeneral.tests.cpp:<line number>: PASSED:
Provide useful and unambigous stringification for static arrays
2018-01-14 18:06:21 +01:00
REQUIRE( Catch::Detail::stringify(singular) == "{ 1 }" )
with expansion:
"{ 1 }" == "{ 1 }"
-------------------------------------------------------------------------------
Static arrays are convertible to string
Multiple
-------------------------------------------------------------------------------
ToStringGeneral.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringGeneral.tests.cpp:<line number>: PASSED:
Provide useful and unambigous stringification for static arrays
2018-01-14 18:06:21 +01:00
REQUIRE( Catch::Detail::stringify(arr) == "{ 3, 2, 1 }" )
with expansion:
"{ 3, 2, 1 }" == "{ 3, 2, 1 }"
-------------------------------------------------------------------------------
Static arrays are convertible to string
Non-trivial inner items
-------------------------------------------------------------------------------
ToStringGeneral.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringGeneral.tests.cpp:<line number>: PASSED:
Provide useful and unambigous stringification for static arrays
2018-01-14 18:06:21 +01:00
REQUIRE( Catch::Detail::stringify(arr) == R"({ { "1:1", "1:2", "1:3" }, { "2:1", "2:2" } })" )
with expansion:
"{ { "1:1", "1:2", "1:3" }, { "2:1", "2:2" } }"
==
"{ { "1:1", "1:2", "1:3" }, { "2:1", "2:2" } }"
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
String matchers
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( testStringForMatching(), ContainsSubstring( "string" ) )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"this string contains 'abc' as a substring" contains: "string"
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( testStringForMatching(), ContainsSubstring( "string", Catch::CaseSensitive::No ) )
Add tests for case insensitive string matching
2017-11-13 15:46:33 +01:00
with expansion:
"this string contains 'abc' as a substring" contains: "string" (case
insensitive)
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
CHECK_THAT( testStringForMatching(), ContainsSubstring( "abc" ) )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"this string contains 'abc' as a substring" contains: "abc"
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
CHECK_THAT( testStringForMatching(), ContainsSubstring( "aBC", Catch::CaseSensitive::No ) )
Add tests for case insensitive string matching
2017-11-13 15:46:33 +01:00
with expansion:
Update Clara to v1.1.5 to fix TextFlow bugs
2018-10-26 18:48:28 +02:00
"this string contains 'abc' as a substring" contains: "abc" (case
Add tests for case insensitive string matching
2017-11-13 15:46:33 +01:00
insensitive)
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( testStringForMatching(), StartsWith( "this" ) )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"this string contains 'abc' as a substring" starts with: "this"
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( testStringForMatching(), StartsWith( "THIS", Catch::CaseSensitive::No ) )
Add tests for case insensitive string matching
2017-11-13 15:46:33 +01:00
with expansion:
"this string contains 'abc' as a substring" starts with: "this" (case
insensitive)
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( testStringForMatching(), EndsWith( "substring" ) )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"this string contains 'abc' as a substring" ends with: "substring"
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( testStringForMatching(), EndsWith( " SuBsTrInG", Catch::CaseSensitive::No ) )
Add tests for case insensitive string matching
2017-11-13 15:46:33 +01:00
with expansion:
"this string contains 'abc' as a substring" ends with: " substring" (case
insensitive)
Added string tests to approvals
2017-06-29 12:19:08 +02:00
-------------------------------------------------------------------------------
StringRef
Empty string
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
String.tests.cpp:<line number>
Added string tests to approvals
2017-06-29 12:19:08 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Added string tests to approvals
2017-06-29 12:19:08 +02:00
REQUIRE( empty.empty() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Added string tests to approvals
2017-06-29 12:19:08 +02:00
REQUIRE( empty.size() == 0 )
with expansion:
0 == 0
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
String.tests.cpp:<line number>: PASSED:
Remove StringRef::isNullTerminated and StringRef::c_str Both of them were fundamentally unsafe to use and shouldn't be used at all.
2021-03-25 20:02:47 +01:00
REQUIRE( std::strcmp( empty.data(), "" ) == 0 )
Added string tests to approvals
2017-06-29 12:19:08 +02:00
with expansion:
0 == 0
-------------------------------------------------------------------------------
StringRef
From string literal
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
String.tests.cpp:<line number>
Added string tests to approvals
2017-06-29 12:19:08 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Added string tests to approvals
2017-06-29 12:19:08 +02:00
REQUIRE( s.empty() == false )
with expansion:
false == false
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Added string tests to approvals
2017-06-29 12:19:08 +02:00
REQUIRE( s.size() == 5 )
with expansion:
5 == 5
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Added string tests to approvals
2017-06-29 12:19:08 +02:00
REQUIRE( std::strcmp( rawChars, "hello" ) == 0 )
with expansion:
0 == 0
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
REQUIRE( s.data() == rawChars )
Added string tests to approvals
2017-06-29 12:19:08 +02:00
with expansion:
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
"hello" == "hello"
Added string tests to approvals
2017-06-29 12:19:08 +02:00
-------------------------------------------------------------------------------
StringRef
From sub-string
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
String.tests.cpp:<line number>
Added string tests to approvals
2017-06-29 12:19:08 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Added string tests to approvals
2017-06-29 12:19:08 +02:00
REQUIRE( original == "original" )
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
REQUIRE_NOTHROW( original.data() )
Added string tests to approvals
2017-06-29 12:19:08 +02:00
Add tests for StringRef's copy operations being shallow
2021-03-08 14:57:59 +01:00
-------------------------------------------------------------------------------
StringRef
Copy construction is shallow
-------------------------------------------------------------------------------
String.tests.cpp:<line number>
...............................................................................
String.tests.cpp:<line number>: PASSED:
REQUIRE( original.begin() == copy.begin() )
with expansion:
"original string" == "original string"
-------------------------------------------------------------------------------
StringRef
Copy assignment is shallow
-------------------------------------------------------------------------------
String.tests.cpp:<line number>
...............................................................................
String.tests.cpp:<line number>: PASSED:
REQUIRE( original.begin() == copy.begin() )
with expansion:
"original string" == "original string"
Added string tests to approvals
2017-06-29 12:19:08 +02:00
-------------------------------------------------------------------------------
StringRef
Substrings
zero-based substring
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
String.tests.cpp:<line number>
Added string tests to approvals
2017-06-29 12:19:08 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Added string tests to approvals
2017-06-29 12:19:08 +02:00
REQUIRE( ss.empty() == false )
with expansion:
false == false
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Added string tests to approvals
2017-06-29 12:19:08 +02:00
REQUIRE( ss.size() == 5 )
with expansion:
5 == 5
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
REQUIRE( std::strncmp( ss.data(), "hello", 5 ) == 0 )
Added string tests to approvals
2017-06-29 12:19:08 +02:00
with expansion:
0 == 0
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Added string tests to approvals
2017-06-29 12:19:08 +02:00
REQUIRE( ss == "hello" )
with expansion:
Added << ostream overload to StringRef
2017-08-14 09:50:44 +02:00
hello == "hello"
Added string tests to approvals
2017-06-29 12:19:08 +02:00
-------------------------------------------------------------------------------
StringRef
Substrings
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
non-zero-based substring
Added string tests to approvals
2017-06-29 12:19:08 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
String.tests.cpp:<line number>
Added string tests to approvals
2017-06-29 12:19:08 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
REQUIRE( ss.size() == 6 )
Added string tests to approvals
2017-06-29 12:19:08 +02:00
with expansion:
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
6 == 6
Added string tests to approvals
2017-06-29 12:19:08 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Remove StringRef::isNullTerminated and StringRef::c_str Both of them were fundamentally unsafe to use and shouldn't be used at all.
2021-03-25 20:02:47 +01:00
REQUIRE( std::strcmp( ss.data(), "world!" ) == 0 )
Added string tests to approvals
2017-06-29 12:19:08 +02:00
with expansion:
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
0 == 0
Added string tests to approvals
2017-06-29 12:19:08 +02:00
Rebased approvals
2019-05-18 21:53:28 +02:00
-------------------------------------------------------------------------------
StringRef
Substrings
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
Pointer values of full refs should match
Rebased approvals
2019-05-18 21:53:28 +02:00
-------------------------------------------------------------------------------
String.tests.cpp:<line number>
...............................................................................
String.tests.cpp:<line number>: PASSED:
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
REQUIRE( s.data() == s2.data() )
Rebased approvals
2019-05-21 01:05:39 +02:00
with expansion:
"hello world!" == "hello world!"
Rebased approvals
2019-05-18 21:53:28 +02:00
Added string tests to approvals
2017-06-29 12:19:08 +02:00
-------------------------------------------------------------------------------
StringRef
Substrings
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
Pointer values of substring refs should also match
Added string tests to approvals
2017-06-29 12:19:08 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
String.tests.cpp:<line number>
Added string tests to approvals
2017-06-29 12:19:08 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
REQUIRE( s.data() == ss.data() )
Added string tests to approvals
2017-06-29 12:19:08 +02:00
with expansion:
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
"hello world!" == "hello world!"
Added string tests to approvals
2017-06-29 12:19:08 +02:00
-------------------------------------------------------------------------------
StringRef
Substrings
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
Past the end substring
Added string tests to approvals
2017-06-29 12:19:08 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
String.tests.cpp:<line number>
Added string tests to approvals
2017-06-29 12:19:08 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
REQUIRE( s.substr(s.size() + 1, 123).empty() )
Added string tests to approvals
2017-06-29 12:19:08 +02:00
with expansion:
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
true
Added string tests to approvals
2017-06-29 12:19:08 +02:00
-------------------------------------------------------------------------------
StringRef
Substrings
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
Substring off the end are trimmed
Added string tests to approvals
2017-06-29 12:19:08 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
String.tests.cpp:<line number>
Added string tests to approvals
2017-06-29 12:19:08 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Remove StringRef::isNullTerminated and StringRef::c_str Both of them were fundamentally unsafe to use and shouldn't be used at all.
2021-03-25 20:02:47 +01:00
REQUIRE( std::strcmp(ss.data(), "world!") == 0 )
Added string tests to approvals
2017-06-29 12:19:08 +02:00
with expansion:
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
0 == 0
Added string tests to approvals
2017-06-29 12:19:08 +02:00
Add more constexpr to StringRef
2020-02-13 15:01:03 +01:00
-------------------------------------------------------------------------------
StringRef
Substrings
substring start after the end is empty
-------------------------------------------------------------------------------
String.tests.cpp:<line number>
...............................................................................
String.tests.cpp:<line number>: PASSED:
REQUIRE( s.substr(1'000'000, 1).empty() )
with expansion:
true
Add test for past-the-end substr on StringRef
2019-09-08 21:04:23 +02:00
-------------------------------------------------------------------------------
StringRef
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
Comparisons are deep
Add test for past-the-end substr on StringRef
2019-09-08 21:04:23 +02:00
-------------------------------------------------------------------------------
String.tests.cpp:<line number>
...............................................................................
String.tests.cpp:<line number>: PASSED:
Fix Wold-style-cast error (#2125) * Add Wold-style-cast to cmake flags * Fix old style cast in catch_stats.hpp * Fix old style cast in catch_stats.cpp
2020-12-28 14:00:19 +01:00
CHECK( reinterpret_cast<char*>(buffer1) != reinterpret_cast<char*>(buffer2) )
Add test for past-the-end substr on StringRef
2019-09-08 21:04:23 +02:00
with expansion:
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
"Hello" != "Hello"
Added string tests to approvals
2017-06-29 12:19:08 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
REQUIRE( left == right )
Added string tests to approvals
2017-06-29 12:19:08 +02:00
with expansion:
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
Hello == Hello
Added string tests to approvals
2017-06-29 12:19:08 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
REQUIRE( left != left.substr(0, 3) )
Added string tests to approvals
2017-06-29 12:19:08 +02:00
with expansion:
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
Hello != Hel
Added string tests to approvals
2017-06-29 12:19:08 +02:00
Rebased with string conversion tests
2017-08-14 09:43:33 +02:00
-------------------------------------------------------------------------------
StringRef
from std::string
implicitly constructed
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
String.tests.cpp:<line number>
Rebased with string conversion tests
2017-08-14 09:43:33 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Rebased with string conversion tests
2017-08-14 09:43:33 +02:00
REQUIRE( sr == "a standard string" )
with expansion:
Added << ostream overload to StringRef
2017-08-14 09:50:44 +02:00
a standard string == "a standard string"
Rebased with string conversion tests
2017-08-14 09:43:33 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Rebased with string conversion tests
2017-08-14 09:43:33 +02:00
REQUIRE( sr.size() == stdStr.size() )
with expansion:
17 == 17
-------------------------------------------------------------------------------
StringRef
from std::string
explicitly constructed
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
String.tests.cpp:<line number>
Rebased with string conversion tests
2017-08-14 09:43:33 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Rebased with string conversion tests
2017-08-14 09:43:33 +02:00
REQUIRE( sr == "a standard string" )
with expansion:
Added << ostream overload to StringRef
2017-08-14 09:50:44 +02:00
a standard string == "a standard string"
Rebased with string conversion tests
2017-08-14 09:43:33 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Rebased with string conversion tests
2017-08-14 09:43:33 +02:00
REQUIRE( sr.size() == stdStr.size() )
with expansion:
17 == 17
-------------------------------------------------------------------------------
StringRef
from std::string
assigned
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
String.tests.cpp:<line number>
Rebased with string conversion tests
2017-08-14 09:43:33 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Rebased with string conversion tests
2017-08-14 09:43:33 +02:00
REQUIRE( sr == "a standard string" )
with expansion:
Added << ostream overload to StringRef
2017-08-14 09:50:44 +02:00
a standard string == "a standard string"
Rebased with string conversion tests
2017-08-14 09:43:33 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Rebased with string conversion tests
2017-08-14 09:43:33 +02:00
REQUIRE( sr.size() == stdStr.size() )
with expansion:
17 == 17
-------------------------------------------------------------------------------
StringRef
to std::string
explicitly constructed
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
String.tests.cpp:<line number>
Rebased with string conversion tests
2017-08-14 09:43:33 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Rebased with string conversion tests
2017-08-14 09:43:33 +02:00
REQUIRE( stdStr == "a stringref" )
with expansion:
"a stringref" == "a stringref"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Rebased with string conversion tests
2017-08-14 09:43:33 +02:00
REQUIRE( stdStr.size() == sr.size() )
with expansion:
11 == 11
-------------------------------------------------------------------------------
StringRef
to std::string
assigned
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
String.tests.cpp:<line number>
Rebased with string conversion tests
2017-08-14 09:43:33 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Rebased with string conversion tests
2017-08-14 09:43:33 +02:00
REQUIRE( stdStr == "a stringref" )
with expansion:
"a stringref" == "a stringref"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
String.tests.cpp:<line number>: PASSED:
Rebased with string conversion tests
2017-08-14 09:43:33 +02:00
REQUIRE( stdStr.size() == sr.size() )
with expansion:
11 == 11
Add op+(StringRef, StringRef) -> std::string
2020-05-31 22:30:41 +02:00
-------------------------------------------------------------------------------
StringRef
std::string += StringRef
-------------------------------------------------------------------------------
String.tests.cpp:<line number>
...............................................................................
String.tests.cpp:<line number>: PASSED:
REQUIRE( lhs == "some string += the stringref contents" )
with expansion:
"some string += the stringref contents"
==
"some string += the stringref contents"
-------------------------------------------------------------------------------
StringRef
StringRef + StringRef
-------------------------------------------------------------------------------
String.tests.cpp:<line number>
...............................................................................
String.tests.cpp:<line number>: PASSED:
REQUIRE( together == "abrakadabra" )
with expansion:
"abrakadabra" == "abrakadabra"
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
-------------------------------------------------------------------------------
StringRef at compilation time
Simple constructors
-------------------------------------------------------------------------------
String.tests.cpp:<line number>
...............................................................................
String.tests.cpp:<line number>: PASSED:
with message:
Add more constexpr to StringRef
2020-02-13 15:01:03 +01:00
empty.size() == 0
String.tests.cpp:<line number>: PASSED:
with message:
empty.begin() == empty.end()
String.tests.cpp:<line number>: PASSED:
with message:
stringref.size() == 3
String.tests.cpp:<line number>: PASSED:
with message:
stringref.data() == abc
String.tests.cpp:<line number>: PASSED:
with message:
stringref.begin() == abc
String.tests.cpp:<line number>: PASSED:
with message:
stringref.begin() != stringref.end()
String.tests.cpp:<line number>: PASSED:
with message:
stringref.substr(10, 0).empty()
String.tests.cpp:<line number>: PASSED:
with message:
stringref.substr(2, 1).data() == abc + 2
Small improvements for StringRef * `operator[]` is constexpr * `operator<<` and `operator+=` are hidden friends
2020-05-10 07:22:11 +02:00
String.tests.cpp:<line number>: PASSED:
with message:
stringref[1] == 'b'
Add more constexpr to StringRef
2020-02-13 15:01:03 +01:00
String.tests.cpp:<line number>: PASSED:
with message:
shortened.size() == 2
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
String.tests.cpp:<line number>: PASSED:
with message:
Add more constexpr to StringRef
2020-02-13 15:01:03 +01:00
shortened.data() == abc
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
String.tests.cpp:<line number>: PASSED:
with message:
Add more constexpr to StringRef
2020-02-13 15:01:03 +01:00
shortened.begin() != shortened.end()
Rework StringRef interface and internals Now it no longer tries to be this weird hybrid between an owning and non-owning reference, and is only ever non-owning. This is also reflected in its interface, for example `StringRef::isNullTerminated` is now public, and `StringRef::c_str()` has the precondition that it is true. Overview of the changes: * The `StringRef::m_data` member has been completely removed, as it had no more uses. * `StringRef::isSubstring()` has been made public and renamed to `StringRef::isNullTerminated()`, so that the name reflects what the method actually does. * `StringRef::currentData()` has been renamed to `StringRef::data()`, to be in line with common C++ containers and container-alikes. * `StringRef::c_str()` will no longer silently make copies. It instead has a precondition that `isNullTerminated()` is true. * If the user needs a null-terminated string, they should use the `std::string` conversion operator and call `c_str()` on the resulting `std::string`. * Some small optimizations in various places. * Basic functionality is now `constexpr`.
2019-10-21 17:44:11 +02:00
-------------------------------------------------------------------------------
StringRef at compilation time
UDL construction
-------------------------------------------------------------------------------
String.tests.cpp:<line number>
...............................................................................
String.tests.cpp:<line number>: PASSED:
with message:
!(sr1.empty())
String.tests.cpp:<line number>: PASSED:
with message:
sr1.size() == 3
String.tests.cpp:<line number>: PASSED:
with message:
sr2.empty()
String.tests.cpp:<line number>: PASSED:
with message:
sr2.size() == 0
Cleanup and optimize stringifying of string-like types More specifically, made the actual implementation of string-like type handling take argument as `Catch::StringRef`, instead of taking `std::string const&`. This means that string-like types that are not `std::string` no longer need to pay for an extra construction of `std::string` (including the potential allocation), before they can be stringified. The actual string stringification routine is now also better about reserving sufficient space.
2021-05-18 00:02:46 +02:00
-------------------------------------------------------------------------------
Stringifying char arrays with statically known sizes - char
-------------------------------------------------------------------------------
ToString.tests.cpp:<line number>
...............................................................................
ToString.tests.cpp:<line number>: PASSED:
CHECK( ::Catch::Detail::stringify( with_null_terminator ) == R"("abc")"s )
with expansion:
""abc"" == ""abc""
ToString.tests.cpp:<line number>: PASSED:
CHECK( ::Catch::Detail::stringify( no_null_terminator ) == R"("abc")"s )
with expansion:
""abc"" == ""abc""
-------------------------------------------------------------------------------
Stringifying char arrays with statically known sizes - signed char
-------------------------------------------------------------------------------
ToString.tests.cpp:<line number>
...............................................................................
ToString.tests.cpp:<line number>: PASSED:
CHECK( ::Catch::Detail::stringify( with_null_terminator ) == R"("abc")"s )
with expansion:
""abc"" == ""abc""
ToString.tests.cpp:<line number>: PASSED:
CHECK( ::Catch::Detail::stringify( no_null_terminator ) == R"("abc")"s )
with expansion:
""abc"" == ""abc""
-------------------------------------------------------------------------------
Stringifying char arrays with statically known sizes - unsigned char
-------------------------------------------------------------------------------
ToString.tests.cpp:<line number>
...............................................................................
ToString.tests.cpp:<line number>: PASSED:
CHECK( ::Catch::Detail::stringify( with_null_terminator ) == R"("abc")"s )
with expansion:
""abc"" == ""abc""
ToString.tests.cpp:<line number>: PASSED:
CHECK( ::Catch::Detail::stringify( no_null_terminator ) == R"("abc")"s )
with expansion:
""abc"" == ""abc""
Add stringification for std::chrono::{duration,time_point} Also hides std::chrono, std::pair and std::chrono::* behind new configuration macros, CATCH_CONFIG_ENABLE_*_STRINGMAKER to avoid dragging in <utility>, <tuple> and <chrono> in common path, unless requested.
2017-10-09 12:31:22 +02:00
-------------------------------------------------------------------------------
Stringifying std::chrono::duration helpers
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
ToStringChrono.tests.cpp:<line number>
Add stringification for std::chrono::{duration,time_point} Also hides std::chrono, std::pair and std::chrono::* behind new configuration macros, CATCH_CONFIG_ENABLE_*_STRINGMAKER to avoid dragging in <utility>, <tuple> and <chrono> in common path, unless requested.
2017-10-09 12:31:22 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringChrono.tests.cpp:<line number>: PASSED:
Add stringification for std::chrono::{duration,time_point} Also hides std::chrono, std::pair and std::chrono::* behind new configuration macros, CATCH_CONFIG_ENABLE_*_STRINGMAKER to avoid dragging in <utility>, <tuple> and <chrono> in common path, unless requested.
2017-10-09 12:31:22 +02:00
REQUIRE( minute == seconds )
with expansion:
1 m == 60 s
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringChrono.tests.cpp:<line number>: PASSED:
Add stringification for std::chrono::{duration,time_point} Also hides std::chrono, std::pair and std::chrono::* behind new configuration macros, CATCH_CONFIG_ENABLE_*_STRINGMAKER to avoid dragging in <utility>, <tuple> and <chrono> in common path, unless requested.
2017-10-09 12:31:22 +02:00
REQUIRE( hour != seconds )
with expansion:
1 h != 60 s
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringChrono.tests.cpp:<line number>: PASSED:
Add stringification for std::chrono::{duration,time_point} Also hides std::chrono, std::pair and std::chrono::* behind new configuration macros, CATCH_CONFIG_ENABLE_*_STRINGMAKER to avoid dragging in <utility>, <tuple> and <chrono> in common path, unless requested.
2017-10-09 12:31:22 +02:00
REQUIRE( micro != milli )
with expansion:
1 us != 1 ms
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringChrono.tests.cpp:<line number>: PASSED:
Add stringification for std::chrono::{duration,time_point} Also hides std::chrono, std::pair and std::chrono::* behind new configuration macros, CATCH_CONFIG_ENABLE_*_STRINGMAKER to avoid dragging in <utility>, <tuple> and <chrono> in common path, unless requested.
2017-10-09 12:31:22 +02:00
REQUIRE( nano != micro )
with expansion:
1 ns != 1 us
-------------------------------------------------------------------------------
Stringifying std::chrono::duration with weird ratios
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
ToStringChrono.tests.cpp:<line number>
Add stringification for std::chrono::{duration,time_point} Also hides std::chrono, std::pair and std::chrono::* behind new configuration macros, CATCH_CONFIG_ENABLE_*_STRINGMAKER to avoid dragging in <utility>, <tuple> and <chrono> in common path, unless requested.
2017-10-09 12:31:22 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringChrono.tests.cpp:<line number>: PASSED:
Add stringification for std::chrono::{duration,time_point} Also hides std::chrono, std::pair and std::chrono::* behind new configuration macros, CATCH_CONFIG_ENABLE_*_STRINGMAKER to avoid dragging in <utility>, <tuple> and <chrono> in common path, unless requested.
2017-10-09 12:31:22 +02:00
REQUIRE( half_minute != femto_second )
with expansion:
1 [30/1]s != 1 fs
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringChrono.tests.cpp:<line number>: PASSED:
Add more weird chrono::duration stringification tests
2017-11-28 21:47:06 +01:00
REQUIRE( pico_second != atto_second )
with expansion:
1 ps != 1 as
Add stringification for std::chrono::{duration,time_point} Also hides std::chrono, std::pair and std::chrono::* behind new configuration macros, CATCH_CONFIG_ENABLE_*_STRINGMAKER to avoid dragging in <utility>, <tuple> and <chrono> in common path, unless requested.
2017-10-09 12:31:22 +02:00
-------------------------------------------------------------------------------
Stringifying std::chrono::time_point<system_clock>
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
ToStringChrono.tests.cpp:<line number>
Add stringification for std::chrono::{duration,time_point} Also hides std::chrono, std::pair and std::chrono::* behind new configuration macros, CATCH_CONFIG_ENABLE_*_STRINGMAKER to avoid dragging in <utility>, <tuple> and <chrono> in common path, unless requested.
2017-10-09 12:31:22 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringChrono.tests.cpp:<line number>: PASSED:
Add stringification for std::chrono::{duration,time_point} Also hides std::chrono, std::pair and std::chrono::* behind new configuration macros, CATCH_CONFIG_ENABLE_*_STRINGMAKER to avoid dragging in <utility>, <tuple> and <chrono> in common path, unless requested.
2017-10-09 12:31:22 +02:00
REQUIRE( now != later )
with expansion:
{iso8601-timestamp}
!=
{iso8601-timestamp}
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Tabs and newlines show in output
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( s1 == s2 )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"if ($b == 10) {
Text formatting rework Rewrote main wrapping loop. Now uses iterators instead of indices and intermediate strings. Differentiates between chars to wrap before, after or instead of. Doesn’t preserve trailing newlines. Wraps or more characters. Dropped support for using tab character as an indent setting control char. Hopefully avoids all the undefined behaviour and other bugs of the previous implementation.
2017-01-17 18:13:23 +01:00
$a = 20;
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
}"
approvals rebase - I *think* this fixes an earlier regression, but I'm not 100% sure where that came from!
2015-07-28 19:24:20 +02:00
==
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"if ($b == 10) {
Text formatting rework Rewrote main wrapping loop. Now uses iterators instead of indices and intermediate strings. Differentiates between chars to wrap before, after or instead of. Doesn’t preserve trailing newlines. Wraps or more characters. Dropped support for using tab character as an indent setting control char. Hopefully avoids all the undefined behaviour and other bugs of the previous implementation.
2017-01-17 18:13:23 +01:00
$a = 20;
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
}
"
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Tag alias can be registered against tag patterns
The same tag alias can only be registered once
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Fix test tag parsing to split [.foo] into [.][foo]
2019-03-29 10:48:56 +01:00
Tag.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
Fix test tag parsing to split [.foo] into [.][foo]
2019-03-29 10:48:56 +01:00
Tag.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
CHECK_THAT( what, ContainsSubstring( "[@zzz]" ) )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Rebased approvals
2017-05-05 19:25:02 +02:00
"error: tag alias, '[@zzz]' already registered.
First seen at: file:2
Redefined at: file:10" contains: "[@zzz]"
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Fix test tag parsing to split [.foo] into [.][foo]
2019-03-29 10:48:56 +01:00
Tag.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
CHECK_THAT( what, ContainsSubstring( "file" ) )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Rebased approvals
2017-05-05 19:25:02 +02:00
"error: tag alias, '[@zzz]' already registered.
First seen at: file:2
Redefined at: file:10" contains: "file"
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Fix test tag parsing to split [.foo] into [.][foo]
2019-03-29 10:48:56 +01:00
Tag.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
CHECK_THAT( what, ContainsSubstring( "2" ) )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
Rebased approvals
2017-05-05 19:25:02 +02:00
"error: tag alias, '[@zzz]' already registered.
First seen at: file:2
Redefined at: file:10" contains: "2"
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Fix test tag parsing to split [.foo] into [.][foo]
2019-03-29 10:48:56 +01:00
Tag.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
CHECK_THAT( what, ContainsSubstring( "10" ) )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
Rebased approvals
2017-05-05 19:25:02 +02:00
"error: tag alias, '[@zzz]' already registered.
First seen at: file:2
Redefined at: file:10" contains: "10"
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Tag alias can be registered against tag patterns
Tag aliases must be of the form [@name]
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Fix test tag parsing to split [.foo] into [.][foo]
2019-03-29 10:48:56 +01:00
Tag.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
Fix test tag parsing to split [.foo] into [.][foo]
2019-03-29 10:48:56 +01:00
Tag.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK_THROWS( registry.add( "[no ampersat]", "", Catch::SourceLineInfo( "file", 3 ) ) )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Fix test tag parsing to split [.foo] into [.][foo]
2019-03-29 10:48:56 +01:00
Tag.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK_THROWS( registry.add( "[the @ is not at the start]", "", Catch::SourceLineInfo( "file", 3 ) ) )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Fix test tag parsing to split [.foo] into [.][foo]
2019-03-29 10:48:56 +01:00
Tag.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK_THROWS( registry.add( "@no square bracket at start]", "", Catch::SourceLineInfo( "file", 3 ) ) )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Fix test tag parsing to split [.foo] into [.][foo]
2019-03-29 10:48:56 +01:00
Tag.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK_THROWS( registry.add( "[@no square bracket at end", "", Catch::SourceLineInfo( "file", 3 ) ) )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Add more tests for various less common tag-related cases
2021-12-27 10:04:48 +01:00
-------------------------------------------------------------------------------
Tags with spaces and non-alphanumerical characters are accepted
-------------------------------------------------------------------------------
Tag.tests.cpp:<line number>
...............................................................................
Tag.tests.cpp:<line number>: PASSED:
REQUIRE( testCase.tags.size() == 2 )
with expansion:
2 == 2
Tag.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( testCase.tags, VectorContains( Tag( "tag with spaces" ) ) && VectorContains( Tag( "I said \"good day\" sir!"_catch_sr ) ) )
with expansion:
{ {?}, {?} } ( Contains: {?} and Contains: {?} )
test approvals for TEMPLATE_LIST_TEST_CASE
2019-05-27 20:41:21 +02:00
-------------------------------------------------------------------------------
Template test case method with test types specified inside std::tuple - MyTypes
- 0
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: PASSED:
REQUIRE( Template_Fixture<TestType>::m_a == 1 )
with expansion:
1 == 1
-------------------------------------------------------------------------------
Template test case method with test types specified inside std::tuple - MyTypes
- 1
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: PASSED:
REQUIRE( Template_Fixture<TestType>::m_a == 1 )
with expansion:
1 == 1
-------------------------------------------------------------------------------
Template test case method with test types specified inside std::tuple - MyTypes
- 2
-------------------------------------------------------------------------------
Class.tests.cpp:<line number>
...............................................................................
Class.tests.cpp:<line number>: PASSED:
REQUIRE( Template_Fixture<TestType>::m_a == 1 )
with expansion:
1.0 == 1
Fix non-default-constructible type lists used in TEMPLATE_LIST_TEST_CASE (#1697) * Fix non-default-constructible type lists used in TEMPLATE_LIST_TEST_CASE std::tuple is not default constructible when the first type is not default-constuctible. Therefore it can not be instantiated. to circumvent this, we have to use std::declval in the unevaluate decltype context.
2019-07-22 12:56:33 +02:00
-------------------------------------------------------------------------------
Allow to use non-copyable and non-movable types in TEMPLATE_LIST_TEST_CASE The parameter given to `convert` may not be copyable therefore it has to be captured by const reference. For example an `std::tuple` that contains a non-copyable type is itself non-copyable. The NonDefaultConstructible test-case was reduced by one example type because it did not add any value.
2019-08-17 11:48:42 +02:00
Template test case with test types specified inside non-copyable and non-
movable std::tuple - NonCopyableAndNonMovableTypes - 0
Fix non-default-constructible type lists used in TEMPLATE_LIST_TEST_CASE (#1697) * Fix non-default-constructible type lists used in TEMPLATE_LIST_TEST_CASE std::tuple is not default constructible when the first type is not default-constuctible. Therefore it can not be instantiated. to circumvent this, we have to use std::declval in the unevaluate decltype context.
2019-07-22 12:56:33 +02:00
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
less copies and allocations in replaceInPlace
2024-02-25 18:01:28 +01:00
REQUIRE( std::is_default_constructible<TestType>::value )
Fix non-default-constructible type lists used in TEMPLATE_LIST_TEST_CASE (#1697) * Fix non-default-constructible type lists used in TEMPLATE_LIST_TEST_CASE std::tuple is not default constructible when the first type is not default-constuctible. Therefore it can not be instantiated. to circumvent this, we have to use std::declval in the unevaluate decltype context.
2019-07-22 12:56:33 +02:00
with expansion:
less copies and allocations in replaceInPlace
2024-02-25 18:01:28 +01:00
true
Fix non-default-constructible type lists used in TEMPLATE_LIST_TEST_CASE (#1697) * Fix non-default-constructible type lists used in TEMPLATE_LIST_TEST_CASE std::tuple is not default constructible when the first type is not default-constuctible. Therefore it can not be instantiated. to circumvent this, we have to use std::declval in the unevaluate decltype context.
2019-07-22 12:56:33 +02:00
Allow to use non-copyable and non-movable types in TEMPLATE_LIST_TEST_CASE The parameter given to `convert` may not be copyable therefore it has to be captured by const reference. For example an `std::tuple` that contains a non-copyable type is itself non-copyable. The NonDefaultConstructible test-case was reduced by one example type because it did not add any value.
2019-08-17 11:48:42 +02:00
-------------------------------------------------------------------------------
Template test case with test types specified inside non-copyable and non-
movable std::tuple - NonCopyableAndNonMovableTypes - 1
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
less copies and allocations in replaceInPlace
2024-02-25 18:01:28 +01:00
REQUIRE( std::is_default_constructible<TestType>::value )
Allow to use non-copyable and non-movable types in TEMPLATE_LIST_TEST_CASE The parameter given to `convert` may not be copyable therefore it has to be captured by const reference. For example an `std::tuple` that contains a non-copyable type is itself non-copyable. The NonDefaultConstructible test-case was reduced by one example type because it did not add any value.
2019-08-17 11:48:42 +02:00
with expansion:
less copies and allocations in replaceInPlace
2024-02-25 18:01:28 +01:00
true
Allow to use non-copyable and non-movable types in TEMPLATE_LIST_TEST_CASE The parameter given to `convert` may not be copyable therefore it has to be captured by const reference. For example an `std::tuple` that contains a non-copyable type is itself non-copyable. The NonDefaultConstructible test-case was reduced by one example type because it did not add any value.
2019-08-17 11:48:42 +02:00
Fix non-default-constructible type lists used in TEMPLATE_LIST_TEST_CASE (#1697) * Fix non-default-constructible type lists used in TEMPLATE_LIST_TEST_CASE std::tuple is not default constructible when the first type is not default-constuctible. Therefore it can not be instantiated. to circumvent this, we have to use std::declval in the unevaluate decltype context.
2019-07-22 12:56:33 +02:00
-------------------------------------------------------------------------------
Template test case with test types specified inside non-default-constructible
Allow to use non-copyable and non-movable types in TEMPLATE_LIST_TEST_CASE The parameter given to `convert` may not be copyable therefore it has to be captured by const reference. For example an `std::tuple` that contains a non-copyable type is itself non-copyable. The NonDefaultConstructible test-case was reduced by one example type because it did not add any value.
2019-08-17 11:48:42 +02:00
std::tuple - MyNonDefaultConstructibleTypes - 0
Fix non-default-constructible type lists used in TEMPLATE_LIST_TEST_CASE (#1697) * Fix non-default-constructible type lists used in TEMPLATE_LIST_TEST_CASE std::tuple is not default constructible when the first type is not default-constuctible. Therefore it can not be instantiated. to circumvent this, we have to use std::declval in the unevaluate decltype context.
2019-07-22 12:56:33 +02:00
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
less copies and allocations in replaceInPlace
2024-02-25 18:01:28 +01:00
REQUIRE( std::is_trivially_copyable<TestType>::value )
Fix non-default-constructible type lists used in TEMPLATE_LIST_TEST_CASE (#1697) * Fix non-default-constructible type lists used in TEMPLATE_LIST_TEST_CASE std::tuple is not default constructible when the first type is not default-constuctible. Therefore it can not be instantiated. to circumvent this, we have to use std::declval in the unevaluate decltype context.
2019-07-22 12:56:33 +02:00
with expansion:
less copies and allocations in replaceInPlace
2024-02-25 18:01:28 +01:00
true
Fix non-default-constructible type lists used in TEMPLATE_LIST_TEST_CASE (#1697) * Fix non-default-constructible type lists used in TEMPLATE_LIST_TEST_CASE std::tuple is not default constructible when the first type is not default-constuctible. Therefore it can not be instantiated. to circumvent this, we have to use std::declval in the unevaluate decltype context.
2019-07-22 12:56:33 +02:00
-------------------------------------------------------------------------------
Template test case with test types specified inside non-default-constructible
Allow to use non-copyable and non-movable types in TEMPLATE_LIST_TEST_CASE The parameter given to `convert` may not be copyable therefore it has to be captured by const reference. For example an `std::tuple` that contains a non-copyable type is itself non-copyable. The NonDefaultConstructible test-case was reduced by one example type because it did not add any value.
2019-08-17 11:48:42 +02:00
std::tuple - MyNonDefaultConstructibleTypes - 1
Fix non-default-constructible type lists used in TEMPLATE_LIST_TEST_CASE (#1697) * Fix non-default-constructible type lists used in TEMPLATE_LIST_TEST_CASE std::tuple is not default constructible when the first type is not default-constuctible. Therefore it can not be instantiated. to circumvent this, we have to use std::declval in the unevaluate decltype context.
2019-07-22 12:56:33 +02:00
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
less copies and allocations in replaceInPlace
2024-02-25 18:01:28 +01:00
REQUIRE( std::is_trivially_copyable<TestType>::value )
Fix non-default-constructible type lists used in TEMPLATE_LIST_TEST_CASE (#1697) * Fix non-default-constructible type lists used in TEMPLATE_LIST_TEST_CASE std::tuple is not default constructible when the first type is not default-constuctible. Therefore it can not be instantiated. to circumvent this, we have to use std::declval in the unevaluate decltype context.
2019-07-22 12:56:33 +02:00
with expansion:
less copies and allocations in replaceInPlace
2024-02-25 18:01:28 +01:00
true
Fix non-default-constructible type lists used in TEMPLATE_LIST_TEST_CASE (#1697) * Fix non-default-constructible type lists used in TEMPLATE_LIST_TEST_CASE std::tuple is not default constructible when the first type is not default-constuctible. Therefore it can not be instantiated. to circumvent this, we have to use std::declval in the unevaluate decltype context.
2019-07-22 12:56:33 +02:00
test approvals for TEMPLATE_LIST_TEST_CASE
2019-05-27 20:41:21 +02:00
-------------------------------------------------------------------------------
Template test case with test types specified inside std::tuple - MyTypes - 0
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
less copies and allocations in replaceInPlace
2024-02-25 18:01:28 +01:00
REQUIRE( std::is_arithmetic<TestType>::value )
test approvals for TEMPLATE_LIST_TEST_CASE
2019-05-27 20:41:21 +02:00
with expansion:
less copies and allocations in replaceInPlace
2024-02-25 18:01:28 +01:00
true
test approvals for TEMPLATE_LIST_TEST_CASE
2019-05-27 20:41:21 +02:00
-------------------------------------------------------------------------------
Template test case with test types specified inside std::tuple - MyTypes - 1
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
less copies and allocations in replaceInPlace
2024-02-25 18:01:28 +01:00
REQUIRE( std::is_arithmetic<TestType>::value )
test approvals for TEMPLATE_LIST_TEST_CASE
2019-05-27 20:41:21 +02:00
with expansion:
less copies and allocations in replaceInPlace
2024-02-25 18:01:28 +01:00
true
test approvals for TEMPLATE_LIST_TEST_CASE
2019-05-27 20:41:21 +02:00
-------------------------------------------------------------------------------
Template test case with test types specified inside std::tuple - MyTypes - 2
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
less copies and allocations in replaceInPlace
2024-02-25 18:01:28 +01:00
REQUIRE( std::is_arithmetic<TestType>::value )
test approvals for TEMPLATE_LIST_TEST_CASE
2019-05-27 20:41:21 +02:00
with expansion:
less copies and allocations in replaceInPlace
2024-02-25 18:01:28 +01:00
true
test approvals for TEMPLATE_LIST_TEST_CASE
2019-05-27 20:41:21 +02:00
Add support for templated tests This adds support for templated tests and test methods via `TEMPLATE_TEST_CASE` and `TEMPLATE_TEST_CASE_METHOD` macros. These work mostly just like their regular counterparts*, but take an unlimited** number of types as their last arguments. * Unlike the plain `TEST_CASE*` macros, the `TEMPLATE*` variants require a tag string. ** In practice there is limit of about 300 types.
2018-11-08 07:26:39 +01:00
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - float
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 5 )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 5 )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - float
resizing bigger changes size and capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 10 )
with expansion:
10 == 10
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 10 )
with expansion:
10 >= 10
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - float
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 5 )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 5 )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - float
resizing smaller changes size but not capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 0 )
with expansion:
0 == 0
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 5 )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - float
resizing smaller changes size but not capacity
We can use the 'swap trick' to reset the capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - float
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 5 )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 5 )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - float
reserving bigger changes capacity but not size
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 5 )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 10 )
with expansion:
10 >= 10
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - float
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 5 )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 5 )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - float
reserving smaller does not change size or capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 5 )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 5 )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - int
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 5 )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 5 )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - int
resizing bigger changes size and capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 10 )
with expansion:
10 == 10
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 10 )
with expansion:
10 >= 10
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - int
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 5 )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 5 )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - int
resizing smaller changes size but not capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 0 )
with expansion:
0 == 0
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 5 )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - int
resizing smaller changes size but not capacity
We can use the 'swap trick' to reset the capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - int
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 5 )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 5 )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - int
reserving bigger changes capacity but not size
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 5 )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 10 )
with expansion:
10 >= 10
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - int
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 5 )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 5 )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - int
reserving smaller does not change size or capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 5 )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 5 )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - std::string
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 5 )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 5 )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - std::string
resizing bigger changes size and capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 10 )
with expansion:
10 == 10
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 10 )
with expansion:
10 >= 10
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - std::string
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 5 )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 5 )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - std::string
resizing smaller changes size but not capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 0 )
with expansion:
0 == 0
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 5 )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - std::string
resizing smaller changes size but not capacity
We can use the 'swap trick' to reset the capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - std::string
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 5 )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 5 )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - std::string
reserving bigger changes capacity but not size
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 5 )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 10 )
with expansion:
10 >= 10
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - std::string
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 5 )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 5 )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - std::string
reserving smaller does not change size or capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 5 )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 5 )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - std::tuple<int,float>
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 5 )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 5 )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - std::tuple<int,float>
resizing bigger changes size and capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 10 )
with expansion:
10 == 10
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 10 )
with expansion:
10 >= 10
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - std::tuple<int,float>
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 5 )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 5 )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - std::tuple<int,float>
resizing smaller changes size but not capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 0 )
with expansion:
0 == 0
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 5 )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - std::tuple<int,float>
resizing smaller changes size but not capacity
We can use the 'swap trick' to reset the capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - std::tuple<int,float>
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 5 )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 5 )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - std::tuple<int,float>
reserving bigger changes capacity but not size
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 5 )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 10 )
with expansion:
10 >= 10
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - std::tuple<int,float>
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 5 )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 5 )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTest: vectors can be sized and resized - std::tuple<int,float>
reserving smaller does not change size or capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 5 )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 5 )
with expansion:
5 >= 5
Nttp support tests approvals
2019-05-23 19:29:18 +02:00
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - (std::tuple<int, float>), 6
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == V )
with expansion:
6 == 6
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= V )
with expansion:
6 >= 6
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - (std::tuple<int, float>), 6
resizing bigger changes size and capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 2 * V )
with expansion:
12 == 12
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 2 * V )
with expansion:
12 >= 12
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - (std::tuple<int, float>), 6
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == V )
with expansion:
6 == 6
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= V )
with expansion:
6 >= 6
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - (std::tuple<int, float>), 6
resizing smaller changes size but not capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 0 )
with expansion:
0 == 0
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= V )
with expansion:
6 >= 6
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - (std::tuple<int, float>), 6
resizing smaller changes size but not capacity
We can use the 'swap trick' to reset the capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - (std::tuple<int, float>), 6
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == V )
with expansion:
6 == 6
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= V )
with expansion:
6 >= 6
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - (std::tuple<int, float>), 6
reserving bigger changes capacity but not size
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == V )
with expansion:
6 == 6
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 2 * V )
with expansion:
12 >= 12
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - (std::tuple<int, float>), 6
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == V )
with expansion:
6 == 6
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= V )
with expansion:
6 >= 6
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - (std::tuple<int, float>), 6
reserving smaller does not change size or capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == V )
with expansion:
6 == 6
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= V )
with expansion:
6 >= 6
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - float,4
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == V )
with expansion:
4 == 4
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= V )
with expansion:
4 >= 4
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - float,4
resizing bigger changes size and capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 2 * V )
with expansion:
8 == 8
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 2 * V )
with expansion:
8 >= 8
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - float,4
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == V )
with expansion:
4 == 4
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= V )
with expansion:
4 >= 4
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - float,4
resizing smaller changes size but not capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 0 )
with expansion:
0 == 0
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= V )
with expansion:
4 >= 4
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - float,4
resizing smaller changes size but not capacity
We can use the 'swap trick' to reset the capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - float,4
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == V )
with expansion:
4 == 4
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= V )
with expansion:
4 >= 4
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - float,4
reserving bigger changes capacity but not size
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == V )
with expansion:
4 == 4
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 2 * V )
with expansion:
8 >= 8
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - float,4
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == V )
with expansion:
4 == 4
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= V )
with expansion:
4 >= 4
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - float,4
reserving smaller does not change size or capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == V )
with expansion:
4 == 4
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= V )
with expansion:
4 >= 4
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - int,5
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == V )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= V )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - int,5
resizing bigger changes size and capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 2 * V )
with expansion:
10 == 10
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 2 * V )
with expansion:
10 >= 10
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - int,5
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == V )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= V )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - int,5
resizing smaller changes size but not capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 0 )
with expansion:
0 == 0
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= V )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - int,5
resizing smaller changes size but not capacity
We can use the 'swap trick' to reset the capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - int,5
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == V )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= V )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - int,5
reserving bigger changes capacity but not size
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == V )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 2 * V )
with expansion:
10 >= 10
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - int,5
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == V )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= V )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - int,5
reserving smaller does not change size or capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == V )
with expansion:
5 == 5
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= V )
with expansion:
5 >= 5
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - std::string,15
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == V )
with expansion:
15 == 15
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= V )
with expansion:
15 >= 15
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - std::string,15
resizing bigger changes size and capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 2 * V )
with expansion:
30 == 30
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 2 * V )
with expansion:
30 >= 30
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - std::string,15
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == V )
with expansion:
15 == 15
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= V )
with expansion:
15 >= 15
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - std::string,15
resizing smaller changes size but not capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == 0 )
with expansion:
0 == 0
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= V )
with expansion:
15 >= 15
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - std::string,15
resizing smaller changes size but not capacity
We can use the 'swap trick' to reset the capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - std::string,15
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == V )
with expansion:
15 == 15
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= V )
with expansion:
15 >= 15
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - std::string,15
reserving bigger changes capacity but not size
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == V )
with expansion:
15 == 15
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= 2 * V )
with expansion:
30 >= 30
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - std::string,15
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == V )
with expansion:
15 == 15
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= V )
with expansion:
15 >= 15
-------------------------------------------------------------------------------
TemplateTestSig: vectors can be sized and resized - std::string,15
reserving smaller does not change size or capacity
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.size() == V )
with expansion:
15 == 15
Misc.tests.cpp:<line number>: PASSED:
REQUIRE( v.capacity() >= V )
with expansion:
15 >= 15
Add more tests for various less common tag-related cases
2021-12-27 10:04:48 +01:00
-------------------------------------------------------------------------------
Test case with identical tags keeps just one
-------------------------------------------------------------------------------
Tag.tests.cpp:<line number>
...............................................................................
Tag.tests.cpp:<line number>: PASSED:
REQUIRE( testCase.tags.size() == 1 )
with expansion:
1 == 1
Tag.tests.cpp:<line number>: PASSED:
REQUIRE( testCase.tags[0] == Tag( "tag1" ) )
with expansion:
{?} == {?}
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Test case with one argument
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
VariadicMacros.tests.cpp:<line number>
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
VariadicMacros.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with message:
no assertions
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Test enum bit values
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Tricky.tests.cpp:<line number>
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( 0x<hex digits> == bit30and31 )
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
3221225472 (0x<hex digits>) == 3221225472
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
Add tests for escaping special characters in CLI
2019-09-21 00:11:45 +02:00
-------------------------------------------------------------------------------
Test with special, characters "in name
-------------------------------------------------------------------------------
CmdLine.tests.cpp:<line number>
...............................................................................
CmdLine.tests.cpp:<line number>: PASSED:
Suppress failure of CHECKED_IF and CHECKED_ELSE (#2187) Resolves #1390 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2021-05-10 21:42:47 +02:00
-------------------------------------------------------------------------------
Testing checked-if
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
CHECKED_IF( true )
Misc.tests.cpp:<line number>: PASSED:
Misc.tests.cpp:<line number>: FAILED - but was ok:
CHECKED_IF( false )
Misc.tests.cpp:<line number>: PASSED:
CHECKED_ELSE( true )
Misc.tests.cpp:<line number>: FAILED - but was ok:
CHECKED_ELSE( false )
Misc.tests.cpp:<line number>: PASSED:
-------------------------------------------------------------------------------
Testing checked-if 2
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
CHECKED_IF( true )
Misc.tests.cpp:<line number>: FAILED:
-------------------------------------------------------------------------------
Testing checked-if 3
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: FAILED - but was ok:
CHECKED_ELSE( false )
Misc.tests.cpp:<line number>: FAILED:
Assert Info reset need to also reset result disposition to normal to handle uncaught exception correctly (#2723) * AssertionEnd does not reset the assertion info yet. That is done after populateReaction. And reset assertion info would also reset the result disposition to normal, so that any uncaught exception would be reported as failure * Approving test output changes due to added unit tests * Unit tests to throw std::runtime_error instead of std::exception * Add a unit test to test incomplete assertion handler --------- Co-authored-by: Ross <ross.tang@gfo-x.com>
2023-08-07 22:07:31 +02:00
-------------------------------------------------------------------------------
Testing checked-if 4
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: PASSED:
CHECKED_ELSE( true )
Misc.tests.cpp:<line number>: FAILED:
{Unknown expression after the reported line}
due to unexpected exception with message:
Uncaught exception should fail!
-------------------------------------------------------------------------------
Testing checked-if 5
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: FAILED - but was ok:
CHECKED_ELSE( false )
Misc.tests.cpp:<line number>: FAILED:
{Unknown expression after the reported line}
due to unexpected exception with message:
Uncaught exception should fail!
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
The NO_FAIL macro reports a failure but does not fail the test
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Message.tests.cpp:<line number>
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Message.tests.cpp:<line number>: FAILED - but was ok:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK_NOFAIL( 1 == 2 )
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
Fixed NoAssertions warning
2018-01-26 17:52:28 +01:00
No assertions in test case 'The NO_FAIL macro reports a failure but does not fail the test'
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
The default listing implementation write to provided stream
Listing tags
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( listingString, ContainsSubstring("[fakeTag]"s) )
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
with expansion:
"All available tags:
1 [fakeTag]
1 tag
" contains: "[fakeTag]"
-------------------------------------------------------------------------------
The default listing implementation write to provided stream
Listing reporters
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
Slight improvement for reporter test
2022-05-10 19:16:50 +02:00
REQUIRE_THAT( listingString, ContainsSubstring( "fake reporter"s ) && ContainsSubstring( "fake description"s ) )
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
with expansion:
"Available reporters:
fake reporter: fake description
Slight improvement for reporter test
2022-05-10 19:16:50 +02:00
" ( contains: "fake reporter" and contains: "fake description" )
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
-------------------------------------------------------------------------------
The default listing implementation write to provided stream
Listing tests
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( listingString, ContainsSubstring( "fake test name"s ) && ContainsSubstring( "fakeTestTag"s ) )
--list-* flags write to target specified by the -o flag Also added tests for the default implementations of list* reporter helpers. Closes #2061
2021-01-26 17:53:59 +01:00
with expansion:
"All available test cases:
fake test name
[fakeTestTag]
1 test case
" ( contains: "fake test name" and contains: "fakeTestTag" )
Add --list-listeners option
2022-05-10 20:00:36 +02:00
-------------------------------------------------------------------------------
The default listing implementation write to provided stream
Listing listeners
-------------------------------------------------------------------------------
Reporters.tests.cpp:<line number>
...............................................................................
Reporters.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( listingString, ContainsSubstring( "fakeListener"s ) && ContainsSubstring( "fake description"s ) )
with expansion:
"Registered listeners:
fakeListener: fake description
" ( contains: "fakeListener" and contains: "fake description" )
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
This test 'should' fail but doesn't
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with message:
oops!
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
Covered more translation possibilities
2018-02-15 19:58:49 +01:00
-------------------------------------------------------------------------------
Thrown string literals are translated
-------------------------------------------------------------------------------
Exception.tests.cpp:<line number>
...............................................................................
Exception.tests.cpp:<line number>: FAILED:
due to unexpected exception with message:
For some reason someone is throwing a string literal!
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
-------------------------------------------------------------------------------
Tracker
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
PartTracker.tests.cpp:<line number>
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase.isOpen() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s1.isOpen() )
with expansion:
true
-------------------------------------------------------------------------------
Tracker
successfully close one section
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
PartTracker.tests.cpp:<line number>
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s1.isSuccessfullyCompleted() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase.isComplete() == false )
with expansion:
false == false
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( ctx.completedCycle() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase.isSuccessfullyCompleted() )
with expansion:
true
-------------------------------------------------------------------------------
Tracker
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
PartTracker.tests.cpp:<line number>
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase.isOpen() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s1.isOpen() )
with expansion:
true
-------------------------------------------------------------------------------
Tracker
fail one section
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
PartTracker.tests.cpp:<line number>
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s1.isComplete() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s1.isSuccessfullyCompleted() == false )
with expansion:
false == false
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase.isComplete() == false )
with expansion:
false == false
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( ctx.completedCycle() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase.isSuccessfullyCompleted() == false )
with expansion:
false == false
-------------------------------------------------------------------------------
Tracker
fail one section
re-enter after failed section
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
PartTracker.tests.cpp:<line number>
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase2.isOpen() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s1b.isOpen() == false )
with expansion:
false == false
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( ctx.completedCycle() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase.isComplete() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase.isSuccessfullyCompleted() )
with expansion:
true
-------------------------------------------------------------------------------
Tracker
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
PartTracker.tests.cpp:<line number>
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase.isOpen() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s1.isOpen() )
with expansion:
true
-------------------------------------------------------------------------------
Tracker
fail one section
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
PartTracker.tests.cpp:<line number>
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s1.isComplete() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s1.isSuccessfullyCompleted() == false )
with expansion:
false == false
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase.isComplete() == false )
with expansion:
false == false
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( ctx.completedCycle() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase.isSuccessfullyCompleted() == false )
with expansion:
false == false
-------------------------------------------------------------------------------
Tracker
fail one section
re-enter after failed section and find next section
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
PartTracker.tests.cpp:<line number>
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase2.isOpen() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s1b.isOpen() == false )
with expansion:
false == false
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s2.isOpen() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( ctx.completedCycle() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase.isComplete() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase.isSuccessfullyCompleted() )
with expansion:
true
-------------------------------------------------------------------------------
Tracker
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
PartTracker.tests.cpp:<line number>
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase.isOpen() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s1.isOpen() )
with expansion:
true
-------------------------------------------------------------------------------
Tracker
successfully close one section, then find another
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
PartTracker.tests.cpp:<line number>
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s2.isOpen() == false )
with expansion:
false == false
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase.isComplete() == false )
with expansion:
false == false
-------------------------------------------------------------------------------
Tracker
successfully close one section, then find another
Re-enter - skips S1 and enters S2
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
PartTracker.tests.cpp:<line number>
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase2.isOpen() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s1b.isOpen() == false )
with expansion:
false == false
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s2b.isOpen() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( ctx.completedCycle() == false )
with expansion:
false == false
-------------------------------------------------------------------------------
Tracker
successfully close one section, then find another
Re-enter - skips S1 and enters S2
Successfully close S2
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
PartTracker.tests.cpp:<line number>
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( ctx.completedCycle() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s2b.isSuccessfullyCompleted() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase2.isComplete() == false )
with expansion:
false == false
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase2.isSuccessfullyCompleted() )
with expansion:
true
-------------------------------------------------------------------------------
Tracker
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
PartTracker.tests.cpp:<line number>
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase.isOpen() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s1.isOpen() )
with expansion:
true
-------------------------------------------------------------------------------
Tracker
successfully close one section, then find another
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
PartTracker.tests.cpp:<line number>
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s2.isOpen() == false )
with expansion:
false == false
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase.isComplete() == false )
with expansion:
false == false
-------------------------------------------------------------------------------
Tracker
successfully close one section, then find another
Re-enter - skips S1 and enters S2
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
PartTracker.tests.cpp:<line number>
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase2.isOpen() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s1b.isOpen() == false )
with expansion:
false == false
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s2b.isOpen() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( ctx.completedCycle() == false )
with expansion:
false == false
-------------------------------------------------------------------------------
Tracker
successfully close one section, then find another
Re-enter - skips S1 and enters S2
fail S2
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
PartTracker.tests.cpp:<line number>
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( ctx.completedCycle() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s2b.isComplete() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s2b.isSuccessfullyCompleted() == false )
with expansion:
false == false
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase2.isSuccessfullyCompleted() == false )
with expansion:
false == false
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase3.isOpen() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s1c.isOpen() == false )
with expansion:
false == false
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s2c.isOpen() == false )
with expansion:
false == false
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase3.isSuccessfullyCompleted() )
with expansion:
true
-------------------------------------------------------------------------------
Tracker
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
PartTracker.tests.cpp:<line number>
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase.isOpen() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s1.isOpen() )
with expansion:
true
-------------------------------------------------------------------------------
Tracker
open a nested section
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
PartTracker.tests.cpp:<line number>
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s2.isOpen() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s2.isComplete() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s1.isComplete() == false )
with expansion:
false == false
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( s1.isComplete() )
with expansion:
true
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase.isComplete() == false )
with expansion:
false == false
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
PartTracker.tests.cpp:<line number>: PASSED:
Approved changes due to "No assertions" warnings now firing correctly on inner sections
2015-11-03 08:33:43 +01:00
REQUIRE( testCase.isComplete() )
with expansion:
true
Start adding tests for string manip functions
2019-09-06 18:50:57 +02:00
-------------------------------------------------------------------------------
Trim strings
-------------------------------------------------------------------------------
StringManip.tests.cpp:<line number>
...............................................................................
StringManip.tests.cpp:<line number>: PASSED:
REQUIRE( trim(std::string(no_whitespace)) == no_whitespace )
with expansion:
"There is no extra whitespace here"
==
"There is no extra whitespace here"
StringManip.tests.cpp:<line number>: PASSED:
REQUIRE( trim(std::string(leading_whitespace)) == no_whitespace )
with expansion:
"There is no extra whitespace here"
==
"There is no extra whitespace here"
StringManip.tests.cpp:<line number>: PASSED:
REQUIRE( trim(std::string(trailing_whitespace)) == no_whitespace )
with expansion:
"There is no extra whitespace here"
==
"There is no extra whitespace here"
StringManip.tests.cpp:<line number>: PASSED:
REQUIRE( trim(std::string(whitespace_at_both_ends)) == no_whitespace )
with expansion:
"There is no extra whitespace here"
==
"There is no extra whitespace here"
Add trim for StringRef
2019-09-07 11:31:00 +02:00
StringManip.tests.cpp:<line number>: PASSED:
REQUIRE( trim(StringRef(no_whitespace)) == StringRef(no_whitespace) )
with expansion:
There is no extra whitespace here
==
There is no extra whitespace here
StringManip.tests.cpp:<line number>: PASSED:
REQUIRE( trim(StringRef(leading_whitespace)) == StringRef(no_whitespace) )
with expansion:
There is no extra whitespace here
==
There is no extra whitespace here
StringManip.tests.cpp:<line number>: PASSED:
REQUIRE( trim(StringRef(trailing_whitespace)) == StringRef(no_whitespace) )
with expansion:
There is no extra whitespace here
==
There is no extra whitespace here
StringManip.tests.cpp:<line number>: PASSED:
REQUIRE( trim(StringRef(whitespace_at_both_ends)) == StringRef(no_whitespace) )
with expansion:
There is no extra whitespace here
==
There is no extra whitespace here
Added ElementsAre and UnorderedElementsAre (#2377) Co-authored-by: Garz4 <fancygarz4@gmail.com> Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2023-01-22 00:33:04 +01:00
-------------------------------------------------------------------------------
Type conversions of RangeEquals and similar
Container conversions
Two equal containers of different container types
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( array_int_a, RangeEquals( c_array ) )
with expansion:
{ 1, 2, 3 } elements are { 1, 2, 3 }
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( array_int_a, UnorderedRangeEquals( c_array ) )
with expansion:
{ 1, 2, 3 } unordered elements are { 1, 2, 3 }
-------------------------------------------------------------------------------
Type conversions of RangeEquals and similar
Container conversions
Two equal containers of different container types (differ in array N)
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( array_int_3, !RangeEquals( array_int_4 ) )
with expansion:
{ 1, 2, 3 } not elements are { 1, 2, 3, 4 }
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( array_int_3, !UnorderedRangeEquals( array_int_4 ) )
with expansion:
{ 1, 2, 3 } not unordered elements are { 1, 2, 3, 4 }
-------------------------------------------------------------------------------
Type conversions of RangeEquals and similar
Container conversions
Two equal containers of different container types and value types
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( array_int_a, RangeEquals( vector_char_a ) )
with expansion:
{ 1, 2, 3 } elements are { 1, 2, 3 }
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( array_int_a, UnorderedRangeEquals( vector_char_a ) )
with expansion:
{ 1, 2, 3 } unordered elements are { 1, 2, 3 }
-------------------------------------------------------------------------------
Type conversions of RangeEquals and similar
Container conversions
Two equal containers, one random access, one not
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
with message:
ContainerIsRandomAccess( array_int_a ) != ContainerIsRandomAccess(
list_char_a )
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( array_int_a, RangeEquals( list_char_a ) )
with expansion:
{ 1, 2, 3 } elements are { 1, 2, 3 }
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( array_int_a, UnorderedRangeEquals( list_char_a ) )
with expansion:
{ 1, 2, 3 } unordered elements are { 1, 2, 3 }
-------------------------------------------------------------------------------
Type conversions of RangeEquals and similar
Value type
Two equal containers of different value types
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( vector_int_a, RangeEquals( vector_char_a ) )
with expansion:
{ 1, 2, 3 } elements are { 1, 2, 3 }
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( vector_int_a, UnorderedRangeEquals( vector_char_a ) )
with expansion:
{ 1, 2, 3 } unordered elements are { 1, 2, 3 }
-------------------------------------------------------------------------------
Type conversions of RangeEquals and similar
Value type
Two non-equal containers of different value types
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( vector_int_a, !RangeEquals( vector_char_b ) )
with expansion:
{ 1, 2, 3 } not elements are { 1, 2, 2 }
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( vector_int_a, !UnorderedRangeEquals( vector_char_b ) )
with expansion:
{ 1, 2, 3 } not unordered elements are { 1, 2, 2 }
-------------------------------------------------------------------------------
Type conversions of RangeEquals and similar
Ranges with begin that needs ADL
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( a, !RangeEquals( b ) )
with expansion:
{ 1, 2, 3 } not elements are { 3, 2, 1 }
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( a, UnorderedRangeEquals( b ) )
with expansion:
{ 1, 2, 3 } unordered elements are { 3, 2, 1 }
-------------------------------------------------------------------------------
Type conversions of RangeEquals and similar
Custom predicate
Two equal non-empty containers (close enough)
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( vector_a, RangeEquals( array_a_plus_1, close_enough ) )
with expansion:
{ 1, 2, 3 } elements are { 2, 3, 4 }
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( vector_a, UnorderedRangeEquals( array_a_plus_1, close_enough ) )
with expansion:
{ 1, 2, 3 } unordered elements are { 2, 3, 4 }
approved tests that were correct the first time (previous approvals were erroneous)
2017-04-09 21:40:01 +02:00
-------------------------------------------------------------------------------
Unexpected exceptions can be translated
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Exception.tests.cpp:<line number>
approved tests that were correct the first time (previous approvals were erroneous)
2017-04-09 21:40:01 +02:00
...............................................................................
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Exception.tests.cpp:<line number>: FAILED:
approved tests that were correct the first time (previous approvals were erroneous)
2017-04-09 21:40:01 +02:00
due to unexpected exception with message:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
3.14000000000000012
approved tests that were correct the first time (previous approvals were erroneous)
2017-04-09 21:40:01 +02:00
Implement a simplified variant of std::unique_ptr<T> This simplified variant supports only a subset of the functionality in `std::unique_ptr<T>`. `Catch::Detail::unique_ptr<T>` only supports single element pointer (no array support) with default deleter. By removing the support for custom deleters, we also avoid requiring significant machinery to support EBO, speeding up instantiations of `unique_ptr<T>` significantly. Catch2 also currently does not need to support `unique_ptr<T[]>`, so that is not supported either.
2020-05-24 23:41:02 +02:00
-------------------------------------------------------------------------------
Upcasting special member functions
Move constructor
-------------------------------------------------------------------------------
UniquePtr.tests.cpp:<line number>
...............................................................................
UniquePtr.tests.cpp:<line number>: PASSED:
REQUIRE( bptr->i == 3 )
with expansion:
3 == 3
-------------------------------------------------------------------------------
Upcasting special member functions
move assignment
-------------------------------------------------------------------------------
UniquePtr.tests.cpp:<line number>
...............................................................................
UniquePtr.tests.cpp:<line number>: PASSED:
REQUIRE( bptr->i == 3 )
with expansion:
3 == 3
Add IsEmpty and SizeIs matchers for ranges/containers `SizeIs` can accept both `size_t` and a matcher. In the first case, it checks whether the size of the range is equal to specified size. In the second case, it checks whether the provided matcher accepts the size of the range.
2020-03-09 11:13:07 +01:00
-------------------------------------------------------------------------------
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
Usage of AllMatch range matcher
Basic usage
Add IsEmpty and SizeIs matchers for ranges/containers `SizeIs` can accept both `size_t` and a matcher. In the first case, it checks whether the size of the range is equal to specified size. In the second case, it checks whether the provided matcher accepts the size of the range.
2020-03-09 11:13:07 +01:00
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
REQUIRE_THAT( data, AllMatch(SizeIs(5)) )
Add IsEmpty and SizeIs matchers for ranges/containers `SizeIs` can accept both `size_t` and a matcher. In the first case, it checks whether the size of the range is equal to specified size. In the second case, it checks whether the provided matcher accepts the size of the range.
2020-03-09 11:13:07 +01:00
with expansion:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
{ { 0, 1, 2, 3, 5 }, { 4, -3, -2, 5, 0 }, { 0, 0, 0, 5, 0 }, { 0, -5, 0, 5, 0
}, { 1, 0, 0, -1, 5 } } all match has size == 5
Add IsEmpty and SizeIs matchers for ranges/containers `SizeIs` can accept both `size_t` and a matcher. In the first case, it checks whether the size of the range is equal to specified size. In the second case, it checks whether the provided matcher accepts the size of the range.
2020-03-09 11:13:07 +01:00
MatchersRanges.tests.cpp:<line number>: PASSED:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
REQUIRE_THAT( data, !AllMatch(Contains(0) && Contains(1)) )
Add IsEmpty and SizeIs matchers for ranges/containers `SizeIs` can accept both `size_t` and a matcher. In the first case, it checks whether the size of the range is equal to specified size. In the second case, it checks whether the provided matcher accepts the size of the range.
2020-03-09 11:13:07 +01:00
with expansion:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
{ { 0, 1, 2, 3, 5 }, { 4, -3, -2, 5, 0 }, { 0, 0, 0, 5, 0 }, { 0, -5, 0, 5, 0
}, { 1, 0, 0, -1, 5 } } not all match ( contains element 0 and contains
element 1 )
-------------------------------------------------------------------------------
Usage of AllMatch range matcher
Type requires ADL found begin and end
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
Add IsEmpty and SizeIs matchers for ranges/containers `SizeIs` can accept both `size_t` and a matcher. In the first case, it checks whether the size of the range is equal to specified size. In the second case, it checks whether the provided matcher accepts the size of the range.
2020-03-09 11:13:07 +01:00
MatchersRanges.tests.cpp:<line number>: PASSED:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
REQUIRE_THAT( needs_adl, AllMatch( Predicate<int>( []( int elem ) { return elem < 6; } ) ) )
Add IsEmpty and SizeIs matchers for ranges/containers `SizeIs` can accept both `size_t` and a matcher. In the first case, it checks whether the size of the range is equal to specified size. In the second case, it checks whether the provided matcher accepts the size of the range.
2020-03-09 11:13:07 +01:00
with expansion:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
{ 1, 2, 3, 4, 5 } all match matches undescribed predicate
-------------------------------------------------------------------------------
Usage of AllMatch range matcher
Shortcircuiting
All are read
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
Add IsEmpty and SizeIs matchers for ranges/containers `SizeIs` can accept both `size_t` and a matcher. In the first case, it checks whether the size of the range is equal to specified size. In the second case, it checks whether the provided matcher accepts the size of the range.
2020-03-09 11:13:07 +01:00
MatchersRanges.tests.cpp:<line number>: PASSED:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
REQUIRE_THAT( mocked, allMatch )
Add IsEmpty and SizeIs matchers for ranges/containers `SizeIs` can accept both `size_t` and a matcher. In the first case, it checks whether the size of the range is equal to specified size. In the second case, it checks whether the provided matcher accepts the size of the range.
2020-03-09 11:13:07 +01:00
with expansion:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
{ 1, 2, 3, 4, 5 } all match matches undescribed predicate
Add IsEmpty and SizeIs matchers for ranges/containers `SizeIs` can accept both `size_t` and a matcher. In the first case, it checks whether the size of the range is equal to specified size. In the second case, it checks whether the provided matcher accepts the size of the range.
2020-03-09 11:13:07 +01:00
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE( mocked.m_derefed[0] )
Add IsEmpty and SizeIs matchers for ranges/containers `SizeIs` can accept both `size_t` and a matcher. In the first case, it checks whether the size of the range is equal to specified size. In the second case, it checks whether the provided matcher accepts the size of the range.
2020-03-09 11:13:07 +01:00
with expansion:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
true
Add IsEmpty and SizeIs matchers for ranges/containers `SizeIs` can accept both `size_t` and a matcher. In the first case, it checks whether the size of the range is equal to specified size. In the second case, it checks whether the provided matcher accepts the size of the range.
2020-03-09 11:13:07 +01:00
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE( mocked.m_derefed[1] )
Add IsEmpty and SizeIs matchers for ranges/containers `SizeIs` can accept both `size_t` and a matcher. In the first case, it checks whether the size of the range is equal to specified size. In the second case, it checks whether the provided matcher accepts the size of the range.
2020-03-09 11:13:07 +01:00
with expansion:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
true
Add IsEmpty and SizeIs matchers for ranges/containers `SizeIs` can accept both `size_t` and a matcher. In the first case, it checks whether the size of the range is equal to specified size. In the second case, it checks whether the provided matcher accepts the size of the range.
2020-03-09 11:13:07 +01:00
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE( mocked.m_derefed[2] )
Add IsEmpty and SizeIs matchers for ranges/containers `SizeIs` can accept both `size_t` and a matcher. In the first case, it checks whether the size of the range is equal to specified size. In the second case, it checks whether the provided matcher accepts the size of the range.
2020-03-09 11:13:07 +01:00
with expansion:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
true
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE( mocked.m_derefed[3] )
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE( mocked.m_derefed[4] )
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
with expansion:
true
Add IsEmpty and SizeIs matchers for ranges/containers `SizeIs` can accept both `size_t` and a matcher. In the first case, it checks whether the size of the range is equal to specified size. In the second case, it checks whether the provided matcher accepts the size of the range.
2020-03-09 11:13:07 +01:00
-------------------------------------------------------------------------------
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
Usage of AllMatch range matcher
Shortcircuiting
Short-circuited
Add IsEmpty and SizeIs matchers for ranges/containers `SizeIs` can accept both `size_t` and a matcher. In the first case, it checks whether the size of the range is equal to specified size. In the second case, it checks whether the provided matcher accepts the size of the range.
2020-03-09 11:13:07 +01:00
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
REQUIRE_THAT( mocked, !allMatch )
Add IsEmpty and SizeIs matchers for ranges/containers `SizeIs` can accept both `size_t` and a matcher. In the first case, it checks whether the size of the range is equal to specified size. In the second case, it checks whether the provided matcher accepts the size of the range.
2020-03-09 11:13:07 +01:00
with expansion:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
{ 1, 2, 3, 4, 5 } not all match matches undescribed predicate
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE( mocked.m_derefed[0] )
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE( mocked.m_derefed[1] )
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE( mocked.m_derefed[2] )
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE_FALSE( mocked.m_derefed[3] )
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
with expansion:
!false
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE_FALSE( mocked.m_derefed[4] )
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
with expansion:
!false
Add IsEmpty and SizeIs matchers for ranges/containers `SizeIs` can accept both `size_t` and a matcher. In the first case, it checks whether the size of the range is equal to specified size. In the second case, it checks whether the provided matcher accepts the size of the range.
2020-03-09 11:13:07 +01:00
Add AllTrue, AnyTrue, NoneTrue matchers
2021-11-14 17:05:31 +01:00
-------------------------------------------------------------------------------
Usage of AllTrue range matcher
Basic usage
All true evaluates to true
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( data, AllTrue() )
with expansion:
{ true, true, true, true, true } contains only true
-------------------------------------------------------------------------------
Usage of AllTrue range matcher
Basic usage
Empty evaluates to true
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( data, AllTrue() )
with expansion:
{ } contains only true
-------------------------------------------------------------------------------
Usage of AllTrue range matcher
Basic usage
Fix spelling
2023-04-25 20:14:27 +02:00
One false evaluates to false
Add AllTrue, AnyTrue, NoneTrue matchers
2021-11-14 17:05:31 +01:00
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( data, !AllTrue() )
with expansion:
{ true, true, false, true, true } not contains only true
-------------------------------------------------------------------------------
Usage of AllTrue range matcher
Basic usage
All false evaluates to false
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( data, !AllTrue() )
with expansion:
{ false, false, false, false, false } not contains only true
-------------------------------------------------------------------------------
Usage of AllTrue range matcher
Contained type is convertible to bool
All true evaluates to true
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( data, AllTrue() )
with expansion:
{ true, true, true, true, true } contains only true
-------------------------------------------------------------------------------
Usage of AllTrue range matcher
Contained type is convertible to bool
Fix spelling
2023-04-25 20:14:27 +02:00
One false evaluates to false
Add AllTrue, AnyTrue, NoneTrue matchers
2021-11-14 17:05:31 +01:00
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( data, !AllTrue() )
with expansion:
{ true, true, false, true, true } not contains only true
-------------------------------------------------------------------------------
Usage of AllTrue range matcher
Contained type is convertible to bool
All false evaluates to false
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( data, !AllTrue() )
with expansion:
{ false, false, false, false, false } not contains only true
-------------------------------------------------------------------------------
Usage of AllTrue range matcher
Shortcircuiting
All are read
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( mocked, AllTrue() )
with expansion:
{ true, true, true, true, true } contains only true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked.m_derefed[0] )
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked.m_derefed[1] )
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked.m_derefed[2] )
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked.m_derefed[3] )
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked.m_derefed[4] )
with expansion:
true
-------------------------------------------------------------------------------
Usage of AllTrue range matcher
Shortcircuiting
Short-circuited
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( mocked, !AllTrue() )
with expansion:
{ true, true, false, true, true } not contains only true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked.m_derefed[0] )
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked.m_derefed[1] )
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked.m_derefed[2] )
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( mocked.m_derefed[3] )
with expansion:
!false
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( mocked.m_derefed[4] )
with expansion:
!false
Add IsEmpty and SizeIs matchers for ranges/containers `SizeIs` can accept both `size_t` and a matcher. In the first case, it checks whether the size of the range is equal to specified size. In the second case, it checks whether the provided matcher accepts the size of the range.
2020-03-09 11:13:07 +01:00
-------------------------------------------------------------------------------
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
Usage of AnyMatch range matcher
Basic usage
Add IsEmpty and SizeIs matchers for ranges/containers `SizeIs` can accept both `size_t` and a matcher. In the first case, it checks whether the size of the range is equal to specified size. In the second case, it checks whether the provided matcher accepts the size of the range.
2020-03-09 11:13:07 +01:00
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
REQUIRE_THAT( data, AnyMatch(SizeIs(5)) )
Add IsEmpty and SizeIs matchers for ranges/containers `SizeIs` can accept both `size_t` and a matcher. In the first case, it checks whether the size of the range is equal to specified size. In the second case, it checks whether the provided matcher accepts the size of the range.
2020-03-09 11:13:07 +01:00
with expansion:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
{ { 0, 1, 2, 3, 5 }, { 4, -3, -2, 5, 0 }, { 0, 0, 0, 5, 0 }, { 0, -5, 0, 5, 0
}, { 1, 0, 0, -1, 5 } } any match has size == 5
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( data, !AnyMatch(Contains(0) && Contains(10)) )
with expansion:
{ { 0, 1, 2, 3, 5 }, { 4, -3, -2, 5, 0 }, { 0, 0, 0, 5, 0 }, { 0, -5, 0, 5, 0
}, { 1, 0, 0, -1, 5 } } not any match ( contains element 0 and contains
element 10 )
Add IsEmpty and SizeIs matchers for ranges/containers `SizeIs` can accept both `size_t` and a matcher. In the first case, it checks whether the size of the range is equal to specified size. In the second case, it checks whether the provided matcher accepts the size of the range.
2020-03-09 11:13:07 +01:00
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
-------------------------------------------------------------------------------
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
Usage of AnyMatch range matcher
Type requires ADL found begin and end
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
REQUIRE_THAT( needs_adl, AnyMatch( Predicate<int>( []( int elem ) { return elem < 3; } ) ) )
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
with expansion:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
{ 1, 2, 3, 4, 5 } any match matches undescribed predicate
-------------------------------------------------------------------------------
Usage of AnyMatch range matcher
Shortcircuiting
All are read
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
MatchersRanges.tests.cpp:<line number>: PASSED:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
REQUIRE_THAT( mocked, !anyMatch )
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
with expansion:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
{ 1, 2, 3, 4, 5 } not any match matches undescribed predicate
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE( mocked.m_derefed[0] )
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
with expansion:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
true
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE( mocked.m_derefed[1] )
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
with expansion:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
true
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE( mocked.m_derefed[2] )
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
with expansion:
true
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE( mocked.m_derefed[3] )
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
with expansion:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
true
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE( mocked.m_derefed[4] )
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
with expansion:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
true
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
-------------------------------------------------------------------------------
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
Usage of AnyMatch range matcher
Shortcircuiting
Short-circuited
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
REQUIRE_THAT( mocked, anyMatch )
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
with expansion:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
{ 1, 2, 3, 4, 5 } any match matches undescribed predicate
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE( mocked.m_derefed[0] )
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
with expansion:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
true
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE_FALSE( mocked.m_derefed[1] )
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
with expansion:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
!false
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE_FALSE( mocked.m_derefed[2] )
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
with expansion:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
!false
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE_FALSE( mocked.m_derefed[3] )
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
with expansion:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
!false
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE_FALSE( mocked.m_derefed[4] )
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
with expansion:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
!false
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
Add AllTrue, AnyTrue, NoneTrue matchers
2021-11-14 17:05:31 +01:00
-------------------------------------------------------------------------------
Usage of AnyTrue range matcher
Basic usage
All true evaluates to true
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( data, AnyTrue() )
with expansion:
{ true, true, true, true, true } contains at least one true
-------------------------------------------------------------------------------
Usage of AnyTrue range matcher
Basic usage
Empty evaluates to false
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( data, !AnyTrue() )
with expansion:
{ } not contains at least one true
-------------------------------------------------------------------------------
Usage of AnyTrue range matcher
Basic usage
Fix spelling
2023-04-25 20:14:27 +02:00
One true evaluates to true
Add AllTrue, AnyTrue, NoneTrue matchers
2021-11-14 17:05:31 +01:00
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( data, AnyTrue() )
with expansion:
{ false, false, true, false, false } contains at least one true
-------------------------------------------------------------------------------
Usage of AnyTrue range matcher
Basic usage
All false evaluates to false
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( data, !AnyTrue() )
with expansion:
{ false, false, false, false, false } not contains at least one true
-------------------------------------------------------------------------------
Usage of AnyTrue range matcher
Contained type is convertible to bool
All true evaluates to true
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( data, AnyTrue() )
with expansion:
{ true, true, true, true, true } contains at least one true
-------------------------------------------------------------------------------
Usage of AnyTrue range matcher
Contained type is convertible to bool
Fix spelling
2023-04-25 20:14:27 +02:00
One true evaluates to true
Add AllTrue, AnyTrue, NoneTrue matchers
2021-11-14 17:05:31 +01:00
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( data, AnyTrue() )
with expansion:
{ false, false, true, false, false } contains at least one true
-------------------------------------------------------------------------------
Usage of AnyTrue range matcher
Contained type is convertible to bool
All false evaluates to false
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( data, !AnyTrue() )
with expansion:
{ false, false, false, false, false } not contains at least one true
-------------------------------------------------------------------------------
Usage of AnyTrue range matcher
Shortcircuiting
All are read
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( mocked, AnyTrue() )
with expansion:
{ false, false, false, false, true } contains at least one true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked.m_derefed[0] )
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked.m_derefed[1] )
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked.m_derefed[2] )
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked.m_derefed[3] )
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked.m_derefed[4] )
with expansion:
true
-------------------------------------------------------------------------------
Usage of AnyTrue range matcher
Shortcircuiting
Short-circuited
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( mocked, AnyTrue() )
with expansion:
{ false, false, true, true, true } contains at least one true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked.m_derefed[0] )
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked.m_derefed[1] )
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked.m_derefed[2] )
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( mocked.m_derefed[3] )
with expansion:
!false
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( mocked.m_derefed[4] )
with expansion:
!false
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
-------------------------------------------------------------------------------
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
Usage of NoneMatch range matcher
Basic usage
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
REQUIRE_THAT( data, NoneMatch(SizeIs(6)) )
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
with expansion:
{ { 0, 1, 2, 3, 5 }, { 4, -3, -2, 5, 0 }, { 0, 0, 0, 5, 0 }, { 0, -5, 0, 5, 0
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
}, { 1, 0, 0, -1, 5 } } none match has size == 6
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
MatchersRanges.tests.cpp:<line number>: PASSED:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
REQUIRE_THAT( data, !NoneMatch(Contains(0) && Contains(1)) )
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
with expansion:
{ { 0, 1, 2, 3, 5 }, { 4, -3, -2, 5, 0 }, { 0, 0, 0, 5, 0 }, { 0, -5, 0, 5, 0
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
}, { 1, 0, 0, -1, 5 } } not none match ( contains element 0 and contains
element 1 )
-------------------------------------------------------------------------------
Usage of NoneMatch range matcher
Type requires ADL found begin and end
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
MatchersRanges.tests.cpp:<line number>: PASSED:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
REQUIRE_THAT( needs_adl, NoneMatch( Predicate<int>( []( int elem ) { return elem > 6; } ) ) )
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
with expansion:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
{ 1, 2, 3, 4, 5 } none match matches undescribed predicate
-------------------------------------------------------------------------------
Usage of NoneMatch range matcher
Shortcircuiting
All are read
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( mocked, noneMatch )
with expansion:
{ 1, 2, 3, 4, 5 } none match matches undescribed predicate
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE( mocked.m_derefed[0] )
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE( mocked.m_derefed[1] )
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE( mocked.m_derefed[2] )
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
with expansion:
true
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE( mocked.m_derefed[3] )
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
with expansion:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
true
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE( mocked.m_derefed[4] )
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
with expansion:
true
-------------------------------------------------------------------------------
Usage of NoneMatch range matcher
Shortcircuiting
Short-circuited
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
MatchersRanges.tests.cpp:<line number>: PASSED:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
REQUIRE_THAT( mocked, !noneMatch )
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
with expansion:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
{ 1, 2, 3, 4, 5 } not none match matches undescribed predicate
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE( mocked.m_derefed[0] )
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
with expansion:
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
true
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE_FALSE( mocked.m_derefed[1] )
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
with expansion:
!false
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE_FALSE( mocked.m_derefed[2] )
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
with expansion:
!false
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE_FALSE( mocked.m_derefed[3] )
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
with expansion:
!false
MatchersRanges.tests.cpp:<line number>: PASSED:
Refactor MatchersRanges test utils (#2386) - do not hardcode content of containers - prefix members with m_ - add const and non-const iterators to `with_mocked_iterator_access` - remove `m_touched` as it wasn't filled properly and isn't used anyway
2022-03-09 23:13:37 +01:00
REQUIRE_FALSE( mocked.m_derefed[4] )
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
with expansion:
!false
Add AllTrue, AnyTrue, NoneTrue matchers
2021-11-14 17:05:31 +01:00
-------------------------------------------------------------------------------
Usage of NoneTrue range matcher
Basic usage
All true evaluates to false
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( data, !NoneTrue() )
with expansion:
{ true, true, true, true, true } not contains no true
-------------------------------------------------------------------------------
Usage of NoneTrue range matcher
Basic usage
Empty evaluates to true
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( data, NoneTrue() )
with expansion:
{ } contains no true
-------------------------------------------------------------------------------
Usage of NoneTrue range matcher
Basic usage
Fix spelling
2023-04-25 20:14:27 +02:00
One true evaluates to false
Add AllTrue, AnyTrue, NoneTrue matchers
2021-11-14 17:05:31 +01:00
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( data, !NoneTrue() )
with expansion:
{ false, false, true, false, false } not contains no true
-------------------------------------------------------------------------------
Usage of NoneTrue range matcher
Basic usage
All false evaluates to true
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( data, NoneTrue() )
with expansion:
{ false, false, false, false, false } contains no true
-------------------------------------------------------------------------------
Usage of NoneTrue range matcher
Contained type is convertible to bool
All true evaluates to false
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( data, !NoneTrue() )
with expansion:
{ true, true, true, true, true } not contains no true
-------------------------------------------------------------------------------
Usage of NoneTrue range matcher
Contained type is convertible to bool
Fix spelling
2023-04-25 20:14:27 +02:00
One true evaluates to false
Add AllTrue, AnyTrue, NoneTrue matchers
2021-11-14 17:05:31 +01:00
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( data, !NoneTrue() )
with expansion:
{ false, false, true, false, false } not contains no true
-------------------------------------------------------------------------------
Usage of NoneTrue range matcher
Contained type is convertible to bool
All false evaluates to true
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( data, NoneTrue() )
with expansion:
{ false, false, false, false, false } contains no true
-------------------------------------------------------------------------------
Usage of NoneTrue range matcher
Shortcircuiting
All are read
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( mocked, NoneTrue() )
with expansion:
{ false, false, false, false, false } contains no true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked.m_derefed[0] )
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked.m_derefed[1] )
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked.m_derefed[2] )
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked.m_derefed[3] )
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked.m_derefed[4] )
with expansion:
true
-------------------------------------------------------------------------------
Usage of NoneTrue range matcher
Shortcircuiting
Short-circuited
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( mocked, !NoneTrue() )
with expansion:
{ false, false, true, true, true } not contains no true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked.m_derefed[0] )
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked.m_derefed[1] )
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked.m_derefed[2] )
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( mocked.m_derefed[3] )
with expansion:
!false
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( mocked.m_derefed[4] )
with expansion:
!false
Added ElementsAre and UnorderedElementsAre (#2377) Co-authored-by: Garz4 <fancygarz4@gmail.com> Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2023-01-22 00:33:04 +01:00
-------------------------------------------------------------------------------
Usage of RangeEquals range matcher
Basic usage
Empty container matches empty container
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( empty_vector, RangeEquals( empty_vector ) )
with expansion:
{ } elements are { }
-------------------------------------------------------------------------------
Usage of RangeEquals range matcher
Basic usage
Empty container does not match non-empty container
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( empty_vector, !RangeEquals( non_empty_vector ) )
with expansion:
{ } not elements are { 1 }
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( non_empty_vector, !RangeEquals( empty_vector ) )
with expansion:
{ 1 } not elements are { }
-------------------------------------------------------------------------------
Usage of RangeEquals range matcher
Basic usage
Two equal 1-length non-empty containers
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( non_empty_array, RangeEquals( non_empty_array ) )
with expansion:
{ 1 } elements are { 1 }
-------------------------------------------------------------------------------
Usage of RangeEquals range matcher
Basic usage
Two equal-sized, equal, non-empty containers
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( array_a, RangeEquals( array_a ) )
with expansion:
{ 1, 2, 3 } elements are { 1, 2, 3 }
-------------------------------------------------------------------------------
Usage of RangeEquals range matcher
Basic usage
Two equal-sized, non-equal, non-empty containers
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( array_a, !RangeEquals( array_b ) )
with expansion:
{ 1, 2, 3 } not elements are { 2, 2, 3 }
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( array_a, !RangeEquals( array_c ) )
with expansion:
{ 1, 2, 3 } not elements are { 1, 2, 2 }
-------------------------------------------------------------------------------
Usage of RangeEquals range matcher
Basic usage
Two non-equal-sized, non-empty containers (with same first elements)
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( vector_a, !RangeEquals( vector_b ) )
with expansion:
{ 1, 2, 3 } not elements are { 1, 2, 3, 4 }
-------------------------------------------------------------------------------
Usage of RangeEquals range matcher
Custom predicate
Two equal non-empty containers (close enough)
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( vector_a, RangeEquals( vector_a_plus_1, close_enough ) )
with expansion:
{ 1, 2, 3 } elements are { 2, 3, 4 }
-------------------------------------------------------------------------------
Usage of RangeEquals range matcher
Custom predicate
Two non-equal non-empty containers (close enough)
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( vector_a, !RangeEquals( vector_b, close_enough ) )
with expansion:
{ 1, 2, 3 } not elements are { 3, 3, 4 }
Fix RangeEquals matcher to handle iterator + sentinel ranges Also added tests for types that require ADL lookup for their `begin` and `end`.
2023-02-03 16:12:09 +01:00
-------------------------------------------------------------------------------
Usage of RangeEquals range matcher
Ranges that need ADL begin/end
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( needs_adl1, RangeEquals( needs_adl2 ) )
with expansion:
{ 1, 2, 3, 4, 5 } elements are { 1, 2, 3, 4, 5 }
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( needs_adl1, RangeEquals( needs_adl3, []( int l, int r ) { return l + 1 == r; } ) )
with expansion:
{ 1, 2, 3, 4, 5 } elements are { 2, 3, 4, 5, 6 }
Provide overloads for {Unordered}RangeEquals taking a std::initializer_list This allows writing something like const auto v = calculateSomeVectorOfInts(); CHECK_THAT(v, RangeEquals({1, 2, 3})); Fixes #2915.
2024-10-12 17:18:59 +02:00
-------------------------------------------------------------------------------
Usage of RangeEquals range matcher
Compare against std::initializer_list
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( array_a, RangeEquals( { 1, 2, 3 } ) )
with expansion:
{ 1, 2, 3 } elements are { 1, 2, 3 }
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( array_a, RangeEquals( { 2, 4, 6 }, []( int l, int r ) { return l * 2 == r; } ) )
with expansion:
{ 1, 2, 3 } elements are { 2, 4, 6 }
Fix RangeEquals matcher to handle iterator + sentinel ranges Also added tests for types that require ADL lookup for their `begin` and `end`.
2023-02-03 16:12:09 +01:00
-------------------------------------------------------------------------------
Usage of RangeEquals range matcher
Check short-circuiting behaviour
Check short-circuits on failure
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( mocked1, !RangeEquals( arr ) )
with expansion:
{ 1, 2, 3, 4 } not elements are { 1, 2, 4, 4 }
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked1.m_derefed[0] )
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked1.m_derefed[1] )
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked1.m_derefed[2] )
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( mocked1.m_derefed[3] )
with expansion:
!false
-------------------------------------------------------------------------------
Usage of RangeEquals range matcher
Check short-circuiting behaviour
All elements are checked on success
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( mocked1, RangeEquals( arr ) )
with expansion:
{ 1, 2, 3, 4 } elements are { 1, 2, 3, 4 }
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked1.m_derefed[0] )
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked1.m_derefed[1] )
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked1.m_derefed[2] )
with expansion:
true
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE( mocked1.m_derefed[3] )
with expansion:
true
Added ElementsAre and UnorderedElementsAre (#2377) Co-authored-by: Garz4 <fancygarz4@gmail.com> Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2023-01-22 00:33:04 +01:00
-------------------------------------------------------------------------------
Usage of UnorderedRangeEquals range matcher
Basic usage
Empty container matches empty container
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( empty_vector, UnorderedRangeEquals( empty_vector ) )
with expansion:
{ } unordered elements are { }
-------------------------------------------------------------------------------
Usage of UnorderedRangeEquals range matcher
Basic usage
Empty container does not match non-empty container
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( empty_vector, !UnorderedRangeEquals( non_empty_vector ) )
with expansion:
{ } not unordered elements are { 1 }
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( non_empty_vector, !UnorderedRangeEquals( empty_vector ) )
with expansion:
{ 1 } not unordered elements are { }
-------------------------------------------------------------------------------
Usage of UnorderedRangeEquals range matcher
Basic usage
Two equal 1-length non-empty containers
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( non_empty_array, UnorderedRangeEquals( non_empty_array ) )
with expansion:
{ 1 } unordered elements are { 1 }
-------------------------------------------------------------------------------
Usage of UnorderedRangeEquals range matcher
Basic usage
Two equal-sized, equal, non-empty containers
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( array_a, UnorderedRangeEquals( array_a ) )
with expansion:
{ 1, 2, 3 } unordered elements are { 1, 2, 3 }
-------------------------------------------------------------------------------
Usage of UnorderedRangeEquals range matcher
Basic usage
Two equal-sized, non-equal, non-empty containers
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( array_a, !UnorderedRangeEquals( array_b ) )
with expansion:
{ 1, 2, 3 } not unordered elements are { 2, 2, 3 }
-------------------------------------------------------------------------------
Usage of UnorderedRangeEquals range matcher
Basic usage
Two non-equal-sized, non-empty containers
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( vector_a, !UnorderedRangeEquals( vector_b ) )
with expansion:
{ 1, 2, 3 } not unordered elements are { 1, 2, 3, 4 }
-------------------------------------------------------------------------------
Usage of UnorderedRangeEquals range matcher
Custom predicate
Two equal non-empty containers (close enough)
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( vector_a, UnorderedRangeEquals( vector_a_plus_1, close_enough ) )
with expansion:
{ 1, 10, 20 } unordered elements are { 11, 21, 2 }
-------------------------------------------------------------------------------
Usage of UnorderedRangeEquals range matcher
Custom predicate
Two non-equal non-empty containers (close enough)
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
CHECK_THAT( vector_a, !UnorderedRangeEquals( vector_b, close_enough ) )
with expansion:
{ 1, 10, 21 } not unordered elements are { 11, 21, 3 }
Enable use of UnorderedRangeEquals with iterator+sentinel pairs
2023-02-06 15:34:32 +01:00
-------------------------------------------------------------------------------
Usage of UnorderedRangeEquals range matcher
Ranges that need ADL begin/end
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( needs_adl1, UnorderedRangeEquals( needs_adl2 ) )
with expansion:
{ 1, 2, 3, 4, 5 } unordered elements are { 1, 2, 3, 4, 5 }
Provide overloads for {Unordered}RangeEquals taking a std::initializer_list This allows writing something like const auto v = calculateSomeVectorOfInts(); CHECK_THAT(v, RangeEquals({1, 2, 3})); Fixes #2915.
2024-10-12 17:18:59 +02:00
-------------------------------------------------------------------------------
Usage of UnorderedRangeEquals range matcher
Compare against std::initializer_list
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( array_a, UnorderedRangeEquals( { 10, 20, 1 } ) )
with expansion:
{ 1, 10, 20 } unordered elements are { 10, 20, 1 }
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( array_a, UnorderedRangeEquals( { 11, 21, 2 }, []( int l, int r ) { return std::abs( l - r ) <= 1; } ) )
with expansion:
{ 1, 10, 20 } unordered elements are { 11, 21, 2 }
Add more comprehensive tests for the quantifier matchers This includes * Testing both positive and negative path through the matchers * Testing them with types whose `begin` and `end` member functions require ADL * Testing them with types that return different types from `begin` and `end`
2020-12-26 23:09:51 +01:00
-------------------------------------------------------------------------------
Usage of the SizeIs range matcher
Some with stdlib containers
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( empty_vec, SizeIs(0) )
with expansion:
{ } has size == 0
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( empty_vec, !SizeIs(2) )
with expansion:
{ } not has size == 2
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( empty_vec, SizeIs(Lt(2)) )
with expansion:
{ } size matches is less than 2
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( arr, SizeIs(2) )
with expansion:
{ 0, 0 } has size == 2
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( arr, SizeIs( Lt(3)) )
with expansion:
{ 0, 0 } size matches is less than 3
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( arr, !SizeIs(!Lt(3)) )
with expansion:
{ 0, 0 } not size matches not is less than 3
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( map, SizeIs(3) )
with expansion:
{ {?}, {?}, {?} } has size == 3
-------------------------------------------------------------------------------
Usage of the SizeIs range matcher
Type requires ADL found size free function
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( unrelated::ADL_size{}, SizeIs(12) )
with expansion:
{?} has size == 12
-------------------------------------------------------------------------------
Usage of the SizeIs range matcher
Type has size member
-------------------------------------------------------------------------------
MatchersRanges.tests.cpp:<line number>
...............................................................................
MatchersRanges.tests.cpp:<line number>: PASSED:
REQUIRE_THAT( has_size{}, SizeIs(13) )
with expansion:
{?} has size == 13
Added AnyMatch, AllMatch and NoneMatch
2020-12-08 00:23:54 +01:00
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Use a custom approx
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Approx.tests.cpp:<line number>
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( d == approx( 1.23 ) )
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.22999999999999998
==
Approx( 1.22999999999999998 )
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( d == approx( 1.22 ) )
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.22999999999999998
==
Approx( 1.21999999999999997 )
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( d == approx( 1.24 ) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.22999999999999998
==
Approx( 1.23999999999999999 )
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( d != approx( 1.25 ) )
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.22999999999999998 != Approx( 1.25 )
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( approx( d ) == 1.23 )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
Approx( 1.22999999999999998 )
==
1.22999999999999998
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( approx( d ) == 1.22 )
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
Approx( 1.22999999999999998 )
==
1.21999999999999997
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( approx( d ) == 1.24 )
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
Approx( 1.22999999999999998 )
==
1.23999999999999999
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Approx.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( approx( d ) != 1.25 )
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
Approx( 1.22999999999999998 ) != 1.25
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
Variadic macros
Section with one argument
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
VariadicMacros.tests.cpp:<line number>
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
VariadicMacros.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with message:
no assertions
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
Added a vector approximate matcher
2019-01-14 15:31:09 +01:00
-------------------------------------------------------------------------------
Vector Approx matcher
Empty vector is roughly equal to an empty vector
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( empty, Approx( empty ) )
Added a vector approximate matcher
2019-01-14 15:31:09 +01:00
with expansion:
{ } is approx: { }
-------------------------------------------------------------------------------
Vector Approx matcher
Vectors with elements
A vector is approx equal to itself
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( v1, Approx( v1 ) )
Added a vector approximate matcher
2019-01-14 15:31:09 +01:00
with expansion:
{ 1.0, 2.0, 3.0 } is approx: { 1.0, 2.0, 3.0 }
Support custom allocators in vector Matchers (#1909) -- Combined with f4fc2dab2c5bb8cab11b0a0dde8a8421076c30f9 during cherry-picking.
2020-04-16 15:36:54 +02:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( v1, Approx<double>( { 1., 2., 3. } ) )
Support custom allocators in vector Matchers (#1909) -- Combined with f4fc2dab2c5bb8cab11b0a0dde8a8421076c30f9 during cherry-picking.
2020-04-16 15:36:54 +02:00
with expansion:
{ 1.0, 2.0, 3.0 } is approx: { 1.0, 2.0, 3.0 }
Added a vector approximate matcher
2019-01-14 15:31:09 +01:00
-------------------------------------------------------------------------------
Vector Approx matcher
Vectors with elements
Different length
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( v1, !Approx( temp ) )
Added a vector approximate matcher
2019-01-14 15:31:09 +01:00
with expansion:
{ 1.0, 2.0, 3.0 } not is approx: { 1.0, 2.0, 3.0, 4.0 }
-------------------------------------------------------------------------------
Vector Approx matcher
Vectors with elements
Same length, different elements
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( v1, !Approx( v2 ) )
Added a vector approximate matcher
2019-01-14 15:31:09 +01:00
with expansion:
{ 1.0, 2.0, 3.0 } not is approx: { 1.5, 2.5, 3.5 }
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( v1, Approx( v2 ).margin( 0.5 ) )
Added a vector approximate matcher
2019-01-14 15:31:09 +01:00
with expansion:
{ 1.0, 2.0, 3.0 } is approx: { 1.5, 2.5, 3.5 }
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( v1, Approx( v2 ).epsilon( 0.5 ) )
Added a vector approximate matcher
2019-01-14 15:31:09 +01:00
with expansion:
{ 1.0, 2.0, 3.0 } is approx: { 1.5, 2.5, 3.5 }
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( v1, Approx( v2 ).epsilon( 0.1 ).scale( 500 ) )
Added a vector approximate matcher
2019-01-14 15:31:09 +01:00
with expansion:
{ 1.0, 2.0, 3.0 } is approx: { 1.5, 2.5, 3.5 }
-------------------------------------------------------------------------------
Vector Approx matcher -- failing
Empty and non empty vectors are not approx equal
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( empty, Approx( t1 ) )
Added a vector approximate matcher
2019-01-14 15:31:09 +01:00
with expansion:
{ } is approx: { 1.0, 2.0 }
-------------------------------------------------------------------------------
Vector Approx matcher -- failing
Just different vectors
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( v1, Approx( v2 ) )
Added a vector approximate matcher
2019-01-14 15:31:09 +01:00
with expansion:
{ 2.0, 4.0, 6.0 } is approx: { 1.0, 3.0, 5.0 }
Added first vector matchers (Contains and Equals)
2017-02-21 17:05:04 +01:00
-------------------------------------------------------------------------------
Vector matchers
Contains (element)
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>
Added first vector matchers (Contains and Equals)
2017-02-21 17:05:04 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( v, VectorContains( 1 ) )
Added first vector matchers (Contains and Equals)
2017-02-21 17:05:04 +01:00
with expansion:
{ 1, 2, 3 } Contains: 1
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( v, VectorContains( 2 ) )
Added first vector matchers (Contains and Equals)
2017-02-21 17:05:04 +01:00
with expansion:
{ 1, 2, 3 } Contains: 2
Support custom allocators in vector Matchers (#1909) -- Combined with f4fc2dab2c5bb8cab11b0a0dde8a8421076c30f9 during cherry-picking.
2020-04-16 15:36:54 +02:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( v5, ( VectorContains<int, CustomAllocator<int>>( 2 ) ) )
Support custom allocators in vector Matchers (#1909) -- Combined with f4fc2dab2c5bb8cab11b0a0dde8a8421076c30f9 during cherry-picking.
2020-04-16 15:36:54 +02:00
with expansion:
{ 1, 2, 3 } Contains: 2
Added first vector matchers (Contains and Equals)
2017-02-21 17:05:04 +01:00
-------------------------------------------------------------------------------
Vector matchers
Contains (vector)
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>
Added first vector matchers (Contains and Equals)
2017-02-21 17:05:04 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( v, Contains( v2 ) )
Added first vector matchers (Contains and Equals)
2017-02-21 17:05:04 +01:00
with expansion:
{ 1, 2, 3 } Contains: { 1, 2 }
Support custom allocators in vector Matchers (#1909) -- Combined with f4fc2dab2c5bb8cab11b0a0dde8a8421076c30f9 during cherry-picking.
2020-04-16 15:36:54 +02:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( v, Contains<int>( { 1, 2 } ) )
Support custom allocators in vector Matchers (#1909) -- Combined with f4fc2dab2c5bb8cab11b0a0dde8a8421076c30f9 during cherry-picking.
2020-04-16 15:36:54 +02:00
with expansion:
{ 1, 2, 3 } Contains: { 1, 2 }
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( v5, ( Contains<int, std::allocator<int>, CustomAllocator<int>>( v2 ) ) )
Support custom allocators in vector Matchers (#1909) -- Combined with f4fc2dab2c5bb8cab11b0a0dde8a8421076c30f9 during cherry-picking.
2020-04-16 15:36:54 +02:00
with expansion:
{ 1, 2, 3 } Contains: { 1, 2 }
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( v, Contains( v2 ) )
Added first vector matchers (Contains and Equals)
2017-02-21 17:05:04 +01:00
with expansion:
{ 1, 2, 3 } Contains: { 1, 2, 3 }
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( v, Contains( empty ) )
Added first vector matchers (Contains and Equals)
2017-02-21 17:05:04 +01:00
with expansion:
{ 1, 2, 3 } Contains: { }
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( empty, Contains( empty ) )
Added first vector matchers (Contains and Equals)
2017-02-21 17:05:04 +01:00
with expansion:
{ } Contains: { }
Support custom allocators in vector Matchers (#1909) -- Combined with f4fc2dab2c5bb8cab11b0a0dde8a8421076c30f9 during cherry-picking.
2020-04-16 15:36:54 +02:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( v5, ( Contains<int, std::allocator<int>, CustomAllocator<int>>( v2 ) ) )
Support custom allocators in vector Matchers (#1909) -- Combined with f4fc2dab2c5bb8cab11b0a0dde8a8421076c30f9 during cherry-picking.
2020-04-16 15:36:54 +02:00
with expansion:
{ 1, 2, 3 } Contains: { 1, 2, 3 }
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( v5, Contains( v6 ) )
Support custom allocators in vector Matchers (#1909) -- Combined with f4fc2dab2c5bb8cab11b0a0dde8a8421076c30f9 during cherry-picking.
2020-04-16 15:36:54 +02:00
with expansion:
{ 1, 2, 3 } Contains: { 1, 2 }
Removed vestigal ComparatorT template arg to MatcherBase
2017-11-13 11:06:26 +01:00
-------------------------------------------------------------------------------
Vector matchers
Contains (element), composed
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>
Removed vestigal ComparatorT template arg to MatcherBase
2017-11-13 11:06:26 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( v, VectorContains( 1 ) && VectorContains( 2 ) )
Removed vestigal ComparatorT template arg to MatcherBase
2017-11-13 11:06:26 +01:00
with expansion:
{ 1, 2, 3 } ( Contains: 1 and Contains: 2 )
Added first vector matchers (Contains and Equals)
2017-02-21 17:05:04 +01:00
-------------------------------------------------------------------------------
Vector matchers
Equals
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>
Added first vector matchers (Contains and Equals)
2017-02-21 17:05:04 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( v, Equals( v ) )
Added first vector matchers (Contains and Equals)
2017-02-21 17:05:04 +01:00
with expansion:
{ 1, 2, 3 } Equals: { 1, 2, 3 }
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( empty, Equals( empty ) )
Added first vector matchers (Contains and Equals)
2017-02-21 17:05:04 +01:00
with expansion:
{ } Equals: { }
Support custom allocators in vector Matchers (#1909) -- Combined with f4fc2dab2c5bb8cab11b0a0dde8a8421076c30f9 during cherry-picking.
2020-04-16 15:36:54 +02:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( v, Equals<int>( { 1, 2, 3 } ) )
Support custom allocators in vector Matchers (#1909) -- Combined with f4fc2dab2c5bb8cab11b0a0dde8a8421076c30f9 during cherry-picking.
2020-04-16 15:36:54 +02:00
with expansion:
{ 1, 2, 3 } Equals: { 1, 2, 3 }
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( v, Equals( v2 ) )
Added first vector matchers (Contains and Equals)
2017-02-21 17:05:04 +01:00
with expansion:
{ 1, 2, 3 } Equals: { 1, 2, 3 }
Support custom allocators in vector Matchers (#1909) -- Combined with f4fc2dab2c5bb8cab11b0a0dde8a8421076c30f9 during cherry-picking.
2020-04-16 15:36:54 +02:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( v5, ( Equals<int, std::allocator<int>, CustomAllocator<int>>( v2 ) ) )
Support custom allocators in vector Matchers (#1909) -- Combined with f4fc2dab2c5bb8cab11b0a0dde8a8421076c30f9 during cherry-picking.
2020-04-16 15:36:54 +02:00
with expansion:
{ 1, 2, 3 } Equals: { 1, 2, 3 }
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( v5, Equals( v6 ) )
Support custom allocators in vector Matchers (#1909) -- Combined with f4fc2dab2c5bb8cab11b0a0dde8a8421076c30f9 during cherry-picking.
2020-04-16 15:36:54 +02:00
with expansion:
{ 1, 2, 3 } Equals: { 1, 2, 3 }
Add UnorderedEqualsMatcher for vectors Closes #1093
2017-12-07 17:07:25 +01:00
-------------------------------------------------------------------------------
Vector matchers
UnorderedEquals
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( v, UnorderedEquals( v ) )
Add UnorderedEqualsMatcher for vectors Closes #1093
2017-12-07 17:07:25 +01:00
with expansion:
{ 1, 2, 3 } UnorderedEquals: { 1, 2, 3 }
Support custom allocators in vector Matchers (#1909) -- Combined with f4fc2dab2c5bb8cab11b0a0dde8a8421076c30f9 during cherry-picking.
2020-04-16 15:36:54 +02:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( v, UnorderedEquals<int>( { 3, 2, 1 } ) )
Support custom allocators in vector Matchers (#1909) -- Combined with f4fc2dab2c5bb8cab11b0a0dde8a8421076c30f9 during cherry-picking.
2020-04-16 15:36:54 +02:00
with expansion:
{ 1, 2, 3 } UnorderedEquals: { 3, 2, 1 }
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( empty, UnorderedEquals( empty ) )
Add UnorderedEqualsMatcher for vectors Closes #1093
2017-12-07 17:07:25 +01:00
with expansion:
{ } UnorderedEquals: { }
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( permuted, UnorderedEquals( v ) )
Add UnorderedEqualsMatcher for vectors Closes #1093
2017-12-07 17:07:25 +01:00
with expansion:
{ 1, 3, 2 } UnorderedEquals: { 1, 2, 3 }
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
REQUIRE_THAT( permuted, UnorderedEquals( v ) )
Add UnorderedEqualsMatcher for vectors Closes #1093
2017-12-07 17:07:25 +01:00
with expansion:
{ 2, 3, 1 } UnorderedEquals: { 1, 2, 3 }
Support custom allocators in vector Matchers (#1909) -- Combined with f4fc2dab2c5bb8cab11b0a0dde8a8421076c30f9 during cherry-picking.
2020-04-16 15:36:54 +02:00
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( v5, ( UnorderedEquals<int, std::allocator<int>, CustomAllocator<int>>( permuted ) ) )
Support custom allocators in vector Matchers (#1909) -- Combined with f4fc2dab2c5bb8cab11b0a0dde8a8421076c30f9 during cherry-picking.
2020-04-16 15:36:54 +02:00
with expansion:
{ 1, 2, 3 } UnorderedEquals: { 2, 3, 1 }
Matchers.tests.cpp:<line number>: PASSED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( v5_permuted, UnorderedEquals( v5 ) )
Support custom allocators in vector Matchers (#1909) -- Combined with f4fc2dab2c5bb8cab11b0a0dde8a8421076c30f9 during cherry-picking.
2020-04-16 15:36:54 +02:00
with expansion:
{ 1, 3, 2 } UnorderedEquals: { 1, 2, 3 }
Added first vector matchers (Contains and Equals)
2017-02-21 17:05:04 +01:00
-------------------------------------------------------------------------------
Vector matchers that fail
Contains (element)
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>
Added first vector matchers (Contains and Equals)
2017-02-21 17:05:04 +01:00
...............................................................................
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( v, VectorContains( -1 ) )
Added first vector matchers (Contains and Equals)
2017-02-21 17:05:04 +01:00
with expansion:
{ 1, 2, 3 } Contains: -1
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( empty, VectorContains( 1 ) )
Added first vector matchers (Contains and Equals)
2017-02-21 17:05:04 +01:00
with expansion:
{ } Contains: 1
-------------------------------------------------------------------------------
Vector matchers that fail
Contains (vector)
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>
Added first vector matchers (Contains and Equals)
2017-02-21 17:05:04 +01:00
...............................................................................
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( empty, Contains( v ) )
Added first vector matchers (Contains and Equals)
2017-02-21 17:05:04 +01:00
with expansion:
{ } Contains: { 1, 2, 3 }
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( v, Contains( v2 ) )
Added first vector matchers (Contains and Equals)
2017-02-21 17:05:04 +01:00
with expansion:
{ 1, 2, 3 } Contains: { 1, 2, 4 }
-------------------------------------------------------------------------------
Vector matchers that fail
Equals
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>
Added first vector matchers (Contains and Equals)
2017-02-21 17:05:04 +01:00
...............................................................................
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( v, Equals( v2 ) )
Added first vector matchers (Contains and Equals)
2017-02-21 17:05:04 +01:00
with expansion:
{ 1, 2, 3 } Equals: { 1, 2 }
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( v2, Equals( v ) )
Added first vector matchers (Contains and Equals)
2017-02-21 17:05:04 +01:00
with expansion:
{ 1, 2 } Equals: { 1, 2, 3 }
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( empty, Equals( v ) )
Added first vector matchers (Contains and Equals)
2017-02-21 17:05:04 +01:00
with expansion:
{ } Equals: { 1, 2, 3 }
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( v, Equals( empty ) )
Added first vector matchers (Contains and Equals)
2017-02-21 17:05:04 +01:00
with expansion:
{ 1, 2, 3 } Equals: { }
Add UnorderedEqualsMatcher for vectors Closes #1093
2017-12-07 17:07:25 +01:00
-------------------------------------------------------------------------------
Vector matchers that fail
UnorderedEquals
-------------------------------------------------------------------------------
Matchers.tests.cpp:<line number>
...............................................................................
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( v, UnorderedEquals( empty ) )
Add UnorderedEqualsMatcher for vectors Closes #1093
2017-12-07 17:07:25 +01:00
with expansion:
{ 1, 2, 3 } UnorderedEquals: { }
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( empty, UnorderedEquals( v ) )
Add UnorderedEqualsMatcher for vectors Closes #1093
2017-12-07 17:07:25 +01:00
with expansion:
{ } UnorderedEquals: { 1, 2, 3 }
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( permuted, UnorderedEquals( v ) )
Add UnorderedEqualsMatcher for vectors Closes #1093
2017-12-07 17:07:25 +01:00
with expansion:
{ 1, 3 } UnorderedEquals: { 1, 2, 3 }
Matchers.tests.cpp:<line number>: FAILED:
Remove the ill-conceived compilation perf tests using real tests
2021-06-20 16:25:57 +02:00
CHECK_THAT( permuted, UnorderedEquals( v ) )
Add UnorderedEqualsMatcher for vectors Closes #1093
2017-12-07 17:07:25 +01:00
with expansion:
{ 3, 1 } UnorderedEquals: { 1, 2, 3 }
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
When checked exceptions are thrown they can be expected or unexpected
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Exception.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Exception.tests.cpp:<line number>: PASSED:
REQUIRE_THROWS_AS is now reported with expected type as well Also updated tests to reflect this change.
2017-02-09 12:41:16 +01:00
REQUIRE_THROWS_AS( thisThrows(), std::domain_error )
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Exception.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE_NOTHROW( thisDoesntThrow() )
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Exception.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE_THROWS( thisThrows() )
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
approved tests that were correct the first time (previous approvals were erroneous)
2017-04-09 21:40:01 +02:00
-------------------------------------------------------------------------------
When unchecked exceptions are thrown directly they are always failures
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Exception.tests.cpp:<line number>
approved tests that were correct the first time (previous approvals were erroneous)
2017-04-09 21:40:01 +02:00
...............................................................................
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Exception.tests.cpp:<line number>: FAILED:
approved tests that were correct the first time (previous approvals were erroneous)
2017-04-09 21:40:01 +02:00
due to unexpected exception with message:
unexpected exception
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Changed exception tests to allow for now throw-from-CHECK behaviour
2017-01-23 18:56:41 +01:00
When unchecked exceptions are thrown during a CHECK the test should continue
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Exception.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Exception.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( thisThrows() == 0 )
due to unexpected exception with message:
expected exception
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
When unchecked exceptions are thrown during a REQUIRE the test should abort
fail
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Exception.tests.cpp:<line number>
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
...............................................................................
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Exception.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( thisThrows() == 0 )
due to unexpected exception with message:
expected exception
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
When unchecked exceptions are thrown from functions they are always failures
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Exception.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Exception.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( thisThrows() == 0 )
due to unexpected exception with message:
expected exception
Added baselines for new test cases
2014-09-03 20:22:47 +02:00
approved tests that were correct the first time (previous approvals were erroneous)
2017-04-09 21:40:01 +02:00
-------------------------------------------------------------------------------
When unchecked exceptions are thrown from sections they are always failures
section name
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Exception.tests.cpp:<line number>
approved tests that were correct the first time (previous approvals were erroneous)
2017-04-09 21:40:01 +02:00
...............................................................................
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Exception.tests.cpp:<line number>: FAILED:
approved tests that were correct the first time (previous approvals were erroneous)
2017-04-09 21:40:01 +02:00
due to unexpected exception with message:
unexpected exception
Fixed NoAssertions warning
2018-01-26 17:52:28 +01:00
-------------------------------------------------------------------------------
When unchecked exceptions are thrown, but caught, they do not affect the test
-------------------------------------------------------------------------------
Exception.tests.cpp:<line number>
...............................................................................
No assertions in test case 'When unchecked exceptions are thrown, but caught, they do not affect the test'
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
X/level/0/a
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Tricky.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
X/level/0/b
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Tricky.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
X/level/1/a
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Tricky.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
X/level/1/b
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Tricky.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
XmlEncode
normal string
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Xml.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Xml.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( encode( "normal string" ) == "normal string" )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"normal string" == "normal string"
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
XmlEncode
empty string
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Xml.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Xml.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( encode( "" ) == "" )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"" == ""
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
XmlEncode
string with ampersand
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Xml.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Xml.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( encode( "smith & jones" ) == "smith &amp; jones" )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"smith &amp; jones" == "smith &amp; jones"
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
XmlEncode
string with less-than
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Xml.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Xml.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( encode( "smith < jones" ) == "smith &lt; jones" )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"smith &lt; jones" == "smith &lt; jones"
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
XmlEncode
string with greater-than
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Xml.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Xml.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( encode( "smith > jones" ) == "smith > jones" )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"smith > jones" == "smith > jones"
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Xml.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( encode( "smith ]]> jones" ) == "smith ]]&gt; jones" )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"smith ]]&gt; jones"
==
"smith ]]&gt; jones"
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
XmlEncode
string with quotes
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Xml.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Xml.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( encode( stringWithQuotes ) == stringWithQuotes )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"don't "quote" me on that"
==
"don't "quote" me on that"
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Xml.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( encode( stringWithQuotes, Catch::XmlEncode::ForAttributes ) == "don't &quot;quote&quot; me on that" )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"don't &quot;quote&quot; me on that"
==
"don't &quot;quote&quot; me on that"
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
XmlEncode
Rebased again - against the right executable this time :-s
2017-02-06 17:25:09 +01:00
string with control char (1)
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Xml.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Xml.tests.cpp:<line number>: PASSED:
XmlWriter reverts to XML 1.0. Character encodings that are not valid in XML 1.0 are instead written using C-style escapes
2017-02-06 17:00:05 +01:00
REQUIRE( encode( "[\x01]" ) == "[\\x01]" )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
XmlWriter reverts to XML 1.0. Character encodings that are not valid in XML 1.0 are instead written using C-style escapes
2017-02-06 17:00:05 +01:00
"[\x01]" == "[\x01]"
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
XmlEncode
Rebased again - against the right executable this time :-s
2017-02-06 17:25:09 +01:00
string with control char (x7F)
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Xml.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Xml.tests.cpp:<line number>: PASSED:
XmlWriter reverts to XML 1.0. Character encodings that are not valid in XML 1.0 are instead written using C-style escapes
2017-02-06 17:00:05 +01:00
REQUIRE( encode( "[\x7F]" ) == "[\\x7F]" )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
XmlWriter reverts to XML 1.0. Character encodings that are not valid in XML 1.0 are instead written using C-style escapes
2017-02-06 17:00:05 +01:00
"[\x7F]" == "[\x7F]"
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Add explicit test for serialization of boolean attributes in XML
2021-05-30 20:02:02 +02:00
-------------------------------------------------------------------------------
XmlWriter writes boolean attributes as true/false
-------------------------------------------------------------------------------
Xml.tests.cpp:<line number>
...............................................................................
Xml.tests.cpp:<line number>: PASSED:
Rename Contains string matcher builder to ContainsSubstring The problem with the old name was that it collided with the range matcher `Contains`, and it was not really possible to disambiguate them just with argument types. Closes #2131
2021-09-23 23:28:59 +02:00
REQUIRE_THAT( stream.str(), ContainsSubstring(R"(attr1="true")") && ContainsSubstring(R"(attr2="false")") )
Add explicit test for serialization of boolean attributes in XML
2021-05-30 20:02:02 +02:00
with expansion:
"<?xml version="1.0" encoding="UTF-8"?>
<Element1 attr1="true" attr2="false"/>
" ( contains: "attr1="true"" and contains: "attr2="false"" )
Add new SKIP macro for skipping tests at runtime (#2360) * Add new SKIP macro for skipping tests at runtime This adds a new `SKIP` macro for dynamically skipping tests at runtime. The "skipped" status of a test case is treated as a first-class citizen, like "succeeded" or "failed", and is reported with a new color on the console. * Don't show "skipped assertions" in console/compact reporters Also extend skip tests to cover a few more use cases. * Return exit code 4 if all test cases are skipped * Use LightGrey for the skip colour This isn't great, but is better than the deep blue that was borderline invisible on dark backgrounds. The fix is to redo the colouring a bit, including introducing light-blue that is actually visible. * Add support for explicit skips in all reporters * --allow-running-no-tests also allows all tests to be skipped * Add docs for SKIP macro, deprecate IEventListener::skipTest Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2023-01-12 15:01:47 +01:00
-------------------------------------------------------------------------------
a succeeding test can still be skipped
-------------------------------------------------------------------------------
Skip.tests.cpp:<line number>
...............................................................................
Skip.tests.cpp:<line number>: PASSED:
Skip.tests.cpp:<line number>: SKIPPED:
Remove CATCH_CONFIG_ENABLE_BENCHMARKING compilation toggle Now that Catch2 is a proper library, we can always build the full library (comparatively minor slowdown) and the user can avoid including benchmarking headers to avoid the compilation slowdown.
2020-02-03 18:08:15 +01:00
-------------------------------------------------------------------------------
analyse no analysis
-------------------------------------------------------------------------------
InternalBenchmark.tests.cpp:<line number>
...............................................................................
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( analysis.mean.point.count() == 23 )
with expansion:
23.0 == 23
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( analysis.mean.lower_bound.count() == 23 )
with expansion:
23.0 == 23
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( analysis.mean.upper_bound.count() == 23 )
with expansion:
23.0 == 23
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( analysis.standard_deviation.point.count() == 0 )
with expansion:
0.0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( analysis.standard_deviation.lower_bound.count() == 0 )
with expansion:
0.0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( analysis.standard_deviation.upper_bound.count() == 0 )
with expansion:
0.0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( analysis.outliers.total() == 0 )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( analysis.outliers.low_mild == 0 )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( analysis.outliers.low_severe == 0 )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( analysis.outliers.high_mild == 0 )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( analysis.outliers.high_severe == 0 )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( analysis.outliers.samples_seen == 0 )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( analysis.outlier_variance == 0 )
with expansion:
0.0 == 0
Added test for stringifying std::arrays
2018-01-04 11:52:55 +01:00
-------------------------------------------------------------------------------
array<int, N> -> toString
-------------------------------------------------------------------------------
ToStringVector.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringVector.tests.cpp:<line number>: PASSED:
Added test for stringifying std::arrays
2018-01-04 11:52:55 +01:00
REQUIRE( Catch::Detail::stringify( empty ) == "{ }" )
with expansion:
"{ }" == "{ }"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringVector.tests.cpp:<line number>: PASSED:
Added test for stringifying std::arrays
2018-01-04 11:52:55 +01:00
REQUIRE( Catch::Detail::stringify( oneValue ) == "{ 42 }" )
with expansion:
"{ 42 }" == "{ 42 }"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringVector.tests.cpp:<line number>: PASSED:
Added test for stringifying std::arrays
2018-01-04 11:52:55 +01:00
REQUIRE( Catch::Detail::stringify( twoValues ) == "{ 42, 250 }" )
with expansion:
"{ 42, 250 }" == "{ 42, 250 }"
Remove CATCH_CONFIG_ENABLE_BENCHMARKING compilation toggle Now that Catch2 is a proper library, we can always build the full library (comparatively minor slowdown) and the user can avoid including benchmarking headers to avoid the compilation slowdown.
2020-02-03 18:08:15 +01:00
-------------------------------------------------------------------------------
benchmark function call
without chronometer
-------------------------------------------------------------------------------
InternalBenchmark.tests.cpp:<line number>
...............................................................................
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( model.started == 1 )
with expansion:
1 == 1
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( model.finished == 0 )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( model.started == 1 )
with expansion:
1 == 1
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( model.finished == 1 )
with expansion:
1 == 1
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( called == 1 )
with expansion:
1 == 1
-------------------------------------------------------------------------------
benchmark function call
with chronometer
-------------------------------------------------------------------------------
InternalBenchmark.tests.cpp:<line number>
...............................................................................
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( model.started == 0 )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( model.finished == 0 )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( model.started == 0 )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( model.finished == 0 )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( called == 1 )
with expansion:
1 == 1
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
boolean member
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Tricky.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Approval tests can use Catch path fixed in env. var, and convert nullptr and __null to 0 for comparison
2017-01-09 15:12:12 +01:00
REQUIRE( obj.prop != 0 )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Approval tests can use Catch path fixed in env. var, and convert nullptr and __null to 0 for comparison
2017-01-09 15:12:12 +01:00
0x<hex digits> != 0
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
checkedElse
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECKED_ELSE( flag )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
true
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( testCheckedElse( true ) )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
true
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
checkedElse, failing
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
Suppress failure of CHECKED_IF and CHECKED_ELSE (#2187) Resolves #1390 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2021-05-10 21:42:47 +02:00
Misc.tests.cpp:<line number>: FAILED - but was ok:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECKED_ELSE( flag )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
false
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( testCheckedElse( false ) )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
false
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
checkedIf
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECKED_IF( flag )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
true
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( testCheckedIf( true ) )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
true
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
checkedIf, failing
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
Suppress failure of CHECKED_IF and CHECKED_ELSE (#2187) Resolves #1390 Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2021-05-10 21:42:47 +02:00
Misc.tests.cpp:<line number>: FAILED - but was ok:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECKED_IF( flag )
with expansion:
false
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( testCheckedIf( false ) )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
false
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Remove CATCH_CONFIG_ENABLE_BENCHMARKING compilation toggle Now that Catch2 is a proper library, we can always build the full library (comparatively minor slowdown) and the user can avoid including benchmarking headers to avoid the compilation slowdown.
2020-02-03 18:08:15 +01:00
-------------------------------------------------------------------------------
classify_outliers
none
-------------------------------------------------------------------------------
InternalBenchmark.tests.cpp:<line number>
...............................................................................
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.samples_seen == static_cast<int>(x.size()) )
with expansion:
6 == 6
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.low_severe == los )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.low_mild == lom )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.high_mild == him )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.high_severe == his )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.total() == los + lom + him + his )
with expansion:
0 == 0
-------------------------------------------------------------------------------
classify_outliers
low severe
-------------------------------------------------------------------------------
InternalBenchmark.tests.cpp:<line number>
...............................................................................
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.samples_seen == static_cast<int>(x.size()) )
with expansion:
6 == 6
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.low_severe == los )
with expansion:
1 == 1
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.low_mild == lom )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.high_mild == him )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.high_severe == his )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.total() == los + lom + him + his )
with expansion:
1 == 1
-------------------------------------------------------------------------------
classify_outliers
low mild
-------------------------------------------------------------------------------
InternalBenchmark.tests.cpp:<line number>
...............................................................................
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.samples_seen == static_cast<int>(x.size()) )
with expansion:
6 == 6
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.low_severe == los )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.low_mild == lom )
with expansion:
1 == 1
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.high_mild == him )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.high_severe == his )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.total() == los + lom + him + his )
with expansion:
1 == 1
-------------------------------------------------------------------------------
classify_outliers
high mild
-------------------------------------------------------------------------------
InternalBenchmark.tests.cpp:<line number>
...............................................................................
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.samples_seen == static_cast<int>(x.size()) )
with expansion:
6 == 6
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.low_severe == los )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.low_mild == lom )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.high_mild == him )
with expansion:
1 == 1
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.high_severe == his )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.total() == los + lom + him + his )
with expansion:
1 == 1
-------------------------------------------------------------------------------
classify_outliers
high severe
-------------------------------------------------------------------------------
InternalBenchmark.tests.cpp:<line number>
...............................................................................
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.samples_seen == static_cast<int>(x.size()) )
with expansion:
6 == 6
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.low_severe == los )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.low_mild == lom )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.high_mild == him )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.high_severe == his )
with expansion:
1 == 1
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.total() == los + lom + him + his )
with expansion:
1 == 1
-------------------------------------------------------------------------------
classify_outliers
mixed
-------------------------------------------------------------------------------
InternalBenchmark.tests.cpp:<line number>
...............................................................................
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.samples_seen == static_cast<int>(x.size()) )
with expansion:
6 == 6
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.low_severe == los )
with expansion:
1 == 1
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.low_mild == lom )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.high_mild == him )
with expansion:
1 == 1
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.high_severe == his )
with expansion:
0 == 0
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( o.total() == los + lom + him + his )
with expansion:
2 == 2
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
comparisons between const int variables
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( unsigned_char_var == 1 )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
1 == 1
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( unsigned_short_var == 1 )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
1 == 1
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( unsigned_int_var == 1 )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
1 == 1
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( unsigned_long_var == 1 )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
1 == 1
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Updated approvals after adding extra tests
2014-05-19 19:21:01 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
comparisons between int variables
Updated approvals after adding extra tests
2014-05-19 19:21:01 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Condition.tests.cpp:<line number>
Updated approvals after adding extra tests
2014-05-19 19:21:01 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( long_var == unsigned_char_var )
Updated approvals after adding extra tests
2014-05-19 19:21:01 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
1 == 1
Updated approvals after adding extra tests
2014-05-19 19:21:01 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( long_var == unsigned_short_var )
Updated approvals after adding extra tests
2014-05-19 19:21:01 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
1 == 1
Updated approvals after adding extra tests
2014-05-19 19:21:01 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( long_var == unsigned_int_var )
Updated approvals after adding extra tests
2014-05-19 19:21:01 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
1 == 1
Updated approvals after adding extra tests
2014-05-19 19:21:01 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Condition.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( long_var == unsigned_long_var )
Updated approvals after adding extra tests
2014-05-19 19:21:01 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
1 == 1
Updated approvals after adding extra tests
2014-05-19 19:21:01 +02:00
Fix ulp distance calculation for numbers with different signs This is a simplification of the fix proposed in #2152, with the critical function split out so that it can be tested directly, without having to go through the ULP matcher. Closes #2152
2021-07-26 22:01:04 +02:00
-------------------------------------------------------------------------------
convertToBits
-------------------------------------------------------------------------------
FloatingPoint.tests.cpp:<line number>
...............................................................................
FloatingPoint.tests.cpp:<line number>: PASSED:
CHECK( convertToBits( 0.f ) == 0 )
with expansion:
0 == 0
FloatingPoint.tests.cpp:<line number>: PASSED:
CHECK( convertToBits( -0.f ) == ( 1ULL << 31 ) )
with expansion:
2147483648 (0x<hex digits>)
==
2147483648 (0x<hex digits>)
FloatingPoint.tests.cpp:<line number>: PASSED:
CHECK( convertToBits( 0. ) == 0 )
with expansion:
0 == 0
FloatingPoint.tests.cpp:<line number>: PASSED:
CHECK( convertToBits( -0. ) == ( 1ULL << 63 ) )
with expansion:
9223372036854775808 (0x<hex digits>)
==
9223372036854775808 (0x<hex digits>)
FloatingPoint.tests.cpp:<line number>: PASSED:
CHECK( convertToBits( std::numeric_limits<float>::denorm_min() ) == 1 )
with expansion:
1 == 1
FloatingPoint.tests.cpp:<line number>: PASSED:
CHECK( convertToBits( std::numeric_limits<double>::denorm_min() ) == 1 )
with expansion:
1 == 1
Add new SKIP macro for skipping tests at runtime (#2360) * Add new SKIP macro for skipping tests at runtime This adds a new `SKIP` macro for dynamically skipping tests at runtime. The "skipped" status of a test case is treated as a first-class citizen, like "succeeded" or "failed", and is reported with a new color on the console. * Don't show "skipped assertions" in console/compact reporters Also extend skip tests to cover a few more use cases. * Return exit code 4 if all test cases are skipped * Use LightGrey for the skip colour This isn't great, but is better than the deep blue that was borderline invisible on dark backgrounds. The fix is to redo the colouring a bit, including introducing light-blue that is actually visible. * Add support for explicit skips in all reporters * --allow-running-no-tests also allows all tests to be skipped * Add docs for SKIP macro, deprecate IEventListener::skipTest Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2023-01-12 15:01:47 +01:00
-------------------------------------------------------------------------------
dynamic skipping works with generators
-------------------------------------------------------------------------------
Skip.tests.cpp:<line number>
...............................................................................
Skip.tests.cpp:<line number>: SKIPPED:
explicitly with message:
skipping because answer = 41
-------------------------------------------------------------------------------
dynamic skipping works with generators
-------------------------------------------------------------------------------
Skip.tests.cpp:<line number>
...............................................................................
Skip.tests.cpp:<line number>: PASSED:
-------------------------------------------------------------------------------
dynamic skipping works with generators
-------------------------------------------------------------------------------
Skip.tests.cpp:<line number>
...............................................................................
Skip.tests.cpp:<line number>: SKIPPED:
explicitly with message:
skipping because answer = 43
Disallow empty tags in test case specification
2021-05-28 20:49:05 +02:00
-------------------------------------------------------------------------------
empty tags are not allowed
-------------------------------------------------------------------------------
Tag.tests.cpp:<line number>
...............................................................................
Tag.tests.cpp:<line number>: PASSED:
REQUIRE_THROWS( Catch::TestCaseInfo("", { "test with an empty tag", "[]" }, dummySourceLineInfo) )
Remove CATCH_CONFIG_ENABLE_BENCHMARKING compilation toggle Now that Catch2 is a proper library, we can always build the full library (comparatively minor slowdown) and the user can avoid including benchmarking headers to avoid the compilation slowdown.
2020-02-03 18:08:15 +01:00
-------------------------------------------------------------------------------
erfc_inv
-------------------------------------------------------------------------------
InternalBenchmark.tests.cpp:<line number>
...............................................................................
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( erfc_inv(1.103560) == Approx(-0.09203687623843015) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
-0.09203687623843014
==
Approx( -0.09203687623843015 )
Remove CATCH_CONFIG_ENABLE_BENCHMARKING compilation toggle Now that Catch2 is a proper library, we can always build the full library (comparatively minor slowdown) and the user can avoid including benchmarking headers to avoid the compilation slowdown.
2020-02-03 18:08:15 +01:00
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( erfc_inv(1.067400) == Approx(-0.05980291115763361) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
-0.05980291115763361
==
Approx( -0.05980291115763361 )
Remove CATCH_CONFIG_ENABLE_BENCHMARKING compilation toggle Now that Catch2 is a proper library, we can always build the full library (comparatively minor slowdown) and the user can avoid including benchmarking headers to avoid the compilation slowdown.
2020-02-03 18:08:15 +01:00
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( erfc_inv(0.050000) == Approx(1.38590382434967796) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
1.38590382434967774
==
Approx( 1.38590382434967796 )
Remove CATCH_CONFIG_ENABLE_BENCHMARKING compilation toggle Now that Catch2 is a proper library, we can always build the full library (comparatively minor slowdown) and the user can avoid including benchmarking headers to avoid the compilation slowdown.
2020-02-03 18:08:15 +01:00
-------------------------------------------------------------------------------
estimate_clock_resolution
-------------------------------------------------------------------------------
InternalBenchmark.tests.cpp:<line number>
...............................................................................
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( res.mean.count() == rate )
with expansion:
2000.0 == 2000 (0x<hex digits>)
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( res.outliers.total() == 0 )
with expansion:
0 == 0
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
even more nested SECTION tests
c
d (leaf)
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
Updated approvals after adding extra tests
2014-05-19 19:21:01 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Updated approvals after adding extra tests
2014-05-19 19:21:01 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
even more nested SECTION tests
c
e (leaf)
Updated approvals after adding extra tests
2014-05-19 19:21:01 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Updated approvals after adding extra tests
2014-05-19 19:21:01 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Updated approvals after adding extra tests
2014-05-19 19:21:01 +02:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
even more nested SECTION tests
f (leaf)
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
Updated approvals after adding extra tests
2014-05-19 19:21:01 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Updated approvals after adding extra tests
2014-05-19 19:21:01 +02:00
Add new SKIP macro for skipping tests at runtime (#2360) * Add new SKIP macro for skipping tests at runtime This adds a new `SKIP` macro for dynamically skipping tests at runtime. The "skipped" status of a test case is treated as a first-class citizen, like "succeeded" or "failed", and is reported with a new color on the console. * Don't show "skipped assertions" in console/compact reporters Also extend skip tests to cover a few more use cases. * Return exit code 4 if all test cases are skipped * Use LightGrey for the skip colour This isn't great, but is better than the deep blue that was borderline invisible on dark backgrounds. The fix is to redo the colouring a bit, including introducing light-blue that is actually visible. * Add support for explicit skips in all reporters * --allow-running-no-tests also allows all tests to be skipped * Add docs for SKIP macro, deprecate IEventListener::skipTest Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2023-01-12 15:01:47 +01:00
-------------------------------------------------------------------------------
failed assertions before SKIP cause test case to fail
-------------------------------------------------------------------------------
Skip.tests.cpp:<line number>
...............................................................................
Skip.tests.cpp:<line number>: FAILED:
CHECK( 3 == 4 )
Skip.tests.cpp:<line number>: SKIPPED:
-------------------------------------------------------------------------------
failing for some generator values causes entire test case to fail
-------------------------------------------------------------------------------
Skip.tests.cpp:<line number>
...............................................................................
Skip.tests.cpp:<line number>: FAILED:
-------------------------------------------------------------------------------
failing for some generator values causes entire test case to fail
-------------------------------------------------------------------------------
Skip.tests.cpp:<line number>
...............................................................................
Skip.tests.cpp:<line number>: SKIPPED:
-------------------------------------------------------------------------------
failing for some generator values causes entire test case to fail
-------------------------------------------------------------------------------
Skip.tests.cpp:<line number>
...............................................................................
Skip.tests.cpp:<line number>: FAILED:
-------------------------------------------------------------------------------
failing for some generator values causes entire test case to fail
-------------------------------------------------------------------------------
Skip.tests.cpp:<line number>
...............................................................................
Skip.tests.cpp:<line number>: SKIPPED:
-------------------------------------------------------------------------------
failing in some unskipped sections causes entire test case to fail
skipped
-------------------------------------------------------------------------------
Skip.tests.cpp:<line number>
...............................................................................
Skip.tests.cpp:<line number>: SKIPPED:
-------------------------------------------------------------------------------
failing in some unskipped sections causes entire test case to fail
not skipped
-------------------------------------------------------------------------------
Skip.tests.cpp:<line number>
...............................................................................
Skip.tests.cpp:<line number>: FAILED:
Fixed NoAssertions warning
2018-01-26 17:52:28 +01:00
-------------------------------------------------------------------------------
first tag
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
No assertions in test case 'first tag'
Cleaned up the output a bit - removed [!shouldfail] test from "green" path - changed "spanner" to more descriptive text
2017-08-11 11:38:29 +02:00
loose text artifact
Fixed NoAssertions warning
2018-01-26 17:52:28 +01:00
-------------------------------------------------------------------------------
has printf
-------------------------------------------------------------------------------
Tricky.tests.cpp:<line number>
...............................................................................
No assertions in test case 'has printf'
Add support for multiply calling lambda parsers in Clara Previously a lambda parser in Clara could only be invoked once, even if it internally was ok with being invoked multiple times. With this change, a lambda parser can mark itself as `accept_many`, in which case it will be invoked multiple times if the appropriate flag was supplied multiple times by the user.
2021-10-27 18:57:56 +02:00
-------------------------------------------------------------------------------
is_unary_function
-------------------------------------------------------------------------------
Clara.tests.cpp:<line number>
...............................................................................
Clara.tests.cpp:<line number>: PASSED:
with message:
Catch::Clara::Detail::is_unary_function<decltype(unary1)>::value
Clara.tests.cpp:<line number>: PASSED:
with message:
Catch::Clara::Detail::is_unary_function<decltype(unary2)>::value
Clara.tests.cpp:<line number>: PASSED:
with message:
Catch::Clara::Detail::is_unary_function<decltype(unary3)>::value
Clara.tests.cpp:<line number>: PASSED:
with message:
Catch::Clara::Detail::is_unary_function<decltype(unary4)>::value
Clara.tests.cpp:<line number>: PASSED:
with message:
Catch::Clara::Detail::is_unary_function<decltype(unary5)>::value
Clara.tests.cpp:<line number>: PASSED:
with message:
Catch::Clara::Detail::is_unary_function<decltype(unary6)>::value
Clara.tests.cpp:<line number>: PASSED:
with message:
!(Catch::Clara::Detail::is_unary_function<decltype(binary1)>::value)
Clara.tests.cpp:<line number>: PASSED:
with message:
!(Catch::Clara::Detail::is_unary_function<decltype(binary2)>::value)
Clara.tests.cpp:<line number>: PASSED:
with message:
!(Catch::Clara::Detail::is_unary_function<decltype(nullary1)>::value)
Clara.tests.cpp:<line number>: PASSED:
with message:
!(Catch::Clara::Detail::is_unary_function<decltype(nullary2)>::value)
Clara.tests.cpp:<line number>: PASSED:
with message:
!(Catch::Clara::Detail::is_unary_function<int>::value)
Clara.tests.cpp:<line number>: PASSED:
with message:
!(Catch::Clara::Detail::is_unary_function<std::string const&>::value)
Cleaned up the output a bit - removed [!shouldfail] test from "green" path - changed "spanner" to more descriptive text
2017-08-11 11:38:29 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
just failure
Updated approvals after adding extra tests
2014-05-19 19:21:01 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Message.tests.cpp:<line number>
Updated approvals after adding extra tests
2014-05-19 19:21:01 +02:00
...............................................................................
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Message.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
explicitly with message:
Previous info should not be seen
Updated approvals after adding extra tests
2014-05-19 19:21:01 +02:00
Add tests for unscoped info Update approval tests as new tests are added for messaging.
2019-02-01 16:36:35 +01:00
-------------------------------------------------------------------------------
just failure after unscoped info
-------------------------------------------------------------------------------
Message.tests.cpp:<line number>
...............................................................................
Message.tests.cpp:<line number>: FAILED:
explicitly with message:
previous unscoped info SHOULD not be seen
Fixed NoAssertions warning
2018-01-26 17:52:28 +01:00
-------------------------------------------------------------------------------
just info
-------------------------------------------------------------------------------
Message.tests.cpp:<line number>
...............................................................................
No assertions in test case 'just info'
Add tests for unscoped info Update approval tests as new tests are added for messaging.
2019-02-01 16:36:35 +01:00
-------------------------------------------------------------------------------
just unscoped info
-------------------------------------------------------------------------------
Message.tests.cpp:<line number>
...............................................................................
No assertions in test case 'just unscoped info'
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
-------------------------------------------------------------------------------
long long
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
REQUIRE( l == std::numeric_limits<long long>::max() )
with expansion:
9223372036854775807 (0x<hex digits>)
==
9223372036854775807 (0x<hex digits>)
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
looped SECTION tests
Deprecated description in SECTION (still accepts it, for now, but doesn't use it anywhere)
2018-06-25 20:04:29 +02:00
b is currently: 0
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
Updated approvals after adding extra tests
2014-05-19 19:21:01 +02:00
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( b > a )
Updated approvals after adding extra tests
2014-05-19 19:21:01 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
0 > 1
Updated approvals after adding extra tests
2014-05-19 19:21:01 +02:00
Deprecated description in SECTION (still accepts it, for now, but doesn't use it anywhere)
2018-06-25 20:04:29 +02:00
-------------------------------------------------------------------------------
looped SECTION tests
b is currently: 1
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
Misc.tests.cpp:<line number>: FAILED:
CHECK( b > a )
with expansion:
1 > 1
-------------------------------------------------------------------------------
looped SECTION tests
b is currently: 2
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Deprecated description in SECTION (still accepts it, for now, but doesn't use it anywhere)
2018-06-25 20:04:29 +02:00
CHECK( b > a )
with expansion:
2 > 1
-------------------------------------------------------------------------------
looped SECTION tests
b is currently: 3
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Deprecated description in SECTION (still accepts it, for now, but doesn't use it anywhere)
2018-06-25 20:04:29 +02:00
CHECK( b > a )
with expansion:
3 > 1
-------------------------------------------------------------------------------
looped SECTION tests
b is currently: 4
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Deprecated description in SECTION (still accepts it, for now, but doesn't use it anywhere)
2018-06-25 20:04:29 +02:00
CHECK( b > a )
with expansion:
4 > 1
-------------------------------------------------------------------------------
looped SECTION tests
b is currently: 5
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Deprecated description in SECTION (still accepts it, for now, but doesn't use it anywhere)
2018-06-25 20:04:29 +02:00
CHECK( b > a )
with expansion:
5 > 1
-------------------------------------------------------------------------------
looped SECTION tests
b is currently: 6
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Deprecated description in SECTION (still accepts it, for now, but doesn't use it anywhere)
2018-06-25 20:04:29 +02:00
CHECK( b > a )
with expansion:
6 > 1
-------------------------------------------------------------------------------
looped SECTION tests
b is currently: 7
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Deprecated description in SECTION (still accepts it, for now, but doesn't use it anywhere)
2018-06-25 20:04:29 +02:00
CHECK( b > a )
with expansion:
7 > 1
-------------------------------------------------------------------------------
looped SECTION tests
b is currently: 8
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Deprecated description in SECTION (still accepts it, for now, but doesn't use it anywhere)
2018-06-25 20:04:29 +02:00
CHECK( b > a )
with expansion:
8 > 1
-------------------------------------------------------------------------------
looped SECTION tests
b is currently: 9
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Deprecated description in SECTION (still accepts it, for now, but doesn't use it anywhere)
2018-06-25 20:04:29 +02:00
CHECK( b > a )
with expansion:
9 > 1
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
looped tests
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( ( fib[i] % 2 ) == 0 )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
1 == 0
with message:
Testing if fib[0] (1) is even
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( ( fib[i] % 2 ) == 0 )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
1 == 0
with message:
Testing if fib[1] (1) is even
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( ( fib[i] % 2 ) == 0 )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
0 == 0
with message:
Testing if fib[2] (2) is even
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( ( fib[i] % 2 ) == 0 )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
1 == 0
with message:
Testing if fib[3] (3) is even
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( ( fib[i] % 2 ) == 0 )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
1 == 0
with message:
Testing if fib[4] (5) is even
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( ( fib[i] % 2 ) == 0 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
0 == 0
with message:
Testing if fib[5] (8) is even
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( ( fib[i] % 2 ) == 0 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
1 == 0
with message:
Testing if fib[6] (13) is even
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( ( fib[i] % 2 ) == 0 )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
1 == 0
with message:
Testing if fib[7] (21) is even
Add test for %debug stream name
2022-04-23 23:34:27 +02:00
-------------------------------------------------------------------------------
makeStream recognizes %debug stream name
-------------------------------------------------------------------------------
Stream.tests.cpp:<line number>
...............................................................................
Stream.tests.cpp:<line number>: PASSED:
REQUIRE_NOTHROW( Catch::makeStream( "%debug" ) )
Implement a simplified variant of std::unique_ptr<T> This simplified variant supports only a subset of the functionality in `std::unique_ptr<T>`. `Catch::Detail::unique_ptr<T>` only supports single element pointer (no array support) with default deleter. By removing the support for custom deleters, we also avoid requiring significant machinery to support EBO, speeding up instantiations of `unique_ptr<T>` significantly. Catch2 also currently does not need to support `unique_ptr<T[]>`, so that is not supported either.
2020-05-24 23:41:02 +02:00
-------------------------------------------------------------------------------
make_unique reimplementation
From lvalue copies
-------------------------------------------------------------------------------
UniquePtr.tests.cpp:<line number>
...............................................................................
UniquePtr.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( lval.has_moved )
with expansion:
!false
-------------------------------------------------------------------------------
make_unique reimplementation
From rvalue moves
-------------------------------------------------------------------------------
UniquePtr.tests.cpp:<line number>
...............................................................................
UniquePtr.tests.cpp:<line number>: PASSED:
REQUIRE( rval.has_moved )
with expansion:
true
-------------------------------------------------------------------------------
make_unique reimplementation
Variadic constructor
-------------------------------------------------------------------------------
UniquePtr.tests.cpp:<line number>
...............................................................................
UniquePtr.tests.cpp:<line number>: PASSED:
REQUIRE( *ptr == std::tuple<int, double, int>{1, 2., 3} )
with expansion:
{?} == {?}
Remove CATCH_CONFIG_ENABLE_BENCHMARKING compilation toggle Now that Catch2 is a proper library, we can always build the full library (comparatively minor slowdown) and the user can avoid including benchmarking headers to avoid the compilation slowdown.
2020-02-03 18:08:15 +01:00
-------------------------------------------------------------------------------
mean
-------------------------------------------------------------------------------
InternalBenchmark.tests.cpp:<line number>
...............................................................................
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( m == 19. )
with expansion:
19.0 == 19.0
-------------------------------------------------------------------------------
measure
-------------------------------------------------------------------------------
InternalBenchmark.tests.cpp:<line number>
...............................................................................
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( x == 17 )
with expansion:
17 == 17
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( x == 23 )
with expansion:
23 == 23
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( r.elapsed.count() == 42 )
with expansion:
42 == 42
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( r.result == 23 )
with expansion:
23 == 23
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( r.iterations == 1 )
with expansion:
1 == 1
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( s.elapsed.count() == 69 )
with expansion:
69 == 69
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( s.result == 17 )
with expansion:
17 == 17
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( s.iterations == 1 )
with expansion:
1 == 1
Add tests for unscoped info Update approval tests as new tests are added for messaging.
2019-02-01 16:36:35 +01:00
-------------------------------------------------------------------------------
mix info, unscoped info and warning
-------------------------------------------------------------------------------
Message.tests.cpp:<line number>
...............................................................................
Message.tests.cpp:<line number>: warning:
info
unscoped info
and warn may mix
Message.tests.cpp:<line number>: warning:
info
unscoped info
they are not cleared after warnings
No assertions in test case 'mix info, unscoped info and warning'
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
more nested SECTION tests
Deprecated description in SECTION (still accepts it, for now, but doesn't use it anywhere)
2018-06-25 20:04:29 +02:00
doesn't equal
equal
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( a == b )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
1 == 2
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
more nested SECTION tests
Deprecated description in SECTION (still accepts it, for now, but doesn't use it anywhere)
2018-06-25 20:04:29 +02:00
doesn't equal
not equal
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( a != b )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
1 != 2
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
more nested SECTION tests
Deprecated description in SECTION (still accepts it, for now, but doesn't use it anywhere)
2018-06-25 20:04:29 +02:00
doesn't equal
less than
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( a < b )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
1 < 2
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
nested SECTION tests
Deprecated description in SECTION (still accepts it, for now, but doesn't use it anywhere)
2018-06-25 20:04:29 +02:00
doesn't equal
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( a != b )
Approved new test output
2014-05-20 19:28:48 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
1 != 2
Approved new test output
2014-05-20 19:28:48 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( b != a )
Approved new test output
2014-05-20 19:28:48 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
2 != 1
Approved new test output
2014-05-20 19:28:48 +02:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
nested SECTION tests
Deprecated description in SECTION (still accepts it, for now, but doesn't use it anywhere)
2018-06-25 20:04:29 +02:00
doesn't equal
not equal
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
Approved new test output
2014-05-20 19:28:48 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( a != b )
Approved new test output
2014-05-20 19:28:48 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
1 != 2
Approved new test output
2014-05-20 19:28:48 +02:00
Add new SKIP macro for skipping tests at runtime (#2360) * Add new SKIP macro for skipping tests at runtime This adds a new `SKIP` macro for dynamically skipping tests at runtime. The "skipped" status of a test case is treated as a first-class citizen, like "succeeded" or "failed", and is reported with a new color on the console. * Don't show "skipped assertions" in console/compact reporters Also extend skip tests to cover a few more use cases. * Return exit code 4 if all test cases are skipped * Use LightGrey for the skip colour This isn't great, but is better than the deep blue that was borderline invisible on dark backgrounds. The fix is to redo the colouring a bit, including introducing light-blue that is actually visible. * Add support for explicit skips in all reporters * --allow-running-no-tests also allows all tests to be skipped * Add docs for SKIP macro, deprecate IEventListener::skipTest Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2023-01-12 15:01:47 +01:00
a-------------------------------------------------------------------------------
nested sections can be skipped dynamically at runtime
A
-------------------------------------------------------------------------------
Skip.tests.cpp:<line number>
...............................................................................
No assertions in section 'A'
!
b1-------------------------------------------------------------------------------
nested sections can be skipped dynamically at runtime
B
B1
-------------------------------------------------------------------------------
Skip.tests.cpp:<line number>
...............................................................................
No assertions in section 'B1'
!
-------------------------------------------------------------------------------
nested sections can be skipped dynamically at runtime
B
B2
-------------------------------------------------------------------------------
Skip.tests.cpp:<line number>
...............................................................................
Skip.tests.cpp:<line number>: SKIPPED:
!
Approved new test output
2014-05-20 19:28:48 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
non streamable - with conv. op
Approved new test output
2014-05-20 19:28:48 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Tricky.tests.cpp:<line number>
Approved new test output
2014-05-20 19:28:48 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( s == "7" )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"7" == "7"
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Added test comparing non-copyable values
2017-08-17 17:48:46 +02:00
-------------------------------------------------------------------------------
non-copyable objects
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Tricky.tests.cpp:<line number>
Added test comparing non-copyable values
2017-08-17 17:48:46 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Added test comparing non-copyable values
2017-08-17 17:48:46 +02:00
CHECK( ti == typeid(int) )
with expansion:
{?} == {?}
Remove CATCH_CONFIG_ENABLE_BENCHMARKING compilation toggle Now that Catch2 is a proper library, we can always build the full library (comparatively minor slowdown) and the user can avoid including benchmarking headers to avoid the compilation slowdown.
2020-02-03 18:08:15 +01:00
-------------------------------------------------------------------------------
normal_quantile
-------------------------------------------------------------------------------
InternalBenchmark.tests.cpp:<line number>
...............................................................................
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( normal_quantile(0.551780) == Approx(0.13015979861484198) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
0.13015979861484195
==
Approx( 0.13015979861484198 )
Remove CATCH_CONFIG_ENABLE_BENCHMARKING compilation toggle Now that Catch2 is a proper library, we can always build the full library (comparatively minor slowdown) and the user can avoid including benchmarking headers to avoid the compilation slowdown.
2020-02-03 18:08:15 +01:00
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( normal_quantile(0.533700) == Approx(0.08457408802851875) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
0.08457408802851875
==
Approx( 0.08457408802851875 )
Remove CATCH_CONFIG_ENABLE_BENCHMARKING compilation toggle Now that Catch2 is a proper library, we can always build the full library (comparatively minor slowdown) and the user can avoid including benchmarking headers to avoid the compilation slowdown.
2020-02-03 18:08:15 +01:00
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( normal_quantile(0.025000) == Approx(-1.95996398454005449) )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
-1.95996398454005405
==
Approx( -1.95996398454005449 )
Remove CATCH_CONFIG_ENABLE_BENCHMARKING compilation toggle Now that Catch2 is a proper library, we can always build the full library (comparatively minor slowdown) and the user can avoid including benchmarking headers to avoid the compilation slowdown.
2020-02-03 18:08:15 +01:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
not allowed
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Add tests for unscoped info Update approval tests as new tests are added for messaging.
2019-02-01 16:36:35 +01:00
-------------------------------------------------------------------------------
not prints unscoped info from previous failures
-------------------------------------------------------------------------------
Message.tests.cpp:<line number>
...............................................................................
Message.tests.cpp:<line number>: PASSED:
REQUIRE( true )
with message:
this MAY be seen only for the FIRST assertion IF info is printed for passing
assertions
Message.tests.cpp:<line number>: PASSED:
REQUIRE( true )
with message:
this MAY be seen only for the SECOND assertion IF info is printed for passing
assertions
Message.tests.cpp:<line number>: FAILED:
REQUIRE( false )
with message:
this SHOULD be seen
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
null strings
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Approval tests can use Catch path fixed in env. var, and convert nullptr and __null to 0 for comparison
2017-01-09 15:12:12 +01:00
REQUIRE( makeString( false ) != static_cast<char*>(0) )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"valid string" != {null string}
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Approval tests can use Catch path fixed in env. var, and convert nullptr and __null to 0 for comparison
2017-01-09 15:12:12 +01:00
REQUIRE( makeString( true ) == static_cast<char*>(0) )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
{null string} == {null string}
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
-------------------------------------------------------------------------------
null_ptr
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Tricky.tests.cpp:<line number>
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
REQUIRE( ptr.get() == 0 )
with expansion:
0 == 0
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
pair<pair<int,const char *,pair<std::string,int> > -> toString
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
ToStringPair.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringPair.tests.cpp:<line number>: PASSED:
Reworked stringification layer, removed Catch::toString Now the order of stringification checks is 1) StringMaker specialization 2) operator<< toString overloads and specializations have been removed.
2017-05-02 23:51:03 +02:00
REQUIRE( ::Catch::Detail::stringify( pair ) == "{ { 42, \"Arthur\" }, { \"Ford\", 24 } }" )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"{ { 42, "Arthur" }, { "Ford", 24 } }"
==
"{ { 42, "Arthur" }, { "Ford", 24 } }"
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Rebased approvals for stringified enum tests
2019-04-26 12:30:19 +02:00
-------------------------------------------------------------------------------
parseEnums
No enums
-------------------------------------------------------------------------------
ToString.tests.cpp:<line number>
...............................................................................
ToString.tests.cpp:<line number>: PASSED:
Use StringRefs through the enum registration
2019-09-08 14:07:18 +02:00
CHECK_THAT( parseEnums( "" ), Equals( std::vector<Catch::StringRef>{} ) )
Rebased approvals for stringified enum tests
2019-04-26 12:30:19 +02:00
with expansion:
{ } Equals: { }
-------------------------------------------------------------------------------
parseEnums
One enum value
-------------------------------------------------------------------------------
ToString.tests.cpp:<line number>
...............................................................................
ToString.tests.cpp:<line number>: PASSED:
Use StringRefs through the enum registration
2019-09-08 14:07:18 +02:00
CHECK_THAT( parseEnums( "ClassName::EnumName::Value1" ), Equals(std::vector<Catch::StringRef>{"Value1"} ) )
Rebased approvals for stringified enum tests
2019-04-26 12:30:19 +02:00
with expansion:
Use StringRefs through the enum registration
2019-09-08 14:07:18 +02:00
{ Value1 } Equals: { Value1 }
Rebased approvals for stringified enum tests
2019-04-26 12:30:19 +02:00
ToString.tests.cpp:<line number>: PASSED:
Use StringRefs through the enum registration
2019-09-08 14:07:18 +02:00
CHECK_THAT( parseEnums( "Value1" ), Equals( std::vector<Catch::StringRef>{"Value1"} ) )
Rebased approvals for stringified enum tests
2019-04-26 12:30:19 +02:00
with expansion:
Use StringRefs through the enum registration
2019-09-08 14:07:18 +02:00
{ Value1 } Equals: { Value1 }
Rebased approvals for stringified enum tests
2019-04-26 12:30:19 +02:00
ToString.tests.cpp:<line number>: PASSED:
Use StringRefs through the enum registration
2019-09-08 14:07:18 +02:00
CHECK_THAT( parseEnums( "EnumName::Value1" ), Equals(std::vector<Catch::StringRef>{"Value1"} ) )
Rebased approvals for stringified enum tests
2019-04-26 12:30:19 +02:00
with expansion:
Use StringRefs through the enum registration
2019-09-08 14:07:18 +02:00
{ Value1 } Equals: { Value1 }
Rebased approvals for stringified enum tests
2019-04-26 12:30:19 +02:00
-------------------------------------------------------------------------------
parseEnums
Multiple enum values
-------------------------------------------------------------------------------
ToString.tests.cpp:<line number>
...............................................................................
ToString.tests.cpp:<line number>: PASSED:
Use StringRefs through the enum registration
2019-09-08 14:07:18 +02:00
CHECK_THAT( parseEnums( "ClassName::EnumName::Value1, ClassName::EnumName::Value2" ), Equals( std::vector<Catch::StringRef>{"Value1", "Value2"} ) )
Rebased approvals for stringified enum tests
2019-04-26 12:30:19 +02:00
with expansion:
Use StringRefs through the enum registration
2019-09-08 14:07:18 +02:00
{ Value1, Value2 } Equals: { Value1, Value2 }
Rebased approvals for stringified enum tests
2019-04-26 12:30:19 +02:00
ToString.tests.cpp:<line number>: PASSED:
Use StringRefs through the enum registration
2019-09-08 14:07:18 +02:00
CHECK_THAT( parseEnums( "ClassName::EnumName::Value1, ClassName::EnumName::Value2, ClassName::EnumName::Value3" ), Equals( std::vector<Catch::StringRef>{"Value1", "Value2", "Value3"} ) )
Rebased approvals for stringified enum tests
2019-04-26 12:30:19 +02:00
with expansion:
Use StringRefs through the enum registration
2019-09-08 14:07:18 +02:00
{ Value1, Value2, Value3 } Equals: { Value1, Value2, Value3 }
Rebased approvals for stringified enum tests
2019-04-26 12:30:19 +02:00
ToString.tests.cpp:<line number>: PASSED:
Use StringRefs through the enum registration
2019-09-08 14:07:18 +02:00
CHECK_THAT( parseEnums( "ClassName::EnumName::Value1,ClassName::EnumName::Value2 , ClassName::EnumName::Value3" ), Equals( std::vector<Catch::StringRef>{"Value1", "Value2", "Value3"} ) )
Rebased approvals for stringified enum tests
2019-04-26 12:30:19 +02:00
with expansion:
Use StringRefs through the enum registration
2019-09-08 14:07:18 +02:00
{ Value1, Value2, Value3 } Equals: { Value1, Value2, Value3 }
Rebased approvals for stringified enum tests
2019-04-26 12:30:19 +02:00
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
pointer to class
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Tricky.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Tricky.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( p == 0 )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Reworked stringification layer, removed Catch::toString Now the order of stringification checks is 1) StringMaker specialization 2) operator<< toString overloads and specializations have been removed.
2017-05-02 23:51:03 +02:00
0 == 0
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Add tests for unscoped info Update approval tests as new tests are added for messaging.
2019-02-01 16:36:35 +01:00
-------------------------------------------------------------------------------
print unscoped info if passing unscoped info is printed
-------------------------------------------------------------------------------
Message.tests.cpp:<line number>
...............................................................................
Message.tests.cpp:<line number>: PASSED:
REQUIRE( true )
with message:
this MAY be seen IF info is printed for passing assertions
-------------------------------------------------------------------------------
prints unscoped info on failure
-------------------------------------------------------------------------------
Message.tests.cpp:<line number>
...............................................................................
Message.tests.cpp:<line number>: FAILED:
REQUIRE( false )
with messages:
this SHOULD be seen
this SHOULD also be seen
-------------------------------------------------------------------------------
prints unscoped info only for the first assertion
-------------------------------------------------------------------------------
Message.tests.cpp:<line number>
...............................................................................
Message.tests.cpp:<line number>: FAILED:
CHECK( false )
with message:
this SHOULD be seen only ONCE
Message.tests.cpp:<line number>: PASSED:
CHECK( true )
Message.tests.cpp:<line number>: PASSED:
CHECK( true )
with message:
this MAY also be seen only ONCE IF info is printed for passing assertions
Message.tests.cpp:<line number>: PASSED:
CHECK( true )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
random SECTION tests
Deprecated description in SECTION (still accepts it, for now, but doesn't use it anywhere)
2018-06-25 20:04:29 +02:00
doesn't equal
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( a != b )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
1 != 2
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( b != a )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
2 != 1
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
random SECTION tests
Deprecated description in SECTION (still accepts it, for now, but doesn't use it anywhere)
2018-06-25 20:04:29 +02:00
not equal
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( a != b )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
1 != 2
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
replaceInPlace
replace single char
-------------------------------------------------------------------------------
Split out the rest of string manipulation tests
2019-09-07 20:22:36 +02:00
StringManip.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Split out the rest of string manipulation tests
2019-09-07 20:22:36 +02:00
StringManip.tests.cpp:<line number>: PASSED:
CHECK( Catch::replaceInPlace(letters, "b", "z") )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
true
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Split out the rest of string manipulation tests
2019-09-07 20:22:36 +02:00
StringManip.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( letters == "azcdefcg" )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"azcdefcg" == "azcdefcg"
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
replaceInPlace
replace two chars
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Split out the rest of string manipulation tests
2019-09-07 20:22:36 +02:00
StringManip.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
Split out the rest of string manipulation tests
2019-09-07 20:22:36 +02:00
StringManip.tests.cpp:<line number>: PASSED:
CHECK( Catch::replaceInPlace(letters, "c", "z") )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
true
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Split out the rest of string manipulation tests
2019-09-07 20:22:36 +02:00
StringManip.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( letters == "abzdefzg" )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"abzdefzg" == "abzdefzg"
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
replaceInPlace
replace first char
-------------------------------------------------------------------------------
Split out the rest of string manipulation tests
2019-09-07 20:22:36 +02:00
StringManip.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Split out the rest of string manipulation tests
2019-09-07 20:22:36 +02:00
StringManip.tests.cpp:<line number>: PASSED:
CHECK( Catch::replaceInPlace(letters, "a", "z") )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
true
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Split out the rest of string manipulation tests
2019-09-07 20:22:36 +02:00
StringManip.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( letters == "zbcdefcg" )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"zbcdefcg" == "zbcdefcg"
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
replaceInPlace
replace last char
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
-------------------------------------------------------------------------------
Split out the rest of string manipulation tests
2019-09-07 20:22:36 +02:00
StringManip.tests.cpp:<line number>
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
...............................................................................
Split out the rest of string manipulation tests
2019-09-07 20:22:36 +02:00
StringManip.tests.cpp:<line number>: PASSED:
CHECK( Catch::replaceInPlace(letters, "g", "z") )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
true
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Split out the rest of string manipulation tests
2019-09-07 20:22:36 +02:00
StringManip.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( letters == "abcdefcz" )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"abcdefcz" == "abcdefcz"
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
replaceInPlace
replace all chars
-------------------------------------------------------------------------------
Split out the rest of string manipulation tests
2019-09-07 20:22:36 +02:00
StringManip.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Split out the rest of string manipulation tests
2019-09-07 20:22:36 +02:00
StringManip.tests.cpp:<line number>: PASSED:
CHECK( Catch::replaceInPlace(letters, letters, "replaced") )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
true
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
Split out the rest of string manipulation tests
2019-09-07 20:22:36 +02:00
StringManip.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( letters == "replaced" )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"replaced" == "replaced"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
replaceInPlace
replace no chars
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Split out the rest of string manipulation tests
2019-09-07 20:22:36 +02:00
StringManip.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
Split out the rest of string manipulation tests
2019-09-07 20:22:36 +02:00
StringManip.tests.cpp:<line number>: PASSED:
CHECK_FALSE( Catch::replaceInPlace(letters, "x", "z") )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
!false
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Split out the rest of string manipulation tests
2019-09-07 20:22:36 +02:00
StringManip.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( letters == letters )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"abcdefcg" == "abcdefcg"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
less copies and allocations in replaceInPlace
2024-02-25 18:01:28 +01:00
-------------------------------------------------------------------------------
replaceInPlace
no replace in already-replaced string
lengthening
-------------------------------------------------------------------------------
StringManip.tests.cpp:<line number>
...............................................................................
StringManip.tests.cpp:<line number>: PASSED:
CHECK( Catch::replaceInPlace(letters, "c", "cc") )
with expansion:
true
StringManip.tests.cpp:<line number>: PASSED:
CHECK( letters == "abccdefccg" )
with expansion:
"abccdefccg" == "abccdefccg"
-------------------------------------------------------------------------------
replaceInPlace
no replace in already-replaced string
shortening
-------------------------------------------------------------------------------
StringManip.tests.cpp:<line number>
...............................................................................
StringManip.tests.cpp:<line number>: PASSED:
CHECK( Catch::replaceInPlace(s, "--", "-") )
with expansion:
true
StringManip.tests.cpp:<line number>: PASSED:
CHECK( s == "--" )
with expansion:
"--" == "--"
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
replaceInPlace
escape '
-------------------------------------------------------------------------------
Split out the rest of string manipulation tests
2019-09-07 20:22:36 +02:00
StringManip.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Split out the rest of string manipulation tests
2019-09-07 20:22:36 +02:00
StringManip.tests.cpp:<line number>: PASSED:
CHECK( Catch::replaceInPlace(s, "'", "|'") )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
true
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Split out the rest of string manipulation tests
2019-09-07 20:22:36 +02:00
StringManip.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( s == "didn|'t" )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"didn|'t" == "didn|'t"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Add %stderr and %stdout as recognized magic stream names
2022-03-07 10:42:26 +01:00
-------------------------------------------------------------------------------
request an unknown %-starting stream fails
-------------------------------------------------------------------------------
Stream.tests.cpp:<line number>
...............................................................................
Stream.tests.cpp:<line number>: PASSED:
REQUIRE_THROWS( Catch::makeStream( "%somestream" ) )
Remove CATCH_CONFIG_ENABLE_BENCHMARKING compilation toggle Now that Catch2 is a proper library, we can always build the full library (comparatively minor slowdown) and the user can avoid including benchmarking headers to avoid the compilation slowdown.
2020-02-03 18:08:15 +01:00
-------------------------------------------------------------------------------
resolution
-------------------------------------------------------------------------------
InternalBenchmark.tests.cpp:<line number>
...............................................................................
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( res.size() == count )
with expansion:
10 == 10
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( res[i] == rate )
with expansion:
1000.0 == 1000 (0x<hex digits>)
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( res[i] == rate )
with expansion:
1000.0 == 1000 (0x<hex digits>)
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( res[i] == rate )
with expansion:
1000.0 == 1000 (0x<hex digits>)
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( res[i] == rate )
with expansion:
1000.0 == 1000 (0x<hex digits>)
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( res[i] == rate )
with expansion:
1000.0 == 1000 (0x<hex digits>)
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( res[i] == rate )
with expansion:
1000.0 == 1000 (0x<hex digits>)
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( res[i] == rate )
with expansion:
1000.0 == 1000 (0x<hex digits>)
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( res[i] == rate )
with expansion:
1000.0 == 1000 (0x<hex digits>)
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( res[i] == rate )
with expansion:
1000.0 == 1000 (0x<hex digits>)
-------------------------------------------------------------------------------
run_for_at_least, chronometer
-------------------------------------------------------------------------------
InternalBenchmark.tests.cpp:<line number>
...............................................................................
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( meter.runs() >= old_runs )
with expansion:
1 >= 1
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( meter.runs() >= old_runs )
with expansion:
2 >= 1
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( meter.runs() >= old_runs )
with expansion:
4 >= 2
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( meter.runs() >= old_runs )
with expansion:
8 >= 4
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( meter.runs() >= old_runs )
with expansion:
16 >= 8
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( meter.runs() >= old_runs )
with expansion:
32 >= 16
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( meter.runs() >= old_runs )
with expansion:
64 >= 32
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( meter.runs() >= old_runs )
with expansion:
128 >= 64
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( Timing.elapsed >= time )
with expansion:
128 ns >= 100 ns
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( Timing.result == Timing.iterations + 17 )
with expansion:
145 == 145
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( Timing.iterations >= time.count() )
with expansion:
128 >= 100
-------------------------------------------------------------------------------
run_for_at_least, int
-------------------------------------------------------------------------------
InternalBenchmark.tests.cpp:<line number>
...............................................................................
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( x >= old_x )
with expansion:
1 >= 1
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( x >= old_x )
with expansion:
2 >= 1
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( x >= old_x )
with expansion:
4 >= 2
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( x >= old_x )
with expansion:
8 >= 4
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( x >= old_x )
with expansion:
16 >= 8
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( x >= old_x )
with expansion:
32 >= 16
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( x >= old_x )
with expansion:
64 >= 32
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( x >= old_x )
with expansion:
128 >= 64
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( Timing.elapsed >= time )
with expansion:
128 ns >= 100 ns
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( Timing.result == Timing.iterations + 17 )
with expansion:
145 == 145
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( Timing.iterations >= time.count() )
with expansion:
128 >= 100
Fixed NoAssertions warning
2018-01-26 17:52:28 +01:00
-------------------------------------------------------------------------------
second tag
-------------------------------------------------------------------------------
Misc.tests.cpp:<line number>
...............................................................................
No assertions in test case 'second tag'
Add new SKIP macro for skipping tests at runtime (#2360) * Add new SKIP macro for skipping tests at runtime This adds a new `SKIP` macro for dynamically skipping tests at runtime. The "skipped" status of a test case is treated as a first-class citizen, like "succeeded" or "failed", and is reported with a new color on the console. * Don't show "skipped assertions" in console/compact reporters Also extend skip tests to cover a few more use cases. * Return exit code 4 if all test cases are skipped * Use LightGrey for the skip colour This isn't great, but is better than the deep blue that was borderline invisible on dark backgrounds. The fix is to redo the colouring a bit, including introducing light-blue that is actually visible. * Add support for explicit skips in all reporters * --allow-running-no-tests also allows all tests to be skipped * Add docs for SKIP macro, deprecate IEventListener::skipTest Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2023-01-12 15:01:47 +01:00
-------------------------------------------------------------------------------
sections can be skipped dynamically at runtime
not skipped
-------------------------------------------------------------------------------
Skip.tests.cpp:<line number>
...............................................................................
Skip.tests.cpp:<line number>: PASSED:
-------------------------------------------------------------------------------
sections can be skipped dynamically at runtime
skipped
-------------------------------------------------------------------------------
Skip.tests.cpp:<line number>
...............................................................................
Skip.tests.cpp:<line number>: SKIPPED:
-------------------------------------------------------------------------------
sections can be skipped dynamically at runtime
also not skipped
-------------------------------------------------------------------------------
Skip.tests.cpp:<line number>
...............................................................................
Skip.tests.cpp:<line number>: PASSED:
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
send a single char to INFO
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( false )
with message:
3
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
sends information to INFO
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Message.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Message.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( false )
with messages:
hi
i := 7
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Fix test tag parsing to split [.foo] into [.][foo]
2019-03-29 10:48:56 +01:00
-------------------------------------------------------------------------------
shortened hide tags are split apart
-------------------------------------------------------------------------------
Tag.tests.cpp:<line number>
...............................................................................
Tag.tests.cpp:<line number>: PASSED:
Refactor implementation of case-insensitivity in tags By not materializing the lower cased tags ahead of time, we save allocations at the cost of worsened performance when comparing two tags. Since there are rarely many tags, and commonly they are not compared even if present, this is almost always a win. The new implementation also improves the robustness of the code responsible for handling tags in a case-insensitive manner.
2021-12-26 22:10:20 +01:00
REQUIRE_THAT( testcase.tags, VectorContains( Tag( "magic-tag" ) ) && VectorContains( Tag( "."_catch_sr ) ) )
Fix test tag parsing to split [.foo] into [.][foo]
2019-03-29 10:48:56 +01:00
with expansion:
Refactor implementation of case-insensitivity in tags By not materializing the lower cased tags ahead of time, we save allocations at the cost of worsened performance when comparing two tags. Since there are rarely many tags, and commonly they are not compared even if present, this is almost always a win. The new implementation also improves the robustness of the code responsible for handling tags in a case-insensitive manner.
2021-12-26 22:10:20 +01:00
{ {?}, {?} } ( Contains: {?} and Contains: {?} )
Fix test tag parsing to split [.foo] into [.][foo]
2019-03-29 10:48:56 +01:00
Add new SKIP macro for skipping tests at runtime (#2360) * Add new SKIP macro for skipping tests at runtime This adds a new `SKIP` macro for dynamically skipping tests at runtime. The "skipped" status of a test case is treated as a first-class citizen, like "succeeded" or "failed", and is reported with a new color on the console. * Don't show "skipped assertions" in console/compact reporters Also extend skip tests to cover a few more use cases. * Return exit code 4 if all test cases are skipped * Use LightGrey for the skip colour This isn't great, but is better than the deep blue that was borderline invisible on dark backgrounds. The fix is to redo the colouring a bit, including introducing light-blue that is actually visible. * Add support for explicit skips in all reporters * --allow-running-no-tests also allows all tests to be skipped * Add docs for SKIP macro, deprecate IEventListener::skipTest Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2023-01-12 15:01:47 +01:00
-------------------------------------------------------------------------------
skipped tests can optionally provide a reason
-------------------------------------------------------------------------------
Skip.tests.cpp:<line number>
...............................................................................
Skip.tests.cpp:<line number>: SKIPPED:
explicitly with message:
skipping because answer = 43
Rebased approvals for stringified enum tests
2019-04-26 12:30:19 +02:00
-------------------------------------------------------------------------------
splitString
-------------------------------------------------------------------------------
Split out the rest of string manipulation tests
2019-09-07 20:22:36 +02:00
StringManip.tests.cpp:<line number>
Rebased approvals for stringified enum tests
2019-04-26 12:30:19 +02:00
...............................................................................
Split out the rest of string manipulation tests
2019-09-07 20:22:36 +02:00
StringManip.tests.cpp:<line number>: PASSED:
CHECK_THAT( splitStringRef("", ','), Equals(std::vector<StringRef>()) )
Rebased approvals for stringified enum tests
2019-04-26 12:30:19 +02:00
with expansion:
{ } Equals: { }
Split out the rest of string manipulation tests
2019-09-07 20:22:36 +02:00
StringManip.tests.cpp:<line number>: PASSED:
CHECK_THAT( splitStringRef("abc", ','), Equals(std::vector<StringRef>{"abc"}) )
Rebased approvals for stringified enum tests
2019-04-26 12:30:19 +02:00
with expansion:
{ abc } Equals: { abc }
Split out the rest of string manipulation tests
2019-09-07 20:22:36 +02:00
StringManip.tests.cpp:<line number>: PASSED:
CHECK_THAT( splitStringRef("abc,def", ','), Equals(std::vector<StringRef>{"abc", "def"}) )
Rebased approvals for stringified enum tests
2019-04-26 12:30:19 +02:00
with expansion:
{ abc, def } Equals: { abc, def }
Add tests for unscoped info Update approval tests as new tests are added for messaging.
2019-02-01 16:36:35 +01:00
-------------------------------------------------------------------------------
stacks unscoped info in loops
-------------------------------------------------------------------------------
Message.tests.cpp:<line number>
...............................................................................
Message.tests.cpp:<line number>: FAILED:
CHECK( false )
with messages:
Count 1 to 3...
1
2
3
Message.tests.cpp:<line number>: FAILED:
CHECK( false )
with messages:
Count 4 to 6...
4
5
6
Change startsWith(char) to take StringRef as argument
2021-09-27 14:52:44 +02:00
-------------------------------------------------------------------------------
startsWith
-------------------------------------------------------------------------------
StringManip.tests.cpp:<line number>
...............................................................................
StringManip.tests.cpp:<line number>: PASSED:
CHECK_FALSE( startsWith("", 'c') )
with expansion:
!false
StringManip.tests.cpp:<line number>: PASSED:
CHECK( startsWith(std::string("abc"), 'a') )
with expansion:
true
StringManip.tests.cpp:<line number>: PASSED:
CHECK( startsWith("def"_catch_sr, 'd') )
with expansion:
true
Added tests for stringifying map and set
2018-01-04 11:03:08 +01:00
-------------------------------------------------------------------------------
std::map is convertible string
empty
-------------------------------------------------------------------------------
ToStringGeneral.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringGeneral.tests.cpp:<line number>: PASSED:
Added tests for stringifying map and set
2018-01-04 11:03:08 +01:00
REQUIRE( Catch::Detail::stringify( emptyMap ) == "{ }" )
with expansion:
"{ }" == "{ }"
-------------------------------------------------------------------------------
std::map is convertible string
single item
-------------------------------------------------------------------------------
ToStringGeneral.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringGeneral.tests.cpp:<line number>: PASSED:
Added tests for stringifying map and set
2018-01-04 11:03:08 +01:00
REQUIRE( Catch::Detail::stringify( map ) == "{ { \"one\", 1 } }" )
with expansion:
"{ { "one", 1 } }" == "{ { "one", 1 } }"
-------------------------------------------------------------------------------
std::map is convertible string
several items
-------------------------------------------------------------------------------
ToStringGeneral.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringGeneral.tests.cpp:<line number>: PASSED:
Added tests for stringifying map and set
2018-01-04 11:03:08 +01:00
REQUIRE( Catch::Detail::stringify( map ) == "{ { \"abc\", 1 }, { \"def\", 2 }, { \"ghi\", 3 } }" )
with expansion:
"{ { "abc", 1 }, { "def", 2 }, { "ghi", 3 } }"
==
"{ { "abc", 1 }, { "def", 2 }, { "ghi", 3 } }"
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
std::pair<int,const std::string> -> toString
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
ToStringPair.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringPair.tests.cpp:<line number>: PASSED:
Reworked stringification layer, removed Catch::toString Now the order of stringification checks is 1) StringMaker specialization 2) operator<< toString overloads and specializations have been removed.
2017-05-02 23:51:03 +02:00
REQUIRE( ::Catch::Detail::stringify(value) == "{ 34, \"xyzzy\" }" )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"{ 34, "xyzzy" }" == "{ 34, "xyzzy" }"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
std::pair<int,std::string> -> toString
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
ToStringPair.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringPair.tests.cpp:<line number>: PASSED:
Reworked stringification layer, removed Catch::toString Now the order of stringification checks is 1) StringMaker specialization 2) operator<< toString overloads and specializations have been removed.
2017-05-02 23:51:03 +02:00
REQUIRE( ::Catch::Detail::stringify( value ) == "{ 34, \"xyzzy\" }" )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"{ 34, "xyzzy" }" == "{ 34, "xyzzy" }"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Added tests for stringifying map and set
2018-01-04 11:03:08 +01:00
-------------------------------------------------------------------------------
std::set is convertible string
empty
-------------------------------------------------------------------------------
ToStringGeneral.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringGeneral.tests.cpp:<line number>: PASSED:
Added tests for stringifying map and set
2018-01-04 11:03:08 +01:00
REQUIRE( Catch::Detail::stringify( emptySet ) == "{ }" )
with expansion:
"{ }" == "{ }"
-------------------------------------------------------------------------------
std::set is convertible string
single item
-------------------------------------------------------------------------------
ToStringGeneral.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringGeneral.tests.cpp:<line number>: PASSED:
Added tests for stringifying map and set
2018-01-04 11:03:08 +01:00
REQUIRE( Catch::Detail::stringify( set ) == "{ \"one\" }" )
with expansion:
"{ "one" }" == "{ "one" }"
-------------------------------------------------------------------------------
std::set is convertible string
several items
-------------------------------------------------------------------------------
ToStringGeneral.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringGeneral.tests.cpp:<line number>: PASSED:
Added tests for stringifying map and set
2018-01-04 11:03:08 +01:00
REQUIRE( Catch::Detail::stringify( set ) == "{ \"abc\", \"def\", \"ghi\" }" )
with expansion:
"{ "abc", "def", "ghi" }"
==
"{ "abc", "def", "ghi" }"
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
std::vector<std::pair<std::string,int> > -> toString
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
ToStringPair.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringPair.tests.cpp:<line number>: PASSED:
Reworked stringification layer, removed Catch::toString Now the order of stringification checks is 1) StringMaker specialization 2) operator<< toString overloads and specializations have been removed.
2017-05-02 23:51:03 +02:00
REQUIRE( ::Catch::Detail::stringify( pr ) == "{ { \"green\", 55 } }" )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"{ { "green", 55 } }"
==
"{ { "green", 55 } }"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Add %stderr and %stdout as recognized magic stream names
2022-03-07 10:42:26 +01:00
-------------------------------------------------------------------------------
stdout and stderr streams have %-starting name
-------------------------------------------------------------------------------
Stream.tests.cpp:<line number>
...............................................................................
Stream.tests.cpp:<line number>: PASSED:
Rename isStdout => isConsole and add doccomment
2022-03-21 00:22:54 +01:00
REQUIRE( Catch::makeStream( "%stderr" )->isConsole() )
Add %stderr and %stdout as recognized magic stream names
2022-03-07 10:42:26 +01:00
with expansion:
true
Stream.tests.cpp:<line number>: PASSED:
Rename isStdout => isConsole and add doccomment
2022-03-21 00:22:54 +01:00
REQUIRE( Catch::makeStream( "%stdout" )->isConsole() )
Add %stderr and %stdout as recognized magic stream names
2022-03-07 10:42:26 +01:00
with expansion:
true
Cleanup some tests
2018-02-15 16:03:24 +01:00
-------------------------------------------------------------------------------
stringify ranges
-------------------------------------------------------------------------------
ToStringWhich.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringWhich.tests.cpp:<line number>: PASSED:
Cleanup some tests
2018-02-15 16:03:24 +01:00
REQUIRE( ::Catch::Detail::stringify(streamable_range{}) == "op<<(streamable_range)" )
with expansion:
"op<<(streamable_range)"
==
"op<<(streamable_range)"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringWhich.tests.cpp:<line number>: PASSED:
Cleanup some tests
2018-02-15 16:03:24 +01:00
REQUIRE( ::Catch::Detail::stringify(stringmaker_range{}) == "stringmaker(streamable_range)" )
with expansion:
"stringmaker(streamable_range)"
==
"stringmaker(streamable_range)"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringWhich.tests.cpp:<line number>: PASSED:
Cleanup some tests
2018-02-15 16:03:24 +01:00
REQUIRE( ::Catch::Detail::stringify(just_range{}) == "{ 1, 2, 3, 4 }" )
with expansion:
"{ 1, 2, 3, 4 }" == "{ 1, 2, 3, 4 }"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringWhich.tests.cpp:<line number>: PASSED:
Remove testing of CATCH_CONFIG_FALLBACK_STRINGIFIER from SelfTest This removes a potential ODR violation and the configuration option is tested in its own separate binary anyway.
2020-01-21 15:14:24 +01:00
REQUIRE( ::Catch::Detail::stringify(disabled_range{}) == "{?}" )
Cleanup some tests
2018-02-15 16:03:24 +01:00
with expansion:
Remove testing of CATCH_CONFIG_FALLBACK_STRINGIFIER from SelfTest This removes a potential ODR violation and the configuration option is tested in its own separate binary anyway.
2020-01-21 15:14:24 +01:00
"{?}" == "{?}"
Cleanup some tests
2018-02-15 16:03:24 +01:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Reworked stringification layer, removed Catch::toString Now the order of stringification checks is 1) StringMaker specialization 2) operator<< toString overloads and specializations have been removed.
2017-05-02 23:51:03 +02:00
stringify( has_maker )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
ToStringWhich.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringWhich.tests.cpp:<line number>: PASSED:
Reworked stringification layer, removed Catch::toString Now the order of stringification checks is 1) StringMaker specialization 2) operator<< toString overloads and specializations have been removed.
2017-05-02 23:51:03 +02:00
REQUIRE( ::Catch::Detail::stringify( item ) == "StringMaker<has_maker>" )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Reworked stringification layer, removed Catch::toString Now the order of stringification checks is 1) StringMaker specialization 2) operator<< toString overloads and specializations have been removed.
2017-05-02 23:51:03 +02:00
"StringMaker<has_maker>"
==
"StringMaker<has_maker>"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Cleanup some tests
2018-02-15 16:03:24 +01:00
stringify( has_maker_and_operator )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
ToStringWhich.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringWhich.tests.cpp:<line number>: PASSED:
Reworked stringification layer, removed Catch::toString Now the order of stringification checks is 1) StringMaker specialization 2) operator<< toString overloads and specializations have been removed.
2017-05-02 23:51:03 +02:00
REQUIRE( ::Catch::Detail::stringify( item ) == "StringMaker<has_maker_and_operator>" )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Reworked stringification layer, removed Catch::toString Now the order of stringification checks is 1) StringMaker specialization 2) operator<< toString overloads and specializations have been removed.
2017-05-02 23:51:03 +02:00
"StringMaker<has_maker_and_operator>"
==
"StringMaker<has_maker_and_operator>"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Add test for overriding the fallback stringifier
2018-02-15 15:12:19 +01:00
-------------------------------------------------------------------------------
stringify( has_neither )
-------------------------------------------------------------------------------
ToStringWhich.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringWhich.tests.cpp:<line number>: PASSED:
Remove testing of CATCH_CONFIG_FALLBACK_STRINGIFIER from SelfTest This removes a potential ODR violation and the configuration option is tested in its own separate binary anyway.
2020-01-21 15:14:24 +01:00
REQUIRE( ::Catch::Detail::stringify(item) == "{?}" )
Add test for overriding the fallback stringifier
2018-02-15 15:12:19 +01:00
with expansion:
Remove testing of CATCH_CONFIG_FALLBACK_STRINGIFIER from SelfTest This removes a potential ODR violation and the configuration option is tested in its own separate binary anyway.
2020-01-21 15:14:24 +01:00
"{?}" == "{?}"
Add test for overriding the fallback stringifier
2018-02-15 15:12:19 +01:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Reworked stringification layer, removed Catch::toString Now the order of stringification checks is 1) StringMaker specialization 2) operator<< toString overloads and specializations have been removed.
2017-05-02 23:51:03 +02:00
stringify( has_operator )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
ToStringWhich.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringWhich.tests.cpp:<line number>: PASSED:
Reworked stringification layer, removed Catch::toString Now the order of stringification checks is 1) StringMaker specialization 2) operator<< toString overloads and specializations have been removed.
2017-05-02 23:51:03 +02:00
REQUIRE( ::Catch::Detail::stringify( item ) == "operator<<( has_operator )" )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Reworked stringification layer, removed Catch::toString Now the order of stringification checks is 1) StringMaker specialization 2) operator<< toString overloads and specializations have been removed.
2017-05-02 23:51:03 +02:00
"operator<<( has_operator )"
==
"operator<<( has_operator )"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Fix ambiguity in stringification Happening when using clang and templated operators, clang cannot decide between the operator provided by ReusableStringStream and the one provided by the value value as both are templates. This is easily solved by calling the operator<< through the member syntax. Fixes #1285
2018-05-31 04:32:59 +02:00
-------------------------------------------------------------------------------
stringify( has_template_operator )
-------------------------------------------------------------------------------
ToStringWhich.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringWhich.tests.cpp:<line number>: PASSED:
Fix ambiguity in stringification Happening when using clang and templated operators, clang cannot decide between the operator provided by ReusableStringStream and the one provided by the value value as both are templates. This is easily solved by calling the operator<< through the member syntax. Fixes #1285
2018-05-31 04:32:59 +02:00
REQUIRE( ::Catch::Detail::stringify( item ) == "operator<<( has_template_operator )" )
with expansion:
"operator<<( has_template_operator )"
==
"operator<<( has_template_operator )"
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Cleanup some tests
2018-02-15 16:03:24 +01:00
stringify( vectors<has_maker> )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Cleanup some tests
2018-02-15 16:03:24 +01:00
ToStringWhich.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringWhich.tests.cpp:<line number>: PASSED:
Cleanup some tests
2018-02-15 16:03:24 +01:00
REQUIRE( ::Catch::Detail::stringify( v ) == "{ StringMaker<has_maker> }" )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Cleanup some tests
2018-02-15 16:03:24 +01:00
"{ StringMaker<has_maker> }"
==
"{ StringMaker<has_maker> }"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Cleanup some tests
2018-02-15 16:03:24 +01:00
stringify( vectors<has_maker_and_operator> )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Cleanup some tests
2018-02-15 16:03:24 +01:00
ToStringWhich.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringWhich.tests.cpp:<line number>: PASSED:
Cleanup some tests
2018-02-15 16:03:24 +01:00
REQUIRE( ::Catch::Detail::stringify( v ) == "{ StringMaker<has_maker_and_operator> }" )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Cleanup some tests
2018-02-15 16:03:24 +01:00
"{ StringMaker<has_maker_and_operator> }"
==
"{ StringMaker<has_maker_and_operator> }"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Cleanup some tests
2018-02-15 16:03:24 +01:00
stringify( vectors<has_operator> )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Cleanup some tests
2018-02-15 16:03:24 +01:00
ToStringWhich.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringWhich.tests.cpp:<line number>: PASSED:
Cleanup some tests
2018-02-15 16:03:24 +01:00
REQUIRE( ::Catch::Detail::stringify( v ) == "{ operator<<( has_operator ) }" )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Cleanup some tests
2018-02-15 16:03:24 +01:00
"{ operator<<( has_operator ) }"
==
"{ operator<<( has_operator ) }"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Update baselines
2018-08-19 23:22:36 +02:00
-------------------------------------------------------------------------------
strlen3
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( data.str.size() == data.len )
with expansion:
3 == 3
-------------------------------------------------------------------------------
strlen3
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( data.str.size() == data.len )
with expansion:
3 == 3
-------------------------------------------------------------------------------
strlen3
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( data.str.size() == data.len )
with expansion:
5 == 5
-------------------------------------------------------------------------------
strlen3
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Generators.tests.cpp:<line number>: PASSED:
Update baselines
2018-08-19 23:22:36 +02:00
REQUIRE( data.str.size() == data.len )
with expansion:
4 == 4
Redo generator interface
2019-01-27 19:46:28 +01:00
-------------------------------------------------------------------------------
tables
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( strlen(std::get<0>(data)) == static_cast<size_t>(std::get<1>(data)) )
with expansion:
5 == 5
-------------------------------------------------------------------------------
tables
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( strlen(std::get<0>(data)) == static_cast<size_t>(std::get<1>(data)) )
with expansion:
6 == 6
-------------------------------------------------------------------------------
tables
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( strlen(std::get<0>(data)) == static_cast<size_t>(std::get<1>(data)) )
with expansion:
5 == 5
-------------------------------------------------------------------------------
tables
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( strlen(std::get<0>(data)) == static_cast<size_t>(std::get<1>(data)) )
with expansion:
6 == 6
Add test for dots in tag names
2021-05-12 21:43:14 +02:00
-------------------------------------------------------------------------------
tags with dots in later positions are not parsed as hidden
-------------------------------------------------------------------------------
Tag.tests.cpp:<line number>
...............................................................................
Tag.tests.cpp:<line number>: PASSED:
Use TestCaseInfo in tests directly
2021-05-28 23:07:50 +02:00
REQUIRE( testcase.tags.size() == 1 )
Add test for dots in tag names
2021-05-12 21:43:14 +02:00
with expansion:
1 == 1
Tag.tests.cpp:<line number>: PASSED:
Use TestCaseInfo in tests directly
2021-05-28 23:07:50 +02:00
REQUIRE( testcase.tags[0].original == "magic.tag"_catch_sr )
Add test for dots in tag names
2021-05-12 21:43:14 +02:00
with expansion:
magic.tag == magic.tag
Add new SKIP macro for skipping tests at runtime (#2360) * Add new SKIP macro for skipping tests at runtime This adds a new `SKIP` macro for dynamically skipping tests at runtime. The "skipped" status of a test case is treated as a first-class citizen, like "succeeded" or "failed", and is reported with a new color on the console. * Don't show "skipped assertions" in console/compact reporters Also extend skip tests to cover a few more use cases. * Return exit code 4 if all test cases are skipped * Use LightGrey for the skip colour This isn't great, but is better than the deep blue that was borderline invisible on dark backgrounds. The fix is to redo the colouring a bit, including introducing light-blue that is actually visible. * Add support for explicit skips in all reporters * --allow-running-no-tests also allows all tests to be skipped * Add docs for SKIP macro, deprecate IEventListener::skipTest Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>
2023-01-12 15:01:47 +01:00
-------------------------------------------------------------------------------
tests can be skipped dynamically at runtime
-------------------------------------------------------------------------------
Skip.tests.cpp:<line number>
...............................................................................
Skip.tests.cpp:<line number>: SKIPPED:
Covered more translation possibilities
2018-02-15 19:58:49 +01:00
-------------------------------------------------------------------------------
thrown std::strings are translated
-------------------------------------------------------------------------------
Exception.tests.cpp:<line number>
...............................................................................
Exception.tests.cpp:<line number>: FAILED:
due to unexpected exception with message:
Why would you throw a std::string?
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Cleanup some tests
2018-02-15 16:03:24 +01:00
toString on const wchar_t const pointer returns the string contents
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Reworked stringification layer, removed Catch::toString Now the order of stringification checks is 1) StringMaker specialization 2) operator<< toString overloads and specializations have been removed.
2017-05-02 23:51:03 +02:00
CHECK( result == "\"wide load\"" )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Reworked stringification layer, removed Catch::toString Now the order of stringification checks is 1) StringMaker specialization 2) operator<< toString overloads and specializations have been removed.
2017-05-02 23:51:03 +02:00
""wide load"" == ""wide load""
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Prefer operator<< to range-based stringification Fixes #1172
2018-02-01 14:07:23 +01:00
-------------------------------------------------------------------------------
Cleanup some tests
2018-02-15 16:03:24 +01:00
toString on const wchar_t pointer returns the string contents
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
Cleanup some tests
2018-02-15 16:03:24 +01:00
Misc.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Cleanup some tests
2018-02-15 16:03:24 +01:00
CHECK( result == "\"wide load\"" )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Cleanup some tests
2018-02-15 16:03:24 +01:00
""wide load"" == ""wide load""
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Re-enable 2 string tests
2017-11-25 18:38:18 +01:00
-------------------------------------------------------------------------------
Cleanup some tests
2018-02-15 16:03:24 +01:00
toString on wchar_t const pointer returns the string contents
Re-enable 2 string tests
2017-11-25 18:38:18 +01:00
-------------------------------------------------------------------------------
Cleanup some tests
2018-02-15 16:03:24 +01:00
Misc.tests.cpp:<line number>
Re-enable 2 string tests
2017-11-25 18:38:18 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Cleanup some tests
2018-02-15 16:03:24 +01:00
CHECK( result == "\"wide load\"" )
Re-enable 2 string tests
2017-11-25 18:38:18 +01:00
with expansion:
Cleanup some tests
2018-02-15 16:03:24 +01:00
""wide load"" == ""wide load""
Re-enable 2 string tests
2017-11-25 18:38:18 +01:00
-------------------------------------------------------------------------------
Cleanup some tests
2018-02-15 16:03:24 +01:00
toString on wchar_t returns the string contents
Re-enable 2 string tests
2017-11-25 18:38:18 +01:00
-------------------------------------------------------------------------------
Cleanup some tests
2018-02-15 16:03:24 +01:00
Misc.tests.cpp:<line number>
Re-enable 2 string tests
2017-11-25 18:38:18 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Cleanup some tests
2018-02-15 16:03:24 +01:00
CHECK( result == "\"wide load\"" )
Re-enable 2 string tests
2017-11-25 18:38:18 +01:00
with expansion:
Cleanup some tests
2018-02-15 16:03:24 +01:00
""wide load"" == ""wide load""
Re-enable 2 string tests
2017-11-25 18:38:18 +01:00
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
-------------------------------------------------------------------------------
toString(enum class w/operator<<)
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
EnumToString.tests.cpp:<line number>
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
EnumToString.tests.cpp:<line number>: PASSED:
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
CHECK( ::Catch::Detail::stringify(e0) == "E2/V0" )
with expansion:
"E2/V0" == "E2/V0"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
EnumToString.tests.cpp:<line number>: PASSED:
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
CHECK( ::Catch::Detail::stringify(e1) == "E2/V1" )
with expansion:
"E2/V1" == "E2/V1"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
EnumToString.tests.cpp:<line number>: PASSED:
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
CHECK( ::Catch::Detail::stringify(e3) == "Unknown enum value 10" )
with expansion:
"Unknown enum value 10"
==
"Unknown enum value 10"
-------------------------------------------------------------------------------
toString(enum class)
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
EnumToString.tests.cpp:<line number>
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
EnumToString.tests.cpp:<line number>: PASSED:
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
CHECK( ::Catch::Detail::stringify(e0) == "0" )
with expansion:
Fix stringifying of unknown enums
2018-01-04 11:21:52 +01:00
"0" == "0"
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
EnumToString.tests.cpp:<line number>: PASSED:
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
CHECK( ::Catch::Detail::stringify(e1) == "1" )
with expansion:
Fix stringifying of unknown enums
2018-01-04 11:21:52 +01:00
"1" == "1"
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
toString(enum w/operator<<)
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
EnumToString.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
Changed the way noexcept support is handled to (hopefully) fix #275 and #273
2014-04-23 19:19:19 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
EnumToString.tests.cpp:<line number>: PASSED:
Reworked stringification layer, removed Catch::toString Now the order of stringification checks is 1) StringMaker specialization 2) operator<< toString overloads and specializations have been removed.
2017-05-02 23:51:03 +02:00
CHECK( ::Catch::Detail::stringify(e0) == "E2{0}" )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"E2{0}" == "E2{0}"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
EnumToString.tests.cpp:<line number>: PASSED:
Reworked stringification layer, removed Catch::toString Now the order of stringification checks is 1) StringMaker specialization 2) operator<< toString overloads and specializations have been removed.
2017-05-02 23:51:03 +02:00
CHECK( ::Catch::Detail::stringify(e1) == "E2{1}" )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"E2{1}" == "E2{1}"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
toString(enum)
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
EnumToString.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
EnumToString.tests.cpp:<line number>: PASSED:
Reworked stringification layer, removed Catch::toString Now the order of stringification checks is 1) StringMaker specialization 2) operator<< toString overloads and specializations have been removed.
2017-05-02 23:51:03 +02:00
CHECK( ::Catch::Detail::stringify(e0) == "0" )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"0" == "0"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
EnumToString.tests.cpp:<line number>: PASSED:
Reworked stringification layer, removed Catch::toString Now the order of stringification checks is 1) StringMaker specialization 2) operator<< toString overloads and specializations have been removed.
2017-05-02 23:51:03 +02:00
CHECK( ::Catch::Detail::stringify(e1) == "1" )
Approved all the changes following name/ tag parser rework
2014-05-16 19:31:15 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"1" == "1"
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
-------------------------------------------------------------------------------
tuple<>
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
ToStringTuple.tests.cpp:<line number>
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringTuple.tests.cpp:<line number>: PASSED:
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
CHECK( "{ }" == ::Catch::Detail::stringify(type{}) )
with expansion:
"{ }" == "{ }"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringTuple.tests.cpp:<line number>: PASSED:
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
CHECK( "{ }" == ::Catch::Detail::stringify(value) )
with expansion:
"{ }" == "{ }"
-------------------------------------------------------------------------------
tuple<float,int>
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
ToStringTuple.tests.cpp:<line number>
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringTuple.tests.cpp:<line number>: PASSED:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
CHECK( "1.5f" == ::Catch::Detail::stringify(float(1.5)) )
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
"1.5f" == "1.5f"
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringTuple.tests.cpp:<line number>: PASSED:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
CHECK( "{ 1.5f, 0 }" == ::Catch::Detail::stringify(type{1.5f,0}) )
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
"{ 1.5f, 0 }" == "{ 1.5f, 0 }"
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
-------------------------------------------------------------------------------
tuple<int>
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
ToStringTuple.tests.cpp:<line number>
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringTuple.tests.cpp:<line number>: PASSED:
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
CHECK( "{ 0 }" == ::Catch::Detail::stringify(type{0}) )
with expansion:
"{ 0 }" == "{ 0 }"
-------------------------------------------------------------------------------
tuple<string,string>
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
ToStringTuple.tests.cpp:<line number>
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringTuple.tests.cpp:<line number>: PASSED:
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
CHECK( "{ \"hello\", \"world\" }" == ::Catch::Detail::stringify(type{"hello","world"}) )
with expansion:
"{ "hello", "world" }"
==
"{ "hello", "world" }"
-------------------------------------------------------------------------------
tuple<tuple<int>,tuple<>,float>
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
ToStringTuple.tests.cpp:<line number>
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringTuple.tests.cpp:<line number>: PASSED:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
CHECK( "{ { 42 }, { }, 1.5f }" == ::Catch::Detail::stringify(value) )
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
"{ { 42 }, { }, 1.5f }"
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
==
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
"{ { 42 }, { }, 1.5f }"
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
Remove CATCH_CONFIG_ENABLE_BENCHMARKING compilation toggle Now that Catch2 is a proper library, we can always build the full library (comparatively minor slowdown) and the user can avoid including benchmarking headers to avoid the compilation slowdown.
2020-02-03 18:08:15 +01:00
-------------------------------------------------------------------------------
uniform samples
-------------------------------------------------------------------------------
InternalBenchmark.tests.cpp:<line number>
...............................................................................
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( e.point == 23 )
with expansion:
23.0 == 23
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( e.upper_bound == 23 )
with expansion:
23.0 == 23
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( e.lower_bound == 23 )
with expansion:
23.0 == 23
InternalBenchmark.tests.cpp:<line number>: PASSED:
CHECK( e.confidence_interval == 0.95 )
with expansion:
Default StringMaker<FloatingPointType>::precision to max_digits10 `max_digits10` is the number of decimal digits that the type _can_ represent, in other words, the number of decimal digits needed to disambiguate any two floating point numbers when serialized to a string.
2024-04-30 16:43:05 +02:00
0.94999999999999996 == 0.94999999999999996
Remove CATCH_CONFIG_ENABLE_BENCHMARKING compilation toggle Now that Catch2 is a proper library, we can always build the full library (comparatively minor slowdown) and the user can avoid including benchmarking headers to avoid the compilation slowdown.
2020-02-03 18:08:15 +01:00
Add uniform_integer_distribution
2023-12-08 22:01:36 +01:00
-------------------------------------------------------------------------------
uniform_integer_distribution can return the bounds
-------------------------------------------------------------------------------
RandomNumberGeneration.tests.cpp:<line number>
...............................................................................
RandomNumberGeneration.tests.cpp:<line number>: PASSED:
REQUIRE( dist.a() == -10 )
with expansion:
-10 == -10
RandomNumberGeneration.tests.cpp:<line number>: PASSED:
REQUIRE( dist.b() == 10 )
with expansion:
10 == 10
Implement a simplified variant of std::unique_ptr<T> This simplified variant supports only a subset of the functionality in `std::unique_ptr<T>`. `Catch::Detail::unique_ptr<T>` only supports single element pointer (no array support) with default deleter. By removing the support for custom deleters, we also avoid requiring significant machinery to support EBO, speeding up instantiations of `unique_ptr<T>` significantly. Catch2 also currently does not need to support `unique_ptr<T[]>`, so that is not supported either.
2020-05-24 23:41:02 +02:00
-------------------------------------------------------------------------------
unique_ptr reimplementation: basic functionality
Default constructed unique_ptr is empty
-------------------------------------------------------------------------------
UniquePtr.tests.cpp:<line number>
...............................................................................
UniquePtr.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( ptr )
with expansion:
!{?}
UniquePtr.tests.cpp:<line number>: PASSED:
REQUIRE( ptr.get() == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
unique_ptr reimplementation: basic functionality
Take ownership of allocation
-------------------------------------------------------------------------------
UniquePtr.tests.cpp:<line number>
...............................................................................
UniquePtr.tests.cpp:<line number>: PASSED:
REQUIRE( ptr )
with expansion:
{?}
UniquePtr.tests.cpp:<line number>: PASSED:
REQUIRE( *ptr == 0 )
with expansion:
0 == 0
UniquePtr.tests.cpp:<line number>: PASSED:
REQUIRE( ptr.get() == naked_ptr )
with expansion:
0x<hex digits> == 0x<hex digits>
-------------------------------------------------------------------------------
unique_ptr reimplementation: basic functionality
Take ownership of allocation
Plain reset deallocates
-------------------------------------------------------------------------------
UniquePtr.tests.cpp:<line number>
...............................................................................
UniquePtr.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( ptr )
with expansion:
!{?}
UniquePtr.tests.cpp:<line number>: PASSED:
REQUIRE( ptr.get() == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
unique_ptr reimplementation: basic functionality
Take ownership of allocation
-------------------------------------------------------------------------------
UniquePtr.tests.cpp:<line number>
...............................................................................
UniquePtr.tests.cpp:<line number>: PASSED:
REQUIRE( ptr )
with expansion:
{?}
UniquePtr.tests.cpp:<line number>: PASSED:
REQUIRE( *ptr == 0 )
with expansion:
0 == 0
UniquePtr.tests.cpp:<line number>: PASSED:
REQUIRE( ptr.get() == naked_ptr )
with expansion:
0x<hex digits> == 0x<hex digits>
-------------------------------------------------------------------------------
unique_ptr reimplementation: basic functionality
Take ownership of allocation
Reset replaces ownership
-------------------------------------------------------------------------------
UniquePtr.tests.cpp:<line number>
...............................................................................
UniquePtr.tests.cpp:<line number>: PASSED:
REQUIRE( ptr )
with expansion:
{?}
UniquePtr.tests.cpp:<line number>: PASSED:
REQUIRE( ptr.get() != 0 )
with expansion:
0x<hex digits> != 0
UniquePtr.tests.cpp:<line number>: PASSED:
REQUIRE( *ptr == 2 )
with expansion:
2 == 2
-------------------------------------------------------------------------------
unique_ptr reimplementation: basic functionality
Release releases ownership
-------------------------------------------------------------------------------
UniquePtr.tests.cpp:<line number>
...............................................................................
UniquePtr.tests.cpp:<line number>: PASSED:
CHECK_FALSE( ptr )
with expansion:
!{?}
UniquePtr.tests.cpp:<line number>: PASSED:
CHECK( ptr.get() == 0 )
with expansion:
0 == 0
-------------------------------------------------------------------------------
unique_ptr reimplementation: basic functionality
Move constructor
-------------------------------------------------------------------------------
UniquePtr.tests.cpp:<line number>
...............................................................................
UniquePtr.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( ptr1 )
with expansion:
!{?}
UniquePtr.tests.cpp:<line number>: PASSED:
REQUIRE( ptr2 )
with expansion:
{?}
UniquePtr.tests.cpp:<line number>: PASSED:
REQUIRE( *ptr2 == 1 )
with expansion:
1 == 1
-------------------------------------------------------------------------------
unique_ptr reimplementation: basic functionality
Move assignment
-------------------------------------------------------------------------------
UniquePtr.tests.cpp:<line number>
...............................................................................
UniquePtr.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( ptr2 )
with expansion:
!{?}
UniquePtr.tests.cpp:<line number>: PASSED:
REQUIRE( ptr1 )
with expansion:
{?}
UniquePtr.tests.cpp:<line number>: PASSED:
REQUIRE( *ptr1 == 2 )
with expansion:
2 == 2
-------------------------------------------------------------------------------
unique_ptr reimplementation: basic functionality
free swap
-------------------------------------------------------------------------------
UniquePtr.tests.cpp:<line number>
...............................................................................
UniquePtr.tests.cpp:<line number>: PASSED:
REQUIRE( *ptr1 == 2 )
with expansion:
2 == 2
UniquePtr.tests.cpp:<line number>: PASSED:
REQUIRE( *ptr2 == 1 )
with expansion:
1 == 1
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
-------------------------------------------------------------------------------
vec<vec<string,alloc>> -> toString
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
ToStringVector.tests.cpp:<line number>
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringVector.tests.cpp:<line number>: PASSED:
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
REQUIRE( ::Catch::Detail::stringify(v) == "{ }" )
with expansion:
"{ }" == "{ }"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringVector.tests.cpp:<line number>: PASSED:
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
REQUIRE( ::Catch::Detail::stringify(v) == "{ { \"hello\" }, { \"world\" } }" )
with expansion:
"{ { "hello" }, { "world" } }"
==
"{ { "hello" }, { "world" } }"
Fix stringifying of unknown enums
2018-01-04 11:21:52 +01:00
-------------------------------------------------------------------------------
vector<bool> -> toString
-------------------------------------------------------------------------------
ToStringVector.tests.cpp:<line number>
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringVector.tests.cpp:<line number>: PASSED:
Fix stringifying of unknown enums
2018-01-04 11:21:52 +01:00
REQUIRE( ::Catch::Detail::stringify(bools) == "{ }" )
with expansion:
"{ }" == "{ }"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringVector.tests.cpp:<line number>: PASSED:
Fix stringifying of unknown enums
2018-01-04 11:21:52 +01:00
REQUIRE( ::Catch::Detail::stringify(bools) == "{ true }" )
with expansion:
"{ true }" == "{ true }"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringVector.tests.cpp:<line number>: PASSED:
Fix stringifying of unknown enums
2018-01-04 11:21:52 +01:00
REQUIRE( ::Catch::Detail::stringify(bools) == "{ true, false }" )
with expansion:
"{ true, false }" == "{ true, false }"
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
-------------------------------------------------------------------------------
vector<int,allocator> -> toString
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
ToStringVector.tests.cpp:<line number>
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringVector.tests.cpp:<line number>: PASSED:
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
REQUIRE( ::Catch::Detail::stringify(vv) == "{ }" )
with expansion:
"{ }" == "{ }"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringVector.tests.cpp:<line number>: PASSED:
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
REQUIRE( ::Catch::Detail::stringify(vv) == "{ 42 }" )
with expansion:
"{ 42 }" == "{ 42 }"
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringVector.tests.cpp:<line number>: PASSED:
Enabled c++11 tests in approvals
2017-07-13 09:52:51 +02:00
REQUIRE( ::Catch::Detail::stringify(vv) == "{ 42, 250 }" )
with expansion:
"{ 42, 250 }" == "{ 42, 250 }"
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
-------------------------------------------------------------------------------
vector<int> -> toString
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
ToStringVector.tests.cpp:<line number>
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringVector.tests.cpp:<line number>: PASSED:
Reworked stringification layer, removed Catch::toString Now the order of stringification checks is 1) StringMaker specialization 2) operator<< toString overloads and specializations have been removed.
2017-05-02 23:51:03 +02:00
REQUIRE( ::Catch::Detail::stringify(vv) == "{ }" )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
"{ }" == "{ }"
Approved tag alias tests
2014-06-30 08:34:27 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringVector.tests.cpp:<line number>: PASSED:
Reworked stringification layer, removed Catch::toString Now the order of stringification checks is 1) StringMaker specialization 2) operator<< toString overloads and specializations have been removed.
2017-05-02 23:51:03 +02:00
REQUIRE( ::Catch::Detail::stringify(vv) == "{ 42 }" )
Approved tag alias tests
2014-06-30 08:34:27 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"{ 42 }" == "{ 42 }"
Approved tag alias tests
2014-06-30 08:34:27 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringVector.tests.cpp:<line number>: PASSED:
Reworked stringification layer, removed Catch::toString Now the order of stringification checks is 1) StringMaker specialization 2) operator<< toString overloads and specializations have been removed.
2017-05-02 23:51:03 +02:00
REQUIRE( ::Catch::Detail::stringify(vv) == "{ 42, 250 }" )
Approved tag alias tests
2014-06-30 08:34:27 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
"{ 42, 250 }" == "{ 42, 250 }"
Approved tag alias tests
2014-06-30 08:34:27 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
vector<string> -> toString
Approved tag alias tests
2014-06-30 08:34:27 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
ToStringVector.tests.cpp:<line number>
Approved tag alias tests
2014-06-30 08:34:27 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringVector.tests.cpp:<line number>: PASSED:
Reworked stringification layer, removed Catch::toString Now the order of stringification checks is 1) StringMaker specialization 2) operator<< toString overloads and specializations have been removed.
2017-05-02 23:51:03 +02:00
REQUIRE( ::Catch::Detail::stringify(vv) == "{ }" )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
"{ }" == "{ }"
Approved tag alias tests
2014-06-30 08:34:27 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringVector.tests.cpp:<line number>: PASSED:
Reworked stringification layer, removed Catch::toString Now the order of stringification checks is 1) StringMaker specialization 2) operator<< toString overloads and specializations have been removed.
2017-05-02 23:51:03 +02:00
REQUIRE( ::Catch::Detail::stringify(vv) == "{ \"hello\" }" )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
"{ "hello" }" == "{ "hello" }"
Approved tag alias tests
2014-06-30 08:34:27 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
ToStringVector.tests.cpp:<line number>: PASSED:
Reworked stringification layer, removed Catch::toString Now the order of stringification checks is 1) StringMaker specialization 2) operator<< toString overloads and specializations have been removed.
2017-05-02 23:51:03 +02:00
REQUIRE( ::Catch::Detail::stringify(vv) == "{ \"hello\", \"world\" }" )
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
with expansion:
"{ "hello", "world" }"
==
"{ "hello", "world" }"
Approved tag alias tests
2014-06-30 08:34:27 +02:00
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
vectors can be sized and resized
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( v.size() == 5 )
with expansion:
5 == 5
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( v.capacity() >= 5 )
with expansion:
5 >= 5
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
vectors can be sized and resized
resizing bigger changes size and capacity
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( v.size() == 10 )
with expansion:
10 == 10
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( v.capacity() >= 10 )
with expansion:
10 >= 10
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
vectors can be sized and resized
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( v.size() == 5 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
5 == 5
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( v.capacity() >= 5 )
with expansion:
5 >= 5
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
vectors can be sized and resized
resizing smaller changes size but not capacity
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( v.size() == 0 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
0 == 0
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( v.capacity() >= 5 )
with expansion:
5 >= 5
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
vectors can be sized and resized
resizing smaller changes size but not capacity
We can use the 'swap trick' to reset the capacity
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( v.capacity() == 0 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
0 == 0
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
vectors can be sized and resized
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( v.size() == 5 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
5 == 5
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( v.capacity() >= 5 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
5 >= 5
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
vectors can be sized and resized
reserving bigger changes capacity but not size
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
REQUIRE( v.size() == 5 )
with expansion:
5 == 5
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
REQUIRE( v.capacity() >= 10 )
with expansion:
10 >= 10
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
vectors can be sized and resized
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( v.size() == 5 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
5 == 5
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( v.capacity() >= 5 )
with expansion:
5 >= 5
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
vectors can be sized and resized
reserving smaller does not change size or capacity
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( v.size() == 5 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
5 == 5
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
REQUIRE( v.capacity() >= 5 )
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
with expansion:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
5 >= 5
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Remove CATCH_CONFIG_ENABLE_BENCHMARKING compilation toggle Now that Catch2 is a proper library, we can always build the full library (comparatively minor slowdown) and the user can avoid including benchmarking headers to avoid the compilation slowdown.
2020-02-03 18:08:15 +01:00
-------------------------------------------------------------------------------
warmup
-------------------------------------------------------------------------------
InternalBenchmark.tests.cpp:<line number>
...............................................................................
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( (iterations * rate) > Catch::Benchmark::Detail::warmup_time.count() )
with expansion:
160000000 (0x<hex digits>) > 100
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( (end - start) > Catch::Benchmark::Detail::warmup_time )
with expansion:
310016000 ns > 100 ms
-------------------------------------------------------------------------------
weighted_average_quantile
-------------------------------------------------------------------------------
InternalBenchmark.tests.cpp:<line number>
...............................................................................
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( q1 == 14.5 )
with expansion:
14.5 == 14.5
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( med == 18. )
with expansion:
18.0 == 18.0
InternalBenchmark.tests.cpp:<line number>: PASSED:
REQUIRE( q3 == 23. )
with expansion:
23.0 == 23.0
Added approvals for new tests
2014-08-20 09:08:13 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
xmlentitycheck
Deprecated description in SECTION (still accepts it, for now, but doesn't use it anywhere)
2018-06-25 20:04:29 +02:00
embedded xml: <test>it should be possible to embed xml characters, such as <,
Update Clara to v1.1.5 to fix TextFlow bugs
2018-10-26 18:48:28 +02:00
" or &, or even whole <xml>documents</xml> within an attribute
Deprecated description in SECTION (still accepts it, for now, but doesn't use it anywhere)
2018-06-25 20:04:29 +02:00
</test>
Added approvals for new tests
2014-08-20 09:08:13 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Added approvals for new tests
2014-08-20 09:08:13 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Added approvals for new tests
2014-08-20 09:08:13 +02:00
-------------------------------------------------------------------------------
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
xmlentitycheck
Deprecated description in SECTION (still accepts it, for now, but doesn't use it anywhere)
2018-06-25 20:04:29 +02:00
encoded chars: these should all be encoded: &&&"""<<<&"<<&"
Added approvals for new tests
2014-08-20 09:08:13 +02:00
-------------------------------------------------------------------------------
All tests files have .tests.cpp suffix. Also moved tests out of TestMain.cpp and moved up a level
2017-11-13 17:03:27 +01:00
Misc.tests.cpp:<line number>
Added approvals for new tests
2014-08-20 09:08:13 +02:00
...............................................................................
ConsoleReporter: minor formatting fix PASSED will now appear on the same line as filename and line number, just like the case with FAILED message formatting
2018-11-04 20:31:49 +01:00
Misc.tests.cpp:<line number>: PASSED:
Added approvals for new tests
2014-08-20 09:08:13 +02:00
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
===============================================================================
Fix bug in TokenStream parser When presented with just '-' it would access the string at position [1]
2024-09-05 23:06:32 +02:00
test cases: 419 | 313 passed | 86 failed | 6 skipped | 14 failed as expected
Provide overloads for {Unordered}RangeEquals taking a std::initializer_list This allows writing something like const auto v = calculateSomeVectorOfInts(); CHECK_THAT(v, RangeEquals({1, 2, 3})); Fixes #2915.
2024-10-12 17:18:59 +02:00
assertions: 2269 | 2087 passed | 147 failed | 35 failed as expected
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Reference in New Issue Copy Permalink