Hi All, The purpose of the test automation framework model is to test the carbon engine which is a collection of admin services. Meanwhile we are automating the sample testing process. Currently the automation framework supports ~70% of esb sample tests. Soon, we will be able to increase that amount.
*How the ESB test automation works* -------------------------------------------------------- * ESB Sample test module* 1. From the code we set the sample number and load the synapse config file accordingly. (We are not maintaining a copy of each sample config inside our framework as the sample configurations (i.e: synapse_sample_#.xml) are subject to change in future releases of ESB) 2. Then we invoke the synapse config admin service progamatically, updated the config and run the client. 3. Finally we set the config to defaults. 4. You can simply run all samples or a selected set of samples. *Functionality test modules* 4. Build the proxy services for a particular scenario (not exactly the same kind of samples we discussed above) using proxy admin service and then sequences using sequences admin service likewise. Hopefully this will enhance the ability to test and verify the back-end functionality without much effort. Kindly appreciate your feedback. thanks *P.S: sorry for the delay in follow up as a result of mail subscription issue. * -- Thilini Ishaka Software Engineer Wso2,Inc http://wso2.com/ <http://wso2.org/> http://wso2.org/ email: [email protected] Contact [image: Linkedin] <http://www.linkedin.com/groups?gid=876687&about=>[image: Facebook]<http://www.facebook.com/home.php?#%21/pages/WSO2/45550523564?v=wall>[image: Twitter] <http://twitter.com/wso2>[image: Blogger] <http://wso2.com/blogs/>[image: Youtube] <http://www.youtube.com/wso2techflicks#p/a>
_______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
