|Re: SWTBot cheat sheet [message #530478 is a reply to message #530420]
||Thu, 29 April 2010 18:14
| Richard Adams
Registered: July 2009
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.
Dr Richard Adams, University of Edinburgh
Powered by FUDForum
. Page generated in 0.03373 seconds