RE: [jmoney-devel] Some starting-out questions

[Nigel W. <ja...@mi...>]

It does seem to me that having all the tests in a single plug-in breaks
the independence of plug-ins.  Consider:

1. If someone with no commit rights writes a plug-in, where do they put
the test code?  If someone writes a private plug-in that would be of no
use to anyone else, where do they put the test code?  We are therefore
going to end up with multiple test plug-ins in any case.

2. If we have a single test plug-in then that plug-in must depend on all
the other plug-ins.  That means I can no longer install just the
plug-ins I want to test.  I have to install every plug-in if I want to
test just one plug-in.

On the other hand I can see that it would be nicer if we did not include
the test code in the released product.

The only way to satisfy all the above requirements would be if every
plug-in also had a test plug-in.  More test plug-ins would run tests
that require more than one independent plug-in.  We would thus have more
test plug-ins than real plug-ins.

Eclipse seems to have a test plug-in for each group of plug-ins.  I am
happy with whatever you decide.  We can always re-structure later if we
find problems, so I would not worry about it.

It will be great to have Alex on board as a developer.  JMoney will
benefit from some test scripts.  I am also looking forward to hearing
his views on the general direction of the project and how it compares to
the vision of the project that he was thinking of starting.

Nigel



-----Original Message-----
From: jmo...@li...
[mailto:jmo...@li...] On Behalf Of Johann
Gyger
Sent: Saturday, March 12, 2005 7:24 AM
To: jmo...@li...
Subject: Re: [jmoney-devel] Some starting-out questions

Alex,

> It works much better in 3.0 - the Navigation view is showing up, so I 
> can create accounts and entries (but not categories or currencies - 
> the only option when right-clicking those is "New Account"...

"Categories" and "Currencies" are edited by double clicking on them. 
Maybe this is not very intuitive because clicking on "Accounts", 
"Charts", and "Reports" has no effect.

> I'm a big fan of unit testing, and Johann mentioned that you guys need

> unit tests written, so why don't I start there?  I imagine that would 
> be one of the best ways to get familiar with the existing code base.

I would highly appreciate having some good tests because this is really 
missing now :)

> Is there a preference for how the tests should be structured?  I see 
> that there is a separate plug-in that contains a couple of tests, but 
> I would think that the unit tests for a given plug-in should be 
> contained in that plug-in, and any tests for functionality that spans 
> plug-ins be contained in the net.sf.jmoney.test plug-in.

Personally, I would put all tests in one plug-in (net.sf.jmoney.test) 
and then put the various tests in Java packages which reflect the 
plug-in structure. If you have a look at the Eclipse repository 
(http://dev.eclipse.org/viewcvs/index.cgi/) you will see that they have 
distinct test plug-ins as well and they don't put the test code in the 
application plug-in itself.

-Johann

P.S. If you need CVS access, I can add you as a developer to the JMoney 
project. Nigel and Olivier, do you agree?



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
jmoney-devel mailing list
jmo...@li...
https://lists.sourceforge.net/lists/listinfo/jmoney-devel