]
Kabir Khan commented on WFCORE-1836:
------------------------------------
[~pferraro] Does FailedOperationTransformationConfig.ChainedConfig help at all? There
should be a few usages of that scattered around the subsystem tests. I'm afraid I
don't remember off the top of my head if it will work for exactly this situation since
it has been a while, but it was done to work around situations like this (at least vaguely
similar situations!).
Rejection-style transformer tests assume each operation generated by
parser has distinct PathAddress
----------------------------------------------------------------------------------------------------
Key: WFCORE-1836
URL:
https://issues.jboss.org/browse/WFCORE-1836
Project: WildFly Core
Issue Type: Bug
Components: Test Suite
Reporter: Paul Ferraro
Assignee: Brian Stansberry
For rejection-style transformer tests, the subsystem test framework stores expected
rejected operations in a map keyed by PathAddress. This is fine when the subsystem's
parser only generates add operations. However, if the parser generates an add operation
as well as a a write-attribute operation, these 2 operations will have the same path
address. If we expect one of these operations to be rejected, but not the other, we end
up with an unexpected rejection - and the test fails.
This is a little hard to explain in the abstract, so let me know if any of the above
doesn't make sense.