Hi,
I digged around the code a little bit and I think where the code is failing the
assert condition is this part :
assertEquals("" +
"Manifest-Version: 1.0\n" +
"Bundle-ManifestVersion: 2\n" +
"Bundle-Name:
com.example\n" +
"Bundle-SymbolicName: com.example;singleton:=true\n" +
"Bundle-Version: 1.0.0.qualifier\n" +
"Bundle-ActivationPolicy: lazy\n" +
"Bundle-Vendor:
ACME Corp.\n" +
"Bundle-RequiredExecutionEnvironment: J2SE-1.5\n" +
"Require-Bundle: org.eclipse.swtbot.go\n" +
"",
contentsOf(project, "META-INF/MANIFEST.MF"));
However, when I check the contents of the created test project com.example
under the target folder of org.eclipse.swtbot.eclipse.ui.test , the contents of
the META-INF/MANIFEST.MF are exactly what they should be. Also, on the
reference build you provided, this test is passing without any issues. None of
the bugs you provide match anything close to the issue I am facing either.
Is there anyway to ignore this test and build the rest of the project?
Thanks,
Rohit
From: swtbot-dev-boun...@eclipse.org [mailto:swtbot-dev-boun...@eclipse.org] On
Behalf Of Mickael Istria
Sent: Monday, April 8, 2013 1:44 PM
To: swtbot-dev@eclipse.org
Subject: Re: [swtbot-dev] [soc-dev] Added SWTBot GSoC proposal
On 04/07/2013 11:04 PM, #ROHIT AGRAWAL# wrote:
I have attached the log output of the project which failed the test, namely :
org.eclipse.swtbot.eclipse.ui.test .
Running tests with SWTBot requires you to keep focus on the test application
while it's running. Otherwise tests will fail. There is a way to avoid active
wait on Linux (
http://wiki.eclipse.org/SWTBot/Automate_test_execution#Linux_hints ), but I'm
not aware of a similar trick on Windows.
Also, there are some tests that are known to be currently failing with Eclipse
4.x version, see
https://hudson.eclipse.org/hudson/view/SWTBot/job/swtbot-tycho-e4.2/ for a
reference build using "mvn clean verify -Pkepler", and
https://bugs.eclipse.org/bugs/show_bug.cgi?id=385527 and
https://bugs.eclipse.org/bugs/show_bug.cgi?id=404346 for more details about the
causes of currently failing tests.
As a startup for you in the project, it would be an interesting (but not easy)
entry-point to try to provide fixes on such bugs. Then you'll understand the
global architecture of SWTBot and get used to the process of contributing.
HTH
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat<http://www.jboss.org/tools>
My blog<http://mickaelistria.wordpress.com> - My
Tweets<http://twitter.com/mickaelistria>
_______________________________________________
swtbot-dev mailing list
swtbot-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/swtbot-dev
