]
Ondrej Lukas commented on WFCORE-2746:
--------------------------------------
Usage of {{(a)FixMethodOrder(MethodSorters.NAME_ASCENDING)}} is based on lexicographic order
which seems very unwieldy and not so intuitive as Arquillian InSequence, but it would
probably work. However I am talking here probably only about unit of test cases so this
approach is applicable (I just tried to avoid to eventual rewriting test to something less
intuitive). Once I will migrate some test case from our internal TS which will use
mentioned above scenario I try to use {{(a)FixMethodOrder(MethodSorters.NAME_ASCENDING)}}.
Thanks!
Another two suggestions are not applicable for following reasons:
# Making separate test still does not reduce number of server reloads since every separate
test case will need it.
# As I understand your point 2. correctly it means that one test method would test more
different scenarios. In case some of private test method will fail then another private
test method will not be executed. It can hide another issue.
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.