@Pixelgrease you might also want to consider migrating to cmake for the long run.

@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.

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.

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", ] } } }