o sketching out details on integration tests that have intentional errors

to we can make sure we deal with problems correctly.


git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@162797 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Jason van Zyl 2004-06-18 11:53:26 +00:00
parent 7e90a62081
commit 9860371d4b
1 changed files with 19 additions and 0 deletions

View File

@ -1,3 +1,4 @@
-------------------------------------------------------------------------------
it0000: The simplest of builds. We have one application class and one test
class. There are no resources, no source generation, no resource
generation and a the super model is employed to provide the build
@ -31,3 +32,21 @@ it0003: Builds upon it0001: we add a jar installation step. We delete the JAR
which which use the reactor and inheritence. we need to have
integration tests that go far beyond what the average user
would ever setup.
-------------------------------------------------------------------------------
These are a set of builds that contain known errors. They should be captured
and reported in a useful manner to the user. We will start at it1000 for
intentially flawed builds.
-------------------------------------------------------------------------------
it1000: A build which contains a malformed pom.xml. We have intentionally
created a mismatch in the first element. We have:
<projectX>...</project>
-------------------------------------------------------------------------------
it1001: A build whose pom.xml does not contain a <groupId/> element.
-------------------------------------------------------------------------------
it1002: A build with a syntax error in the first field declaration.
-------------------------------------------------------------------------------
it1003: A build with a simple test failure.
-------------------------------------------------------------------------------
- checksum mismatch