Integrating Junit Testreport into the maven site

["Pleines, Karsten (I B 3)" <Ka...@bva.bund.de>]

Hi,
I've started to generate a maven site and it succeeds. The problem is, I
don't know how to integrate the Junit report into the site. 
Can somebody help me?

Thank you 
Karsten

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Integrating Junit Testreport into the maven site

[Jurgen De Landsheer <ju...@ugent.be>]

Pleines, Karsten (I B 3) wrote:

>Hi,
>I've started to generate a maven site and it succeeds. The problem is, I
>don't know how to integrate the Junit report into the site. 
>Can somebody help me?
>
>Thank you 
>Karsten
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>  
>

if you get a numberformatexception build version 2.0-beta-2 from the 
sources in subversion codehaus


all config settings are the defaults
except <testFailureIgnore>true</<testFailureIgnore> because if you do not set this to true,
you well never see failed tests in the site report because you wont have a site (junit failure
makes site generation stop)


...
    <reporting>

		<plugins>
			<plugin>
				<groupId>org.codehaus.mojo</groupId>
				<artifactId>surefire-report-maven-plugin</artifactId>
				<configuration>
					<!-- The base directory of the project being tested. This can be obtained in your unit test by System.getProperty("basedir"). -->
					<basedir>${basedir}</basedir>
					<!-- The directory containing generated classes of the project being tested. -->
					<classesDirectory>
						${project.build.outputDirectory}
					</classesDirectory>
					<!-- List of patterns (separated by commas) used to specify the tests that should be excluded in testing. When not specified and whent the test parameter is not specified, the default excludes will be **/Abstract*Test.java **/Abstract*TestCase.java -->
					<!--excludes>List</excludes-->
					<!-- List of patterns (separated by commas) used to specify the tests that should be included in testing. When not specified and whent the test parameter is not specified, the default includes will be **/Test*.java **/*Test.java **/*TestCase.java -->
					<!--includes>List</includes-->
					<!-- ArtifactRepository of the localRepository. To obtain the directory of localRepository in unit tests use System.setProperty( "localRepository"). -->
					<LocalRepository>
						${localRepository}
					</LocalRepository>
					<!-- List of of Plugin Artifacts. -->
					<pluginArtifacts>
						${plugin.artifacts}
					</pluginArtifacts>
					<!-- Option to print summary of test suites or just print the test cases that has errors. -->
					<printSummary>true</printSummary>
					<!-- Selects the formatting for the test report to be generated. Can be set as brief, plain, or xml. -->
					<reportFormat>brief</reportFormat>
					<!-- Base directory where all reports are written to. -->
					<reportsDirectory>
						${project.build.directory}/surefire-reports
					</reportsDirectory>
					<!-- Set this to 'true' to bypass unit tests entirely. Its use is NOT RECOMMENDED, but quite convenient on occasion. -->
					<skip>${maven.test.skip}</skip>
					<!-- List of System properties to pass to the JUnit tests. -->
					<!--systemProperties>Properties</systemProperties-->
					<!-- Specify this parameter if you want to use the test regex notation to select tests to run. The regular expression will be used to create an include pattern formatted like **/${test}.java When used, the includes and excludes patterns parameters are ignored -->
					<test>${test}</test>
					<!-- The directory containing generated test classes of the project being tested. -->
					<testClassesDirectory>
						${project.build.testOutputDirectory}
					</testClassesDirectory>
					<!-- Set this to true to ignore a failure during testing. Its use is NOT RECOMMENDED, but quite convenient on occasion. -->
					<testFailureIgnore>true</testFailureIgnore>
					<!-- Option to generate a file test report or just output the test report to the console. -->
					<useFile>true</useFile>
				</configuration>
			</plugin>

....


-- 


met vriendelijke groeten