You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Tom White (JIRA)" <ji...@apache.org> on 2010/06/08 22:32:12 UTC
[jira] Created: (WHIRR-22) Separate unit and integration (system)
tests
Separate unit and integration (system) tests
--------------------------------------------
Key: WHIRR-22
URL: https://issues.apache.org/jira/browse/WHIRR-22
Project: Whirr
Issue Type: Improvement
Components: core
Reporter: Tom White
Fix For: 0.1.0
It should be possible to run unit and integration tests independently of one another. Maven doesn't appear to have a convention for where to put integration tests (http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html), so we might use JUnit categories, or just Java packaging to segregate the two.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WHIRR-22) Separate unit and integration (system)
tests
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876866#action_12876866 ]
Patrick Hunt commented on WHIRR-22:
-----------------------------------
doing this would facilitate hudson/buildbot integration (run only the unit tests, that is unless/until we get mock provider support from jclouds)
> Separate unit and integration (system) tests
> --------------------------------------------
>
> Key: WHIRR-22
> URL: https://issues.apache.org/jira/browse/WHIRR-22
> Project: Whirr
> Issue Type: Improvement
> Components: core
> Reporter: Tom White
> Fix For: 0.1.0
>
>
> It should be possible to run unit and integration tests independently of one another. Maven doesn't appear to have a convention for where to put integration tests (http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html), so we might use JUnit categories, or just Java packaging to segregate the two.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WHIRR-22) Separate unit and integration (system)
tests
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated WHIRR-22:
---------------------------
Status: Patch Available (was: Open)
Assignee: Tom White
> Separate unit and integration (system) tests
> --------------------------------------------
>
> Key: WHIRR-22
> URL: https://issues.apache.org/jira/browse/WHIRR-22
> Project: Whirr
> Issue Type: Improvement
> Components: core
> Reporter: Tom White
> Assignee: Tom White
> Fix For: 0.1.0
>
> Attachments: WHIRR-22.patch
>
>
> It should be possible to run unit and integration tests independently of one another. Maven doesn't appear to have a convention for where to put integration tests (http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html), so we might use JUnit categories, or just Java packaging to segregate the two.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WHIRR-22) Separate unit and integration (system)
tests
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12880910#action_12880910 ]
Tom White commented on WHIRR-22:
--------------------------------
Maven Failsafe can be used to run integration tests: http://maven.apache.org/plugins/maven-failsafe-plugin/. See also http://onjavahell.blogspot.com/2009/05/integration-testing-with-maven-20.html.
> Separate unit and integration (system) tests
> --------------------------------------------
>
> Key: WHIRR-22
> URL: https://issues.apache.org/jira/browse/WHIRR-22
> Project: Whirr
> Issue Type: Improvement
> Components: core
> Reporter: Tom White
> Fix For: 0.1.0
>
>
> It should be possible to run unit and integration tests independently of one another. Maven doesn't appear to have a convention for where to put integration tests (http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html), so we might use JUnit categories, or just Java packaging to segregate the two.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WHIRR-22) Separate unit and integration (system)
tests
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated WHIRR-22:
---------------------------
Status: Resolved (was: Patch Available)
Resolution: Fixed
I've just committed this.
> Separate unit and integration (system) tests
> --------------------------------------------
>
> Key: WHIRR-22
> URL: https://issues.apache.org/jira/browse/WHIRR-22
> Project: Whirr
> Issue Type: Improvement
> Components: core
> Reporter: Tom White
> Assignee: Tom White
> Fix For: 0.1.0
>
> Attachments: WHIRR-22.patch
>
>
> It should be possible to run unit and integration tests independently of one another. Maven doesn't appear to have a convention for where to put integration tests (http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html), so we might use JUnit categories, or just Java packaging to segregate the two.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WHIRR-22) Separate unit and integration (system)
tests
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated WHIRR-22:
---------------------------
Attachment: WHIRR-22.patch
This patch moves integration tests to packages ending with ".integration", these can be run with "mvn verify" (as well as setting the arguments for the cloud provider settings). There's now a unit test for RunUrlBuilder. Tests are run with "mvn test".
> Separate unit and integration (system) tests
> --------------------------------------------
>
> Key: WHIRR-22
> URL: https://issues.apache.org/jira/browse/WHIRR-22
> Project: Whirr
> Issue Type: Improvement
> Components: core
> Reporter: Tom White
> Fix For: 0.1.0
>
> Attachments: WHIRR-22.patch
>
>
> It should be possible to run unit and integration tests independently of one another. Maven doesn't appear to have a convention for where to put integration tests (http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html), so we might use JUnit categories, or just Java packaging to segregate the two.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.