Alright, than I have a few questions. If you can't or don't want to answer them, no problem
It seems that it doesn't work and the author has no plan on porting it: https://github.com/OpenCppCoverage/Open ... /issues/31. This is not too bad though because gcov does the job well enough I think It's also the most popular choice and is supported by many tools.
Hi, I just had a look at it and it appears to be very similar to googletest. It's also a xUnit inspired testing library and those are all not that much different from one another meaning that technical differences are less significant in my opinion. I think much more important is the user base. I (and I think most developers) don't want to learn all the macros of a new framework which in the end is more or less the same than every other framework. For pure C++ googletest seems to be the default option, has a very large userbase and there are many tutorials and resources from the community. That why I opted for googletest. Yes it's comes from google but it's BSD licensed everyone can contribute. I don't wan't to say that googletest is the only option or that CppUTest is bad, I just wanted to express what I think our priorities should be when choosing a framework.ascaron wrote: ↑Fri Jul 26, 2019 7:13 amI'm not a big fan of Google either.
What do you think about https://cpputest.github.io/ ?
It's a little smaller than Google Test and maintained by one of the agile manifesto guys, James Grenning. I've used it throughout his book on unit testing of embedded devices and liked it so far. Though I have to say I never used Google Test before and so can not compare.
Yes you are of course right, google doesn't have the best track record. I think with unit test frameworks it's not so bad because there is normally very little innovation in a unit test library and I'm positive that even if it is shut down that the community will continue to support it. One alternative I also considered is Boost.Test. It's of course also a good option but I have not worked with it yet.ascaron wrote: ↑Fri Jul 26, 2019 3:24 pmJust wanted to throw in an alternative
I have no problem using gtest, I simply associate mostly bad stuff with Google. Randomly abandoning projects, keeping the project lead of open source projects in the company and so on. There was an interesting discussion about the Go Language, whether it's a Google or community language.
Cool, keep in mind that at the moment the C++ unit tests are compiled into a separate executable. This was more like a proof of concept till now. My plan is to somehow make a similar workflow possible for python and C++ unit tests which means that there may be a lot of changes during the next month. This and probably next week I'm still busy writing python tests but after that I'm going to start working on the infrastructure and overall structure of the test case organization. If you have any questions feel free to contact me