[arquillian-issues] [JBoss JIRA] Commented: (ARQ-228) Using Managed Container fails for first test case but runs the next
Aslak Knutsen (JIRA)
jira-events at lists.jboss.org
Tue Jul 27 11:27:33 EDT 2010
[ https://jira.jboss.org/browse/ARQ-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12541233#action_12541233 ]
Aslak Knutsen commented on ARQ-228:
-----------------------------------
When using JUnit, throwing a Exception from Runner does not stop the rest of the run. So when a check if server has started fails in @BeforeSuite, the next testcase goes straight threw @BeforeSuite to @BeforeClass. At this point the Container is setup enough to deploy.
> Using Managed Container fails for first test case but runs the next
> -------------------------------------------------------------------
>
> Key: ARQ-228
> URL: https://jira.jboss.org/browse/ARQ-228
> Project: Arquillian
> Issue Type: Bug
> Components: Test Harness Integration
> Affects Versions: 1.0.0.Alpha3
> Reporter: Aslak Knutsen
> Assignee: Aslak Knutsen
> Fix For: 1.0.0.Alpha3
>
>
> Managed Containers should not support to attach them selves to running instances to due to security issues.
> When running multiple test cases using the JBoss AS Managed 6 container, the first test case fail with "The server is already running!...", but the second test case deploys fine and runs.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the arquillian-issues
mailing list