[jboss-jira] [JBoss JIRA] (WFCORE-2746) Move elytron management security tests from full to core

[Ondrej Lukas (JIRA)]

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

Ondrej Lukas commented on WFCORE-2746:
--------------------------------------

[~jamezp] [~luck3y] I totally agree, I am also not a big fan of running test in some pre-defined order since common tests should be independent on each other. However point of usage InSequence is decreasing a time needed for running particular test case if server reloads are needed there.

See the example:
Configure 4 different Elytron ssl-contexts. We want to run 4 tests for every of that ssl-context used in http-interface. We setup server configuration in @BeforeClass, then there are two ways how to simply run the tests:
* Definitely, clear solution is setup needed ssl-context in http-interface (through write-attribute) for particular test case which means that test are independent. However, every this change needs to reload server, which means 16 server reload.
* In case we use InSequence, then we can setup ssl-context A and run all tests for it, then setup ssl-context B and run all tests for it and so on. It means 4 server reloads are needed.

It is just an example, but I think it describes use case for current usage of InSequence annotation. Is there any different way how to deal with mentioned above scenario in general?

> Move elytron management security tests from full to core
> --------------------------------------------------------
>
>                 Key: WFCORE-2746
>                 URL: https://issues.jboss.org/browse/WFCORE-2746
>             Project: WildFly Core
>          Issue Type: Task
>          Components: Domain Management, Security, Test Suite
>            Reporter: Brian Stansberry
>
> Since until recently the elytron subsystem wasn't part of the core feature pack, a lot of integration tests of its use ended up in the WildFly full testsuite instead of in core. This task is to get tests that are only testing core functionality moved into the core testsuite. Because that's the right thing to do, but also because it's useful in practice by eliminating a cause for messy coordinated changes to core and full such that code changes in core can be tested.
> Corresponding Wildfly JIRA: https://issues.jboss.org/browse/WFLY-8723
> There are a number of aspects to this, for which I'll create subtasks.
> Following is an initial list of tests that should be moved. *This is meant to be a living list, with things added as they are noticed.* So anyone should feel free to edit this JIRA description to add things to the list.
> -org.jboss.as.test.integration.security.perimeter.* [2]-
> -org.jboss.as.test.manualmode.mgmt.elytron.HttpMgmtInterfaceElytronAuthenticationTestCase-
> -org.jboss.as.test.integration.domain.AbstractSlaveHCAuthenticationTestCase and subclasses.[1]-
> org.jboss.as.test.integration.security.credentialreference [2]
> integration/elytron/
> [1] One subclass of this is not related to elytron but should be moved to core too. I haven't looked closely but it uses vault, which may be why it is in full. But we can use vault in the core testsuite now.
> [2] Currently using Arquillian.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)