>One -- you're actually limiting or biasing the test coverage for this >particular test because you're testing against a particular >implementation rather than a more abstract mock object.
Yes, this is an argument that is as old as QA itself ;) >Two -- by requiring impl to be a dependency for the test code, you >allow the possibility of unintentionally using impl classes in the >non-test code. As long as impl is scoped as "test" in the pom.xml for tomahawk, I don't see how maven would allow one of us to compile the non-test code. >Another observation is that end-users cannot download, build, test >Tomahawk without MyFaces impl. Since Tomahawk is supposed to be >JSF-implementation independent, it's contrary to our stated goal to >require a specific implementation for testing or development. Obviously we want people to use tomahawk w/out myFaces impl. If you would like to make it possible for them to test tomahawk w/out impl than more power to you. I think this is taking it too far and we will never get a pat on the back for this. Dennis Byrne
