Community
Participate
Working Groups
[Usability] Converting standard JUnit tests to TPTP JUnit test suites is not intuitive. When converting standard JUnit tests to TPTP JUnit test suites, the following usability issues exist: 1) The action of converting standard JUnit tests to TPTP JUnit test suites is an import action and not a 'convert' action, as such. Consider creating a context menu for Java/JUnit classes in the JDT to create a TPTP JUnit test suite. Of course, multiple selection would be required. 2) The two types of JUnit tests (JUnit and JUnit plugin) supported by this action, have separate import wizards. Consider using the same import or context menu wizard with a drop-down or something for the user to select the type of generate JUnit test suite. This would be beneficial for feature #74791. See defects #113480 and #74791 for background information.
About point 1: I am fine with adding a context menu to JUnit classes (since a JUnit class is what the user initially has), but I think we need to discuss whether 'convert' is the appropriate word to describe what the wizard does. After the wizard has been applied to a JUnit test, the user can still keep working with it in the Java perspective, with the JDT tooling. The JUnit test is not modified in any way. The only result of the wizard is that the same JUnit test is now recognized as a test by the TPTP framework. This is visually identified by the presence of the JUnit test in the test navigator. So it can be run using TPTP. 'Convert' would make the user believe that the test will be either modified in-place by TPTP, or that this test will be copied and transformed, and that the original JUnit test is not used at all by TPTP. None of these beliefs are true. So, unless someone suggests a better verb, I think "import" is more accurate than "convert" to describe what the wizard does.
(In reply to comment #1) Agreed. How about 'create'? Wayne: Any comments?
Consider the following: -In the File >> New >> Other... >> Test >> TPTP JUnit Test wizard, allow the user to select one or more existing JUnit test classes. The wizard would create a TPTP JUnit test suite for each JUnit test class selected by the user. This would allow the removal of the File >> Import... >> JUnit test to TPTP. -Modify the TPTP JUnit runner to run JUnit tests. When the user selects a JUnit test, create a temporary TPTP JUnit test suite for deployment and execution.
We will retain the second suggestion. Due to the amount of tasks required and lack of resource, retargetting to future.
Triaging.
Based on priority and available resources, this defect is considered for deferral from 4.3. If you object to this deferral, please provide a comment ASAP explaining the reason that you need this in 4.3 and we will take that into consideration.
Please target to 4.4 since all non-blocking/critical defects will be deferred as decided in today's AG call.
Reassigning to the component leads to triage for 4.4.
This defect is covered by the 4.3 test feature #90628. Feel free to reopen if this is not the case.
Reporter: Please verify and close in preparation for shutting down the TPTP 4.4 release. Thanks.
Closing by default since not verified/closed by the originator in the 6+ months since being resolved. Please reopen if the issue is still present in the latest TPTP release or the resolution is not correct.
