GitLab

Change-Id: I5a77e8fd629343bc059a03e6c27f45103b96101a
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>

Change-Id: I3ce6e711392f35c89dfcbecc3c8fcb8aca293602
Reviewed-by: Christian Stenger <christian.stenger@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>

Change-Id: Ie9474da2a4c9c2e461bdd15e859e1a53f820a1d1
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>

Change-Id: I07dbde221632ec0aeca758f684c8ada2c71f3969
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>

Change-Id: If433c621466f2e1160a016d2b7b2539e4dc8b3d6
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>

Change-Id: Ic6c3e3beaba15e83c8524394ccc6a1953e76d59a
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>

Change-Id: I4ca2f7d82e70306ffae50d5eea31357e9fcfd0aa
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>

Change-Id: I1f12323e1de481f800fcf835a12213059b72bfd4
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>

Change-Id: I521065577c195713bc252e6762a88011996f045c
Reviewed-by: Tim Jenssen <tim.jenssen@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>

Change-Id: I5f20741492dbb3d553bea30a677965d46d6d8eb3
Reviewed-by: Marco Bubke <marco.bubke@theqtcompany.com>
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>

Change-Id: I55d69bac267f6f601682aeeca9eedcf944e8b55a
Reviewed-by: Marco Bubke <marco.bubke@theqtcompany.com>
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>

Change-Id: Iec90cfcd74192f13d270180db91db95d41253bc5
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>

Change-Id: Ia504e453b6cacc254ea598c629c3762c03cfa783
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>

Change-Id: Idcb2c328f3313dac38997765c2569d6861d34a20
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>

also move it to an extra file

Change-Id: Ia76c9b3be4c11207a564e7cc7fcb2eae730ae505
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>

Change-Id: I7af93eb587e55f7d6e4ee14ed9808ceeb41ed8a3
Reviewed-by: Tim Jenssen <tim.jenssen@theqtcompany.com>

Change-Id: I78e700734e2b5ec6bad31df71419bbc1a8b1b3c8
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>

Change-Id: I7636e819f41a3fc0592a36f330f30695760cad6a
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>

Only lock if necessary to avoid dead-lock situations.

Change-Id: I39d1158749131a72805e55f28aba79e1827f158b
Reviewed-by: Christian Stenger <christian.stenger@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>

Change-Id: Ia6fef10bc577f9722b6c063c2df4d1651a8be50d
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>

Change-Id: I56ba8f9d0d4abe7627f9dd0d980774dda814d456
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>

This takes especially configurations in account when subprojects
are enabled/disabled conditionally.

This had lead to crashes when executing projects with some more
tests or more test output. Now it's using a mutex to avoid
concurrent access.

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.

Additionally preparation of filtering has been done.

...and display fatal messages on the summary as well.

No need for having this more complicated than necessary.

If there are items inside the results pane that match the filter
item filtering for these kind of results will be enabled.