[arquillian-issues] [JBoss JIRA] (ARQ-1813) REST TestSuite has execution order issues

[Aslak Knutsen (JIRA)]

    [ https://issues.jboss.org/browse/ARQ-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981210#comment-12981210 ] 

Aslak Knutsen commented on ARQ-1813:
------------------------------------

Created temp fix to allow Alpha3 release to go through; https://github.com/arquillian/arquillian-extension-rest/commit/c9146cc4a82a6634a0a01110a7f76f67e7285c5a

> 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.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)