- 
    
Bug
 - 
    Resolution: Done
 - 
    
P2: Important
 - 
    1.5.1
 - 
    None
 
- 
        d7fb2f24e251c058bdab17bbd737639d9a1c8efd
 
When using the AutotestRunner item, the command qbs build -p autotest-runner cause execution of the unit tests in their build directory.
It would be nice if the tests were executed in the install root directory instead.
The command qbs run -p autotest-runner returns this weird result:
Restoring build graph from disk Building for configuration qt57-lnxgcc53_64-debug Running test tst_PathAutotests Running test tst_XDLSymbol Running test tst_DocumentAutotests Running test tst_XDLSymbolWriter Running test tst_XDLSymbolReader /home/krys/Projects/LibreEDA/qt57-lnxgcc53_64-debug/bin/tst_PathAutotests ********* Start testing of tst_Path ********* [...] ********* Finished testing of tst_Symbol ********* Build done for configuration qt57-lnxgcc53_64-debug. Installing ERROR: Cannot run: Product 'autotest-runner' is not an application.
Basically, depedencies and test suites are built, then run from their build directory, then executed but qbs finally fails.
Notes:
- My use case is that some of my unit tests requires the project to be fully installed (need to access data and config files from their "well-known" locations)
 - Althought, Qbs and QtCreator don't depend on each other, there's an inconsistency. QtC run any 'runnable' (CTRL-R) from their install dir.
 - Original request on QBS mailing list: http://lists.qt-project.org/pipermail/qbs/2016-July/001537.html
 
| For Gerrit Dashboard: QBS-993 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V | 
| 164310,2 | AutotestRunner: Run installed test executables from install location | 1.6 | qbs/qbs | Status: MERGED | +2 | 0 |