catch3/projects/SelfTest/IntrospectiveTests, branch v2.10.1 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. Have the random generators use the global rng instance 2019-10-07T19:53:07+00:00 Martin Hořeňovský 2019-10-07T18:24:37+00:00 a5a22cdadb0e0573de7dc2547165736349439298 This means that if you nest multiple random generators inside one test case, they will not return the same sequence of numbers. Idea taken from #1736 by Amit Herman. Closes #1736 Closes #1734 
This means that if you nest multiple random generators inside one
test case, they will not return the same sequence of numbers.

Idea taken from #1736 by Amit Herman.

Closes #1736
Closes #1734
Introduce Catch's own RNG based on the PCG family of RNGs 2019-10-07T17:56:23+00:00 Martin Hořeňovský 2019-10-06T19:47:54+00:00 535da5c5132bcbba6f29c60ed6bb7ded29b9ec3e 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. 
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.
Add tests for escaping special characters in CLI 2019-09-20T22:50:17+00:00 Martin Hořeňovský 2019-09-20T22:11:45+00:00 fc2066bf18e4f20cc1609d1083adcfe3764866af 






Ignore leading/trailing whitespace in test/section specs
2019-09-09T12:28:11+00:00

Martin Hořeňovský

2019-09-09T09:30:45+00:00

af8b2538a62db34b3cec10ceb74e3d29bd06e37f

The leading/trailing whitespace is problematic because of e.g.
`WHEN` macro having preceeding whitespace for alignment, and it is
generally messy.

Credits to Phil who did lot of the original work.

Closes #1708





The leading/trailing whitespace is problematic because of e.g.
`WHEN` macro having preceeding whitespace for alignment, and it is
generally messy.

Credits to Phil who did lot of the original work.

Closes #1708







Add test for past-the-end substr on StringRef
2019-09-08T19:07:21+00:00

Martin Hořeňovský

2019-09-08T19:04:23+00:00

dab0296b64483034d7b802a0635fae840ba31727












Make StringRef's operator std::string explicit
2019-09-08T13:58:10+00:00

Martin Hořeňovský

2019-09-08T12:49:40+00:00

7b865daccc7bba2dcc25a4f0b9ea7348b1b4d61f

This way it is explicit when there is a `StringRef` -> `std::string`
conversion and makes it easier to look for allocations that could
be avoided.

Doing this has already removed one allocation per registered test
case, as there was a completely pointless `StringRef` -> `std::string`
conversion when parsing tags of a test case.





This way it is explicit when there is a `StringRef` -> `std::string`
conversion and makes it easier to look for allocations that could
be avoided.

Doing this has already removed one allocation per registered test
case, as there was a completely pointless `StringRef` -> `std::string`
conversion when parsing tags of a test case.







Use StringRefs through the enum registration
2019-09-08T12:14:46+00:00

Martin Hořeňovský

2019-09-08T12:07:18+00:00

923db163228b2eb0d8acdf970c2a285e9c6e7983












Split out the rest of string manipulation tests
2019-09-07T18:22:36+00:00

Martin Hořeňovský

2019-09-07T18:22:36+00:00

6da00c1b64b0826bdc735805a65c7dd2147fdf2b












Remove the ill-considered StringRef::numberOfCharacters
2019-09-07T18:13:22+00:00

Martin Hořeňovský

2019-09-07T18:13:22+00:00

fe967b1f4122a67ae1b31febf26cf1751917a0eb

It never counted characters, only codepoints. If you think these
are interchangeable, you should not touch non-ascii text.





It never counted characters, only codepoints. If you think these
are interchangeable, you should not touch non-ascii text.







Add trim for StringRef
2019-09-07T09:31:00+00:00

Martin Hořeňovský

2019-09-07T09:31:00+00:00

f2c2711bdcc583938e444f2039b9ceba840defcf