Yes, I agree 100% with this "school of thought". I want the tests to
be fast and no external dependencies, even files. I treat the need to
fall back on external resources in programmer tests as a potential
code/design smell. Same with extensive/complex fixture setup.
>>>>> On Thu, 30 Oct 2003 21:48:02 +1100, Peter Donald <[EMAIL PROTECTED]> said:
> On Thu, 30 Oct 2003 01:05 pm, Ben Walding wrote:
>> The rationale is this:
>>
>> If you have src/java and src/test, then where do you put resources
>> for testing?
>>
>> eg: src/resources, src/test-resources
> One school of thought suggests that no test should NEVER require
> resources external to the TestCase. You can always use Mock objects
> or manually construct pre-conditions for test, run the test and then
> test the output.
> External resources for unit tests are only required if there is
> badly written code or badly written tests. While I previously used
> to litter my unit tests with other resources I now think it is a
> really bad idea. Can you give an example where there is a good
> reason to have resources associated with unit tests?
> (Integration tests are another thing entirely).
How would integration tests be handled in this respect? ( Maybe this
is another thread starting up ). How do you handle integration
testing, and their potential test resources, using Maven?
--
=====================================================================
Jeffrey D. Brekke [EMAIL PROTECTED]
Wisconsin, USA [EMAIL PROTECTED]
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
