Community
Participate
Working Groups
When running a Hyades test, Junit or URL, using the new launch configuration for the test perspective I can only run the first test in the list reliably. When any other test is run, an execution history file is created but it doesn't have the correct results and contains the name of the first test in the launch configuration list. I will attach a screenshot of the problem that I see.
Created attachment 10362 [details] screenshot of launch config problem
Correction: launch config only works on the first test suite that is run, it doesn't matter where it shows up in the list.
There seems to be two different problems that make the situation confusing, though I don't think there is a bug under this: 1) The name of the Test Execution Result (i.e. the one that appears when you open a .execution file, which is also shown as the unique child of an Execution node in the Test Navigator) is the one that is chosen in the "Execution Results" tab. By default, the "Name" field in this tab reflects the selected Test's name. That is to say, if you select the test "Jibe" in the "Test" tab, the "Name" field in the "Execution Results" tab contains "Jibe". If you go back to the first tab and select the test "cnn", the field "Name" in the second tab contains "cnn". BUT: if you edit the field "Name" and choose another name (for instance "foo"), this field is no more automically modified when you change the selected Test in the first tab. This means that once you have edited this field, it is no more automatically updated, and if you type "Jibe" in that field, even if you select test "cnn" in the first tab, the execution results name will be "Jibe". This problem doesn't happen if you don't modify the "Name" by default (you can check this by deleting your Launch Configuration and re-create one). 2) The file name of the execution file is named by the TEH according to the Test Suite's file name. That is to say, if you run a Test Suite named "Jibe" but stored in "test1.testsuite", the execution file is named "test1_xxxxxxxx.execution". I think the solution to this problem is to name the .execution file according to what was selected in the Launch Configuration, instead of following the Test Suite file name.
I forgot to mention that I did not reproduce the problem with the second test launched containing incorrect results. I ran two tests, using the same Launch Configuration, and both executed and all the expected Test Cases appeared in the Test Navigator.
About the confusing problems that may lead to this situation, I entered a defect and an enhancement request. See dependencies.
*** Bug 63731 has been marked as a duplicate of this bug. ***
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
