[
https://issues.jboss.org/browse/WFLY-143?page=com.atlassian.jira.plugin.s...
]
RH Bugzilla Integration commented on WFLY-143:
----------------------------------------------
Chao Wang <chaowan(a)redhat.com> made a comment on [bug
969915|https://bugzilla.redhat.com/show_bug.cgi?id=969915]
Description of problem:
Failed line at #67 used a wrong LifecycleInterceptorNoProceed instead of
LifecycleInterceptorWithProceed.
Version-Release number of selected component (if applicable):
EAP 6.1.0, upstream
How reproducible:
running single testInterceptorPostConstructWithProceed, or running
testInterceptorPostConstructWithProceed at first place, we can constantly see the
failure.
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Improve testing of Infinispan subsystem management features
-----------------------------------------------------------
Key: WFLY-143
URL:
https://issues.jboss.org/browse/WFLY-143
Project: WildFly
Issue Type: Bug
Components: Clustering, Domain Management
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 8.0.0.Alpha2
We current use InfinispanSubsystemTest to test the integrity of the Infinispan subsystem
implementation.
From the documentation:
{noformat}
Tests the ability to create a model from an xml configuration, marshal the model back to
xml, re-read that marshalled model
into a new model that matches the first one, execute a "describe" operation for
the model, create yet another model
from executing the results of that describe operation, and compare that model to first
model.
{noformat}
Over and above these tests, we need more specific tests which cover use cases such as:
- every attribute can be read/written as required and that the subsequent reload-required
state is as expected
- operation sequences such as add/remove/add, add/add give expected results for all
resources in the subsystem
- validating that the XML configuration specified gets translated into the desired
Infinispan configuration
- and many others
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira