You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Stefan Seelmann <se...@apache.org> on 2008/06/08 15:07:51 UTC
Re: [Studio] Framework for Integration Tests
Hi,
here is an update.
I finished the integration testing framework for Studio and I'm going to
merge it into trunk soon.
How to use it:
1)
Building Studio with maven from command line works like before, there is
no change to the current process.
2)
To run the integration test with maven from command line you need a
local installation of Eclipse and to set a eclipse-home property that
points to the Eclipse installation path, see [1]
Then the tests could be started with
- Core tests only: mvn -Pintegration-core test
- UI tests only: mvn -Pintegration-ui test
- Core and UI tests: mvn -Pintegration-core,integration-ui test
When running the tests all relevant plugins are copied from different
locations to the "test-sandbox":
- from a previous "mvn install" the complete Studio distribution
- from the resource folder the SWTBot plugins
- the test-integration-[core|ui] plugin itself
- some additional plugins from the local eclipse installation
Then the tests are lauched.
3)
For development you need to install the SWTBot plugins because the
test-integration-ui plugin depends on the SWTBot plugins [2]. I added
two launch configurations that could be used to launch the tests within
Eclipse.
The next step is to create some more tests :-)
Kind Regards,
Stefan
[1] http://directory.apache.org/studio/building.html
[2] http://directory.apache.org/studio/working.html
Stefan Seelmann wrote:
> Hi Dev,
>
> I am working on a framework for integration tests for studio. I added
> two plugins into my sandbox, one for core and one for UI tests.
>
>
> Core Integration Tests
> ----------------------
>
> The core tests don't depend on any UI code, but on the Eclipse runtime.
> So it is necessary to startup Eclipse in headless mode, then it is
> possible to access things like Jobs, Preferences, etc.
>
> It is already possible to run these test within eclipse or from maven.
> However in the maven pom there are some fixed paths, I need to remove
> them, maybe I need some help from a maven guru.
>
>
> UI Integration Tests
> --------------------
>
> For UI test I selected SWTBot (http://www.swtbot.org). There are still
> some features missing in the current version 0.2, but it looks very
> stable and the API is very easy to use. An UI-Recorder is under
> development. Last not least it is licenced under ASLv2.
>
> Here is an example how a test looks like: http://tinyurl.com/3j5ujs
> It opens the New Connection wizard, enters all connection parameters,
> does some checks and closes the connection.
>
> There are some open issues:
>
> 1) We have to extend SWTBot, I already contacted the author that I am
> interested in contributing.
>
> 2) SWTBot depends on many Eclipse plugins. To run the tests from maven
> we need to add about 50MB of plugins to our repository. Atm I just have
> a tarball containing all these plugins, but I don't want to commit them
> to svn.
>
>
> I'll keep you informed.
>
>
> Kind Regards,
> Stefan Seelmann
Re: [Studio] Framework for Integration Tests
Posted by Emmanuel Lecharny <el...@apache.org>.
Stefan Seelmann wrote:
> Hi,
>
> here is an update.
>
Stefan, I just looked at the new tool you just committed on
Pierre-Arnaud computer, and I must say that it's just great !
Thanks !
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
Re: [Studio] Framework for Integration Tests
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
For the record, here's the crash report:
********************************************************************************
Process: java [360]
Path:
/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/java
Identifier: java
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: java [326]
Date/Time: 2008-06-09 16:03:24.904 +0200
OS Version: Mac OS X 10.5.3 (9D34)
Report Version: 6
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: 0x000000000000000d, 0x0000000000000000
Crashed Thread: 0
Thread 0 Crashed:
0 libclient.dylib 0x003c66f0 0x3b9000 + 55024
1 libclient.dylib 0x003c63cb 0x3b9000 + 54219
2 libclient.dylib 0x005af9ff JNI_CreateJavaVM_Impl + 959
3 libswt-carbon-3349.jnilib 0x1d7a6d81 callback + 317
4 ??? 0x1d798655 0 + 494503509
5 com.apple.CoreFoundation 0x962f39a2 __CFRunLoopDoObservers +
466
6 com.apple.CoreFoundation 0x962f5414 CFRunLoopRunSpecific + 2660
7 com.apple.CoreFoundation 0x962f5cf8 CFRunLoopRunInMode + 88
8 java 0x0000513e 0x1000 + 16702
9 java 0x0000258a 0x1000 + 5514
Thread 1:
0 dyld 0x8fe21eeb strcpy + 107
1 libSystem.B.dylib 0x9683b60b dlsym + 85
2 libjava.jnilib 0x000483d5
Java_java_lang_ClassLoader_00024NativeLibrary_find + 122
3 ??? 0x035859b1 0 + 56121777
4 ??? 0x0357fa54 0 + 56097364
5 ??? 0x0357d227 0 + 56087079
6 libclient.dylib 0x004d263a 0x3b9000 + 1152570
7 libclient.dylib 0x004d9e53 0x3b9000 + 1183315
8 libclient.dylib 0x004d9db2 0x3b9000 + 1183154
9 libclient.dylib 0x004abd35 0x3b9000 + 994613
10 libclient.dylib 0x004ab2be 0x3b9000 + 991934
11 libclient.dylib 0x004ab113 0x3b9000 + 991507
12 libclient.dylib 0x004d5ce5 0x3b9000 + 1166565
13 ??? 0x03585881 0 + 56121473
14 ??? 0x0357fa7f 0 + 56097407
15 ??? 0x0357f9d3 0 + 56097235
16 ??? 0x0357f9d3 0 + 56097235
17 ??? 0x0357f9d3 0 + 56097235
18 ??? 0x0357f9d3 0 + 56097235
19 ??? 0x0357f9d3 0 + 56097235
20 ??? 0x0357faaa 0 + 56097450
21 ??? 0x0357faaa 0 + 56097450
22 ??? 0x0357faaa 0 + 56097450
23 ??? 0x0357fdb0 0 + 56098224
24 ??? 0x0357faaa 0 + 56097450
25 ??? 0x0357faaa 0 + 56097450
26 ??? 0x0357fdb0 0 + 56098224
27 ??? 0x0357fdb0 0 + 56098224
28 ??? 0x0357faaa 0 + 56097450
29 ??? 0x0357faaa 0 + 56097450
30 ??? 0x0357faaa 0 + 56097450
31 ??? 0x0357d227 0 + 56087079
32 libclient.dylib 0x004d263a 0x3b9000 + 1152570
33 libclient.dylib 0x004d2356 0x3b9000 + 1151830
34 libclient.dylib 0x004744b1 0x3b9000 + 767153
35 libclient.dylib 0x00490e4f 0x3b9000 + 884303
36 libclient.dylib 0x0060f78b JVM_InvokeMethod + 411
37 ??? 0x035859b1 0 + 56121777
38 ??? 0x0357faaa 0 + 56097450
39 ??? 0x0357faaa 0 + 56097450
40 ??? 0x0357fdb0 0 + 56098224
41 ??? 0x0357faaa 0 + 56097450
42 ??? 0x0357f9d3 0 + 56097235
43 ??? 0x0357f9d3 0 + 56097235
44 ??? 0x0357fa7f 0 + 56097407
45 ??? 0x0357f9d3 0 + 56097235
46 ??? 0x0357d227 0 + 56087079
47 libclient.dylib 0x004d263a 0x3b9000 + 1152570
48 libclient.dylib 0x004d2356 0x3b9000 + 1151830
49 libclient.dylib 0x00470422 0x3b9000 + 750626
50 libclient.dylib 0x005cfa70 JNI_CreateJavaVM_Impl +
132144
51 java 0x00002633 0x1000 + 5683
52 java 0x00004485 0x1000 + 13445
53 java 0x00004d3b 0x1000 + 15675
54 libSystem.B.dylib 0x968406f5 _pthread_start + 321
55 libSystem.B.dylib 0x968405b2 thread_start + 34
Thread 2:
0 libSystem.B.dylib 0x9680f4a6 mach_msg_trap + 10
1 libSystem.B.dylib 0x96816c9c mach_msg + 72
2 libSystem.B.dylib 0x96884f67 mach_msg_server + 491
3 libclient.dylib 0x003c7ed5 0x3b9000 + 61141
4 libclient.dylib 0x003c7c95 0x3b9000 + 60565
5 libclient.dylib 0x0067dcc5 JVM_RaiseSignal + 441189
6 libSystem.B.dylib 0x9688bfef _pthread_body + 27
Thread 3:
0 libSystem.B.dylib 0x9680f4a6 mach_msg_trap + 10
1 libSystem.B.dylib 0x96816c9c mach_msg + 72
2 libclient.dylib 0x004d1563 0x3b9000 + 1148259
3 libclient.dylib 0x004d13fc 0x3b9000 + 1147900
4 libclient.dylib 0x004161ed 0x3b9000 + 381421
5 libclient.dylib 0x00415d57 0x3b9000 + 380247
6 libclient.dylib 0x0067dcc5 JVM_RaiseSignal + 441189
7 libSystem.B.dylib 0x9688bfef _pthread_body + 27
Thread 4:
0 libSystem.B.dylib 0x9680f4a6 mach_msg_trap + 10
1 libSystem.B.dylib 0x96816c9c mach_msg + 72
2 libclient.dylib 0x004d161a 0x3b9000 + 1148442
3 libclient.dylib 0x0041728a 0x3b9000 + 385674
4 libclient.dylib 0x00416875 0x3b9000 + 383093
5 libclient.dylib 0x005f8201 JVM_MonitorWait + 465
6 ??? 0x035859b1 0 + 56121777
7 ??? 0x0357f9d3 0 + 56097235
8 ??? 0x0357f9d3 0 + 56097235
9 ??? 0x0357d227 0 + 56087079
10 libclient.dylib 0x004d263a 0x3b9000 + 1152570
11 libclient.dylib 0x00416763 0x3b9000 + 382819
12 libclient.dylib 0x00416655 0x3b9000 + 382549
13 libclient.dylib 0x00416595 0x3b9000 + 382357
14 libclient.dylib 0x004164b8 0x3b9000 + 382136
15 libclient.dylib 0x0067dcc5 JVM_RaiseSignal + 441189
16 libSystem.B.dylib 0x9688bfef _pthread_body + 27
Thread 5:
0 libSystem.B.dylib 0x9680f4a6 mach_msg_trap + 10
1 libSystem.B.dylib 0x96816c9c mach_msg + 72
2 libclient.dylib 0x004d161a 0x3b9000 + 1148442
3 libclient.dylib 0x0041728a 0x3b9000 + 385674
4 libclient.dylib 0x00416875 0x3b9000 + 383093
5 libclient.dylib 0x005f8201 JVM_MonitorWait + 465
6 ??? 0x035859b1 0 + 56121777
7 ??? 0x03719184 0 + 57774468
8 ??? 0x03718f4c 0 + 57773900
9 ??? 0x035f1dc0 0 + 56565184
10 ??? 0x0357faaa 0 + 56097450
11 ??? 0x0357d227 0 + 56087079
12 libclient.dylib 0x004d263a 0x3b9000 + 1152570
13 libclient.dylib 0x00416763 0x3b9000 + 382819
14 libclient.dylib 0x00416655 0x3b9000 + 382549
15 libclient.dylib 0x00416595 0x3b9000 + 382357
16 libclient.dylib 0x004164b8 0x3b9000 + 382136
17 libclient.dylib 0x0067dcc5 JVM_RaiseSignal + 441189
18 libSystem.B.dylib 0x9688bfef _pthread_body + 27
Thread 6:
0 libSystem.B.dylib 0x9680f4e2 semaphore_wait_trap + 10
1 libclient.dylib 0x004179ae 0x3b9000 + 387502
2 libclient.dylib 0x00417695 0x3b9000 + 386709
3 libclient.dylib 0x004164b8 0x3b9000 + 382136
4 libclient.dylib 0x0067dcc5 JVM_RaiseSignal + 441189
5 libSystem.B.dylib 0x9688bfef _pthread_body + 27
Thread 7:
0 libSystem.B.dylib 0x9680f4a6 mach_msg_trap + 10
1 libSystem.B.dylib 0x96816c9c mach_msg + 72
2 libclient.dylib 0x004d161a 0x3b9000 + 1148442
3 libclient.dylib 0x004d12b9 0x3b9000 + 1147577
4 libclient.dylib 0x00417fdb 0x3b9000 + 389083
5 libclient.dylib 0x00417cb8 0x3b9000 + 388280
6 libclient.dylib 0x004164b8 0x3b9000 + 382136
7 libclient.dylib 0x0067dcc5 JVM_RaiseSignal + 441189
8 libSystem.B.dylib 0x9688bfef _pthread_body + 27
Thread 8:
0 libSystem.B.dylib 0x9680f4a6 mach_msg_trap + 10
1 libSystem.B.dylib 0x96816c9c mach_msg + 72
2 libclient.dylib 0x004d161a 0x3b9000 + 1148442
3 libclient.dylib 0x004d13fc 0x3b9000 + 1147900
4 libclient.dylib 0x004180f0 0x3b9000 + 389360
5 libclient.dylib 0x004164b8 0x3b9000 + 382136
6 libclient.dylib 0x0067dcc5 JVM_RaiseSignal + 441189
7 libSystem.B.dylib 0x9688bfef _pthread_body + 27
Thread 9:
0 libSystem.B.dylib 0x9680f4a6 mach_msg_trap + 10
1 libSystem.B.dylib 0x96816c9c mach_msg + 72
2 libclient.dylib 0x004d1563 0x3b9000 + 1148259
3 libclient.dylib 0x0041890f 0x3b9000 + 391439
4 libclient.dylib 0x0041845a 0x3b9000 + 390234
5 libclient.dylib 0x0067dcc5 JVM_RaiseSignal + 441189
6 libSystem.B.dylib 0x9688bfef _pthread_body + 27
Thread 10:
0 libSystem.B.dylib 0x9680f4a6 mach_msg_trap + 10
1 libSystem.B.dylib 0x96816c9c mach_msg + 72
2 libclient.dylib 0x004d161a 0x3b9000 + 1148442
3 libclient.dylib 0x0041728a 0x3b9000 + 385674
4 libclient.dylib 0x00416875 0x3b9000 + 383093
5 libclient.dylib 0x005f8201 JVM_MonitorWait + 465
6 ??? 0x035859b1 0 + 56121777
7 ??? 0x0357f9d3 0 + 56097235
8 ??? 0x0357f9d3 0 + 56097235
9 ??? 0x0357faaa 0 + 56097450
10 ??? 0x0357d227 0 + 56087079
11 libclient.dylib 0x004d263a 0x3b9000 + 1152570
12 libclient.dylib 0x00416763 0x3b9000 + 382819
13 libclient.dylib 0x00416655 0x3b9000 + 382549
14 libclient.dylib 0x00416595 0x3b9000 + 382357
15 libclient.dylib 0x004164b8 0x3b9000 + 382136
16 libclient.dylib 0x0067dcc5 JVM_RaiseSignal + 441189
17 libSystem.B.dylib 0x9688bfef _pthread_body + 27
Thread 11:
0 libSystem.B.dylib 0x9680f4a6 mach_msg_trap + 10
1 libSystem.B.dylib 0x96816c9c mach_msg + 72
2 libclient.dylib 0x004d1563 0x3b9000 + 1148259
3 libclient.dylib 0x0041728a 0x3b9000 + 385674
4 libclient.dylib 0x00416875 0x3b9000 + 383093
5 libclient.dylib 0x005f8201 JVM_MonitorWait + 465
6 ??? 0x035859b1 0 + 56121777
7 ??? 0x0357f9d3 0 + 56097235
8 ??? 0x0357fcd9 0 + 56098009
9 ??? 0x0357d227 0 + 56087079
10 libclient.dylib 0x004d263a 0x3b9000 + 1152570
11 libclient.dylib 0x00416763 0x3b9000 + 382819
12 libclient.dylib 0x00416655 0x3b9000 + 382549
13 libclient.dylib 0x00416595 0x3b9000 + 382357
14 libclient.dylib 0x004164b8 0x3b9000 + 382136
15 libclient.dylib 0x0067dcc5 JVM_RaiseSignal + 441189
16 libSystem.B.dylib 0x9688bfef _pthread_body + 27
Thread 12:
0 libSystem.B.dylib 0x9680f4a6 mach_msg_trap + 10
1 libSystem.B.dylib 0x96816c9c mach_msg + 72
2 libclient.dylib 0x004d161a 0x3b9000 + 1148442
3 libclient.dylib 0x0041728a 0x3b9000 + 385674
4 libclient.dylib 0x00416875 0x3b9000 + 383093
5 libclient.dylib 0x005f8201 JVM_MonitorWait + 465
6 ??? 0x035859b1 0 + 56121777
7 ??? 0x0357f9d3 0 + 56097235
8 ??? 0x0357f9d3 0 + 56097235
9 ??? 0x0357faaa 0 + 56097450
10 ??? 0x0357d227 0 + 56087079
11 libclient.dylib 0x004d263a 0x3b9000 + 1152570
12 libclient.dylib 0x00416763 0x3b9000 + 382819
13 libclient.dylib 0x00416655 0x3b9000 + 382549
14 libclient.dylib 0x00416595 0x3b9000 + 382357
15 libclient.dylib 0x004164b8 0x3b9000 + 382136
16 libclient.dylib 0x0067dcc5 JVM_RaiseSignal + 441189
17 libSystem.B.dylib 0x9688bfef _pthread_body + 27
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x80020000 ebx: 0x003c668e ecx: 0x00000002 edx: 0x8000ffdc
edi: 0x01025210 esi: 0x0102524c ebp: 0xbfffea80 esp: 0xbfffea38
ss: 0x0000001f efl: 0x00010a87 eip: 0x003c66f0 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x210aa61a
Binary Images:
0x1000 - 0xaff0 java ??? (???) <d6497b1474b7ff34e83c58522f253969>
/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/java
0x11000 - 0x16ffd com.apple.JavaVM 12.1.0 (12.1.0)
<25c546c36e5bed978579d281080ab4c8>
/System/Library/Frameworks/JavaVM.framework/Versions/A/JavaVM
0x39000 - 0x40fe0 libverify.dylib ??? (???)
<7a69785e6278690ecba70a4ec32d732a>
/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Libraries/libverify.dylib
0x46000 - 0x60fef libjava.jnilib ??? (???)
<42b19094a14d6f296d7186946847ce86>
/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Libraries/libjava.jnilib
0x6e000 - 0x79ffb libzip.jnilib ??? (???)
<8d58d4a6b64d83d08732a310918c7f5a>
/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Libraries/libzip.jnilib
0x3b9000 - 0x708ffb libclient.dylib ??? (???)
<5bd51fa3ce82d6e1bd1582f46b2b8bac>
/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Libraries/libclient.dylib
0x17d8000 - 0x17e3ffb libnet.jnilib ??? (???)
<d6087c096127755a3769819c04fe6a19>
/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Libraries/libnet.jnilib
0x60c8000 - 0x60cbffc libnio.jnilib ??? (???)
<57a95ec155863e0a0e7b2636d7c461f2>
/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Libraries/libnio.jnilib
0x6122000 - 0x6129fff +eclipse_1023.so ??? (???)
/Users/pajbam/Development/Apache/Studio/test-integration-ui/target/test-sandbox/Apache
Directory
Studio.app/Contents/Resources/Java/plugins/org.eclipse.equinox.launcher.carbon.macosx_1.0.3.R33x_v20080118/eclipse_1023.so
0x1d7a4000 - 0x1d7a6ffd +libswt-carbon-3349.jnilib ??? (???)
/Users/pajbam/Development/Apache/Studio/test-integration-ui/target/test-sandbox/Apache
Directory
Studio.app/Contents/Resources/Java/configuration/org.eclipse.osgi/bundles/106/1/.cp/libswt-carbon-3349.jnilib
0x1d7aa000 - 0x1d7dcfff +libswt-pi-carbon-3349.jnilib ??? (???)
/Users/pajbam/Development/Apache/Studio/test-integration-ui/target/test-sandbox/Apache
Directory
Studio.app/Contents/Resources/Java/configuration/org.eclipse.osgi/bundles/106/1/.cp/libswt-pi-carbon-3349.jnilib
0x8fe00000 - 0x8fe2da53 dyld 96.2 (???) <7af47d3b00b2268947563c7fa8c59a07>
/usr/lib/dyld
0x9007e000 - 0x900a6ff7 com.apple.shortcut 1 (1.0)
<057783867138902b52bc0941fedb74d1>
/System/Library/PrivateFrameworks/Shortcut.framework/Versions/A/Shortcut
0x900a7000 - 0x900edfef com.apple.Metadata 10.5.2 (398.18)
<adbb3a14e8f7da444e16d2fd61862771>
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
0x900ee000 - 0x900eeffd com.apple.Accelerate.vecLib 3.4.2 (vecLib 3.4.2)
/System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
0x900ef000 - 0x9016bfeb com.apple.audio.CoreAudio 3.1.0 (3.1)
<70bb7c657061631491029a61babe0b26>
/System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x9016c000 - 0x90173ff7 libCGATS.A.dylib ??? (???)
<9b29a5500efe01cc3adea67bbc42568e>
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGATS.A.dylib
0x902ef000 - 0x902f3fff libGIF.dylib ??? (???)
<d4234e6f5e5f530bdafb969157f1f17b>
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
0x902f4000 - 0x902fbffe libbsm.dylib ??? (???)
<d25c63378a5029648ffd4b4669be31bf> /usr/lib/libbsm.dylib
0x902fc000 - 0x9031bffa libJPEG.dylib ??? (???)
<0cfb80109d624beb9ceb3c43b6c5ec10>
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x9031c000 - 0x90396ff8 com.apple.print.framework.PrintCore 5.5.3 (245.3)
<222dade7b33b99708b8c09d1303f93fc>
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
0x90517000 - 0x9051ffff com.apple.DiskArbitration 2.2.1 (2.2.1)
<75b0c8d8940a8a27816961dddcac8e0f>
/System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x90520000 - 0x90548fff libcups.2.dylib ??? (???)
<ece20dff2a2c8ed3ae6ef735ef440c37> /usr/lib/libcups.2.dylib
0x9054a000 - 0x90555ff9 com.apple.helpdata 1.0 (14)
/System/Library/PrivateFrameworks/HelpData.framework/Versions/A/HelpData
0x90556000 - 0x90a29ffe libGLProgrammability.dylib ??? (???)
<475db64244e011cd8811e076035b2632>
/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib
0x90a2a000 - 0x90abdfff com.apple.ink.framework 101.3 (86)
<bf3fa8927b4b8baae92381a976fd2079>
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
0x90abe000 - 0x90d98ff3 com.apple.CoreServices.CarbonCore 786.4 (786.4)
<059c4803a7a95e3c1a95a332baeb1edf>
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
0x90d99000 - 0x90e18ff5 com.apple.SearchKit 1.2.0 (1.2.0)
<277b460da86bc222785159fe77e2e2ed>
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
0x9113a000 - 0x91140fff com.apple.print.framework.Print 218.0.2 (220.1)
<8bf7ef71216376d12fcd5ec17e43742c>
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print
0x91141000 - 0x91148fe9 libgcc_s.1.dylib ??? (???)
<f53c808e87d1184c0f9df63aef53ce0b> /usr/lib/libgcc_s.1.dylib
0x91153000 - 0x9128bff7 libicucore.A.dylib ??? (???)
<5031226ea28b371d8dfdbb32acfb48b5> /usr/lib/libicucore.A.dylib
0x912bc000 - 0x91318ff7 com.apple.htmlrendering 68 (1.1.3)
<fe87a9dede38db00e6c8949942c6bd4f>
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering.framework/Versions/A/HTMLRendering
0x9134b000 - 0x915c6fe7 com.apple.Foundation 6.5.5 (677.19)
<bfd4ebea1a7739dd6b523f15dca01a37>
/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x915c7000 - 0x915c9ff5 libRadiance.dylib ??? (???)
<20eadb285da83df96c795c2c5fa20590>
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
0x9160d000 - 0x91617feb com.apple.audio.SoundManager 3.9.2 (3.9.2)
<0f2ba6e891d3761212cf5a5e6134d683>
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.framework/Versions/A/CarbonSound
0x91818000 - 0x9189fff7 libsqlite3.0.dylib ??? (???)
<6978bbcca4277d6ae9f042beff643f7d> /usr/lib/libsqlite3.0.dylib
0x92fa2000 - 0x92fcdfe7 libauto.dylib ??? (???)
<42d8422dc23a18071869fdf7b5d8fab5> /usr/lib/libauto.dylib
0x92fcf000 - 0x92ff3fff libxslt.1.dylib ??? (???)
<4933ddc7f6618743197aadc85b33b5ab> /usr/lib/libxslt.1.dylib
0x92ff4000 - 0x92ff7fff com.apple.help 1.1 (36)
<b507b08e484cb89033e9cf23062d77de>
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help
0x930c1000 - 0x93207ff7 com.apple.ImageIO.framework 2.0.2 (2.0.2)
<77dfee73f4c0d230425a5151ee0bce05>
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO
0x93208000 - 0x93292fe3 com.apple.DesktopServices 1.4.6 (1.4.6)
<94d1a28b351b7dff77becadab0967772>
/System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv
0x93293000 - 0x9335aff2 com.apple.vImage 3.0 (3.0)
/System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
0x9335b000 - 0x9335dfff com.apple.securityhi 3.0 (30817)
<2b2854123fed609d1820d2779e2e0963>
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI
0x9335e000 - 0x939fafff com.apple.CoreGraphics 1.351.31 (???)
<c97a42498636b2596764e48669f98e00>
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
0x939fb000 - 0x93a11fe7 com.apple.CoreVideo 1.5.0 (1.5.0)
<bad2d3a9a92fdecd02e64f0b73a76f27>
/System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x93a12000 - 0x93a17fff com.apple.CommonPanels 1.2.4 (85)
<ea0665f57cd267609466ed8b2b20e893>
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels
0x93a18000 - 0x93af9ff7 libxml2.2.dylib ??? (???)
<1baef3d4972ee789d8fa6c1fa44da45c> /usr/lib/libxml2.2.dylib
0x93bc1000 - 0x93bd5ff3 com.apple.ImageCapture 4.0 (5.0.0)
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture
0x93bd6000 - 0x93c26ff7 com.apple.HIServices 1.7.0 (???)
<f7e78891a6d08265c83dca8e378be1ea>
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
0x93c27000 - 0x93c84ffb libstdc++.6.dylib ??? (???)
<04b812dcec670daa8b7d2852ab14be60> /usr/lib/libstdc++.6.dylib
0x93c85000 - 0x93d6aff3 com.apple.CoreData 100.1 (186)
<8e28162ef2288692615b52acc01f8b54>
/System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x93de3000 - 0x93e3dff7 com.apple.CoreText 2.0.2 (???)
<9fde11f84a72e890bbf2aa8b0b13b79a>
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreText.framework/Versions/A/CoreText
0x93e3e000 - 0x941d4fff com.apple.QuartzCore 1.5.3 (1.5.3)
<1b65c05f89e81a499302fd63295b242d>
/System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x941dd000 - 0x9420cfe3 com.apple.AE 402.2 (402.2)
<e01596187e91af5d48653920017b8c8e>
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
0x9420d000 - 0x9424ffef com.apple.NavigationServices 3.5.2 (163)
<91844980804067b07a0b6124310d3f31>
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationServices.framework/Versions/A/NavigationServices
0x94250000 - 0x9432ffff libobjc.A.dylib ??? (???)
<a53206274b6c2d42691f677863f379ae> /usr/lib/libobjc.A.dylib
0x94346000 - 0x94346ff8 com.apple.ApplicationServices 34 (34)
<8f910fa65f01d401ad8d04cc933cf887>
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
0x94347000 - 0x94350fff com.apple.speech.recognition.framework 3.7.24
(3.7.24) <d3180f9edbd9a5e6f283d6156aa3c602>
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
0x94376000 - 0x943b5fef libTIFF.dylib ??? (???)
<6d0f80e9d4d81f3f64c876aca005bd53>
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
0x943b6000 - 0x943c6fff com.apple.speech.synthesis.framework 3.7.1 (3.7.1)
<06d8fc0307314f8ffc16f206ad3dbf44>
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x943c7000 - 0x943e2ff3 libPng.dylib ??? (???)
<c0484bec6e2432b406755591924fe664>
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
0x943e3000 - 0x944aefff com.apple.ColorSync 4.5.0 (4.5.0)
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync
0x944af000 - 0x9453bff7 com.apple.LaunchServices 289.2 (289.2)
<3577886e3a6d56ee3949850c4fde76c9>
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
0x9457a000 - 0x94588ffd libz.1.dylib ??? (???)
<5ddd8539ae2ebfd8e7cc1c57525385c7> /usr/lib/libz.1.dylib
0x945d9000 - 0x945ddfff libmathCommon.A.dylib ??? (???)
/usr/lib/system/libmathCommon.A.dylib
0x945de000 - 0x945deffa com.apple.CoreServices 32 (32)
<2fcc8f3bd5bbfc000b476cad8e6a3dd2>
/System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x9461e000 - 0x9462effc com.apple.LangAnalysis 1.6.4 (1.6.4)
<cbeb17ab39f28351fe2ab5b82bf465bc>
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
0x9462f000 - 0x94e2cfef com.apple.AppKit 6.5.3 (949.33)
<84b236f43802f4c15011513d18efa101>
/System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x94e2d000 - 0x94e2dfff com.apple.Carbon 136 (136)
<98a5e3bc0c4fa44bbb09713bb88707fe>
/System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x94e2e000 - 0x94ec1ff3 com.apple.ApplicationServices.ATS 3.3 (???)
<064eb6d96417afa38a80b1735c4113aa>
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
0x94f5c000 - 0x9500effb libcrypto.0.9.7.dylib ??? (???)
<330b0e48e67faffc8c22dfc069ca7a47> /usr/lib/libcrypto.0.9.7.dylib
0x95237000 - 0x95404fe7 com.apple.security 5.0.3 (33532)
<3bef414f3c6f433e707ac5abee340e16>
/System/Library/Frameworks/Security.framework/Versions/A/Security
0x95405000 - 0x9541bfff com.apple.DictionaryServices 1.0.0 (1.0.0)
<ad0aa0252e3323d182e17f50defe56fc>
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
0x9542e000 - 0x9546cff7 libGLImage.dylib ??? (???)
<093b1b698ca93a0380f5fa262459ea28>
/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
0x95503000 - 0x958c1fea libLAPACK.dylib ??? (???)
/System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
0x958c8000 - 0x958fffff com.apple.SystemConfiguration 1.9.2 (1.9.2)
<8b26ebf26a009a098484f1ed01ec499c>
/System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
0x95900000 - 0x95959ff7 libGLU.dylib ??? (???)
/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
0x95bea000 - 0x95c6cffb com.apple.CFNetwork 330 (330)
<6c5eda16e640b09334809ba4c1df985d>
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
0x95c6d000 - 0x95cf8fff com.apple.framework.IOKit 1.5.1 (???)
<60cfc4b175c4ef60bb8e9036716a29f4>
/System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x95cf9000 - 0x95cf9ffd com.apple.Accelerate 1.4.2 (Accelerate 1.4.2)
/System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x95cfa000 - 0x95d18fff libresolv.9.dylib ??? (???)
<0629b6dcd71f4aac6a891cbe26253e85> /usr/lib/libresolv.9.dylib
0x95d19000 - 0x96129fef libBLAS.dylib ??? (???)
/System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
0x961b6000 - 0x96266fff edu.mit.Kerberos 6.0.12 (6.0.12)
<1dc515ebe407292db8e603938c72d4e8>
/System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
0x96275000 - 0x96281fe7 com.apple.opengl 1.5.6 (1.5.6)
<125de77ea2434a91364e79a0905a7771>
/System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x96282000 - 0x96282ffc com.apple.audio.units.AudioUnit 1.5 (1.5)
/System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x96283000 - 0x963b5fff com.apple.CoreFoundation 6.5.2 (476.13)
<b633d15f2901d73670cb1475628df1b3>
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x963b6000 - 0x9645dfeb com.apple.QD 3.11.52 (???)
<c72bd7bd2ce12694c3640a731d1ad878>
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
0x9645e000 - 0x96765ff7 com.apple.HIToolbox 1.5.3 (???)
<e36f5c553e5a32f64b7eb458dadadc71>
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
0x96773000 - 0x9678bfff com.apple.openscripting 1.2.6 (???)
<b8e553df643f2aec68fa968b3b459b2b>
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting
0x967c1000 - 0x967e1ff2 libGL.dylib ??? (???)
/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x9680d000 - 0x9680dffd com.apple.vecLib 3.4.2 (vecLib 3.4.2)
/System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
0x9680e000 - 0x9696eff3 libSystem.B.dylib ??? (???)
<a12f397abf2285077b89bd726bff5b18> /usr/lib/libSystem.B.dylib
0x9696f000 - 0x96a93fe3 com.apple.audio.toolbox.AudioToolbox 1.5.1 (1.5.1)
/System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x96aa4000 - 0x96adefff com.apple.coreui 1.1 (61)
/System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
0x96adf000 - 0x96b0cfeb libvDSP.dylib ??? (???)
<b232c018ddd040ec4e2c2af632dd497f>
/System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
0x96b0d000 - 0x96bc7fe3 com.apple.CoreServices.OSServices 226.3 (226.3)
<456bdd65b936baf1ef497b74b4f960a8>
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
0x96fd6000 - 0x96fd7ffc libffi.dylib ??? (???)
<a3b573eb950ca583290f7b2b4c486d09> /usr/lib/libffi.dylib
0x96fd8000 - 0x96fd8ffb com.apple.installserver.framework 1.0 (8)
/System/Library/PrivateFrameworks/InstallServer.framework/Versions/A/InstallServer
0x970a8000 - 0x97125fef libvMisc.dylib ??? (???)
/System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
0xfffe8000 - 0xfffebfff libobjc.A.dylib ??? (???) /usr/lib/libobjc.A.dylib
0xffff0000 - 0xffff1780 libSystem.B.dylib ??? (???)
/usr/lib/libSystem.B.dylib
********************************************************************************
Regards,
Pierre-Arnaud
On Mon, Jun 9, 2008 at 3:57 PM, Pierre-Arnaud Marcelot <pa...@marcelot.net>
wrote:
> I fixed the integration-core test but I still got an error with the
> integration-ui test.
> The application is launched but it crashes just after.
>
> I will investigate more...
>
> Regards,
> Pierre-Arnaud
>
>
> On Mon, Jun 9, 2008 at 1:32 PM, Pierre-Arnaud Marcelot <pa...@marcelot.net>
> wrote:
>
>> Hi Stefan,
>>
>> I'm getting an error, when I try to launch the integration core tests on
>> my Mac:
>> -------------------------------------------------------
>> T E S T S
>> -------------------------------------------------------
>> There are no tests to run.
>>
>> Results :
>>
>> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
>>
>> [INFO] [antrun:run {execution: integration-ui}]
>> [INFO] Executing tasks
>> [delete] Deleting directory
>> /Users/pajbam/Development/Apache/Studio/test-integration-core/target/test-sandbox
>> [mkdir] Created dir:
>> /Users/pajbam/Development/Apache/Studio/test-integration-core/target/test-sandbox
>> [mkdir] Created dir:
>> /Users/pajbam/Development/Apache/Studio/test-integration-core/target/test-sandbox/workspace
>> [copy] Copying 752 files to
>> /Users/pajbam/Development/Apache/Studio/test-integration-core/target/test-sandbox
>> [copy] Copying 16 files to
>> /Users/pajbam/Development/Apache/Studio/test-integration-core/target/test-sandbox/plugins
>> [copy] Copying 1 file to
>> /Users/pajbam/Development/Apache/Studio/test-integration-core/target/test-sandbox/plugins
>> [copy] Copying 380 files to
>> /Users/pajbam/Development/Apache/Studio/test-integration-core/target/test-sandbox/plugins
>> [copy] Copied 54 empty directories to 5 empty directories under
>> /Users/pajbam/Development/Apache/Studio/test-integration-core/target/test-sandbox/plugins
>> [java] Exception in thread "main" java.lang.NoClassDefFoundError:
>> org/eclipse/core/launcher/Main
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Error executing ant tasks
>>
>> Embedded error: Java returned: 1
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] For more information, run Maven with the -e switch
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 2 minutes 5 seconds
>> [INFO] Finished at: Mon Jun 09 13:20:30 CEST 2008
>> [INFO] Final Memory: 44M/63M
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> I'll try to see why it's failing.
>>
>> Regards,
>> Pierre-Arnaud
>>
>>
>> On Mon, Jun 9, 2008 at 11:40 AM, Pierre-Arnaud Marcelot <pa...@marcelot.net>
>> wrote:
>>
>>> Hi Stefan,
>>>
>>> This looks very slick!!!
>>>
>>> I'm going to test that...
>>>
>>> Thanks a lot,
>>> Pierre-Arnaud
>>>
>>>
>>> On Sun, Jun 8, 2008 at 3:07 PM, Stefan Seelmann <se...@apache.org>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> here is an update.
>>>>
>>>> I finished the integration testing framework for Studio and I'm going to
>>>> merge it into trunk soon.
>>>>
>>>> How to use it:
>>>>
>>>> 1)
>>>> Building Studio with maven from command line works like before, there is
>>>> no change to the current process.
>>>>
>>>> 2)
>>>> To run the integration test with maven from command line you need a
>>>> local installation of Eclipse and to set a eclipse-home property that
>>>> points to the Eclipse installation path, see [1]
>>>>
>>>> Then the tests could be started with
>>>> - Core tests only: mvn -Pintegration-core test
>>>> - UI tests only: mvn -Pintegration-ui test
>>>> - Core and UI tests: mvn -Pintegration-core,integration-ui test
>>>>
>>>> When running the tests all relevant plugins are copied from different
>>>> locations to the "test-sandbox":
>>>> - from a previous "mvn install" the complete Studio distribution
>>>> - from the resource folder the SWTBot plugins
>>>> - the test-integration-[core|ui] plugin itself
>>>> - some additional plugins from the local eclipse installation
>>>> Then the tests are lauched.
>>>>
>>>> 3)
>>>> For development you need to install the SWTBot plugins because the
>>>> test-integration-ui plugin depends on the SWTBot plugins [2]. I added
>>>> two launch configurations that could be used to launch the tests within
>>>> Eclipse.
>>>>
>>>>
>>>> The next step is to create some more tests :-)
>>>>
>>>>
>>>> Kind Regards,
>>>> Stefan
>>>>
>>>>
>>>> [1] http://directory.apache.org/studio/building.html
>>>> [2] http://directory.apache.org/studio/working.html
>>>>
>>>>
>>>> Stefan Seelmann wrote:
>>>> > Hi Dev,
>>>> >
>>>> > I am working on a framework for integration tests for studio. I added
>>>> > two plugins into my sandbox, one for core and one for UI tests.
>>>> >
>>>> >
>>>> > Core Integration Tests
>>>> > ----------------------
>>>> >
>>>> > The core tests don't depend on any UI code, but on the Eclipse
>>>> runtime.
>>>> > So it is necessary to startup Eclipse in headless mode, then it is
>>>> > possible to access things like Jobs, Preferences, etc.
>>>> >
>>>> > It is already possible to run these test within eclipse or from maven.
>>>> > However in the maven pom there are some fixed paths, I need to remove
>>>> > them, maybe I need some help from a maven guru.
>>>> >
>>>> >
>>>> > UI Integration Tests
>>>> > --------------------
>>>> >
>>>> > For UI test I selected SWTBot (http://www.swtbot.org). There are
>>>> still
>>>> > some features missing in the current version 0.2, but it looks very
>>>> > stable and the API is very easy to use. An UI-Recorder is under
>>>> > development. Last not least it is licenced under ASLv2.
>>>> >
>>>> > Here is an example how a test looks like: http://tinyurl.com/3j5ujs
>>>> > It opens the New Connection wizard, enters all connection parameters,
>>>> > does some checks and closes the connection.
>>>> >
>>>> > There are some open issues:
>>>> >
>>>> > 1) We have to extend SWTBot, I already contacted the author that I am
>>>> > interested in contributing.
>>>> >
>>>> > 2) SWTBot depends on many Eclipse plugins. To run the tests from maven
>>>> > we need to add about 50MB of plugins to our repository. Atm I just
>>>> have
>>>> > a tarball containing all these plugins, but I don't want to commit
>>>> them
>>>> > to svn.
>>>> >
>>>> >
>>>> > I'll keep you informed.
>>>> >
>>>> >
>>>> > Kind Regards,
>>>> > Stefan Seelmann
>>>>
>>>>
>>>>
>>>
>>
>
Re: [Studio] Framework for Integration Tests
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
I fixed the integration-core test but I still got an error with the
integration-ui test.
The application is launched but it crashes just after.
I will investigate more...
Regards,
Pierre-Arnaud
On Mon, Jun 9, 2008 at 1:32 PM, Pierre-Arnaud Marcelot <pa...@marcelot.net>
wrote:
> Hi Stefan,
>
> I'm getting an error, when I try to launch the integration core tests on my
> Mac:
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> There are no tests to run.
>
> Results :
>
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
>
> [INFO] [antrun:run {execution: integration-ui}]
> [INFO] Executing tasks
> [delete] Deleting directory
> /Users/pajbam/Development/Apache/Studio/test-integration-core/target/test-sandbox
> [mkdir] Created dir:
> /Users/pajbam/Development/Apache/Studio/test-integration-core/target/test-sandbox
> [mkdir] Created dir:
> /Users/pajbam/Development/Apache/Studio/test-integration-core/target/test-sandbox/workspace
> [copy] Copying 752 files to
> /Users/pajbam/Development/Apache/Studio/test-integration-core/target/test-sandbox
> [copy] Copying 16 files to
> /Users/pajbam/Development/Apache/Studio/test-integration-core/target/test-sandbox/plugins
> [copy] Copying 1 file to
> /Users/pajbam/Development/Apache/Studio/test-integration-core/target/test-sandbox/plugins
> [copy] Copying 380 files to
> /Users/pajbam/Development/Apache/Studio/test-integration-core/target/test-sandbox/plugins
> [copy] Copied 54 empty directories to 5 empty directories under
> /Users/pajbam/Development/Apache/Studio/test-integration-core/target/test-sandbox/plugins
> [java] Exception in thread "main" java.lang.NoClassDefFoundError:
> org/eclipse/core/launcher/Main
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error executing ant tasks
>
> Embedded error: Java returned: 1
> [INFO]
> ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 2 minutes 5 seconds
> [INFO] Finished at: Mon Jun 09 13:20:30 CEST 2008
> [INFO] Final Memory: 44M/63M
> [INFO]
> ------------------------------------------------------------------------
>
> I'll try to see why it's failing.
>
> Regards,
> Pierre-Arnaud
>
>
> On Mon, Jun 9, 2008 at 11:40 AM, Pierre-Arnaud Marcelot <pa...@marcelot.net>
> wrote:
>
>> Hi Stefan,
>>
>> This looks very slick!!!
>>
>> I'm going to test that...
>>
>> Thanks a lot,
>> Pierre-Arnaud
>>
>>
>> On Sun, Jun 8, 2008 at 3:07 PM, Stefan Seelmann <se...@apache.org>
>> wrote:
>>
>>> Hi,
>>>
>>> here is an update.
>>>
>>> I finished the integration testing framework for Studio and I'm going to
>>> merge it into trunk soon.
>>>
>>> How to use it:
>>>
>>> 1)
>>> Building Studio with maven from command line works like before, there is
>>> no change to the current process.
>>>
>>> 2)
>>> To run the integration test with maven from command line you need a
>>> local installation of Eclipse and to set a eclipse-home property that
>>> points to the Eclipse installation path, see [1]
>>>
>>> Then the tests could be started with
>>> - Core tests only: mvn -Pintegration-core test
>>> - UI tests only: mvn -Pintegration-ui test
>>> - Core and UI tests: mvn -Pintegration-core,integration-ui test
>>>
>>> When running the tests all relevant plugins are copied from different
>>> locations to the "test-sandbox":
>>> - from a previous "mvn install" the complete Studio distribution
>>> - from the resource folder the SWTBot plugins
>>> - the test-integration-[core|ui] plugin itself
>>> - some additional plugins from the local eclipse installation
>>> Then the tests are lauched.
>>>
>>> 3)
>>> For development you need to install the SWTBot plugins because the
>>> test-integration-ui plugin depends on the SWTBot plugins [2]. I added
>>> two launch configurations that could be used to launch the tests within
>>> Eclipse.
>>>
>>>
>>> The next step is to create some more tests :-)
>>>
>>>
>>> Kind Regards,
>>> Stefan
>>>
>>>
>>> [1] http://directory.apache.org/studio/building.html
>>> [2] http://directory.apache.org/studio/working.html
>>>
>>>
>>> Stefan Seelmann wrote:
>>> > Hi Dev,
>>> >
>>> > I am working on a framework for integration tests for studio. I added
>>> > two plugins into my sandbox, one for core and one for UI tests.
>>> >
>>> >
>>> > Core Integration Tests
>>> > ----------------------
>>> >
>>> > The core tests don't depend on any UI code, but on the Eclipse runtime.
>>> > So it is necessary to startup Eclipse in headless mode, then it is
>>> > possible to access things like Jobs, Preferences, etc.
>>> >
>>> > It is already possible to run these test within eclipse or from maven.
>>> > However in the maven pom there are some fixed paths, I need to remove
>>> > them, maybe I need some help from a maven guru.
>>> >
>>> >
>>> > UI Integration Tests
>>> > --------------------
>>> >
>>> > For UI test I selected SWTBot (http://www.swtbot.org). There are still
>>> > some features missing in the current version 0.2, but it looks very
>>> > stable and the API is very easy to use. An UI-Recorder is under
>>> > development. Last not least it is licenced under ASLv2.
>>> >
>>> > Here is an example how a test looks like: http://tinyurl.com/3j5ujs
>>> > It opens the New Connection wizard, enters all connection parameters,
>>> > does some checks and closes the connection.
>>> >
>>> > There are some open issues:
>>> >
>>> > 1) We have to extend SWTBot, I already contacted the author that I am
>>> > interested in contributing.
>>> >
>>> > 2) SWTBot depends on many Eclipse plugins. To run the tests from maven
>>> > we need to add about 50MB of plugins to our repository. Atm I just have
>>> > a tarball containing all these plugins, but I don't want to commit them
>>> > to svn.
>>> >
>>> >
>>> > I'll keep you informed.
>>> >
>>> >
>>> > Kind Regards,
>>> > Stefan Seelmann
>>>
>>>
>>>
>>
>
Re: [Studio] Framework for Integration Tests
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Hi Stefan,
I'm getting an error, when I try to launch the integration core tests on my
Mac:
-------------------------------------------------------
T E S T S
-------------------------------------------------------
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [antrun:run {execution: integration-ui}]
[INFO] Executing tasks
[delete] Deleting directory
/Users/pajbam/Development/Apache/Studio/test-integration-core/target/test-sandbox
[mkdir] Created dir:
/Users/pajbam/Development/Apache/Studio/test-integration-core/target/test-sandbox
[mkdir] Created dir:
/Users/pajbam/Development/Apache/Studio/test-integration-core/target/test-sandbox/workspace
[copy] Copying 752 files to
/Users/pajbam/Development/Apache/Studio/test-integration-core/target/test-sandbox
[copy] Copying 16 files to
/Users/pajbam/Development/Apache/Studio/test-integration-core/target/test-sandbox/plugins
[copy] Copying 1 file to
/Users/pajbam/Development/Apache/Studio/test-integration-core/target/test-sandbox/plugins
[copy] Copying 380 files to
/Users/pajbam/Development/Apache/Studio/test-integration-core/target/test-sandbox/plugins
[copy] Copied 54 empty directories to 5 empty directories under
/Users/pajbam/Development/Apache/Studio/test-integration-core/target/test-sandbox/plugins
[java] Exception in thread "main" java.lang.NoClassDefFoundError:
org/eclipse/core/launcher/Main
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error executing ant tasks
Embedded error: Java returned: 1
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 2 minutes 5 seconds
[INFO] Finished at: Mon Jun 09 13:20:30 CEST 2008
[INFO] Final Memory: 44M/63M
[INFO]
------------------------------------------------------------------------
I'll try to see why it's failing.
Regards,
Pierre-Arnaud
On Mon, Jun 9, 2008 at 11:40 AM, Pierre-Arnaud Marcelot <pa...@marcelot.net>
wrote:
> Hi Stefan,
>
> This looks very slick!!!
>
> I'm going to test that...
>
> Thanks a lot,
> Pierre-Arnaud
>
>
> On Sun, Jun 8, 2008 at 3:07 PM, Stefan Seelmann <se...@apache.org>
> wrote:
>
>> Hi,
>>
>> here is an update.
>>
>> I finished the integration testing framework for Studio and I'm going to
>> merge it into trunk soon.
>>
>> How to use it:
>>
>> 1)
>> Building Studio with maven from command line works like before, there is
>> no change to the current process.
>>
>> 2)
>> To run the integration test with maven from command line you need a
>> local installation of Eclipse and to set a eclipse-home property that
>> points to the Eclipse installation path, see [1]
>>
>> Then the tests could be started with
>> - Core tests only: mvn -Pintegration-core test
>> - UI tests only: mvn -Pintegration-ui test
>> - Core and UI tests: mvn -Pintegration-core,integration-ui test
>>
>> When running the tests all relevant plugins are copied from different
>> locations to the "test-sandbox":
>> - from a previous "mvn install" the complete Studio distribution
>> - from the resource folder the SWTBot plugins
>> - the test-integration-[core|ui] plugin itself
>> - some additional plugins from the local eclipse installation
>> Then the tests are lauched.
>>
>> 3)
>> For development you need to install the SWTBot plugins because the
>> test-integration-ui plugin depends on the SWTBot plugins [2]. I added
>> two launch configurations that could be used to launch the tests within
>> Eclipse.
>>
>>
>> The next step is to create some more tests :-)
>>
>>
>> Kind Regards,
>> Stefan
>>
>>
>> [1] http://directory.apache.org/studio/building.html
>> [2] http://directory.apache.org/studio/working.html
>>
>>
>> Stefan Seelmann wrote:
>> > Hi Dev,
>> >
>> > I am working on a framework for integration tests for studio. I added
>> > two plugins into my sandbox, one for core and one for UI tests.
>> >
>> >
>> > Core Integration Tests
>> > ----------------------
>> >
>> > The core tests don't depend on any UI code, but on the Eclipse runtime.
>> > So it is necessary to startup Eclipse in headless mode, then it is
>> > possible to access things like Jobs, Preferences, etc.
>> >
>> > It is already possible to run these test within eclipse or from maven.
>> > However in the maven pom there are some fixed paths, I need to remove
>> > them, maybe I need some help from a maven guru.
>> >
>> >
>> > UI Integration Tests
>> > --------------------
>> >
>> > For UI test I selected SWTBot (http://www.swtbot.org). There are still
>> > some features missing in the current version 0.2, but it looks very
>> > stable and the API is very easy to use. An UI-Recorder is under
>> > development. Last not least it is licenced under ASLv2.
>> >
>> > Here is an example how a test looks like: http://tinyurl.com/3j5ujs
>> > It opens the New Connection wizard, enters all connection parameters,
>> > does some checks and closes the connection.
>> >
>> > There are some open issues:
>> >
>> > 1) We have to extend SWTBot, I already contacted the author that I am
>> > interested in contributing.
>> >
>> > 2) SWTBot depends on many Eclipse plugins. To run the tests from maven
>> > we need to add about 50MB of plugins to our repository. Atm I just have
>> > a tarball containing all these plugins, but I don't want to commit them
>> > to svn.
>> >
>> >
>> > I'll keep you informed.
>> >
>> >
>> > Kind Regards,
>> > Stefan Seelmann
>>
>>
>>
>
Re: [Studio] Framework for Integration Tests
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Hi Stefan,
This looks very slick!!!
I'm going to test that...
Thanks a lot,
Pierre-Arnaud
On Sun, Jun 8, 2008 at 3:07 PM, Stefan Seelmann <se...@apache.org> wrote:
> Hi,
>
> here is an update.
>
> I finished the integration testing framework for Studio and I'm going to
> merge it into trunk soon.
>
> How to use it:
>
> 1)
> Building Studio with maven from command line works like before, there is
> no change to the current process.
>
> 2)
> To run the integration test with maven from command line you need a
> local installation of Eclipse and to set a eclipse-home property that
> points to the Eclipse installation path, see [1]
>
> Then the tests could be started with
> - Core tests only: mvn -Pintegration-core test
> - UI tests only: mvn -Pintegration-ui test
> - Core and UI tests: mvn -Pintegration-core,integration-ui test
>
> When running the tests all relevant plugins are copied from different
> locations to the "test-sandbox":
> - from a previous "mvn install" the complete Studio distribution
> - from the resource folder the SWTBot plugins
> - the test-integration-[core|ui] plugin itself
> - some additional plugins from the local eclipse installation
> Then the tests are lauched.
>
> 3)
> For development you need to install the SWTBot plugins because the
> test-integration-ui plugin depends on the SWTBot plugins [2]. I added
> two launch configurations that could be used to launch the tests within
> Eclipse.
>
>
> The next step is to create some more tests :-)
>
>
> Kind Regards,
> Stefan
>
>
> [1] http://directory.apache.org/studio/building.html
> [2] http://directory.apache.org/studio/working.html
>
>
> Stefan Seelmann wrote:
> > Hi Dev,
> >
> > I am working on a framework for integration tests for studio. I added
> > two plugins into my sandbox, one for core and one for UI tests.
> >
> >
> > Core Integration Tests
> > ----------------------
> >
> > The core tests don't depend on any UI code, but on the Eclipse runtime.
> > So it is necessary to startup Eclipse in headless mode, then it is
> > possible to access things like Jobs, Preferences, etc.
> >
> > It is already possible to run these test within eclipse or from maven.
> > However in the maven pom there are some fixed paths, I need to remove
> > them, maybe I need some help from a maven guru.
> >
> >
> > UI Integration Tests
> > --------------------
> >
> > For UI test I selected SWTBot (http://www.swtbot.org). There are still
> > some features missing in the current version 0.2, but it looks very
> > stable and the API is very easy to use. An UI-Recorder is under
> > development. Last not least it is licenced under ASLv2.
> >
> > Here is an example how a test looks like: http://tinyurl.com/3j5ujs
> > It opens the New Connection wizard, enters all connection parameters,
> > does some checks and closes the connection.
> >
> > There are some open issues:
> >
> > 1) We have to extend SWTBot, I already contacted the author that I am
> > interested in contributing.
> >
> > 2) SWTBot depends on many Eclipse plugins. To run the tests from maven
> > we need to add about 50MB of plugins to our repository. Atm I just have
> > a tarball containing all these plugins, but I don't want to commit them
> > to svn.
> >
> >
> > I'll keep you informed.
> >
> >
> > Kind Regards,
> > Stefan Seelmann
>
>
>