Test the testing framework #6
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
|
||
| #include <gtest/gtest.h> | ||
|
|
||
|
|
There was a problem hiding this comment.
[pre-commit] reported by reviewdog 🐶
There was a problem hiding this comment.
Can we use this one instead: https://github.com/boost-ext/ut
I don't care for gtest and have had good experience with this one. Note that since Boost.ut is a single header we can avoid all the package issues by simplying copying into our repo while all the cmake stuff gets figured out.
There was a problem hiding this comment.
I don't know this framework, but after a short look at the documentation, I don't have a problem with it.
As long as we have someone who can help resolve any issues, then no problem.
There was a problem hiding this comment.
I use it extensively so I can help -- but you won't need it -- it just works.
There was a problem hiding this comment.
My $0.02 is who writes the tests decide which testing framework to use.
There has been a lot of talks in beman about moving to a shining new testing framework from Google Test (lit, ut, you name it), but right now no actual project is using anything other than Google Test or a single executable with bunch of static_asserts.
I think if @JeffGarland want us to use ut, @JeffGarland should submit a PR with some test cases to start us off. I can help with the setup.
The same arguments applies for @robert-andrzejuk , I think initial tests and the test framework should be packed into a single PR.
There was a problem hiding this comment.
I can most certainly submit a PR, but if I do that I think we wouldn't need this one. I'm going to be on airplanes for the next 24 hours -- and jet lagged after that -- so relying on me in the short run would mean no progress for a couple days likely. gtest can most certainly be replaced later as well -- but time spent get it said up will just be wasted.
Meanwhile one could take 10 minutes -- copy the boost.ut header into the test directory and write a test -- the hello world for boost.ut isn't complicated in the least
https://godbolt.org/z/czTrKzo8Y
Sorry, gotta catch a plane -- have fun!
robert-andrzejuk
changed the title
|
I tried to have a look at ut, but I had issues: boost-ext/ut#662 So in the mean time I configured Catch2. |
No description provided.