o incorporating andy's suggestion about test includes/excludes which will

lead people to ask how they customize that so i stubbed out a mini guide
  for test customization


git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@306871 13f79535-47bb-0310-9956-ffa450edef68

maven-site/src/site/apt/guides/getting-started/index.apt

@@ -354,8 +354,6 @@ m2 install
 
  Upon executing this command you should see the following output:
 
-~~ [!:glick] tell users what the defaults are for the includes and excludes
-
 +----+
 
 [INFO] ----------------------------------------------------------------------------
@@ -394,6 +392,25 @@ Results :
 
 +----+
 
+ Note that the surefire plugin looks for tests contained in files with a particular naming convention. By default
+ the tests included are:
+
+ * <<<\*\*/\*Test.java>>>
+
+ * <<<\*\*/Test\*.java>>>
+
+ * <<<\*\*/\*TestCase.java>>>
+
+ []
+
+ And the default excludes are:
+
+ * <<<\*\*/Abstract\\*Test.java>>>
+
+ * <<<\*\*/Abstract\*TestCase.java>>>
+
+ []
+
  Now you have walked through setting up setting up a typical Maven project, building, testing, packaging and installing.
  This is likely the vast majority of what you will be doing with Maven and if you'ved noticed everything you've been
  able to do up to this point has been driven by an 18 line file, namely the project's model or POM. If you look at

maven-site/src/site/apt/guides/mini/guide-test-customization.apt

@@ -0,0 +1,9 @@
+ ------
+ Guide to test customization
+ ------
+ Jason van Zyl
+ ------
+ 12 October 2005
+ ------
+
+Guide to test customization