Folks, As of now, we are simply focusing on testing the admin services and samples. There are other aspects on the server side that are not exposed via either of these. For example, all admin services should be exposed only via HTTPS. It is alway possible that somebody accidentally exposes these services via other transports. To test something like that, we can get some tests to run on the server side, and return results. These server side components could be simple AAR services. The JUnit tests could trigger these services, the tests will be executed on the server side, the results will be returned and verified on the client side.
In fact, this is how EJBs are tested using the Cactus framework. -- *Afkham Azeez* Senior Software Architect & Senior Manager; 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
