[
http://jira.codehaus.org/browse/MGWT-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169023#action_169023
]
nicolas de loof commented on MGWT-21:
-------------------------------------
I've migrated gwt-maven documentation here :
http://mojo.codehaus.org/gwt-maven-plugin/testing.html
The TestMojo includes pattern defaults to "**/GwtTest*.java,**/Gwt*Suite.java"
so it may run your testSuite if you follow this naming convention.
To be honnest I don't use GwtTestCase myself so please test latest SNAPSHOT and
report any issue
> support for running GWTTestSuite instead of GWTTestCase
> -------------------------------------------------------
>
> Key: MGWT-21
> URL: http://jira.codehaus.org/browse/MGWT-21
> Project: Maven 2.x GWT Plugin
> Issue Type: New Feature
> Reporter: Arthur Kalmenson
>
> I've mentioned this before, but I figured I'd post a feature request for it.
> For GWT projects that make extensive use of GWTTestCase for integration
> testing, running each GWTTestCase separately increases the build time
> substantially. This happens because a headless hosted mode needs to be
> launched for each test class. GWT offers an optimization called GWTTestSuite
> that allows you to group GWTTestCases together into a suite that launches the
> headless hosted mode once. This feature is currently supported in the Google
> Code gwt-maven plugin. See this for more information:
> http://code.google.com/docreader/#p=google-web-toolkit-doc-1-5&s=google-web-toolkit-doc-1-5&t=DevGuideJUnitSuites
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
