Gitiles
Code Review
Sign In
gerrit.cesnet.cz
/
github
/
onqtam
/
doctest
/
5bf36c0fc275b672e2cc33b7ccc0e980b6670c78
5bf36c0
changelog for 2.2.0
by onqtam
· 6 years ago
2.2.0
72ca33b
version 2.2
by onqtam
· 6 years ago
24e4879
updated docs
by onqtam
· 6 years ago
819f72a
windows benchmarks
by onqtam
· 6 years ago
3b26089
linux benchmarks for doctest asserts updated
by onqtam
· 6 years ago
349a7f0
moved the benchmarking scripts to the new assert types
by onqtam
· 6 years ago
348b109
small docs fixes and preparations for the benchmarking to be done tomorrow
by onqtam
· 6 years ago
c494843
fixes #166 and fixes #167 - TODO: update benchmarks page
by onqtam
· 6 years ago
abb864e
changelog for 2.1.0
by onqtam
· 6 years ago
2.1.0
2d97b85
version 2.1
by onqtam
· 6 years ago
21dcb41
small fixes after merging #158
by onqtam
· 6 years ago
a420d8c
Make it possible to change the command line options prefix (#158)
by Thomas Bleher
· 6 years ago
4af24f8
fixed #151
by onqtam
· 6 years ago
efa6102
no more shadowing of size() with param size - fixes warning on CI
by onqtam
· 6 years ago
8cf9041
users can now pass both just the exception type and a const(+ref) version of it to the <LEVEL>_THROWS_AS macros and it means the same - const and & are always removed (if present) and then added
by onqtam
· 6 years ago
0e6236a
added support for CHECK_THROWS_WITH macro - currently accepts only a C string but in the future will be extended for matchers support - fixes #97
by onqtam
· 6 years ago
62c5f32
fixed another broken link
by onqtam
· 6 years ago
2520377
small docs fixes
by onqtam
· 6 years ago
55d9f05
fixed #165
by onqtam
· 6 years ago
835a0fa
small fixes in the docs
by onqtam
· 6 years ago
95bd26d
removed unnecessary init code for struct sigaction
by onqtam
· 6 years ago
c544f9c
fixes after merging #162 - fixes #163
by onqtam
· 6 years ago
bd347ec
Fixed build error under Android NDK (#162)
by Tal Sh
· 6 years ago
1527482
Added clang-7 to travis build (#161)
by AMS21
· 6 years ago
288e34f
Merge pull request #159 from rantasub/StaticNoLint
by Viktor Kirilov
· 6 years ago
218c9c7
Silent clang-tidy warnings for static fields
by Stephan Fackler
· 6 years ago
f4e82db
changelog for 2.0.1
by onqtam
· 6 years ago
2.0.1
8360550
Merge branch 'dev'
by onqtam
· 6 years ago
9639cee
version 2.0.1
by onqtam
· 6 years ago
dc01198
fixed issue #149
by onqtam
· 6 years ago
af39bae
Correct format string for unsigned char (#154)
by Thomas Bleher
· 6 years ago
04f3798
Correctly document when a main() entry point will be created (#155)
by Thomas Bleher
· 6 years ago
f3843c4
fixed ussue #147
by onqtam
· 6 years ago
1204486
added reporters link in reference sections
by onqtam
· 6 years ago
cb6a29f
minor stuff
by onqtam
· 6 years ago
bba24e8
changelog for version 2.0.0
by onqtam
· 6 years ago
2.0.0
c734f30
sloppy documentation of the current state of the reporter interface.
by onqtam
· 6 years ago
f8d5719
version 2.0.0
by onqtam
· 6 years ago
2865aa0
small docs fixes
by onqtam
· 6 years ago
8954085
using the .svg files for the logo/icon (and also moved and renamed them) - relates #141 and #145
by onqtam
· 6 years ago
80718be
small docs update
by onqtam
· 6 years ago
a9f53e7
Update README.md
by area55
· 6 years ago
1172609
Add files via upload
by area55
· 6 years ago
25277bb
finally resolved issue #126 and #143 "properly" - turns out the problem is this: when using clang from xcode - that means libc++. in that case I include <iosfwd> instead of forward-declaring std::ostream myself. Then if the user includes somewhere only the doctest header and <string> and then does a comparison - then and only then will there be some linker issue which I previously had managed to resolve by telling the users to also include <iostream> in that place in their tests. This is a toolchain issue when using the <iosfwd> header - the details are still not clear to me but I managed to get the linker to pull in what is necessary by adding a dummy unused global function in the implementation of doctest that uses operator<< of std::string to print to std::cout.
by onqtam
· 6 years ago
d221656
removed the last traces of gcc on osx in travis CI
by onqtam
· 6 years ago
cec8faa
updated numbers for benchmarks
by onqtam
· 6 years ago
169d4c8
updated charts for benchmarks
by onqtam
· 6 years ago
4d6c853
latest benchmark numbers from linux
by onqtam
· 6 years ago
24bd962
benchmarks under windows redone for doctest/catch
by onqtam
· 6 years ago
4ab5e6b
fixed #143 for real - found the reason for the errors related to the REQUIRE macro not being defined - was disabling exceptions in the feature detection after clang/msvc became non-mutually exclusive. Also detecting if exceptions are disabled for MSVC properly - relates to 44
by onqtam
· 6 years ago
b62ecf4
reworked warning suppression macros in order to properly support clang-cl - relates #143
by onqtam
· 6 years ago
8f10044
clang builds should finally be passing now!
by onqtam
· 6 years ago
8aecdee
oh come on! clang builds - warnings...
by onqtam
· 6 years ago
65cf692
builds should pass now...
by onqtam
· 6 years ago
d9340f5
updates to documentation - relates #4
by onqtam
· 6 years ago
a2e77c7
implemented a full example of using doctest in a threaded environment - relates to #4
by onqtam
· 6 years ago
1f2750f
documented the thread safety features of doctest - relates #4
by onqtam
· 6 years ago
2d48a31
my previous commit was wrong - the actual problem was that I was supplying -ltsan to all sanitizers - not just tsan - so that is why asan builds were failing
by onqtam
· 6 years ago
a4d2069
changed order of flags - since that is the only change since the gcc 5-8 tsan builds started failing...
by onqtam
· 6 years ago
3c549c9
disabled thread sanitizer for a few clang versions - see these builds: https://travis-ci.org/onqtam/doctest/builds/417926743
by onqtam
· 6 years ago
7a72f31
So I just asked myself: "why...? why are you doing this to yourself? where is the self love" - and now I remove all CI builds on travis with GCC installed with homebrew on Mac OS - life should be a bit better now. Not sure why I did those initially and why it took me 2+ years to figure out that they bring 0 value. Letting go is hard. Only XCode/clang builds on Mac OS from now on.
by onqtam
· 6 years ago
d9d22d7
removed a no-longer needed include guard and also removing the -ltsan and gold linker for clang on linux for the thread sanitizer - lets see...
by onqtam
· 6 years ago
b4297f4
fixed #143 for real - had to separate the windows/clang compiler detection since they are not mutually exclusive because of clang-cl... (+ suppressed a clang warning about strtok)
by onqtam
· 6 years ago
009691a
set the linker to gold for the rest of the GCC sanitizer builds (also clang - even though there I get a segmentation fault and not a linking error) and moved the -ltsan linking flag from all sanitizer builds to only linux builds to fix OSX
by onqtam
· 6 years ago
4391967
trying again the thread sanitizers...
by onqtam
· 6 years ago
f150276
added the gold linker for the sanitizers where needed... I guess that's when a newer than the default GCC is used but ld is not the latest so we need gold
by onqtam
· 6 years ago
1ee2d2b
lets see if we need the gold linker still for the sanitizers... since these are the only 4 builds that just failed on the CI (god I hate this part of the project development)
by onqtam
· 6 years ago
e58aa53
removed last reference to 32/64 bitness
by onqtam
· 6 years ago
558afbb
re-enabled some ASAN options which were problematic a few years ago with old GCC versions (patched since)
by onqtam
· 6 years ago
589fd21
removed 32 bit mode builds from travis CI - its about time I simplify my life and make builds faster... 32 bit mode is still checked with VS 2015 and 2017 on appveyor!
by onqtam
· 6 years ago
dd40fa9
moved the -std=c++0x flag in a single place
by onqtam
· 6 years ago
2cd4f08
made the travis config a bit better
by onqtam
· 6 years ago
531e9ca
suppressing warnings for deprecated declarations such as isatty and fileno when using clang-cl - closes #143
by onqtam
· 6 years ago
ae08840
adding -ltsan and also proper TSAN_OPTIONS - relates #4 - lets see if atleast some builds pass... :(
by onqtam
· 6 years ago
7b7bb8a
windows builds with mingw should pass now
by onqtam
· 6 years ago
258aff5
linking the executables for the thread sanitizer as potision independent
by onqtam
· 6 years ago
7b7d161
should link properly on linux/osx
by onqtam
· 6 years ago
5017768
added thread sanitizer tests - relates #4
by onqtam
· 6 years ago
ce1b204
bumping the osx image for gcc 6/7/8 from a no-longer supported xcode 9.3 to the latest
by onqtam
· 6 years ago
25fff35
removing asan 64 for osx images with xcode older than 10 - see this build: https://travis-ci.org/onqtam/doctest/builds/417181981
by onqtam
· 6 years ago
10c2018
removing support for xcode 6 and 7 - only 8+ is supported due to the support for thread_local - relates #4 - see this: https://stackoverflow.com/questions/28094794/why-does-apple-clang-disallow-c11-thread-local-when-official-clang-supports
by onqtam
· 6 years ago
c9b4e1f
added an example with concurrent threads doing assertions - relates #4 (currently ctest fails on it...)
by onqtam
· 6 years ago
4ca0078
last bit of thread-synchronization done (for the debug output window reporter for windows when attached to a VS debugger) - relates #4
by onqtam
· 6 years ago
2151e3c
removed support for GCC 4.7 and VS 2013 ... they have extensions for thread local storage (__thread and __declspec(thread) respectively) but it works only for POD types... relates #4
by onqtam
· 6 years ago
224e167
all CI builds (VS 2013, GCC 4.7) should pass now! Also the other VS builds should pass - doing a normal ostringstream resetting... relates $4
by onqtam
· 6 years ago
f03cfd9
made all logging macros thread-safe (and also optimized stringification - no need to allocate streams anymore - reusing a single one) - relates #4
by onqtam
· 6 years ago
09fd51d
added xcode10 osx image - https://blog.travis-ci.com/2018-08-16-xcode-10-beta-is-now-available
by onqtam
· 6 years ago
7c606ea
updating osx build matrix according to this: https://blog.travis-ci.com/2018-07-19-xcode9-4-default-announce
by onqtam
· 6 years ago
8bf6dc6
support for VS 15.8
by onqtam
· 6 years ago
b170581
docs... non-interesting change
by onqtam
· 6 years ago
81d496f
calling asserts from different threads spawned from within a single test case is now safe! using the SUBCASE macro in multiple threads will remain a big NO. TODO: logging macros such as INFO() and CAPTURE()... relates #4 and also PR #117 which was a good starting point for this!
by onqtam
· 6 years ago
758d092
the last 0 as null usages are gone
by onqtam
· 6 years ago
4d87d56
moved to nullptr, removed c++98-compat warning suppressions for clang (also long-long and 0 as null for gcc/clang)
by onqtam
· 6 years ago
eac6787
tiny changes
by onqtam
· 6 years ago
25bfda9
hopefully fixing builds...
by onqtam
· 6 years ago
917d79d
fixing builds... relates #114
by onqtam
· 6 years ago
8171c48
polished the feature for allowing the use of asserts outside of a testing context (also example and docs) - relates #114
by onqtam
· 6 years ago
6b05c20
disabling output comparison for the playground project
by onqtam
· 6 years ago
1d68a13
- added the ability to call asserts outside of a testing context without recompiling! currently the fast asserts are optimized for runtime speed to the maximum but the other asserts are not. Sadly logging macros - like INFO() - aren't supported... yet! - closes #114 - the way to do it is to call setAsDefaultForAssertsOutOfTestCases() on a doctest::Context and optionally to register a custom handler with doctest::Context::setAssertHandler()
by onqtam
· 6 years ago
6439abc
clearing some flags after each call to the test_case_end function when reentering for subcases
by onqtam
· 6 years ago
Next »