Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <27404766.1180076956641.JavaMail.jira@brutus>
Date: Fri, 25 May 2007 00:09:16 -0700 (PDT)
From: "Nina Rinskaya (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Commented: (HARMONY-3391) [JDK][EUT] 2 tests fail in
 org.eclipse.jdt.ui.tests.all suit
In-Reply-To: <29044725.1173869769389.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/HARMONY-3391?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498961 ]=20

Nina Rinskaya commented on HARMONY-3391:
----------------------------------------

Andrey, if I'm not mistaken this test belongs to jdtuirefactoring suite.=20

Please let me also give you the description how to run this test separately=
 from command line and as JUnit test in Eclipse project, I was able to repr=
oduce the failure in that ways.

The description below is a common description for any EUT test suite, and f=
or this specific test suite you should use the following plug-in and classn=
ames:

plug-in: org.eclipse.jdt.ui.refactoring
classname (to use when running from command line, see (3)): org.eclipse.jdt=
.ui.tests.nls.NLSSourceModifierTest
Test class (when running through Eclipse see (4)): org.eclipse.jdt.ui.tests=
.all.AllAllTests

Example of the command line that I used for reproducing:
C:\work\harmony-hdk-r541143\jdk\bin\java.exe -jar startup.jar -application =
org.eclipse.test.uitestapplication -dev bin formatter=3Dorg.apache.tools.an=
t.taskdefs.optional.junit.XMLJUnitResultFormatter,log.xml -testpluginname o=
rg.eclipse.jdt.ui.tests.refactoring -classname org.eclipse.jdt.ui.tests.nls=
.NLSSourceModifierTest

(results are written to the currecnt directory to log.xml).

-----------------------------------------
Note: the description below is applicable to Eclipse 3.2 only (checked on W=
indows version)

1. (you could probably skip this step because you might have these archives=
 downloaded earlier)  Download Eclipse and Eclipse Unit Tests (3.2) archive=
 from  http://download.eclipse.org/eclipse/downloads/drops/R-3.2-2006062919=
05/index.php, download =09
eclipse-SDK-3.2-win32.zip (eclipse-SDK-3.2-linux-gtk.tar.gz for Linux) and =
eclipse-Automated-Tests-3.2.zip   . Direct links are:=20

http://mirrors.nsa.co.il/eclipse/eclipse/downloads/drops/R-3.2-200606291905=
/eclipse-SDK-3.2-win32.zip (or =20

http://mirrors.nsa.co.il/eclipse/eclipse/downloads/drops/R-3.2-200606291905=
/eclipse-SDK-3.2-linux- gtk.tar.gz for Linux)

http://mirrors.nsa.co.il/eclipse/eclipse/downloads/drops/R-3.2-200606291905=
/eclipse-Automated-Tests-3.2.zip


2. Unpack eclipse-Automated-Tests-3.2.zip, this will create a top-level dir=
ectory  "eclipse-testing" that contains eclipse-junit-tests-M20060629-1905.=
zip archive. Unpack this archive, this  will create "eclipse" directory. No=
w unpack Eclipse 3.2 archive to eclipse-testing directory (it will be unpac=
ked to eclipse-testing/eclipse directory that already exists, say  "Yes" to=
 overwrite whenever it asks).

3. Running the Test Suite from the command line
>From the eclipse-testing/eclipse directory, use the command:
${path.to.jre}/bin/java -jar startup.jar -application ${launcher} -dev bin =
formatter=3Dorg.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultForm=
atter,${log} -testpluginname ${plugin-name} -classname ${test-classname}

where ${launcher} is one of: org.eclipse.test.uitestapplication or org.ecli=
pse.test.coretestapplication depending on whether or not you need to run yo=
ur tests within an active Workbench (try both if there are any doubts).
${plugin-name} is one of:=20
org.eclipse.ant.tests.core, org.eclipse.ant.tests.ui, org.eclipse.compare.t=
ests, org.eclipse.core.expressions.tests, org.eclipse.core.tests.resources,=
 org.eclipse.core.tests.runtime, org.eclipse.core.filebuffers.tests, org.ec=
lipse.help.tests, org.eclipse.jdt.apt.tests, org.eclipse.jdt.core.tests.bui=
lder, org.eclipse.jdt.core.tests.compiler, org.eclipse.jdt.core.tests.model=
, org.eclipse.jdt.core.tests.performance, org.eclipse.jdt.debug.tests, org.=
eclipse.jdt.text.tests, org.eclipse.jdt.ui.tests, org.eclipse.jdt.ui.tests.=
refactoring, org.eclipse.jface.text.tests, org.eclipse.jface.tests.databind=
ing, org.eclipse.ltk.core.refactoring.tests, org.eclipse.ltk.ui.refactoring=
.tests, org.eclipse.osgi.tests, org.eclipse.pde.ui.tests, org.eclipse.relen=
g.tests, org.eclipse.swt.tests, org.eclipse.team.tests.core, org.eclipse.te=
am.tests.cvs.core, org.eclipse.text.tests, org.eclipse.ua.tests, org.eclips=
e.ui.tests, org.eclipse.ui.editors.tests, org.eclipse.ui.tests.navigator, o=
rg.eclipse.ui.tests.performance, org.eclipse.ui.tests.rcp, org.eclipse.ui.t=
ests.views.properties.tabbed, org.eclipse.ui.workbench.texteditor.tests, or=
g.eclipse.update.tests.core=20
${test-classname} is a full classname.
${log} is the path to the xml file with test suites results.

