Hi all, I would like to propose $subject. The test automation framework heavily depends on admin service clients which use service-stubs to invoke backend admin services. This approach will by-pass the management UI and call the backend web services directly. Maintaining set of Admin service clients inside test automation framework has it's own pros and cons.
The main problems is maintenance overhead. There were incidents that service API has changed and no one build the branch up to test framework level before the commit. So this introduced compilation failures in test framework API. With our new git based repository model, eliminating this kind of mistakes are required to scale fast. Moving these clients to service-stub level guarantee to detect any compilation failures at repository level. Since the framework support for platform level test automation, all most all service-stubs were taken as dependencies to test framework API. This will introduce many drawbacks when it comes to single product release. Moving admin services clients will improve test-ability and provide user friendly way for product users to consume admin services. Also this will eliminate necessity of releasing all service stubs at the time of automation framework release (in initial phase) Please let me know your suggestions? Thanks, Krishantha. -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear.
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
