This was possible as triggering further test runs could happen
while the current test run was still building the project.
Additionally it's now possible to stop the build process (if any)
by hitting the Stop button of the test results pane as this is
part of the test run.
Change-Id: I38940b5b8f4ba9e373785921c04cbceaeb2e5acf
Reviewed-by: David Schulz <david.schulz@theqtcompany.com>
Additionally provide a setting to not display warnings regarding
using a guessed run configuration.
Change-Id: Ia7647f55e5085ffc84044281c5107770cd30d504
Reviewed-by: Tobias Hunger <tobias.hunger@theqtcompany.com>
On windows we are only interested in .exe files. For example
QProcess("test.cmd") does not work.
renamed which to executableFilePath
Change-Id: Ib9aa2d011c3d0525b618a1b0a6bd32b556c02010
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
This is a preparation for later refactoring. Also moved
the get settings values outside from the threaded code.
Change-Id: I0acceece4bc55a453880f4235e02a5712443b32d
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
...use signals and slots instead.
Additionally re-use the existing item that is displaying the
"Entering Test Function..." information.
Change-Id: Ibedac01ced9e987d542aa4dc878588fbec84d585
Reviewed-by: Tim Jenssen <tim.jenssen@theqtcompany.com>
This message just states which function actually is executed and will
always be on the bottom of the list of results.
When test run finishes this message will be completely removed.
Change-Id: Ie8fedfc74f67eba71a2bcf55f4dc1553754fca9a
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
Instead just remove these from the current test run and add a
respective warning to the test results pane.
Additionally made a the message of having no test cases at all
a warning instead of a fatal.
