[ http://jira.codehaus.org/browse/MNG-1563?page=comments#action_56564 ]
John Casey commented on MNG-1563: --------------------------------- I think we need to reach some consensus on the extent to which maven will dictate a default integration test approach before we try to document this. Since integration tests are meant to execute in some larger context, there will be much more variability during this phase of the build than in the unit test phase, with many different plugins eventually coming into play. I'm going to reassign this to the best practices component so we can talk about this stuff some more. > guide to integration test writing > --------------------------------- > > Key: MNG-1563 > URL: http://jira.codehaus.org/browse/MNG-1563 > Project: Maven 2 > Type: Improvement > Components: Design, Patterns & Best Practices > Reporter: Matthew Pocock > Fix For: documentation > > > There doesn't seem to be a guide about either testing or integration testing. > It would be nice to see two guides: > plain vanilla junit tests: > how to write a simple one that will run in m2 > how to write one that uses the test suite API > integration testing: > test building e.g. plugin that does code generation > test resulting application e.g. command-line app or gui > test deployment e.g. to a test web service container > I have no idea what of this is currently implemented or even possible using > mvn, but then the documentation isn't giving my wishes any boundaries > either... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