4. Running the Test Suite from Eclipse=20
Run Eclipse 3.2 installation that was setup during step 2 (eclipse-testing/=
eclipse), select new workspace directory. Then select menu "File"->"Import"=
, in  the newly appeared "Import"dialog expand "Plug-in Development", selec=
t "Plug-ins and Fragments", click  "Next" button. In the next dialog unchec=
k the checkbox "The target platform (as specified in the  preferences)", ma=
ke sure that Plug-in location is set to your Eclipse 3.2 location. Click "S=
ource code  locations" button. When "Preferences" dialog is opened, go to "=
Source code locations" tab, click "Add..."  button, and select the followin=
g location:
<patch to Eclipse 3.2>/plugins/org.eclipse.sdk.tests.source_3.2.0.v20060329=
/src
Click "Ok" to submit your selection, then click "Ok" to close "Preferences"=
 dialog. In the "Import Plug-ins and Fragments" dialog check "Import As Pro=
jects with source folders" checkbox. Then click "Next"  button in "Import P=
lug-ins and Fragments" dialog. In the next dialog ("Selection") select plug=
-in under test from the list and click "Add -->" button. Then click "Finish=
" button to  close the dialog.=20

Now the test suite 'ui' is imprted as an Eclipse project. You can expand th=
e project and see the sources in  "src-uitests" folder. I had to comment se=
veral lines in "plugin.xml" file because some extensions  descriptions prev=
ented the plug-in (test suite) from being correctly compiled.

When it shows no errors, select the project in "Package Explorer" view, the=
n go to menu "Run"->"Run...",  select "JUnit Plug-in Test", click "New" ico=
n (left top corner). In the "Run" dialog, "Test" tab check "Run  a single t=
est" and specify

Project: ${project-name}
Test class: ${launching-test-classname}

where ${launching-test-classname} might differ from the test class under te=
st, this is usually the class name that you find in test suite execution lo=
g in <testsuite/> line.
Then go to the "Main" tab, select "Run an application" checkbox and select =
"org.eclipse.ui.ide.workbench"  from the list. In the same tab click to "In=
stalled JREs" button in order to specify the path to Harmony JRE, then sele=
ct it as "Runtime JRE" and click "Run" button. In a minute the suite will b=
e launched and you will  have "Junit" view opened with test and testcases t=
ree. You can use this view to re-run one test class (or testcase) if  neces=
sary.=20

> [JDK][EUT] 2 tests fail in org.eclipse.jdt.ui.tests.all suit
> ------------------------------------------------------------
>
>                 Key: HARMONY-3391
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3391
>             Project: Harmony
>          Issue Type: Bug
>          Components: JDK
>            Reporter: Aleksey Ignatenko
>
> 2 tests fail in org.eclipse.jdt.ui.tests.all suit of EUT.
> <testcase classname=3D"org.eclipse.jdt.ui.tests.nls.NLSSourceModifierTest=
" name=3D"testBug95708_2" time=3D"0.625">
>       <failure message=3D"expected:&lt;...key_0;  private String str2=3DA=
ccessor.nls...&gt; but was:&lt;...nls_0;  private String str2=3DAccessor.ke=
y...&gt;"  type=3D"
> junit.framework.ComparisonFailure">junit.framework.ComparisonFailure: exp=
ected:&lt;...key_0;
>         private String str2=3DAccessor.nls...&gt; but was:&lt;...nls_0;
>         private String str2=3DAccessor.key...&gt;
>         at org.eclipse.jdt.ui.tests.nls.NLSSourceModifierTest.testBug9570=
8_2(NLSSourceModifierTest.java:858)
>         at java.lang.reflect.VMReflection.invokeMethod(VMReflection.java)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:18)
>         at junit.extensions.TestSetup.run(TestSetup.java:16)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:18)
>         at junit.extensions.TestSetup.run(TestSetup.java:16)
>         at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:=
326)
>         at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:=
203)
>         at org.eclipse.test.UITestApplication$3.run(UITestApplication.jav=
a:188)
>         at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
>         at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchron=
izer.java:121)
>         at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java)
>         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2=
971)
>         at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:=
1912)
>         at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1875)
>         at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbe=
nch.java:417)
>         at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.jav=
a)
>         at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.=
java:96)
>         at org.eclipse.test.UITestApplication.runApplication(UITestApplic=
ation.java:130)
>         at org.eclipse.test.UITestApplication.run(UITestApplication.java:=
55)
>         at org.eclipse.core.internal.runtime.PlatformActivator$1.run(Plat=
formActivator.java:77)
>         at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.r=
unApplication(EclipseAppLauncher.java:92)
>         at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.s=
tart(EclipseAppLauncher.java:66)
>         at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseSta=
rter.java:396)
>         at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseSta=
rter.java:176)
>         at java.lang.reflect.VMReflection.invokeMethod(VMReflection.java)
>         at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
>         at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
>         at org.eclipse.core.launcher.Main.run(Main.java:975)
>         at org.eclipse.core.launcher.Main.main(Main.java:952)
>         at java.lang.reflect.VMReflection.invokeMethod(VMReflection.java)
>         at org.apache.harmony.vm.JarRunner.main(JarRunner.java:80)
> </failure>

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.