Ah, well that makes some sense. Apologies for not noticing that; I didn't have Pas Author Runtime checked out.
EasyMock also works by creating mock implementations of classes. It's called the EasyMock Class Extension. http://easymock.org/EasyMock2_2_ClassExtension_Documentation.html I added it to PAR and updated the main to EasyMock 2.2. Then I got rid of IPasStep and made BasicInfoUITest use PasStep. This solved two problems written up in TODO source comments: finding the "hints" property Swing components and the "Type:" label check. Incidentally, I'm pleased as a pickle to see unit testing of the GUI. The more hands we have on the codebase, the more valuable unit testing is becoming. Now that I'm out of the inner loop now, I can see very clearly why outside developers would/should be skiddish about making changes without unit tests to show them they're not breaking anything. -Turadg On 1/9/07, Scott Cytacki <[EMAIL PROTECTED]> wrote: > > It looks like Laurel committed it. It is being used in the author > runtime. And it looks like it is needed because the author tool is now > using an automatic testing library called EasyMock. Which works by > creating mock implementations of interfaces. > > Scott > > On Tue, 2007-01-09 at 13:29 -0500, Turadg Aleahmad wrote: > > What is IPasStep for? PasStep is an abstract class, not an interface. > > Any class that implements IPasStep will be extending PasStep. The > > interface just adds fruitless complexity and ambiguity. > > > > Can the committer please remove it? > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
