We are successfully
using RCPTT for Eclipse GUI testing: both for for automated
nightly testing and for manually-launched pre-commit runs of
the test suite by developers. However there are two usability
issues we don't have solutions for and would appreciate
suggestions:
1) When
manually launching the test suite, the AUT does not exit as
part of the test suite. Scripting a test containing something
like 'get-menu "File/Exit" | click' does not work. It would be
very handy if some command worked, or even better, if the
Eclipse Run Configuration had an option to terminate the AUT
when the test suite completes.
2) After
doing some development work, one has to manually build the
plugin files as part of an updateSite and copy them to the
AUT's dropins folder, before launching them. Since developers
are used to JUnit testing where such a step is not needed, it
is easy to forget to do, with the result that the RCPTT tests
confusingly behave just as the did in the previous test run.
Automating this step as part of launching the test suite would
be great.
I'm eager
to hear the experience of others on these points.
- David
