]
Marek Kopecký updated WFLY-8109:
--------------------------------
Git Pull Request:
Improve timeouts in AS TS
-------------------------
Key: WFLY-8109
URL:
https://issues.jboss.org/browse/WFLY-8109
Project: WildFly
Issue Type: Enhancement
Components: Test Suite
Reporter: Marek Kopecký
Assignee: Marek Kopecký
Improve timeouts in AS TS
* JMSMessageDrivenBeanTestCase should use TimeoutUtil for timeout
* increase timeout in PassivationTestCase
* JspCompilerTestCase should use TimeoutUtil for timeout
* increase timeout in MDBTestCase
* increase the default forked process timeout for basic module to hour, [same timeout is
used in clustering
module|https://github.com/wildfly/wildfly/blob/master/testsuite/integrati...]
* remove usage of TimeoutUtil from TxTestUtil. If -Dts.timeout.factor=200 is used,
MessageDrivenTimeoutTestCase.transactionTimeoutAnnotation and
MessageDrivenTimeoutTestCase.transactionTimeoutActivationProperty fail:
{noformat}
java.lang.AssertionError: Sent and received message does not match at expected way
expected:<replying annotation timeout> but was:<null>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at
org.jboss.as.test.integration.ejb.transaction.mdb.timeout.MessageDrivenTimeoutTestCase.transactionTimeoutAnnotation(MessageDrivenTimeoutTestCase.java:109)
java.lang.AssertionError: No message should be received as mdb timeouted expected null,
but was:<replying annotation timeout>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotNull(Assert.java:755)
at org.junit.Assert.assertNull(Assert.java:737)
at
org.jboss.as.test.integration.ejb.transaction.mdb.timeout.MessageDrivenTimeoutTestCase.transactionTimeoutActivationProperty(MessageDrivenTimeoutTestCase.java:126)
{noformat}
This stabilizes TS on slower machines.