You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2003/12/02 23:15:06 UTC
[jira] Updated: (MAVEN-515) unit test levels
The following issue has been updated:
Updater: Jason van Zyl (mailto:jason@zenplex.com)
Date: Tue, 2 Dec 2003 4:14 PM
Changes:
environment changed to
Component changed to pom
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-515&page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-515
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-515
Summary: unit test levels
Type: Improvement
Status: Open
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
pom
Fix Fors:
1.1
Assignee: Brett Porter
Reporter: Brett Porter
Created: Mon, 23 Jun 2003 9:53 AM
Updated: Tue, 2 Dec 2003 4:14 PM
Description:
This is to track the progress of what is decided about this feature. Once again, happy to implement when I get time as I need it for work :)
here is the proposal sent to the list:
proposal: allow multiple unit test sets in the POM
justification: some take a long time to run or require resources not always present, and should be omitted in regular development, but run in nightly builds for example.
implementation:
<unitTest>
<type>default</type> (same as if type ommitted)
... as before ...
</unitTest>
<unitTest>
<type>performance</type>
...
</unitTest>
<unitTest>
<type>integration</type>
...
</unitTest>
<unitTest>
<type>touchstone</type>
...
</unitTest>
By default, just the first is run, but by setting -Dmaven.test.sets=performance,integration
Then those will be run (and default which is always run)
There will also be the special case of -Dmaven.test.sets=all, which will run everything. Or perhaps test:test-all?
They could all use the same unitTestSourceDirectory, or move those into each unitTest set (with code to keep it backwards compatible).
Each set would have its own junit report I imagine.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org