C++ unit testing with Qt Test, part 2: advanced testing

blog.davidecoppola.com

54 points·vivaladav··12 comments

Talking about unit testing, what are people using for coverage, and more specifically on Windows + MSVC (Professional, or Community)?

What are the sane choices there? (I've installed OpenCppCoverage two days ago, and so far so good, but wondering about other choices)

https://opencppcoverage.codeplex.com/ https://github.com/OpenCppCoverage/OpenCppCoverage https://github.com/OpenCppCoverage/OpenCppCoveragePlugin

The only free thing I found to sort of work is gcov. It's integrated in gcc. Many projects compile on both gcc and msvc.

Compile the unit tests with the coverage flags. Run the exe. Collect the coverage file.

Not possible for us yet, or maybe I haven't tried it well enough...

Qt creator integration relies

Heavily on the directory structure and how one sets up the the qmake's pro files. This is very cumbersome for mono repos with multiple build targets.

qtcreator works well with mono repo+multiple targets if you use cmake (which is well supported).

I know :( just wanted to point that out and emphasize that it's partly due to qmake and how it's handled within qt creator.

You can edit your previous comment.

I think it was on purpose, nested comments being an illustration of a (small) directory structure. Some comments about Lisp achieve a similar effect by littering themselves with parentheses.

No it wasn't intentional - and iOS client I currently have installed does not have edit and account password is something I don't remember without password manager so I couldn't just switch to web :(

Sorry

When someone suggests that something you did was smart, don't go ahead and tell them they're wrong ;)

Hey, finnish stereotype here! Brutal honesty :)

Reply on news.ycombinator.com