[jboss-jira] [JBoss JIRA] (WFLY-2507) InflowFlatTestCase and InflowJarTestCase are failing on Windows

[Kabir Khan (JIRA)]

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

Kabir Khan edited comment on WFLY-2507 at 11/15/13 8:59 AM:
------------------------------------------------------------

A good way to debug test ordering problems is to implement a temporary testsuite, which last time I tried this ran the tests in the order specified in SuiteClasses

{code}
@RunWith(Suite.class)
@Suite.SuiteClasses ({
...
})
public class __Throwaway {
{code}
Then you can quickly run with 'mvn clean install -Dtest=__Throwaway' and add/remove test classes until you isolate the two causing the problems
                
      was (Author: kabirkhan):
    A good way to debug test ordering problems is to implement a temporary testsuite

{code}
@RunWith(Suite.class)
@Suite.SuiteClasses ({
...
})
public class __Throwaway {
{code}
Then you can quickly run with 'mvn clean install -Dtest=__Throwaway' and add/remove test classes until you isolate the two causing the problems
                  
> InflowFlatTestCase and InflowJarTestCase are failing on Windows
> ---------------------------------------------------------------
>
>                 Key: WFLY-2507
>                 URL: https://issues.jboss.org/browse/WFLY-2507
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JCA
>            Reporter: Brian Stansberry
>            Assignee: Jesper Pedersen
>             Fix For: 8.0.0.CR1
>
>
> Tests are consisently failing on Windows but not on Linux:
> http://brontes.lab.eng.brq.redhat.com/project.html?projectId=WF&testNameId=-4393166542338832492&tab=testDetails
> Typically that would indicate a problem that manifests when tests are run in a different order; i.e. one test leaving behind something that impacts another.
> I suspect what's happening here is an RA is getting left behind and these tests are finding the wrong one and making assertions against it.
> Note this in the test is used to find the RA id:
> Set<String> ids = repository.getResourceAdapters();
> {code}
> 		assertNotNull(ids);
> 		System.out.println("////RA" + ids.toString());
> 		String piId = getElementContaining(ids,        "MultipleResourceAdapter");
> {code}
> The test logging shows there are two RAs that would match:
> 03:45:54,709 INFO  [stdout] (pool-1-thread-4) ////RA[org.jboss.as.test.integration.jca.rar.MultipleResourceAdapter#27, org.jboss.as.test.integration.jca.rar.MultipleResourceAdapter#28]

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