>>>>> On Thu, 30 Oct 2003 11:37:23 -0500, Alain Javier Guarnieri del Gesu <[EMAIL
>>>>> PROTECTED]> said:
>> What does a standalone test case buy you over one with a resource?
> More importantly, are those that adhere to this school of thought
> seeking a solution in Maven to make addendence compulsory?
> If my I want to use external resources in my projects, shouldn't we
> create me a place in the Maven directory structure where I can
> pursue my folly?
> I appreciate that Maven seeks to establish best practices in project
> structure, I just don't think this argument is one that Maven needs
> to resolve.
I am interested, from a Maven pov, regarding this issue. Where this
line is drawn is interesting. Multiple source directories, multiple
artifacts, skipping unit tests, etc. ? Issues like this are one of
the things that sets the Maven project and team apart from other build
tools/teams.
I have external resources in my tests. I try not to, I don't want to,
but I'm still learning and sometimes I just need to get my code
written. When I refactor my tests, I may see a better way to loose
the dependency on external resources. I usually get knotted up like
this when working with legacy, not too often on test-driven code.
Sometimes I can only test from an integration or customer test level.
Maybe no resources in programmer tests, but integration and acceptance
are ok?
--
=====================================================================
Jeffrey D. Brekke [EMAIL PROTECTED]
Wisconsin, USA [EMAIL PROTECTED]
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
