Every intermittent test failure has a reason which need bit of patience figure what went wrong. I'm petty much sure test classes executes before the failure case causing this trouble. You need to isolate which test class causing the failure when run in package.
Can you please check the following. 1. Check whether any other class use the same resources referred by failure cases. 2. Check all resources are deleted correctly @AfterClass 3. Divide the test suite into two and include failure case to it and execute (you need to include test classes to testng xml). Keep on dividing test suite and try to find the exact test case casing the problem. Thanks, Krishantha. On Thu, Jul 17, 2014 at 4:18 PM, Sameera Kannangara <[email protected]> wrote: > Hi all, > > I have following test cases which passes when ran alone, and fails when > running as test packages. > > addWSDL(org.wso2.carbon.registry.jira.issues.test.Carbon11572TestCase): > expected:<false> but was:<true> > > cleanup(org.wso2.carbon.registry.jira2.issues.test2.Registry633TestCase): > Failed to perform delete operation > > Unlike previous similar case mentioned in the mail thread [1], these > classes have "depends on" attributes added to @test annotations. > repository used for testing is located at [2]. > > > Thank you, > SameeraK. > > [1] [Dev][G-Reg][integration-testing] Interleaving test classes > [2] https://github.com/sameerak/product-greg > > > -- > Sameera Kannangara, > Software Engineer, > WSO2 Inc. > -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear.
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
