comment on

Don't know how modular your project is.

I think it does not matter if it is just one module or if it consists of many components if you choose a good OO design.

I write tests for every class/module with the standard tool for the language (Test::More on Perl,JUnit for Java,...) because they are well documented (good for other developers) and mature.

for example if Java component X does the main calculations and Perl Module Y uses some of this Java libs, then test in X with JUnit that the calculations are correct and in Y with Test::More that the communication is ok.

In reply to Re: Testing framework in Perl by lima1
in thread Testing framework in Perl by crenz

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Come for the quick hacks, stay for the epiphanies.
	PerlMonks