| SWTBot cheat sheet [message #530420] |
Thu, 29 April 2010 11:22  |
Eclipse User |
|
|
|
I'm putting together a very long document[1] that will walk users
through getting up and running with SWTBot.
The existing user guide[2] needs significant improvement since it makes
a lot of assumptions about users knowing java, the eclipse install
process, junit and possibly a few others.
I'm trying to ensure that users have a smoother experience with getting
started with swtbot.
Later I'll be putting down thoughts in a cheatsheet with some neat tips
and tricks that will improve productivity.
Let me know if there is anything you'd like for me to document. I'm sure
a lot of you have faced hurdles at some point or the other and any
thoughts on improving those would be of great help.
Thanks!
--
Ketan
http://ketan.padegaonkar.name | http://eclipse.org/swtbot
[1] - http://swtbot.org/doc
[2] - http://wiki.eclipse.org/SWTBot/UsersGuide
|
|
|
| Re: SWTBot cheat sheet [message #530478 is a reply to message #530420] |
Thu, 29 April 2010 14:14  |
| Eclipse User |
|
|
|
Hi Ketan
It will be good to have all this info in one place!
It would be good to include snippets/ descriptions for the correct, standard way to do certain common operations. For example:
- activating a newly opened dialog to access its controls.
- tidying up after tests, even if they have failed, so that all dialogs are closed and the next test can begin in a 'clean' state. This is still the commonest cause of test failures in our suite
- writing wait conditions.
One thing I found challenging was how hamcrest.matcher works , and what functionality is already available for matching things in the SWTBot api - e.g., checking if views are opened, for example.
Richard
|
|
|
Powered by
FUDForum. Page generated in 0.03194 seconds
Home