Also take into consideration scenarios where we need more than one server up. For example, BAM needs AS/ ESB with data publishers for the basic test to be done.
We right now write tests with a simple client firing events at the BAM server. But from a QA point of view, this automation doesn't make sense as he has to verify the whole scenario manually anyway. To verify that the data publishers get installed and fire events properly. On Fri, Jul 22, 2011 at 11:01 AM, Charitha Kankanamge <chari...@wso2.com>wrote: > > On Fri, Jul 22, 2011 at 10:49 AM, Rajika Kumarasiri <raj...@wso2.com>wrote: > >> >> >> On Thu, Jul 21, 2011 at 9:59 PM, Charitha Kankanamge >> <chari...@wso2.com>wrote: >> >>> Hi Folks, >>> >>> During Carbon-3.20 release cycle, automated integration tests have been >>> merged to carbon trunk and now they are part of carbon build. Because of >>> this, these tests cannot be executed against an external carbon server >>> setup. For example, if we need to do regression testing of a custom setup, >>> we are unable to use the integration tests since the tests are run based on >>> a server which starts up at the build time. >>> Can we customize the existing integration tests to run against any binary >>> product or Is there any alternative approach? >>> Or else, do we need to maintain a replica of integration test framework >>> so that we can run them separately from carbon build process? >> >> >> >> I had the same question, because I wanted to test the features ( and make >> sure they remain un-broken when adding new code) at component compilation >> time. >> >> According to the way how integrated test work it can't use at component >> compilation time. So I fixed my Junit test such that they point to a live >> server at compilation time and run the test ( one flaw is in >> this approach is you need to have a build of the server in advance before >> run the tests). >> >> Off the topic. >> From the QA point of view I think we should automate everything that can >> be automated. We should auto-mate repeating tasks. A human interaction only >> need to verify the result. I think we should have a dedicated resource for >> QA development. Also see [0], to see what we can learn from others. >> > > Agree. There were success and failures in test automation at WSO2. The > biggest concerns were the maintainability of some tests and the QA team have > always been busy with releases and support work, hence we could not continue > a focused effort on automation. Now we have a dedicated team for automation. > Lets hope for the best :) > > >> >> Rajika >> >> [0] - http://google-engtools.blogspot.com/ >> >> >>> >>> >>> Regards >>> Charitha >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> Carbon-dev@wso2.org >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> _______________________________________________ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Regards, Tharindu
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
