[jbosstools-issues] [JBoss JIRA] (JBIDE-13796) rename jbosstools-integration-tests to jbosstools-itests
Nick Boldt (JIRA)
jira-events at lists.jboss.org
Thu Mar 28 01:49:42 EDT 2013
[ https://issues.jboss.org/browse/JBIDE-13796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761826#comment-12761826 ]
Nick Boldt edited comment on JBIDE-13796 at 3/28/13 1:48 AM:
-------------------------------------------------------------
The "itest" convention is everywhere, you just need to google a bit:
http://maven.apache.org/maven-1.x/plugins/itest/
http://henningpetersen.com/post/5/integration-testing-with-spring-and-maven
http://repo1.maven.org/maven2/openejb/openejb-itests/2.1.1/openejb-itests-2.1.1.pom
http://mvnrepository.com/artifact/org.fusesource.fabric.itests/
http://mvnrepository.com/search.html?query=itest
http://stackoverflow.com/questions/1228709/best-practices-for-integration-tests-with-maven (suggests putting source in src/itest/java)
We already have a project called "jbosstools-integration-stack" and another called "jbosstools-integration-tests". These are completely different things, so we should rename one of them for clarity. Renaming jbosstools-integration-stack to jbosstools-is is an option but why not put the itests into projects called jbosstools*-itests? Thus we would have:
{code}
jbosstools-integration-stack
jbosstools-integration-stack-itests
jbosstools-*
jbosstools-itests
{code}
was (Author: nickboldt):
The "itest" convention is everywhere, you just need to google a bit:
http://maven.apache.org/maven-1.x/plugins/itest/
http://henningpetersen.com/post/5/integration-testing-with-spring-and-maven
http://repo1.maven.org/maven2/openejb/openejb-itests/2.1.1/openejb-itests-2.1.1.pom
http://mvnrepository.com/artifact/org.fusesource.fabric.itests/
http://mvnrepository.com/search.html?query=itest
http://stackoverflow.com/questions/1228709/best-practices-for-integration-tests-with-maven (suggests putting source in src/itest/java)
We already have a project called "jbosstools-integration-stack" and another called "jbosstools-integration-tests". These are completely different things, so we should rename one of them for clarity. Renaming jbosstools-integration-stack to jbosstools-is is an option but why not put the itests into projects called jbosstools*-itests? Thus we would have:
{code}
jbosstools-integration-stack
jbosstools-integration-stack-itests
jbosstools-*
jbosstools-integration-tests
{code}
> rename jbosstools-integration-tests to jbosstools-itests
> --------------------------------------------------------
>
> Key: JBIDE-13796
> URL: https://issues.jboss.org/browse/JBIDE-13796
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools, updatesite
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.0.Alpha2
>
>
> To be consistent and more clear about purpose/content, I propose we rename the github project jbosstools-integration-tests to jbosstools-itests.
> Once renamed, will need to refactor:
> * job name
> * destination publishing folder - http://download.jboss.org/jbosstools/updates/nightly/integrationtests/ -> http://download.jboss.org/jbosstools/updates/nightly/itests/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list