Earlier quoted context omitted.
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).
C++ unit testing with Qt Test, part 2: advanced testing
11–14 of 14 posts
Re: C++ unit testing with Qt Test, part 2: advanced testing
#12Earlier quoted context omitted.
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 ;)
Re: C++ unit testing with Qt Test, part 2: advanced testing
#13Talking 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
Compile the unit tests with the coverage flags. Run the exe. Collect the coverage file.
Re: C++ unit testing with Qt Test, part 2: advanced testing
#14Talking 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.