These bots... sigh

You can select in your IDE which program should be run. The IDE will not run more than one executable. You can run all tests on the command line with 'make test' or 'cmake --test' (iirc)

@SGaist @mchinand Thank you so much. Unit testing is a new concept for me and I am trying to learn how to do it and best practices.

@SGaist Thank you for taking the time. Now, I am happy that I've more or less applied the architecture and workflow suggested by the man himself already. The example you used toward the end is exactly my case, which leads me to ask for tips here. I will be checking the source tree for more specific cases and will be making modifications accordingly.

@jkwok678 Conceptually yes (Stackoverflow would say no because the technical terms you used are not very precise but high-level you got the concept) P.S. If you don't want unnecessary pain in the future with cross-platform support, keep your .c/.cpp/.h,/.hpp etc files lower-case only

CTest is the test runner. Yes that's the starting point. Then you can have separated functional tests where you validate the high level functionalities and finally integration tests where you ensure that the final application is working as expected.

@jpnurmi said in Can QTest or Qt Quick Test be used for automated system (not unit) testing of QtQuick Control2/C++ application?: How about Squish? It's also used for release test automation of Qt. Thank you for the suggestion! Yes we noticed Squish. But now we develop an application prototype using QML and until some milestone would like not to use commercial tools. On the other hand we don't need a thorough test coverage yet. We'd like mostly sanity tests to validate. And we want to try Qt test frameworks or implement feeding navigation commands and verification ourselves with Qt C++/QML means.

@Jakob Ah, yes. From Qt4 you get: # define Q_SIGNALS protected I firmly believe that this change was made to accommodate the new way of connecting signals. I don't find it to be a great improvement, but this is a personal opinion ... In the new framework it seems every object can easily rise another object's signal, which is a bit ... hm ... suspicious ... not that it was impossible before, but you had to go the extra mile, by using the QMetaObject class.

Hi and welcome to devnet, Looks interesting ! Thanks for sharing !