Skip to main content



      Home
Home » Eclipse Projects » RCP Testing Tool » [SOLVED] #set up RCPTT TEST RUNNER(#set up RCPTT TEST RUNNER)
[SOLVED] #set up RCPTT TEST RUNNER [message #1707847] Wed, 09 September 2015 12:53 Go to next message
Eclipse UserFriend
Hi Folks,
Today I start to to see RCPTT Test Runner.
I'm Following the guide
https://www.eclipse.org/rcptt/documentation/userguide/runner/arguments/

I download RCPTT the test runner.

I download the 2 files
build.xml sample Ant script
runner.cmd sample CMD script for Windows
Where I have to put them ?

Regarding the following parameters
SET AUT - It is the application under test or is the application created in the workspace by rcptt ?

SET PROJECT- It is the rcptt project ?

Thanks in advance buddies.


[Updated on: Thu, 08 October 2015 07:22] by Moderator

Re: #set up RCPTT TEST RUNNER [message #1707871 is a reply to message #1707847] Thu, 10 September 2015 02:44 Go to previous messageGo to next message
Eclipse UserFriend
Hi Angelo,

I'm also currently setting up the runner, so hopefully I can help you with my findings:

- First you have to decide how you want to execute the runner. If you want to start it from an ANT script (e.g. automatically from a build system), you need the build.xml. If you just want to start it from a Windows command line you need the runner.cmd.

In my case I used the build.xml to run it from ANT.

- To start the runner and automatically run your test you have to set up a test environment (folder structure) containing the following folder:
1. Your application you want to test (AUT - Application Under Test). SET AUT in runner.cmd or aut-path in build.xml must point to the path of this application (in detail the folder containing the plugins folder).
2. The runner itself (SET RUNNER or runner-path must point to that folder)
3. Your RCPTT test project which contains the tests or test suites. SET PROJECT is pointing to that in the runner.cmd, in the build.xml it is directly passed to the -import parameter

With that configuration, you can put the runner script somewhere and execute it, as it will find the other folders by the given paths. At least you should get some console output that points to other problems if it's not running.

Hope that helps, best regards
Andreas
Re: #set up RCPTT TEST RUNNER [message #1707884 is a reply to message #1707871] Thu, 10 September 2015 04:00 Go to previous messageGo to next message
Eclipse UserFriend
Thank you Andreas for sharing your findings.
Buddies I have inserted data as Andrea told me I'm using directly the 'runner.cmd'.
SET AUT=D:\XDMClient2\plugins
SET RUNNER=C:\Users\Administrator\Desktop\rcptt.runner-2.0.0\eclipse
SET PROJECT=C:\QA\workspace2\q

When I run the runner.cmd raise the exception below.

!ENTRY org.eclipse.osgi 4 0 2015-09-10 09:55:12.712
!MESSAGE Application error
!STACK 1
org.eclipse.core.runtime.CoreException: Invalid project description.
at org.eclipse.rcptt.core.workspace.ProjectUtil.printAndThrow(ProjectUtil.java:144)
at org.eclipse.rcptt.core.workspace.ProjectUtil.importProjects(ProjectUtil.java:114)
at org.eclipse.rcptt.runner.util.TestsRunner.findScenarios(TestsRunner.java:124)
at org.eclipse.rcptt.runner.util.TestsRunner.findAndRunTests(TestsRunner.java:86)
at org.eclipse.rcptt.runner.HeadlessRunner.performCoolThings(HeadlessRunner.java:53)
at org.eclipse.rcptt.runner.HeadlessRunnerApp.start(HeadlessRunnerApp.java:54)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
Contains: OK
Contains: C:\QA\workspace2\q overlaps the workspace location: C:\QA\workspace2\q\results\runner-workspace
Re: #set up RCPTT TEST RUNNER [message #1707889 is a reply to message #1707884] Thu, 10 September 2015 04:29 Go to previous messageGo to next message
Eclipse UserFriend
Hi Angelo,

1. I think the AUT path must be one level up (point to the folder containing the plugins folder, not to the plugins folder directly):
SET AUT=D:\XDMClient2

2. Contains: C:\QA\workspace2\q overlaps the workspace location: C:\QA\workspace2\q\results\runner-workspace

I also got this error at the beginning, it seems the workspace used for the runner must not be part of the RCPTT project folder.

In your case, your RCPTT project is:
SET PROJECT=C:\QA\workspace2\q

Regarding the default runner.cmd,
SET RESULTS=%PROJECT%\..\results
-data %RESULTS%/runner-workspace/

the runner workspace should be:
C:\QA\workspace2\results\runner-workspace

But the error message says its C:\QA\workspace2\q\results\runner-workspace, which will be inside the RCPTT project what is not allowed.

Have you changed the configuration of the result directory?

Best regards,
Andreas
icon14.gif  Re: #set up RCPTT TEST RUNNER [message #1707902 is a reply to message #1707889] Thu, 10 September 2015 05:42 Go to previous message
Eclipse UserFriend
Hi Andrea,
I changed the configuration of the result directory and it works. Cool
Thank you mate.
Previous Topic:Need Help in this ECL Script
Next Topic:TreeViewers with Lazy Decorators
Goto Forum:
  


Current Time: Thu Jun 19 03:38:56 EDT 2025

Powered by FUDForum. Page generated in 0.04338 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top