| How does the Eclipse project test it's GUI? [message #329537] |
Fri, 27 June 2008 08:14  |
Eclipse User |
|
|
|
I just want to verify that I understood it, how Eclipse itself tests the
GUI of its product.
I've downloaded the plugin tests of Eclipse 3.2.2 and run some of them in
Eclipse. Then dialogs pop up, close etc.
When I looked into the code for the plugin tests
"org.eclipse.jdt.ui.tests", it seems that it is a kind of white box GUI
testing because the dialogs are created in the classes directly
(JavaProjectHelper.createJavaProject(...)) and methods of the GUI objects
are called, for example setSomething(...).
For this approach one needs to know a lot of the GUI classes. It seems
that it also relies on additional manual testing, since there can't be
automated everything by using this approach.
It is not a black box testing, since a generic technique ("click on a
button named OK in the dialog", "enter text into box by keypress events")
is not used as it seems.
Did I understand it right?
|
|
|
|
| Re: How does the Eclipse project test it's GUI? [message #329547 is a reply to message #329541] |
Fri, 27 June 2008 11:19  |
| Eclipse User |
|
|
|
You are very successful, since the quality is great. I just wondered how
you achieve such a good quality.
We are currently starting to use SWT Bot to test our RCP application. It
seems to me that it is a promising project in an early stage. It is black
box testing. The GUI tests are Java programs by design (no XML, script or
whatever), which I like.
|
|
|
Powered by
FUDForum. Page generated in 0.06722 seconds
Home