On 11-Jul-08, at 10:38 AM, Somesh Sasalatti wrote: > 2) I see that SWTBotTable.java has changed quite a bit. it used to > have several methods but i only see click and doubleclick() i'll try > it out.
Don't think there's anything that has been removed, I'm keeping strict eye on API breakage, and this is definitely not one of them. > 3) so about click()... take a look at notify(int, event, widget ). > version number 519 i think from 2008-05-13. there is an syncExec at > the end of the notify. this is where the click lands and hence was > waiting. now there's a sleep there. > Conditions.Shellcloses() ...hmm...that's new...i'll try that too.. As I've mentioned in the previous email, I've put this back, so there's a sleep (to slow down) and a syncExec(). > 4) so here's a truth table kind of way of what things are > 3.3.1 && 1.1(released) - works fine. the apache.commons.logging > throws and exception but continues. > 3.3.1 && nightly : all the failures i mentioned ...but that can be > attributed to a lot of changes. > 3.3.2 && 1.1 - see stack trace above . apache commons.logging > screwing things up > 3.3.2 && nightly : same as 3.3.1 && nightly Great, so you see the same behavior of SWTBot (apart from API changes) nightly and 1.1, which is a good thing! > the bottom line is i don't want to use the trunk till its officially > released or there is a real compelling reason. Why? we're developing > a plugin too..the nightly isn't the most stable > so, basically i need to get the 3.3.2 && 1.1 working. which is the > commons.logging error. Can you suggest a way to fix this. maybe > delete the commons.jar file from plugins and change the feature.xml/ > manifest of the released plugin.? Pull in the source from svn make local changes and build it to suit your needs. OR Trial and error: Figure out what plugin works for you (and modify feature.xml from swtbot) > this doesn't seem to be a compelling reason to switch to the nightly > cos it might be an easy fix that i don't know about and also a whole > bunch of my tests will fail... Reasons why you'd take nightly: - There's more people downloading from nightly build than from the stable 1.1 release as of now :) - new API and features - You just filed a bug/feature request which was fixed in trunk - very stable (atleast the SWTBot tests say so) - Provide feedback on things that don't work for you, and get them fixed -- you just did this, BTW. Reasons why you'd not take nightly: - new API *sometimes* changes - Hard to keep track on a daily basis Taking trunk everyday is probably not a good idea, but it'd be good to take a look at trunk every week or so and provide feedback. Some API from the 1.1 release is *DELETED* *DEPRECATED* or works in a different way, and you'd like to make sure your tests are in sync with the new API and work fine when the new release comes along with minimum changes. -- Ketan ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ SWTBot-users mailing list SWTBot-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/swtbot-users http://swtbot.org/ - a functional testing tool for SWT/Eclipse
