Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] how to do automation test in the tycho context?

well, finally I got my tests running in tycho... :)

Just for the records...
The problem was that my POM-First bundle created by maven-bundle-plugin had an "org.hamcrest" on the Import-Package (automatically generated). But the Hamcrest bundle that I'm collecting from Orbit repository doesn't export this package, but org.hamcrest.core.

cheers

Cristiano

On 03/06/11 19:18, Cristiano Gavião wrote:
I couldn't understand you very well (maybe my poor english). But it seems that I have to define a target platform for test? If so, could you, please, point me how can I setup target platform for the integration tests ?

I really don't know what is happening here. I can install my projects nicely, my P2 repository is being create right now (without UI things), but I can't run the integration-test.

Tycho can't find some classes, and those were added to built repository. here is the log:

!SESSION 2011-06-03 18:53:10.218 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_24
java.vendor=Apple Inc.
BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US
Framework arguments: -application org.eclipse.tycho.surefire.osgibooter.headlesstest -testproperties /Users/cvgaviao/Development/Development_Projects/OPENSOURCE/jbehave-fork/jbehave-osgi/jbehave-osgi-equinox-commands.test/target/surefire.properties Command-line arguments: -debug -consolelog -data /Users/cvgaviao/Development/Development_Projects/OPENSOURCE/jbehave-fork/jbehave-osgi/jbehave-osgi-equinox-commands.test/target/work/data -dev file:/Users/cvgaviao/Development/Development_Projects/OPENSOURCE/jbehave-fork/jbehave-osgi/jbehave-osgi-equinox-commands.test/target/dev.properties -application org.eclipse.tycho.surefire.osgibooter.headlesstest -testproperties /Users/cvgaviao/Development/Development_Projects/OPENSOURCE/jbehave-fork/jbehave-osgi/jbehave-osgi-equinox-commands.test/target/surefire.properties

!ENTRY org.eclipse.osgi 2 0 2011-06-03 18:53:15.362
!MESSAGE One or more bundles are not resolved because the following root constraints are not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-06-03 18:53:15.362
!MESSAGE Bundle initial@reference:file:../../../../../../../../.m2/repository/org/jbehave/osgi/jbehave-osgi-services/1.0.0-SNAPSHOT/jbehave-osgi-services-1.0.0-SNAPSHOT.jar/ was not resolved. !SUBENTRY 2 org.jbehave.osgi.jbehave-osgi-services 2 0 2011-06-03 18:53:15.362
!MESSAGE Missing imported package org.hamcrest_0.0.0.

!ENTRY org.eclipse.osgi 2 0 2011-06-03 18:53:15.374
!MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-06-03 18:53:15.375
!MESSAGE Bundle org.jbehave.osgi.jbehave-osgi-services_1.0.0.SNAPSHOT [8] was not resolved. !SUBENTRY 2 org.jbehave.osgi.jbehave-osgi-services 2 0 2011-06-03 18:53:15.375
!MESSAGE Missing imported package org.hamcrest_0.0.0.
!SUBENTRY 2 org.jbehave.osgi.jbehave-osgi-services 2 0 2011-06-03 18:53:15.375
!MESSAGE Missing imported package org.jbehave.osgi.services_0.0.0.
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-06-03 18:53:15.375
!MESSAGE Bundle org.jbehave.osgi.equinox.commands.test_1.0.0.qualifier [12] was not resolved. !SUBENTRY 2 org.jbehave.osgi.equinox.commands.test 2 0 2011-06-03 18:53:15.375
!MESSAGE Missing host org.jbehave.osgi.equinox.commands_0.0.0.
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-06-03 18:53:15.376
!MESSAGE Bundle org.jbehave.osgi.equinox.commands_1.0.0.201106031853 [59] was not resolved.
!SUBENTRY 2 org.jbehave.osgi.equinox.commands 2 0 2011-06-03 18:53:15.376
!MESSAGE Missing required bundle org.jbehave.osgi.jbehave-osgi-services_1.0.0.

