- 05 Jul, 2019 1 commit
-
-
We use the `__LINE__` macro in several places throughout clar to allow easier traceability when e.g. a test fails. While `__LINE__` is of type `size_t`, the clar functions all accept an integer and thus may loose precision. While unlikely that any file in our codebase will exceed a linecount of `INT_MAX`, let's convert it anyway to silence any compiler warnings.
Patrick Steinhardt committed
-
- 06 Sep, 2018 1 commit
-
-
This makes it possible to keep track of every test status (even successful ones), and their errors, if any.
Etienne Samson committed
-
- 13 Nov, 2017 1 commit
-
-
motivation: (for someone new to the tests) it's puzzling to find the odd 'S' interspersed in the test output proposed alternative test output (extract): $ cmake --build . && ./libgit2_clar -srepo -v ... Loaded 340 suites: Started (test status codes: OK='.' FAILURE='F' SKIPPED='S') repo::config... repo::discover.......... repo::env. repo::getters... repo::hashfile.. repo::head...................... repo::headtree.... repo::init.........................S repo::message.. repo::new.. repo::open............. repo::pathspec.......... repo::reservedname..... repo::setters..... repo::shallow.... repo::state.............
Christine Poerschke committed
-
- 02 Apr, 2014 1 commit
-
-
Vicent Marti committed
-
- 14 Nov, 2013 1 commit
-
-
Ben Straub committed
-
- 21 Jan, 2013 1 commit
-
-
Russell Belfer committed
-
- 03 Jan, 2013 3 commits
-
-
Vicent Marti committed
-
Vicent Marti committed
-
Vicent Marti committed
-
- 02 Jan, 2013 4 commits
-
-
Vicent Marti committed
-
Vicent Marti committed
-
Vicent Marti committed
-
Vicent Marti committed
-