> Yeah it could be even *shooting* in your *own* *foot*.! > It's just so nice to be in the situation when second version > of the same > project and it just happen that API is very different and you have to > put to the garbage all your mock objects :).
You should have a look at the dynamic mocks. No need to write mocks any more, so you don't waste your investment. All you need to write is the tests themselves. > I do believe > that standalone test data is valuable outcome of any project. > It just > happen that I have (I really regret that) quite big experience > with legacy system written even in different progr. lang without any > resuable test data. When you are re-doing the same thing in completly > different way > but you have the same input and the same output such data in simply > priceless. > > Other importand aspect: Mock object/test data inside Java code often > results in inclination toward "white box testing". > For a complete software examination, both white box and black > box tests > are required. Black box testing is not unit testing AFAIC. > > mm > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
