Note on integration testing

This commit is contained in:
Jason van Zyl 2013-11-29 15:13:13 -05:00
parent d23316a690
commit 6cf9d7444b
2 changed files with 5 additions and 3 deletions

View File

@ -1,3 +0,0 @@
Maven Core Integration Tests
Maven Developers List: dev@maven.apache.org

5
its/README.md Normal file
View File

@ -0,0 +1,5 @@
Maven Core Integration Tests
Maven Developers List: dev@maven.apache.org
A little background to help understand things: A good IT does not depend on external repos like central, it uses dedicated test plugins and test repositories. The default settings.xml used by ITs helps to enforce this by pointing central at file:target/null which obviously can't resolve anything. This setup using a file-based dummy repo also helps execution time because this repo produces (expected) 404s much faster than a HTTP-based repo. The one place where access to central is desired is in the MavenITBootstrapTest which doesn't really test anything but just primes the local repo with any artifacts the ITs will need. So some care needs to be taken when introducing new dependencies into the ITs themselves or the support plugins. Many times the failures that we encounter are discrepancies between actual artifact consumption required and what is populated during bootstraping.