...to avoid blocking the ui thread. Parsing will now performed
in a separate thread, except for small changes where this would
create too much overhead.
Change-Id: I1db441594f1684f969bb86c9423c0fb0bcb1a53a
Reviewed-by: Andre Poenitz <andre.poenitz@theqtcompany.com>
The new approach enables the parser as soon the Tests navigation
widget or the Tests results pane is visible.
If none is displayed parsing will be disabled.
This additionally fixes an issue of not parsing a project
when having a project opened already before triggering the
first Tests navigation widget to become visible.
Change-Id: I7163268d405e07e85814097d65ff34790a98a3d1
Reviewed-by: Andre Poenitz <andre.poenitz@theqtcompany.com>
Handling of parsing has slightly changed. The parser now uses simple
states to be capable of postponing triggered parses if there is already
a parsing in progress. Furthermore the parser now waits for the current
project to be completely scanned.
Change-Id: I6d4968d28194ba8d23d3a0ee6ab454d81a549e67
Reviewed-by: Andre Poenitz <andre.poenitz@theqtcompany.com>
...for code split up into header and source.
Change-Id: I8f1bf01e6ff6f88afc1e054318cd384b5f231eb6
Reviewed-by: Andre Poenitz <andre.poenitz@theqtcompany.com>
Additionally some minor refactorings to increase readability.
Change-Id: I0be120fcedcf31dbb0116d84f0d3c23cf95e7d91
Reviewed-by: Andre Poenitz <andre.poenitz@theqtcompany.com>
If the current project mixed named and unnamed Quick tests
determing the test configuration failed due to running into
the assert if you had no auto tests for the current project
selected as well.
Change-Id: I5c98316fada704cd7e021becab897d168a19b99b
Reviewed-by: Andre Poenitz <andre.poenitz@theqtcompany.com>
This fixes two different crashes when TestCodeParser tried
to access m_currentProject, but the object this pointer was
referencing had been deleted already.
Change-Id: Ie59e027394e613a8ef1e4f32f97abed6e8cb007a
Reviewed-by: Tim Jenssen <tim.jenssen@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>
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>
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
André Pönitz
Tim Jenssen
Christian Stenger