Hi, Existing Integration tests in BPS consist of following modules. Login - (1 Test) Management - (5 Tests) BPEL - (8 Tests) Instance Cleanup - (1 Test) External Data sources - (1 Test) BPEL Security - (2 Tests)
I have completed migrating Management tests, then added Login/Logout, SecurityVerifier tests. Hoping to complete rest of the migration within this week. BTW, since some of us are presenting papers in the ERU Research Symposium at UOM tomorrow at different time slots, I think it might be difficult to arrange a meeting tomorrow. Thanks, Keheliya On Wed, Dec 21, 2011 at 8:28 PM, Afkham Azeez <[email protected]> wrote: > We need to have a meeting tomorrow to check on the progress of the test > migration effort. I have so far received a patch from Suho with the CEP > migration & CEP integration tests are working fine now. How about the > others? > > On Fri, Dec 16, 2011 at 3:32 PM, Afkham Azeez <[email protected]> wrote: > >> The following team of people will be working on product integration >> testing over the next 3 working weeks. They will start working on this >> immediately. The objective is to improve the code coverage of all products. >> Nobody has been assigned from G-Reg & Carbon core. >> >> BPS - Keheliya >> BAM - Sinthuja >> DSS - Shelan and Lakmali >> Achala and Maninda will be working on GS and MS >> GS - Achala >> MS - Maninda >> CEP - Suhothayan >> BRS - Ishara >> AS - KasunG >> IS - Johann >> ESB - Nuwan and Ishan >> G-Reg - ? >> Carbon Core - ? >> >> *Plan for each product* >> 1. Spend up to one day learning TestNG >> 2. Migrate existing integration tests to TestNG. This has already been >> done for Carbon core, AS & BRS >> 3. Fix all failing integration tests >> 4. Add SecurityVerification test to each product >> 5. Identify the functional areas of each product & add integration tests >> >> *Best Practices* >> 1. No sysouts after running tests. Use assert statements. >> 2. Comments & test descriptions should be adde >> 3. Follow coding conventions >> 4. Do not follow the "Catch & Fail" antipattern [0]. If exceptions are >> expected, use the @ExpectedExceptions [1] annotation. Throw all unexpected >> exceptions from the test methods so that these tests result in errors, not >> failures. >> >> Team, please make this an opportunity to learn & master the art of unit & >> integration testing. >> >> Thanks >> Azeez >> >> 0. >> http://www.exubero.com/junit/antipatterns.html#Catching_Unexpected_Exceptions >> 1. >> http://testng.org/javadoc/org/testng/annotations/ExpectedExceptions.html >> >> >> -- >> *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* >> >> > > > -- > *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 > > -- Keheliya Gallaba Software Engineer WSO2 Inc. E-mail: keheliya AT wso2.com M: +94 71 551 8881
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
