Hi,
Also I need to clear this thing in case I am doing it wrong :
After I download the SWTBot git repository, how should I import it in Eclipse? Should I import it as a Git repository or should I import it as a Maven Project? Till now I was importing it
as a Git Repository. However, I tried importing it as a maven project just now and I am getting this error repeatedly after importing the project as a Maven Project :
Plugin execution not covered by lifecycle configuration: org.jacoco:jacoco-maven-plugin:0.5.8.201207111220:prepare-agent (execution: default, phase: initialize) pom.xml /indigo
line 19 Maven Project Build Lifecycle Mapping Problem
An API baseline has not been set for the current workspace. org.eclipse.swtbot.eclipse.finder Unknown Default API Baseline Problem
Can you please let me know if I should stick to Importing as Git Repository or change to Import as Maven Project ?
Also, after installing SWTBot , when I right click on ProjectCreationWizardTest.java and click on Run as -> SWTBot Test, I get the following error on console :
Error occurred during initialization of VM
Could not reserve enough space for object heap
Thanks,
Rohit
From: swtbot-dev-bounces@xxxxxxxxxxx [mailto:swtbot-dev-bounces@xxxxxxxxxxx]
On Behalf Of Matthias Sohn
Sent: Thursday, April 11, 2013 6:22 AM
To: SWTBot developers list
Subject: Re: [swtbot-dev] Test issue
On Wed, Apr 10, 2013 at 11:52 PM, #ROHIT AGRAWAL# <ROHI0012@xxxxxxxxxxxx> wrote:
Hi,
I have been trying all day without any luck. Just so I am not missing anything obvious , are there
any additional plugins which need to be installed for SWTBot ? Right now I am just using a Eclipse Juno version also with EGit installed and M2E plugin.
I tried running the maven command in Eclipse IDE also but got the same error. However, when I skip
tests, it does build successfully. The failing test is :
Results :
Failed tests: canCreateSWTBotProject(org.eclipse.swtbot.eclipse.ui.functional.ProjectCreationWizardTest):
expected:<...anifest-Version: 1.0[
What do you suggest I do since I cant seem to get the tests running?
you could mark the failing test with @Ignore annotation to see if the other tests work for you.
Did you try to run the failing test without Maven via "Run as > SWTBot test" [1] ? This way you can
also debug the test. Prerequisite for that is to install the SWTBot plugin into Eclipse.
Do you have any other heavy background processes running on your machine ? This may influence
timing behavior. If you face timeouts you could try to increase timeouts [2].