[
https://issues.jboss.org/browse/WFLY-1407?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on WFLY-1407:
-----------------------------------------------
Chao Wang <chaowan(a)redhat.com> made a comment on [bug
968781|https://bugzilla.redhat.com/show_bug.cgi?id=968781]
Description of problem:
org.jboss.as.test.integration.ejb.interceptor.method.EjbMethodInterceptorTestCase failed
intermittently due to dependency of test ordering on
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-AS-T...
This test assumes testMethodLevelInterceptors() run at first which does not contain
variable TopSecretInterceptor.called reset to false at beginning like second test method
does. If test run in different order, then it will fail, should isolate this
"connection" between test methods.
Version-Release number of selected component (if applicable):
EAP 6.1.1
How reproducible:
Use @InSequence to run testMethodOverloaded() before testMethodLevelInterceptors(), then
test will fail.
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
No dependency between test order.
Additional info:
Correct test methods dependency in EjbMethodInterceptorTestCase
---------------------------------------------------------------
Key: WFLY-1407
URL:
https://issues.jboss.org/browse/WFLY-1407
Project: WildFly
Issue Type: Bug
Components: Test Suite
Affects Versions: 8.0.0.Alpha1
Reporter: Chao Wang
Assignee: Chao Wang
Priority: Minor
Fix For: 8.0.0.Alpha2
Attachments: failure-stacktrace.txt, WFLY-1407.patch
org.jboss.as.test.integration.ejb.interceptor.method.EjbMethodInterceptorTestCase failed
intermittently due to dependency of test ordering on
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-AS-T...
In upstream code, its bean fixed by forcing test running in order, however, the real
issue behind is that it assumes testMethodLevelInterceptors() run at first which does not
contain variable TopSecretInterceptor.called reset to false at beginning like second test
method does.
--
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