Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Test and Performance Tools Platform (TPTP) » How does the Eclipse project test it's GUI?
How does the Eclipse project test it's GUI? [message #131499] Fri, 20 June 2008 03:27 Go to next message
Hans Schwaebli is currently offline Hans Schwaebli
Messages: 70
Registered: July 2009
Member
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 #131818 is a reply to message #131499] Thu, 26 June 2008 09:12 Go to previous messageGo to next message
Paul Slauenwhite is currently offline Paul Slauenwhite
Messages: 970
Registered: July 2009
Senior Member
Hi Hans,
Since your question is specific to the Eclipse Platform Project, please
post your question to their news group
( http://www.eclipse.org/newsportal/thread.php?group=eclipse.p latform).

FYI, the Eclipse Platform Project uses JUnit and JUnit Plug-in test
suites to test their code. The test suites are executed using the JDT JUnit
runner. TPTP provides the same support (JUnit and JUnit Plug-in test
suites), with the addition of remote test execution, test log, BIRT-based
test reports, and automated test execution/results reporting via Ant:

http://help.eclipse.org/ganymede/topic/org.eclipse.hyades.te st.doc.user/concepts/ccommontestingtasksandconcepts.htm

Paul
"Hans Schwaebli" <hans_schwaebli@yahoo.com> wrote in message
news:4f69b763d0ef2d1d8f4bdf591e6a42f3$1@www.eclipse.org...
>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 #131839 is a reply to message #131818] Fri, 27 June 2008 08:17 Go to previous messageGo to next message
Hans Schwaebli is currently offline Hans Schwaebli
Messages: 70
Registered: July 2009
Member
I have now posted my question there:

http://www.eclipse.org/newsportal/article.php?id=76052&g roup=eclipse.platform#76052

Your answer is a technical one. I meant it more as a software development
process question in general. The GUI test philosophy of Eclipse if you
want, not so technical, with answering "why this way" and not so much "how
this way".
Re: How does the Eclipse project test it's GUI? [message #131869 is a reply to message #131839] Fri, 27 June 2008 13:12 Go to previous message
Paul Slauenwhite is currently offline Paul Slauenwhite
Messages: 970
Registered: July 2009
Senior Member
Hi Hans,
Yes, you will need to discuss Eclipse testing processes on the Eclipse
Platform news group.

If you are interested, here is the TPTP Testing Strategy:

http://www.eclipse.org/tptp/home/documents/process/TPTP_Test ing_Strategy.html

Paul
"Hans Schwaebli" <hans_schwaebli@yahoo.com> wrote in message
news:bf056150a83bcca4c54e6af5bf00fd53$1@www.eclipse.org...
>I have now posted my question there:
>
> http://www.eclipse.org/newsportal/article.php?id=76052&g roup=eclipse.platform#76052
>
> Your answer is a technical one. I meant it more as a software development
> process question in general. The GUI test philosophy of Eclipse if you
> want, not so technical, with answering "why this way" and not so much "how
> this way".
>
Previous Topic:NoClassDefFoundError: org.eclipse.hyades.test.common...?
Next Topic:Re: TPTP profile files too large
Goto Forum:
  


Current Time: Thu Jul 31 23:55:49 EDT 2014

Powered by FUDForum. Page generated in 0.01741 seconds