version 1.2.9
diff --git a/README.md b/README.md
index 7efd57c..5c02b49 100644
--- a/README.md
+++ b/README.md
@@ -82,7 +82,7 @@
[](https://raw.githubusercontent.com/onqtam/doctest/master/doctest/doctest.h)
[](https://bestpractices.coreinfrastructure.org/projects/503)
[](https://gitter.im/onqtam/doctest?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
-[](https://wandbox.org/permlink/cuvJ2XfsChtgIYyk)
+[](https://wandbox.org/permlink/oD4eD9NgDDs7qO0d)
<!--
[](https://isocpp.org/)
[](https://github.com/onqtam/doctest/blob/master/doc/markdown/readme.md#reference)
diff --git a/doc/html_generated/commandline.html b/doc/html_generated/commandline.html
index cc15cd0..82715b5 100644
--- a/doc/html_generated/commandline.html
+++ b/doc/html_generated/commandline.html
@@ -53,6 +53,7 @@
| ```-fc``` ```--force-colors=<bool>``` | Forces the use of colors even when a tty cannot be detected |
| ```-nb``` ```--no-breaks=<bool>``` | Disables breakpoints in debuggers when an assertion fails |
| ```-ns``` ```--no-skip=<bool>``` | Don't skip test cases marked as skip with a decorator |
+| ```-gfl``` ```--gnu-file-line=<bool>``` | ```:n:``` vs ```(n):``` for line numbers in output (gnu mode is usually for linux tools/IDEs and is with the ```:``` separator) |
| ```-npf``` ```--no-path-filenames=<bool>``` | Paths are removed from the output when a filename is printed - useful if you want the same output from the testing framework on different environments |
| ```-nln``` ```--no-line-numbers=<bool>``` | Line numbers are replaced with ```0``` in the output when a source location is printed - useful if you want the same output from the testing framework even when test positions change within a source file |
| | |
diff --git a/doc/html_generated/features.html b/doc/html_generated/features.html
index aa74ca7..456d4a5 100644
--- a/doc/html_generated/features.html
+++ b/doc/html_generated/features.html
@@ -27,8 +27,8 @@
## Extremely portable:
- Standards compliant **C++98** code - should work with any **C++98** compiler
-- tested with **GCC**: **4.4**, **4.5**, **4.6**, **4.7**, **4.8**, **4.9**, **5**, **6**, **7**
-- tested with **Clang**: **3.5**, **3.6**, **3.7**, **3.8**, **3.9**, **4**, **5**
+- tested with **GCC**: **4.4**, **4.5**, **4.6**, **4.7**, **4.8**, **4.9**, **5**, **6**, **7**, **8**
+- tested with **Clang**: **3.5**, **3.6**, **3.7**, **3.8**, **3.9**, **4**, **5**, **6**
- tested with **MSVC**: **2008**, **2010**, **2012**, **2013**, **2015**, **2017**
- per-commit tested on **travis** and **appveyor** CI services
- warnings as errors even on the most aggressive warning levels - see [**here**](../../scripts/cmake/common.cmake#L84)
diff --git a/doc/html_generated/roadmap.html b/doc/html_generated/roadmap.html
index 6b00f87..853649b 100644
--- a/doc/html_generated/roadmap.html
+++ b/doc/html_generated/roadmap.html
@@ -14,23 +14,30 @@
### For 1.3:
-- move from printf to using streams in the current console reporter and clean that mess
- reporters
- output to file
- a system for writing custom reporters
- ability to use multiple reporters at once (but only 1 to stdout)
- a compact reporter
- a progress reporter - or maybe just an option for the console reporter
- - an xml reporter
+ - an xml reporter ([junit related stuff](https://github.com/ujiro99/doctest-junit-report))
- xUnit reporter
- a listener interface - similar to a reporter - look at Catch
- ability to have no output when everything succeeds
- option to output summary only
-- log levels - like in [boost test](http://www.boost.org/doc/libs/1_63_0/libs/test/doc/html/boost_test/utf_reference/rt_param_reference/log_level.html)
+- thread safety - asserts/subcases/captures should be safe to be used by multiple threads simultaneously
+ - https://github.com/blastrock/doctest/tree/threadsafe
- matchers - should investigate what they are - look at google test/mock and Catch (also predicates and boost test)
- convolution support for the assertion macros (with a predicate)
+
+### For 1.4:
+
- Value-Parameterized test cases
- generators? - look at Catch - and investigate what they are
+- look at property based testing
+ - [rapidcheck](https://github.com/emil-e/rapidcheck)
+ - [autocheck](https://github.com/thejohnfreeman/autocheck)
+ - [CppQuickCheck](https://github.com/grogers0/CppQuickCheck)
- proper conan package
- https://github.com/onqtam/doctest/issues/103
- https://github.com/bincrafters/conan-doctest
@@ -40,11 +47,6 @@
- https://github.com/conan-io/docs/issues/67
- https://github.com/agauniyal/rang
- https://github.com/conan-io/conan/issues/324
-- look at property based testing
- - [rapidcheck](https://github.com/emil-e/rapidcheck)
- - [autocheck](https://github.com/thejohnfreeman/autocheck)
- - [CppQuickCheck](https://github.com/grogers0/CppQuickCheck)
-- support for LibIdentify
- IDE integration
- https://blogs.msdn.microsoft.com/vcblog/2017/05/10/unit-testing-and-the-future-announcing-the-test-adapter-for-google-test/
- https://www.reddit.com/r/cpp/comments/65c0f1/run_cpp_unit_tests_from_xcode_and_visual_studio/
@@ -61,8 +63,9 @@
- https://www.jetbrains.com/clion/features/unit-testing.html
- https://blog.jetbrains.com/clion/2017/03/clion-2017-1-released/#catch
-### For 1.4:
+### For 1.5:
+- log levels - like in [boost test](http://www.boost.org/doc/libs/1_63_0/libs/test/doc/html/boost_test/utf_reference/rt_param_reference/log_level.html)
- running tests a [few times](https://github.com/google/googletest/blob/master/googletest/docs/AdvancedGuide.html#repeating-the-tests)
- test execution in [separate processes](https://github.com/philsquared/Catch/issues/853) - ```fork()``` for UNIX and [this](https://github.com/nemequ/munit/issues/2) for Windows
- killing a test that exceeds a time limit (will perhaps require threading or processes)
@@ -100,19 +103,18 @@
### Things that are being considered but not part of the roadmap yet:
-- FakeIt mocking integration - like [catch](https://github.com/eranpeer/FakeIt/tree/master/config/catch)
+- FakeIt mocking integration - like [catch](https://github.com/eranpeer/FakeIt/tree/master/config/catch) (also checkout [this](https://github.com/ujiro99/doctest-sample))
- look into https://github.com/cpp-testing/GUnit - https://www.youtube.com/watch?v=NVrZjT5lW5o
- consider the following 2 properties for the MSVC static code analyzer: EnableCppCoreCheck, EnableExperimentalCppCoreCheck
- rpm package? like this: https://github.com/vietjtnguyen/argagg/blob/master/packaging/rpm/argagg.spec
- get the current test case/section path - https://github.com/philsquared/Catch/issues/522
-- when no assertion is encountered in a test case it should fail
+- when no assertion is encountered in a test case it should fail - and should also add a SUCCEED() call
- failure reporting should print out previous SECTIONs for data-driven testing - as requested [here](https://github.com/philsquared/Catch/issues/734)
- ```Bitwise()``` class that has overloaded operators for comparison - to be used to check objects bitwise against each other
- detect floating point exceptions
- checkpoint/passpoint - like in [boost test](http://www.boost.org/doc/libs/1_63_0/libs/test/doc/html/boost_test/test_output/test_tools_support_for_logging/checkpoints.html) (also make all assert/subcase/logging macros to act as passpoints and print the last one on crashes or exceptions)
- queries for the current test case - name (and probably decorators)
-- thread safety - asserts/subcases/captures should be safe to be used by multiple threads simultaneously
- - https://github.com/blastrock/doctest/tree/threadsafe
+- support for LibIdentify
- support for running tests in parallel in multiple threads
- death tests - as in [google test](https://github.com/google/googletest/blob/master/googletest/docs/AdvancedGuide.html#death-tests)
- config options
@@ -126,7 +128,7 @@
- option to list files in which there are test cases who match the current filters
- option for filters to switch from "match any" to "match all" mode
- option to list test suites and test cases in a tree view
- - add a "wait key" option - as requested [here](https://github.com/philsquared/Catch/issues/477#issuecomment-256417686)
+ - add a "wait key" option (before and after tests) - as requested [here](https://github.com/philsquared/Catch/issues/477#issuecomment-256417686)
- decorators for test cases and test suites- like in boost test
- depends_on
- precondition
diff --git a/doc/html_generated/stringification.html b/doc/html_generated/stringification.html
index 70c2846..b6392ef 100644
--- a/doc/html_generated/stringification.html
+++ b/doc/html_generated/stringification.html
@@ -8,6 +8,8 @@
**doctest** needs to be able to convert types you use in assertions and logging expressions into strings (for logging and reporting purposes).
Most built-in types are supported out of the box but there are three ways that you can tell **doctest** how to convert your own types (or other, third-party types) into strings.
+For stringifying enums checkout [this issue](https://github.com/onqtam/doctest/issues/121).
+
## ```operator<<``` overload for ```std::ostream```
This is the standard way of providing string conversions in C++ - and the chances are you may already provide this for your own purposes. If you're not familiar with this idiom it involves writing a free function of the form:
diff --git a/doc/markdown/features.md b/doc/markdown/features.md
index 3356ecb..0064437 100644
--- a/doc/markdown/features.md
+++ b/doc/markdown/features.md
@@ -22,8 +22,8 @@
## Extremely portable:
- Standards compliant **C++98** code - should work with any **C++98** compiler
-- tested with **GCC**: **4.4**, **4.5**, **4.6**, **4.7**, **4.8**, **4.9**, **5**, **6**, **7**
-- tested with **Clang**: **3.5**, **3.6**, **3.7**, **3.8**, **3.9**, **4**, **5**
+- tested with **GCC**: **4.4**, **4.5**, **4.6**, **4.7**, **4.8**, **4.9**, **5**, **6**, **7**, **8**
+- tested with **Clang**: **3.5**, **3.6**, **3.7**, **3.8**, **3.9**, **4**, **5**, **6**
- tested with **MSVC**: **2008**, **2010**, **2012**, **2013**, **2015**, **2017**
- per-commit tested on **travis** and **appveyor** CI services
- warnings as errors even on the most aggressive warning levels - see [**here**](../../scripts/cmake/common.cmake#L84)
diff --git a/doctest/doctest.h b/doctest/doctest.h
index 719e421..e160b7f 100644
--- a/doctest/doctest.h
+++ b/doctest/doctest.h
@@ -53,8 +53,8 @@
#define DOCTEST_VERSION_MAJOR 1
#define DOCTEST_VERSION_MINOR 2
-#define DOCTEST_VERSION_PATCH 8
-#define DOCTEST_VERSION_STR "1.2.8"
+#define DOCTEST_VERSION_PATCH 9
+#define DOCTEST_VERSION_STR "1.2.9"
#define DOCTEST_VERSION \
(DOCTEST_VERSION_MAJOR * 10000 + DOCTEST_VERSION_MINOR * 100 + DOCTEST_VERSION_PATCH)
diff --git a/doctest/parts/doctest_fwd.h b/doctest/parts/doctest_fwd.h
index 5a0b2d0..0cb5733 100644
--- a/doctest/parts/doctest_fwd.h
+++ b/doctest/parts/doctest_fwd.h
@@ -50,8 +50,8 @@
#define DOCTEST_VERSION_MAJOR 1
#define DOCTEST_VERSION_MINOR 2
-#define DOCTEST_VERSION_PATCH 8
-#define DOCTEST_VERSION_STR "1.2.8"
+#define DOCTEST_VERSION_PATCH 9
+#define DOCTEST_VERSION_STR "1.2.9"
#define DOCTEST_VERSION \
(DOCTEST_VERSION_MAJOR * 10000 + DOCTEST_VERSION_MINOR * 100 + DOCTEST_VERSION_PATCH)
diff --git a/examples/all_features/test_output/version.txt b/examples/all_features/test_output/version.txt
index a8cbe8a..a57e958 100644
--- a/examples/all_features/test_output/version.txt
+++ b/examples/all_features/test_output/version.txt
@@ -1 +1 @@
-[doctest] doctest version is "1.2.8"
+[doctest] doctest version is "1.2.9"
diff --git a/scripts/version.txt b/scripts/version.txt
index 5975b14..434dcac 100644
--- a/scripts/version.txt
+++ b/scripts/version.txt
@@ -1 +1 @@
-1.2.8
\ No newline at end of file
+1.2.9
\ No newline at end of file