[jboss-jira] [JBoss JIRA] Created: (JBAS-7537) allow find grained testing with server start/stop

[Jonathan Halliday (JIRA)]

allow find grained testing with server start/stop
-------------------------------------------------

                 Key: JBAS-7537
                 URL: https://jira.jboss.org/jira/browse/JBAS-7537
             Project: JBoss Application Server
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Test Suite
    Affects Versions: JBossAS-6.0.0.M1
            Reporter: Jonathan Halliday
            Assignee: Shelly McGowan
             Fix For: JBossAS-6.0.0.M2


I wish to be able to configure hudson runs that smoke test using a given group or groups of tests. When testing interactively, the process is:

(start desired server in another shell)
cd testsuite; ./build.sh -Dtest=foo test
(stop server)

However, I'd like to be able to do this as a single command, so it can be easily automated in hudson runs.

Suggested approach:

testsuite/build.xml:

    <target name="test-with-server" if="server" depends="init"
            description="Execute a singe test with specified server config startup/shutdown">
        <server:start name="${server}"/>
        <antcall target="test" inheritRefs="true"/>
        <server:stop name="${server}"/>
    </target>

and likewise for one-test.

Whilst this change is minimal, making it work would also require fixing server:start so it does not incorrectly barf when passed an arg of "default":

java.lang.IllegalArgumentException: There is no server named: default
	at org.jboss.jbossas.servermanager.ServerManager.getServer(ServerManager.java:124)
	at org.jboss.jbossas.servermanager.ServerManager.startServer(ServerManager.java:163)
	at org.jboss.ant.taskdefs.server.StartServerTask.startServer(StartServerTask.java:72)



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira