Community
Participate
Working Groups
The "Test" option in run configurations is confusing to the user. It is not clear what "Test" should be run with it. This causes user confusing since I have been generating Hyades JUnit test code and then running the test code with the JUnit wizard. Suggestion: Rename "Test" to "Hyades JUnit Test" to clear up confusion. Another possibility is to integrate it with JUnit Test run configurations. One of the added benefits of renaming it to "Hyades JUnit Test" would be that all the Hyades options in the run configurations dialog would be organized together.
Wayne, we have discussed of this for a while without having a good solution. What do you suggest?
In the short term, renaming the "Test" launch configuration type is a possible solution. If the "Test" launch config type is only used for Hyades JUnit test (suite) then Andrew's suggestion of "Hyades JUnit Test" is reasonable. Given that we are surfacing the "Hyades" term in other cases (e.g., Hyades URL Test) it seems reasonable to surface this term in this case as well, especially when needing to distinguish it from the Eclipse JUnit launch config type. In the long term, we need to work with the Eclipse Platform team to improve the Launch Configuration Dialog to better handle the interaction of launch config types (especially ones that are difficult for users to differentiate).
Fyi, there is a defect in TPTP 4.0 to remove all occurrences of 'Hyades' from the UI. So, an alternate solution may be required for TPTP 4.0. https://bugs.eclipse.org/bugs/show_bug.cgi?id=83007
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.
*** This bug has been marked as a duplicate of 66105 ***
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.
