Although logging is very good, debugging has its specific advantages in some
cases I think.
Debugging of SWT Bot could be made a little bit easier concerning breakpoints
and stepping over if results of method calls are stored in a variable before
they are passed to another method or returned.
Here are some examples:
public List findControls(IMatcher matcher) {
return findControls(activeShell(), matcher, true);
}
This could be refactored for debugging into:
public List findControls(IMatcher matcher) {
Shell activeShell = activeShell();
List controls = findControls(activeShell, matcher, true);
return controls;
}
Or:
public SWTBotButton button(String buttonText, int index) {
return new SWTBotButton(finder, buttonText, index);
}
Could be refactored for debugging into:
public SWTBotButton button(String buttonText, int index) {
SWTBotButton button = new SWTBotButton(finder, buttonText, index);
return button;
}
-------------------------------------------------------------------------
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