!ENTRY org.eclipse.osgi 2 0 2011-06-03 18:53:15.457
!MESSAGE One or more bundles are not resolved because the following root constraints are not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-06-03 18:53:15.458
!MESSAGE Bundle initial@reference:file:../../../../../../../../.m2/repository/org/jbehave/osgi/jbehave-osgi-services/1.0.0-SNAPSHOT/jbehave-osgi-services-1.0.0-SNAPSHOT.jar/ was not resolved. !SUBENTRY 2 org.jbehave.osgi.jbehave-osgi-services 2 0 2011-06-03 18:53:15.458
!MESSAGE Missing imported package org.hamcrest_0.0.0.

!ENTRY org.eclipse.osgi 2 0 2011-06-03 18:53:15.472
!MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-06-03 18:53:15.472
!MESSAGE Bundle org.jbehave.osgi.jbehave-osgi-services_1.0.0.SNAPSHOT [8] was not resolved. !SUBENTRY 2 org.jbehave.osgi.jbehave-osgi-services 2 0 2011-06-03 18:53:15.473
!MESSAGE Missing imported package org.hamcrest_0.0.0.
!SUBENTRY 2 org.jbehave.osgi.jbehave-osgi-services 2 0 2011-06-03 18:53:15.473
!MESSAGE Missing imported package org.jbehave.osgi.services_0.0.0.
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-06-03 18:53:15.473
!MESSAGE Bundle org.jbehave.osgi.equinox.commands.test_1.0.0.qualifier [12] was not resolved. !SUBENTRY 2 org.jbehave.osgi.equinox.commands.test 2 0 2011-06-03 18:53:15.473
!MESSAGE Missing host org.jbehave.osgi.equinox.commands_0.0.0.
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-06-03 18:53:15.473
!MESSAGE Bundle org.jbehave.osgi.equinox.commands_1.0.0.201106031853 [59] was not resolved.
!SUBENTRY 2 org.jbehave.osgi.equinox.commands 2 0 2011-06-03 18:53:15.474
!MESSAGE Missing required bundle org.jbehave.osgi.jbehave-osgi-services_1.0.0.

!ENTRY org.eclipse.osgi 4 0 2011-06-03 18:53:15.474
!MESSAGE Application error
!STACK 1
java.lang.RuntimeException: Bundle org.jbehave.osgi.equinox.commands.test is not found at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.getBundleClassLoader(OsgiSurefireBooter.java:120) at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:48) at org.eclipse.tycho.surefire.osgibooter.HeadlessTestApplication.run(HeadlessTestApplication.java:21)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
    at org.eclipse.equinox.launcher.Main.main(Main.java:1386)

!ENTRY org.eclipse.osgi 2 0 2011-06-03 18:53:15.481
!MESSAGE Info: cycle(s) found while stopping bundles: [[org.slf4j.api,ch.qos.logback.slf4j,ch.qos.logback.classic]].


thanks

Cristiano


On 03/06/11 09:56, Igor Fedorenko wrote:
IIFC, .target fully defines project compile and test target platrform
defines and it is as is, i.e. nothing added or removed (normal platform
filtering still takes place, of course).

There are special provisions in Eclipse Workbench to run tests that
require user interface and useUIHarness=true enables this. This has the
same effect as checking "Run In UI thread" in PDE launch configuration
dialog.

--
Regards,
Igor

On 11-06-02 1:35 PM, Cristiano Gavião wrote:
Hi Igor,

I'm learning how to test with tycho too.

Some doubts, in my case I've created a Target Definition and have set it
on target-platform-configuration.

So, should I infer that all the bundles in this file definition plus the
ones that I'm building will be installed and started (following the
definition) and be available to my test classes in integration-test phase?

In your example there is a <useUIHarness>true</useUIHarness>. What this
means ? If I'm using equinox without ui should I set it to false or just
remove it?

thanks a lot

Cristiano

On 02/06/11 10:44, Igor Fedorenko wrote:
You can find basic test bundle as part of tycho demo projects [1]

[1]
https://github.com/sonatype/sonatype-tycho/tree/master/tycho-demo/itp01

--
Regards,
Igor

On 10-05-31 4:39 AM, oliver_tech wrote:
hi,everyone
i have use tycho build all my plugins successfully, it's very friendly
to use tycho,great!
now i want write do some tests, anyone can introduce me how to start
wirte unit test for eclipse plugins?
it's better introduce me some opensource plugin projects which using
tycho (or other tech ) to do test
thank you very much!
2010-05-31
------------------------------------------------------------------------
oliver_tech



_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user

_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user




Back to the top