ESB UI tests were executed and there were three test failures. Two test cases were fixed.
I have seen dead page while executing EndpointsListTestCase, this test case is added for JIRA at https://wso2.org/jira/browse/ESBJAVA-2586 Can ESB team please check the patch is provided in the JIRA is properly applied. Thanks, Krishantha. On Thu, Jan 30, 2014 at 10:59 AM, Krishantha Samaraweera < krishan...@wso2.com> wrote: > Thanks IsuruU for the update. > > Can you send me the class names of those two failed cases. I will have a > look. If we cannot fix it property before the release, we need to disable > those tests. > > With regard to the UI test failures. I think issue is with browser version > compatibility with selenium version we used. Updating selenium version in > test framework at this stage is not a good decision. Because it could > introduce dependency conflicts with axis2 dependencies (we experience this > before) > > Thus, my recommendation is to use -Dwebdriver.firefox.bin option with > maven and point it to earlier version of firefox 20~24. Note that you don't > need to downgrade firefox, just pointing to firefox binary will be enough. > > e.g > maven install -Dwebdriver.firefox.bin=/path/to/your/firefox/firefox-20-bin > > Thanks, > Krishantha. > > > On Thu, Jan 30, 2014 at 10:38 AM, Isuru Udana <isu...@wso2.com> wrote: > >> Hi Krishantha, >> >> All unit tests got passed in chunk-07 yesterday. >> We run all ESB integration tests at once and only 2 tests cases failed >> due to read timeouts. Those two got passed when run in isolation. >> Breaking tests into 6 modules has made a significant improvement. >> >> There are 4 other ui tests failures. >> According to Malka and NuwanW those failures are due to browser issues in >> the builder machine. >> >> BPS team is running integration tests for BPS. >> >> Thanks. >> >> >> On Wed, Jan 29, 2014 at 12:49 PM, Krishantha Samaraweera < >> krishan...@wso2.com> wrote: >> >>> Hi all, >>> >>> Can product RMs make sure to do the final release with zero test >>> failures. Otherwise we will have to fix them before creating custom >>> branches etc.. And test failure will directly impact to the current chunk >>> build stabilization process. So try to run all unit/integration >>> (backend/UI) test cases before the release. >>> >>> Please let automation team know, if you find any difficulty with fixing >>> failure cases. >>> >>> Thanks, >>> Krishantha. >>> >>> -- >>> Krishantha Samaraweera >>> Senior Technical Lead - Test Automation >>> Mobile: +94 77 7759918 >>> WSO2, Inc.; http://wso2.com/ >>> lean . enterprise . middlewear. >>> >>> _______________________________________________ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Isuru Udana* >> Senior >> * Software Engineer* >> WSO2 Inc.; http://wso2.com >> email: isu...@wso2.com cell: +94 77 3791887 >> blog: http://mytecheye.blogspot.com/ >> twitter: http://twitter.com/isudana >> > > > > -- > Krishantha Samaraweera > Senior Technical Lead - Test Automation > Mobile: +94 77 7759918 > WSO2, Inc.; http://wso2.com/ > lean . enterprise . middlewear. > -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear.
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
