- 09 Dec, 2014 1 commit
-
-
Christian Stenger authored
Change-Id: Ia6fef10bc577f9722b6c063c2df4d1651a8be50d Reviewed-by:
Christian Stenger <christian.stenger@theqtcompany.com>
-
- 05 Dec, 2014 1 commit
-
-
Christian Stenger authored
Change-Id: I56ba8f9d0d4abe7627f9dd0d980774dda814d456 Reviewed-by:
Christian Stenger <christian.stenger@theqtcompany.com>
-
- 04 Dec, 2014 23 commits
-
-
Christian Stenger authored
-
Christian Stenger authored
-
Christian Stenger authored
This takes especially configurations in account when subprojects are enabled/disabled conditionally.
-
Christian Stenger authored
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.
-
Christian Stenger authored
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.
-
Christian Stenger authored
-
Christian Stenger authored
Additionally preparation of filtering has been done.
-
Christian Stenger authored
-
Christian Stenger authored
-
Christian Stenger authored
-
Christian Stenger authored
...and display fatal messages on the summary as well.
-
Christian Stenger authored
-
Christian Stenger authored
-
Christian Stenger authored
No need for having this more complicated than necessary.
-
Christian Stenger authored
If there are items inside the results pane that match the filter item filtering for these kind of results will be enabled.
-
Christian Stenger authored
-
Christian Stenger authored
-
Christian Stenger authored
-
Christian Stenger authored
Additionally * fixed some deletion of pointers * const correctness * small refactorings for readability * better separation of responsibilities
-
Christian Stenger authored
-
Christian Stenger authored
-
Christian Stenger authored
-
Christian Stenger authored
-