> I am trying to use some automatic testing in the areas of the plugin
> that I am touching. I think we can step on more solid ground when we
> have good tests, and I like to step on solid ground because I think it
> makes me move faster.
> I am trying to use Abbot (and Abbot SWT) for the testing, basically
> GUI testing for the 'New > Haskell Project' wizard that I am working
> on. But I am getting into some trouble with it. It doesn't seem to
> work with my Linux system out of the box. Maybe I'll be able to find a
> workaround for this, but I need to know if do any of you know any
> other GUI testing tools, just in case.
> And what do you all think about writing some automatic tests?
Yes, automated testing is a very good thing. I have JUnit tests for some
of the more tricky functionality. I thought they were in the repo, but
I'll have to check ...
I haven't used Abbot, so I would have to have a look at it. Mainly, I am
suspicious of UI testing. Usually, if there is a good design that puts
all interesting functionality into core objects, there is not much left
to test on the UI (apart from some selection/disabling stuff etc., for
which one can use PDE JUnit). The interesting things can be tested in
the core without any UI stuff required.
That would not work if the programming style is like in some of the
Eclipse wizards, where huge functionality is just implemented into the
performFinish() method, of course ;-)
What I usually do is to use a Presentation model pattern for wizards,
i.e. I create an 'info' object that contains things that are displayed
in the wizard, and in the performFinish() I just run an operation to
which I pass that info object.
> Thiago Arrais
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> eclipsefp-develop mailing list