Re: Re: JUnit Test writer for Eclipse based viPlugin

Michael Bartl wrote:
> On Tue, Dec 02, 2003 at 09:28:51AM -0800, Zubair wrote:
> 
>>Hi there, 
>>
>>It would be great if I get a chance to help you out with your 
>>endeavour if I can. 
>>
>>Hope u consider this offer of mine.
>>Regards,
>>Zubair
> 
> 
> Hello!
> 
> I would love to get more JUnit test to provide the users a better tested
> release!
> 
> Have fun,
>     Michael

Just one note. The class TextModificatorTest is not used anymore and it
will be probably completely removed.
It's better to test *Command* classes as far as it is possible. See
*Command*Test classes. Another advantage is that it will force us to
move more functinality to command classes (which should be the main aim
for the next few releases or the code become unmaintainable).

Here is the comment from the TextModificator class:

* TextModificator is a utility class for all kinds of operations on text
* strings. Sooner or later this will be split into the single Commands
* of the viplugin.commands package, ViDocument class and a TextUtil
* class.

So there should be one ViDocument (wrapper for Document) per ViLayer and
TextModificator.getInstance() should be eliminated.

ToMichael> Correct me if I'm wrong somewhere. I'll appreciate more insinght.

It seems that I will have some free time again since tomorrow. So I hope
I will start to code something again (even on my lazy laptop ;) ).

   emdot



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/