Community
Participate
Working Groups
It shows them in a view instead. Could you please provide any capability for text mode, for example some default file to hold the results (in plain text). Thank you in advance, Boris.
It depends on how you start the application. Give VectorTest from the JUnit distribution as an example, the output - is presented in the console if you start VectorTest using the launcher for a "normal" Java application - if presented in the JUnit view if you start VectorTest using the launcher for JUnit test cases. OK to close PR ?
Hi Dirk. Thank you for answering. No, I think that is not all that simple. I'm talking of testing a plugin, thus of pde.junit. Therefore, as I understand, a pde.junit project is needed to upload all the plugins, among the rest. If a simple java project is launched, this will not happen, to my best knowledge. Best Regards, Boris. ------------------------------------------------------------------------ Boris Litvak Programming Languages and Environments IBM Haifa Research Lab, Israel E-mail: borisl@il.ibm.com, Tel: 972-4-8281074
Erich, any comments how this can be achieved.
Not clear what you are trying to do here. If you want to test a plugin then you should use pde.junit. If you use pde.junit there is no need for junit.textui.TestRunner. pde.junit runs your tests and shows the results of the tests in the JUnit results view and the console output of the tests will show up in the standard console. What else do you need?
Hi Erich, Thank you for answering. I'll try to cover all the problems in this mail. Here are the facts: 1. I use pde.junit. 2. I was not aware of the fact that main should not be called in AllTests when using pde.junit_2.0.0. // Note: The org.junit plugin version is org.junit_3.7.0 (This is FYI, I do not invoke it, but pde.junit probably relies on it). Eclipse version is 2.0.1. WSAD build id is 200208291828. My code now looks like: public class AllTests { // public static void main(String[] args) { // junit.textui.TestRunner.run(AllTests.class); // junit.extensions.jfunc.textui.JFuncRunner.run(AllTests.class); // } public static Test suite() { JFuncSuite suite = new JFuncSuite(); //$JUnit-BEGIN$ suite.addTest(new ActionVerifyTest ("testVerificationRecieverResultActionDescriptorRefObject")); //$JUnit-END$ return suite; } } 3. The project launch configuration is JUnit Test Plugin, coretestapplication. 4. The JUnit GUI view shows the results correctly. 5. The console includes ONLY the following: !ENTRY org.eclipse.core.runtime 2 1 Nov 19, 2002 13:49:21.934 !MESSAGE Problems encountered loading the plug-in registry. !SUBENTRY 1 org.eclipse.core.runtime 2 1 Nov 19, 2002 13:49:21.934 !MESSAGE Plug-in descriptor "org.eclipse.emf.codegen.ui" not found for fragment "org.eclipse.emf.codegen.ui.nl1". Fragment ignored. !SUBENTRY 1 org.eclipse.core.runtime 2 1 Nov 19, 2002 13:49:21.934 !MESSAGE Plug-in descriptor "org.eclipse.emf.codegen" not found for fragment "org.eclipse.emf.codegen.nl1". Fragment ignored. In RADPlugin startup.... // This is my Plugin In RADPlugin startup after init.... // This is my Plugin 6. We would like to receive a text view of the results, in the console or in a file. We do NOT see the junit output in the console. I hope this clears things up. Appendix: 1. pde.junit_2.1.0 bug: The following exception is thrown on Eclipse 2.0.2, WSAD build 200211071448, when launching the similar application: org.eclipse.core.runtime.CoreException[5013]: java.lang.NoClassDefFoundError: org/eclipse/pde/internal/core/TargetPlatform at org.eclipse.pde.internal.junit.launcher.JUnitPdeLaunchConfiguration.createVMRunn er(JUnitPdeLaunchConfiguration.java:81) at org.eclipse.jdt.internal.junit.launcher.JUnitBaseLaunchConfiguration.launch (JUnitBaseLaunchConfiguration.java:80) at org.eclipse.debug.internal.core.LaunchConfiguration.launch (LaunchConfiguration.java:136) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog$10. run(LaunchConfigurationDialog.java:2299) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run (ModalContext.java:98) The Target Platform resides in ui, and not in core. The pde.junit version is 2.1.0. in this run. Remember that the pde.junit site says that pde.junit_2.1.0 works for eclipse 2.0 as well. 2. http://bugs.eclipse.org/bugs/show_bug.cgi?id=26556 ([Bug 26556] PDE Junit does not read plugin info from the plugins directory.) - this was assigned to you. Sorry that I supply so many bugs to you, Erich :-) 3. JUnit extension (such as JFunc) integration in eclipse.pde. How can it be done? Is it sufficient to use JFunc class names instead of JUnit class names, and to put the jfunc jars into the pde.junit plugin, at the <runtime> ConfigurationElement? Or a new plugin is a must? How will the JUnit GUI handle this? Again, I mean pde.Junit only. I know this is hard work :) Thank you in advance, Boris. P.S: Never though I would discuss anything with Erich Gamma :-)
I think that the patch for bug 36352 would resolve the main complaint. Can this be marked as a duplicate? The others should be logged as separate bugs, potentially.
I agree it would resolve the main complaint. Another option would be to allows show the junit test run output in a console tab with hyperlinks etc. This cannot happen for 3.1. So as a workaround copying the tree to the clipboard would be OK by me. However, we should not attempt to duplicate the Ant formatting options.
*** This bug has been marked as a duplicate of 36352 ***
