Oh yes, it's logic. Thanks !!!

I found a solution for the issue: Simply split the main() from the rest of the Project . Here is the updated Production Code Product specification: import qbs Project { name: "TheRealApp" QtApplication { name: "TheApp" Depends { name: "cpp" } Depends { name: "library" } Group { name: "Main" files: [ "main.cpp", ] } } StaticLibrary{ name: "library" Depends { name: "cpp" } Depends { name: "Qt.core" } Export { Depends { name: "cpp" } cpp.includePaths: product.sourceDirectory } Group{ name: "Grp_Main" files: [ "mycustomclass.cpp", "mycustomclass.h", ] } } }

Hi, IIRC, you can't directly do that. However, there where some scripts in the qtqa repository to run the tests in the CI, you might be able to leverage that. Hope it helps

I've partialy analysed AutoTest code. For QTest it checks if given source file (after macro preprocesing) has QTest include and QTest::exec() somewhere in code. In my case it lead to usage of TestRunner modified to store function object #define DECLARE_TEST_RUNNER(className) \ namespace { \ int executeTestClass(int argc, char* argv[]) \ { \ className test; \ return QTest::qExec(&test, argc, argv); \ }; \ static char test_##className = \ TestRunner::Instance().RegisterTestClassRunner(executeTestClass); \ } Macro is placed at begining of each CPP file with test details (to decouple as much as possible) However Autotest still acts strangely. Sometimes it discover tests, sometimes not. I believe that it may search in source context of currently selected run target. PS: When I expanded one of DECLARE_TEST_RUNNER macro - AutoTest start displaying green arrows. Not before. Building main exe or ut.exe isn't helping. Calling 'Refresh test' from Tools->Tests also doesn't help. I still don't know what triggers test gathering. PSS: In each test binary at least one QTest::qExec should be expanded out of MACRO. From this point - AutoTest shows also test runners hidden in MACRO and run then all.

Nice ! Thanks for sharing :)

Nice one ! I've missed that function. Thanks !

Hi @CharlieG AFAIK that is not possible from QML. But you can try checking for errors by loading the QML from C++ side. For eg. if you use QQmlComponent you can check for errors using errors.

@Paul-Colby Thank you for reporting back. This is very important info for people using this function as "stuff" will happen if you upgrade from older Qt.

@Sam2304 you are welcome Well, sometimes "we programmers do not see the forest because of trees" ;) Glad, that it worked out for you.

Hi and welcome to devnet, reading from docs QWidget::cursor() should do the job. Have you tried it?