Excellent thoughts Shariq. Integration tests for Stratos are essential. I guess what we should do is, do a full build, run the Stratos setup script, create tenants, run some tenant management tests, run some tenant specific tests, platform sample test etc.
Please consult your MC on working with the automation team to get this done. On Fri, Jan 20, 2012 at 9:51 AM, Muhammed Shariq <[email protected]> wrote: > Hi Krishantha et al, > > If I am not mistaken we are running these test for products only right, at > the moment? How about the possibility of running these test on the stratos > services too ? I had a chat with Dhrashana and we most of the tests that > covers multitenancy aspect, so its a matter of setting up a stratos > deployment in the bamboo machins right? I can work with the automation team > to get this running. IIRC we even used these test suite to smoke test SLive > after migrations etc, so we already have it. > > My concern is that, once we start developing new features we usually do > development and testing cycles with the product. Ultimately the services > gets side lined until quite late in the release cycle. If we can run a full > test round once a week maybe and get notifications of the failures (or on > the build status dashboard itself), we wouldn't need to worry about the > status of the trunk at any time. WDYT ? > > On a related note, there was a thread on adding TestNG integration test to > cover tenant aspects as well, wonder if we have made any progress in that > front? Thinking about it, we first need to create a tenant, and also some > of the tenant related test would require a proper setup (with mounting etc) > prior to running the tests. Guess we need to put more thought into that? > > On Fri, Jan 20, 2012 at 12:23 AM, Krishantha Samaraweera < > [email protected]> wrote: > >> Hi, >> >> We have done the $subject on Bamboo machine and it is working. You can >> find the last successful test build at [1]. >> >> Test framework has been configured to use packs generated by trunk build. >> The test setup consists of five products (ESB, G-Reg, AS, BPS and DSS) with >> registry mounts on top of Mysql. This include Selenium test for G-Reg as >> well. I had to exclude Ravana tests due to few issues after updating the >> Ravana framework. Will get them fix by tomorrow. >> >> Thanks, >> Krishantha. >> >> [1] http://wso2.org/bamboo/browse/WSO2CARBONTUNK-AUTOMATIONTEST-13/ >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > Thanks, > Shariq. > Phone: +94 777 202 225 > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **[email protected]* <[email protected]>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
