3rd-party/catch2
1
0
Fork 0
mirror of https://github.com/catchorg/Catch2.git synced 2024-11-17 03:02:24 +01:00
Code Issues Packages Projects Releases Wiki Activity
33704524d8
catch2/tests/SelfTest/Baselines/console.swa4.approved.txt

1149 lines
36 KiB
Plaintext
Raw Normal View History

Hidden tests now require positive filter match to be selected This also required some refactoring of how the pattern matching works. This means that the concepts of include and exclude patterns are no longer unified, with exclusion patterns working as just negation of an inclusion patterns (which led to including hidden tags by default, as they did not match the exclusion), but rather both include and exclude patterns are handled separately. The new logic is that given a filter and a test case, the test case must match _all_ include patterns and _no_ exclude patterns to be included by the filter. Furthermore, if the test case is hidden, then the filter must have at least one include pattern for the test case to be used. Closes #1184
2019-06-22 20:26:03 +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
Split approve file into multiple files
2013-09-27 20:01:14 +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
-------------------------------------------------------------------------------
CmdLine.tests.cpp:<line number>
...............................................................................
CmdLine.tests.cpp:<line number>: PASSED:
REQUIRE( spec.matches(*fakeTestCase("spec . char")) )
with expansion:
true
CmdLine.tests.cpp:<line number>: PASSED:
REQUIRE( spec.matches(*fakeTestCase("spec , char")) )
with expansion:
true
CmdLine.tests.cpp:<line number>: PASSED:
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
-------------------------------------------------------------------------------
CmdLine.tests.cpp:<line number>
...............................................................................
CmdLine.tests.cpp:<line number>: PASSED:
REQUIRE( spec.matches(*fakeTestCase(R"(spec {a} char)")) )
with expansion:
true
CmdLine.tests.cpp:<line number>: PASSED:
REQUIRE( spec.matches(*fakeTestCase(R"(spec [a] char)")) )
with expansion:
true
CmdLine.tests.cpp:<line number>: PASSED:
REQUIRE_FALSE( spec.matches(*fakeTestCase("differs but has similar tag", "[a]")) )
with expansion:
!false
-------------------------------------------------------------------------------
#1912 -- test spec parser handles escaping
backslash in test name
-------------------------------------------------------------------------------
CmdLine.tests.cpp:<line number>
...............................................................................
CmdLine.tests.cpp:<line number>: PASSED:
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
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 1 generator
line:267: GENERATE(1, 2)
value: 1
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:
6 < 7
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 1 generator
line:267: GENERATE(1, 2)
value: 2
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 - GENERATEs can share a line
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( i != j )
with expansion:
1 != 3
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 2 generators
line:276: GENERATE(1, 2)
value: 1
line:276: GENERATE(3, 4)
value: 3
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 - GENERATEs can share a line
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( i != j )
with expansion:
1 != 4
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 2 generators
line:276: GENERATE(1, 2)
value: 1
line:276: GENERATE(3, 4)
value: 4
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 - GENERATEs can share a line
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( i != j )
with expansion:
2 != 3
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 2 generators
line:276: GENERATE(1, 2)
value: 2
line:276: GENERATE(3, 4)
value: 3
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 - GENERATEs can share a line
-------------------------------------------------------------------------------
Generators.tests.cpp:<line number>
...............................................................................
Generators.tests.cpp:<line number>: PASSED:
REQUIRE( i != j )
with expansion:
2 != 4
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 2 generators
line:276: GENERATE(1, 2)
value: 2
line:276: GENERATE(3, 4)
value: 4
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
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
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 1 generator
line:216: GENERATE(1, 2, 3)
value: 1
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
B
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
2
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 1 generator
line:216: GENERATE(1, 2, 3)
value: 2
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
B
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
3
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 1 generator
line:216: GENERATE(1, 2, 3)
value: 3
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 - 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
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 1 generator
line:252: GENERATE(2, 3)
value: 2
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 - Section followed by flat generate
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
3
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 1 generator
line:252: GENERATE(2, 3)
value: 3
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 - flat generate
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
1
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 1 generator
line:223: GENERATE(1, 2, 3)
value: 1
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 - flat generate
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
2
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 1 generator
line:223: GENERATE(1, 2, 3)
value: 2
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 - flat generate
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
3
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 1 generator
line:223: GENERATE(1, 2, 3)
value: 3
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 - mixed sections and generates
A
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 1 generator
line:235: GENERATE(1, 2)
value: 1
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
with message:
A
-------------------------------------------------------------------------------
#1938 - mixed sections and generates
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 2 generators
line:239: GENERATE(3, 4)
value: 3
line:243: GENERATE(5, 6)
value: 5
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
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:
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 2 generators
line:235: GENERATE(1, 2)
value: 1
line:239: GENERATE(3, 4)
value: 3
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
with message:
B
-------------------------------------------------------------------------------
#1938 - mixed sections and generates
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 1 generator
line:243: GENERATE(5, 6)
value: 6
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
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:
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 2 generators
line:235: GENERATE(1, 2)
value: 1
line:239: GENERATE(3, 4)
value: 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
with message:
B
-------------------------------------------------------------------------------
#1938 - mixed sections and generates
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 1 generator
line:243: GENERATE(5, 6)
value: 5
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
with messages:
i := 1
j := 4
k := 5
-------------------------------------------------------------------------------
#1938 - mixed sections and generates
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 3 generators
line:235: GENERATE(1, 2)
value: 1
line:239: GENERATE(3, 4)
value: 4
line:243: GENERATE(5, 6)
value: 6
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
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:
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 1 generator
line:235: GENERATE(1, 2)
value: 2
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
with message:
A
-------------------------------------------------------------------------------
#1938 - mixed sections and generates
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 2 generators
line:239: GENERATE(3, 4)
value: 3
line:243: GENERATE(5, 6)
value: 5
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
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:
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 2 generators
line:235: GENERATE(1, 2)
value: 2
line:239: GENERATE(3, 4)
value: 3
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
with message:
B
-------------------------------------------------------------------------------
#1938 - mixed sections and generates
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 1 generator
line:243: GENERATE(5, 6)
value: 6
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
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:
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 2 generators
line:235: GENERATE(1, 2)
value: 2
line:239: GENERATE(3, 4)
value: 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
with message:
B
-------------------------------------------------------------------------------
#1938 - mixed sections and generates
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 1 generator
line:243: GENERATE(5, 6)
value: 5
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
with messages:
i := 2
j := 4
k := 5
-------------------------------------------------------------------------------
#1938 - mixed sections and generates
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 3 generators
line:235: GENERATE(1, 2)
value: 2
line:239: GENERATE(3, 4)
value: 4
line:243: GENERATE(5, 6)
value: 6
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
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
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 2 generators
line:228: GENERATE(1, 2, 3)
value: 1
line:229: GENERATE(1, 2, 3)
value: 1
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
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( n )
with expansion:
1
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 2 generators
line:228: GENERATE(1, 2, 3)
value: 1
line:229: GENERATE(1, 2, 3)
value: 1
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 - nested generate
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
1
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 2 generators
line:228: GENERATE(1, 2, 3)
value: 1
line:229: GENERATE(1, 2, 3)
value: 2
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
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( n )
with expansion:
2
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 2 generators
line:228: GENERATE(1, 2, 3)
value: 1
line:229: GENERATE(1, 2, 3)
value: 2
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 - nested generate
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
1
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 2 generators
line:228: GENERATE(1, 2, 3)
value: 1
line:229: GENERATE(1, 2, 3)
value: 3
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
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( n )
with expansion:
3
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 2 generators
line:228: GENERATE(1, 2, 3)
value: 1
line:229: GENERATE(1, 2, 3)
value: 3
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 - nested generate
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
2
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 2 generators
line:228: GENERATE(1, 2, 3)
value: 2
line:229: GENERATE(1, 2, 3)
value: 1
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
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( n )
with expansion:
1
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 2 generators
line:228: GENERATE(1, 2, 3)
value: 2
line:229: GENERATE(1, 2, 3)
value: 1
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 - nested generate
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
2
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 2 generators
line:228: GENERATE(1, 2, 3)
value: 2
line:229: GENERATE(1, 2, 3)
value: 2
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
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( n )
with expansion:
2
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 2 generators
line:228: GENERATE(1, 2, 3)
value: 2
line:229: GENERATE(1, 2, 3)
value: 2
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 - nested generate
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
2
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 2 generators
line:228: GENERATE(1, 2, 3)
value: 2
line:229: GENERATE(1, 2, 3)
value: 3
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
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( n )
with expansion:
3
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 2 generators
line:228: GENERATE(1, 2, 3)
value: 2
line:229: GENERATE(1, 2, 3)
value: 3
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 - nested generate
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
3
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 2 generators
line:228: GENERATE(1, 2, 3)
value: 3
line:229: GENERATE(1, 2, 3)
value: 1
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
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( n )
with expansion:
1
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 2 generators
line:228: GENERATE(1, 2, 3)
value: 3
line:229: GENERATE(1, 2, 3)
value: 1
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 - nested generate
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
3
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 2 generators
line:228: GENERATE(1, 2, 3)
value: 3
line:229: GENERATE(1, 2, 3)
value: 2
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
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( n )
with expansion:
2
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 2 generators
line:228: GENERATE(1, 2, 3)
value: 3
line:229: GENERATE(1, 2, 3)
value: 2
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 - nested generate
-------------------------------------------------------------------------------
PartTracker.tests.cpp:<line number>
...............................................................................
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( m )
with expansion:
3
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 2 generators
line:228: GENERATE(1, 2, 3)
value: 3
line:229: GENERATE(1, 2, 3)
value: 3
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
PartTracker.tests.cpp:<line number>: PASSED:
REQUIRE( n )
with expansion:
3
Report generator states for failed assertions
2022-08-27 16:40:41 +02:00
with 2 generators
line:228: GENERATE(1, 2, 3)
value: 3
line:229: GENERATE(1, 2, 3)
value: 3
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
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])
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
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( 42 == f )
with expansion:
42 == {?}
-------------------------------------------------------------------------------
#833
-------------------------------------------------------------------------------
All tests files 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( 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
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
'Not' 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( false != 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
Condition.tests.cpp:<line number>: FAILED:
Sort test ordering during Approval testing
2016-11-29 12:32:16 +01:00
CHECK( true != true )
Added [!mayfail] tag to indicate test case that can fail without failing the suite. Overhauled the summary report (including the expected failure count)
2014-07-03 09:09:57 +02: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
test cases: 32 | 27 passed | 3 failed | 2 failed as expected
assertions: 101 | 94 passed | 4 failed | 3 failed as expected
Split approve file into multiple files
2013-09-27 20:01:14 +02:00
Reference in New Issue Copy Permalink