We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If I run executable like <binary> -d yes -o temp I get a file looking like this
<binary> -d yes -o temp
Successful tests -- REQUIRE completed in 3.9219s Successful tests -- CHECK completed in 4.2232s ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Benchmark.exe is a Catch v1.6.0 host application. Run with -? for options ------------------------------------------------------------------------------- Unsuccessful tests -- CHECK ------------------------------------------------------------------------------- C:\Users\Xarn\Documents\GitHub\Catch\projects\Benchmark\StringificationBench.cpp(30) ............................................................................... C:\Users\Xarn\Documents\GitHub\Catch\projects\Benchmark\StringificationBench.cpp(37): FAILED: <shortened> Completed in 0.136898s =============================================================================== test cases: 3 | 2 passed | 1 failed assertions: 2098176 | 2097152 passed | 1024 failed
Notice the test case timing information.
If I run the same binary like <binary> -d yes -r compact -o temp2, then the output is like this
<binary> -d yes -r compact -o temp2
C:\Users\Xarn\Documents\GitHub\Catch\projects\Benchmark\StringificationBench.cpp(37): failed: vec.size() == i for: 1 == 0 C:\Users\Xarn\Documents\GitHub\Catch\projects\Benchmark\StringificationBench.cpp(37): failed: vec.size() == i for: 2 == 1 C:\Users\Xarn\Documents\GitHub\Catch\projects\Benchmark\StringificationBench.cpp(37): failed: vec.size() == i for: 3 == 2 <shortened> Failed 1 test case, failed 1024 assertions.
Notice no test case timing information.
Also the output for default reporter is weird, I'd expect the "Benchmark.exe is a Catch..." banner to come before timing information.
The text was updated successfully, but these errors were encountered:
40f6a5b
No branches or pull requests
If I run executable like
<binary> -d yes -o temp
I get a file looking like thisNotice the test case timing information.
If I run the same binary like
<binary> -d yes -r compact -o temp2
, then the output is like thisNotice no test case timing information.
Also the output for default reporter is weird, I'd expect the "Benchmark.exe is a Catch..." banner to come before timing information.
The text was updated successfully, but these errors were encountered: