Community
Participate
Working Groups
There are inconsistent references to Manual and JUnit tests. In the File->New wizard you can create a 'JUnit Test Suite Definition' and 'Test Suite' (which is a Hyades Manual Test). In the run configuration wizard, you can create a 'Hyades Manual Test' configuration or a 'Test' (which is a JUnit Test). I'm not sure if this is PII or not, but it should be fixed at some point.
Created attachment 11704 [details] File->New
Created attachment 11705 [details] run config
Now that we have a "3.3" Version in bugzilla, updating bugzillas targeted to 3.3 or a 3.3 iteration so that their Version matches their Target. "future", "unspecified", "4.0", and "4.1" Versions will not be updated.
*** Bug 76910 has been marked as a duplicate of this bug. ***
'Hyades Manual Test' is now displayed to the user. No more ambiguity.
Just some clarification, is this fix strictly for 3.3? I believe there may be other terminology/name requirements for 4.0 as discussed during the 2005-03-17 TPTP Test UX meeting (minutes available in the tptp-testing-tools-dev mailing list). For example, for 4.0 the term 'Hyades' will likely be replaced with 'TPTP'.
The launch configuration wizard still shows 'Test' for a Hyades JUnit Test.
To be consistent with other test launch configuration names, the word "Hyades" should be appended to the "Test" label in the launch configuration. However, we cannot add the word "Junit", as this launch configuration type is meant to receive any new type of test contributed by downstream products. Their tests, which are not necessarily related to JUnit, would end up in the "Hyades JUnit Test" launch configuration, which would not make sense. So I'll change "Test" to "Hyades Test", provided that the PII change is accepted (request pending).
Julien, I agree with your comment for TPTP 4.0, but not for 3.3 which is the version this defect was filed on. The other test types are shown as 'URL Test' and 'Manual', but JUnit is simply referred to as 'Test'.
Todd, In the latest 3.3 build, the other launch configuration types are shown as "Hyades Manual Test" and "Hyades URL Test". So changing "Test" to "Hyades Test" makes sense. However I cannot add the word "JUnit" to "Hyades Test". That's because this launch configuration type is supposed to host not only JUnit tests, but also test types defined in downstream products. "Hyades JUnit Test" would be too restrictive in regard to what this launch configurations type is supposed to do. We want to encourage downstream products to add their test types to the existing "Hyades Test" launch configuration type, and avoid defining yet another type of test launch configuration, as it has been done for Manual and URL Tests.
I just got feedback from Ruth Lee and unfortunately PII changes are not allowed any more in the 3.3 stream. Marking this defect as WONTFIX.
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.
