fixed the tests-governance-api module test by downgrading testng version to 6.1.1 from 6.8. Now all tests(59) are passed in tests-governance-api. module. will work on tests-new to fix the test failures.
On Thu, Aug 22, 2013 at 11:50 AM, Lasith Chandrasekara <[email protected]>wrote: > +1 for est execution flow. > > > On Thu, Aug 22, 2013 at 11:47 AM, Nuwan Wimalasekara <[email protected]>wrote: > >> All tests were executed sequentially in previous releases. and Tests are >> not designed to run parallel. so need to fix the test execution flow. >> >> >> On Thu, Aug 22, 2013 at 11:32 AM, Lasith Chandrasekara >> <[email protected]>wrote: >> >>> Out tests are not designed to run in parallel. So either we should >>> change tests to run in parallel or should change test framework to execute >>> tests sequentially. >>> Changing tests to support this is not that easy also not possible for >>> some situations (like configuration changes to greg config files). >>> >>> >>> >>> On Thu, Aug 22, 2013 at 11:26 AM, Nuwan Wimalasekara <[email protected]>wrote: >>> >>>> Hi Ajith >>>> I am looking into this. >>>> >>>> Thanks, >>>> Nuwanw >>>> >>>> >>>> On Thu, Aug 22, 2013 at 11:20 AM, Ajith Vitharana <[email protected]>wrote: >>>> >>>>> +1. But we are observing weird behavior in the test framework (may be >>>>> TestNG issue) even with the default pack. The main problem is test >>>>> framework load all the test cases in all the packages and execute >>>>> randomly. >>>>> This makes the different results at each time we run all the tests >>>>> together. >>>>> >>>>> Thanks >>>>> Ajith. >>>>> >>>>> >>>>> On Thu, Aug 22, 2013 at 11:06 AM, Krishantha Samaraweera < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi All, >>>>>> >>>>>> I think we can easily run G-Reg integration test with different DB >>>>>> configs. We have to get G-Reg pack and edit DB configs, then >>>>>> compress it and put it to the correct location and execute tests. >>>>>> >>>>>> We can generate a pack with all integration tests and point and run >>>>>> but, but all test cases depends on the run time configuration changes >>>>>> will >>>>>> be skipped, To get the full benefit of automated tests I highly recommend >>>>>> to run the tests on the branch. >>>>>> >>>>>> Thanks, >>>>>> Krishantha. >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Ajith Vitharana. >>>>> WSO2 Inc. - http://wso2.org >>>>> Email : [email protected] >>>>> Mobile : +94772217350 >>>>> >>>>> >>>>> _______________________________________________ >>>>> Dev mailing list >>>>> [email protected] >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Nuwan Wimalasekara >>>> Senior Software Engineer - Test Automation >>>> WSO2, Inc.: http://wso2.com >>>> lean. enterprise. middleware >>>> >>>> phone: +94 71 668 4620 >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >> >> >> -- >> Nuwan Wimalasekara >> Senior Software Engineer - Test Automation >> WSO2, Inc.: http://wso2.com >> lean. enterprise. middleware >> >> phone: +94 71 668 4620 >> >> >> >> > -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
