[jbosstools-issues] [JBoss JIRA] (JBIDE-6317) Run As targets for Arquillian

[Max Rydahl Andersen (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707551#comment-12707551 ] 

Max Rydahl Andersen commented on JBIDE-6317:
--------------------------------------------

Talking with Aslak reminded me there is actually a more than one kind of "launch" to support.

Need to consider what we would like/spend time on.
Some of these might overlap/"be identical" in the implementation, more investigation needed.

A. Run arquillian test with the default profile. (i.e. no customization, just what would happen if you do Run As > JUnit/Testng test

B. Run arquillian test with specific named profile (i.e. pass in -Darquillian.launch=<name of profile in arq configuration> to the launch.)

C. Run arquillian against one of the servers loaded in Eclipse (generate an arquillian.properties/xml and pass in via -Darquillian.properties|xml property + -Darquillian.launch=<unique name> or pass in enough -Darquillian.XXX properties to redefine a server and select it for the launch).

Link from Alsak that "documents" these options https://github.com/arquillian/arquillian-core/commit/9d3b82f736b7ab5407930af9954d2b88b2d416ac

One problem no matter what option here is that the classpath is fully controlled by maven - not sure we can fix that. For now just rely on user to manually select the right maven profile before hand.

Down the road (this might need its own launch config type) we could do the proper classpath resolution at test launch time instead of project wide.





                
> Run As targets for Arquillian
> -----------------------------
>
>                 Key: JBIDE-6317
>                 URL: https://issues.jboss.org/browse/JBIDE-6317
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: testing
>            Reporter: Pete Muir
>            Assignee: Snjezana Peco
>             Fix For: 3.3.x
>
>
> Arquillian allows you to run tests on multiple containers, which can be configured via which dependency you use in Maven, or in the future programmatically/declaratively.
> JBoss Tools could offer a "Run As" option for all supported containers, overriding this choice on a one-off basis.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira