News for hackers. Stuff that matters.
Re:C++ unit testing with Qt Test, part 2: advanced testing by malkia on Wednesday November 29, 2017 @12:06PM (#15808494)
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

Re:C++ unit testing with Qt Test, part 2: advanced testing by user5994461 on Wednesday November 29, 2017 @02:07PM (#15809775)
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.

Re:C++ unit testing with Qt Test, part 2: advanced testing by malkia on Wednesday November 29, 2017 @03:03PM (#15810335)
Not possible for us yet, or maybe I haven't tried it well enough...
Re:C++ unit testing with Qt Test, part 2: advanced testing by rasjani on Wednesday November 29, 2017 @10:30AM (#15807497)
Qt creator integration relies
Re:C++ unit testing with Qt Test, part 2: advanced testing by rasjani on Wednesday November 29, 2017 @10:32AM (#15807514)
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.
Re:C++ unit testing with Qt Test, part 2: advanced testing by hhmc on Wednesday November 29, 2017 @11:00AM (#15807781)
qtcreator works well with mono repo+multiple targets if you use cmake (which is well supported).
Re:C++ unit testing with Qt Test, part 2: advanced testing by rasjani on Wednesday November 29, 2017 @01:18PM (#15809317)
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.
Re:C++ unit testing with Qt Test, part 2: advanced testing by oblio on Wednesday November 29, 2017 @10:42AM (#15807616)
You can edit your previous comment.
Re:C++ unit testing with Qt Test, part 2: advanced testing by loup-vaillant on Wednesday November 29, 2017 @10:49AM (#15807677)
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.
Re:C++ unit testing with Qt Test, part 2: advanced testing by rasjani on Wednesday November 29, 2017 @11:31AM (#15808070)
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

Re:C++ unit testing with Qt Test, part 2: advanced testing by blattimwind on Wednesday November 29, 2017 @11:49AM (#15808282)
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 by rasjani on Wednesday November 29, 2017 @01:19PM (#15809324)
Hey, finnish stereotype here! Brutal honesty :)