[CXX-1744] Investigate alternatives to Catch2 Created: 22/Feb/19 Updated: 08/Feb/23 |
|
| Status: | Backlog |
| Project: | C++ Driver |
| Component/s: | Testing |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Kevin Albertson | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | CXX Driver Testing (Evergreen) |
| Description |
|
As described in https://codingnest.com/the-future-of-catch2/ after the next major release the plans to maintain Catch2 are up in the air. The next major release plans to drop support for VS2015/gcc 4.8, which we may not want to drop support for. Let's investigate alternatives like google test or decide if Catch2 is still okay with these downsides. |
| Comments |
| Comment by Andrew Morrow (Inactive) [ 23/Feb/19 ] |
|
I think at this point it might be reasonable to consider a "toolchain/language" bump for the C++ driver. Move to requiring C++17, drop the polyfills, require GCC 8, clang 7, XCode 10, VS 2017. In that case, you would probably be better prepared to deal with changes coming for catch2. |