]
Aslak Knutsen updated ARQ-1813:
-------------------------------
Fix Version/s: rest_1.0.0.next
(was: rest_1.0.0.Alpha3)
REST TestSuite has execution order issues
-----------------------------------------
Key: ARQ-1813
URL:
https://issues.jboss.org/browse/ARQ-1813
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Extension - REST
Reporter: Aslak Knutsen
Assignee: Bernard Labno
Fix For: rest_1.0.0.next
Depending on the @Test method execution order the REST test suite randomly fail.
This seems to effect all ftests and local tests, RestClientTestCase.
If the ban* @Test methods are executed first, everything is ok. The banX methods will
call findAllCustomers on CustomerResourceImpl and if it's the first call create
Customer with id (nextId()) 1 and 2 which the Test Case is trying to lookup.
If on the other hand some of the following @Test methods run first,
createCustomerBareResource, manualClassModifier, nextId() is invoked and when banX methods
are called later and the 'customer list' is created, the expected Customers now
have id 3-4.