Generally the fact that it's UI related is pretty irrelevant. There's
probably very little that actually requires you to see if a physical
checkbox is checked or a text is in a particular place.
It's more about confirming a certain list of items are stored in your
model/data-table rather than physically added to a JList or whatever.
You should be able to mock whatever external interfaces are used in any of
your classes so you can test those classes in isolation and just confirm
what the expectations of each individual class are. Of course, that's in a
perfect world and requires a lot of interfaces being passed around rather
than classes. :)
-----Original Message-----
From: Mark Phippard [mailto:MarkP@softlanding.com]
Sent: Friday, 1 July 2005 11:00 AM
To: dev@subclipse.tigris.org
Subject: RE: [Subclipse-dev] Synchronize performance patch
"Greg Irvine" <greg.irvine@thalesatm.com> wrote on 06/30/2005 08:57:18 PM:
> Sounds like JUnit tests would come in handy around now. ;)
They sure would! Is it even possible to do them for this sort of stuff
yet? Does the CVS plugin have JUnit tests that are able to test at this
level of the code. We have JUnit tests for the actual code that works
with Subversion, but not for the stuff that works in Eclipse, and
certainly nothing that is UI-related.
Mark
____________________________________________________________________________
_
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management
Services powered by MessageLabs.
____________________________________________________________________________
_
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: dev-help@subclipse.tigris.org
Received on Fri Jul 1 11:06:41 2005