|Re: How does the Eclipse project test it's GUI? [message #131818 is a reply to message #131499]
||Thu, 26 June 2008 13:12
| Paul Slauenwhite
Registered: July 2009
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:
"Hans Schwaebli" <firstname.lastname@example.org> wrote in message
>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?
Powered by FUDForum
. Page generated in 0.42221 seconds