4 ms·

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

54 points by vivaladav 9y ago

rasjani 9y ago
Qt creator integration relies
- rasjani 9y ago
  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.
  - oblio 9y ago
    You can edit your previous comment.
    - loup-vaillant 9y ago
      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.
      - rasjani 9y ago
        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
        blattimwind 9y ago
        When someone suggests that something you did was smart, don't go ahead and tell them they're wrong ;)
        rasjani 9y ago
        Hey, finnish stereotype here! Brutal honesty :)
  - hhmc 9y ago
    qtcreator works well with mono repo+multiple targets if you use cmake (which is well supported).
    - rasjani 9y ago
      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.
happy_rust44 9y ago
Still writing in the undefined language, huh? Problem with unit-testing is that it's impossible to catch all possible bugs, especially the insecure buffer overflow and multithreading data races ones. Your only bet is to use a sane programming language like Rust and move forward. Drop your old codebases, I bet maintaining them is more painful than switching to rust. I'll also urge QT developers to focus more time and money towards migrating QT to rust, one step at a time so that we can live in a defined future ahead.
malkia 9y ago
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://opencppcoverage.codeplex.com/ https://github.com/OpenCppCoverage/OpenCppCoverage https://github.com/OpenCppCoverage/OpenCppCoverage https://github.com/OpenCppCoverage/OpenCppCoveragePlugin https://github.com/OpenCppCoverage/OpenCppCoveragePlugin
- user5994461 9y ago
  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.
  - malkia 9y ago
    Not possible for us yet, or maybe I haven't tried it well enough...

54 points by vivaladav 9y ago

rasjani 9y ago

Qt creator integration relies

rasjani 9y ago
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.
- oblio 9y ago
  You can edit your previous comment.
  - loup-vaillant 9y ago
    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.
    - rasjani 9y ago
      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
      - blattimwind 9y ago
        When someone suggests that something you did was smart, don't go ahead and tell them they're wrong ;)
        rasjani 9y ago
        Hey, finnish stereotype here! Brutal honesty :)
- hhmc 9y ago
  qtcreator works well with mono repo+multiple targets if you use cmake (which is well supported).
  - rasjani 9y ago
    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.

happy_rust44 9y ago

Still writing in the undefined language, huh? Problem with unit-testing is that it's impossible to catch all possible bugs, especially the insecure buffer overflow and multithreading data races ones. Your only bet is to use a sane programming language like Rust and move forward. Drop your old codebases, I bet maintaining them is more painful than switching to rust. I'll also urge QT developers to focus more time and money towards migrating QT to rust, one step at a time so that we can live in a defined future ahead.

malkia 9y ago

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://opencppcoverage.codeplex.com/ https://github.com/OpenCppCoverage/OpenCppCoverage https://github.com/OpenCppCoverage/OpenCppCoverage https://github.com/OpenCppCoverage/OpenCppCoveragePlugin https://github.com/OpenCppCoverage/OpenCppCoveragePlugin

user5994461 9y ago
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.
- malkia 9y ago
  Not possible for us yet, or maybe I haven't tried it well enough...