[jboss-jira] [JBoss JIRA] (WFLY-8630) Tests broken as part of WildFly Core 3.0.0.Beta16
[
https://issues.jboss.org/browse/WFLY-8630?page=com.atlassian.jira.plugin....
]
Brian Stansberry updated WFLY-8630:
-----------------------------------
Comment: was deleted
(was: It's *possible* these can be corrected via a change in full tomorrow. Two of the
4 (SwitchIdentityTestCase) had edits in the ladybird PR, so maybe something needs
tweaking. And the CLISecurityTestCase is checking the CLI can't authenticate, and it
can't, which is good. But the output from the CLI is different than the assert. That
may or may not be a meaningful issue.
SlaveHostControllerElytronAuthenticationTestCase is failing in a test of using PLAIN auth.
So of course we want that fixed but I don't know whether it's critical enough to
delay the DR or cram in a new core release.)
Tests broken as part of WildFly Core 3.0.0.Beta16
-------------------------------------------------
Key: WFLY-8630
URL: https://issues.jboss.org/browse/WFLY-8630
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Brian Stansberry
Assignee: Darran Lofthouse
Tests shown here are going to be ignored or otherwise modified in order to get the core
3.0.0.Beta16 release integrated.
org.jboss.as.test.integration.domain.elytron.SlaveHostControllerElytronAuthenticationTestCase.testSlaveRegistration
org.jboss.as.test.integration.ejb.container.interceptor.security.SwitchIdentityTestCase.testClientLoginModule
org.jboss.as.test.integration.ejb.container.interceptor.security.api.SwitchIdentityTestCase.testClientLoginModule
org.jboss.as.test.integration.security.perimeter.CLISecurityTestCase.testConnect
Failure examples:
http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=113878&bui...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)