Re: [Dev] Making Listner Extension class to work with the parameters defined in automation.xml
Thanks Nuwan!! Seems like we need to add new configuration to all automation.xml files in products integration tests modules. Product teams please note on this. We are in the process of updating all automation.xml and *automationXMLSchema.xsd *files. You might find build failures at integration test phase due to this change. Thanks, Krishantha. On Fri, Aug 15, 2014 at 2:10 PM, Nuwan Wimalasekara nuw...@wso2.com wrote: Hi Krishantha Please merge the pull request [1] and [2] for $subject. Please note that all the product integration test which use Test Framework 4.3.0, need to update(only the listenerExtensions element) the automation.xml and automationXMLSchema.xsd as [3] and [4]. [1] https://github.com/wso2/carbon-platform-integration/pull/10 [2] https://github.com/wso2/carbon-platform-integration-utils/pull/13 [3] https://github.com/wso2-dev/carbon-platform-integration/blob/master/test-automation-framework/org.wso2.carbon.automation.engine/src/main/resources/automation.xml [4] https://github.com/wso2-dev/carbon-platform-integration/blob/master/test-automation-framework/org.wso2.carbon.automation.engine/src/main/resources/automationXMLSchema.xsd Thanks, Nuwanw On Wed, Aug 13, 2014 at 12:54 PM, Nuwan Wimalasekara nuw...@wso2.com wrote: Hi I have created a redmine entry[1] and finished the initial phase of the implementation to support $subject. [1] https://redmine.wso2.com/issues/3149 Thanks, Nuwanw On Tue, Aug 12, 2014 at 11:18 AM, Dharshana Warusavitharana dharsha...@wso2.com wrote: +1 , Implemetation is on the way will add to the redmine . This is a required scenario On Tue, Aug 12, 2014 at 11:15 AM, Nuwan Wimalasekara nuw...@wso2.com wrote: Hi Current implementation of the extension class is designed not to refer any parameters outside. Ex : CarbonServerExtension class starts the carbon server with default configuration for the integration test. extentionClasses className org.wso2.carbon.integration.common.extensions.carbonserver.CarbonServerExtension/ className /extentionClasses But we need to pass some parameters into those extension classes to improve the flexibility of those extensions as below. Then we can refer those parameters inside the extension class and make those classes more flexible. Then we can start the carbon server with dynamic configuration. extentionClasses class name org.wso2.carbon.integration.common.extensions.carbonserver.CarbonServerExtension/name parameter name=portOffSet value=2 / parameter name=cmdArg value=debug 5005 / /class /extentionClasses Currently those extension classes implement ExecutionListenerExtension class. But in order to implement $subject we need to change ExecutionListenerExtension interface to abstract class and make some changes to automation.xml. Then we can provide the parameter list into the actual class extends the ExecutionListenerExtension. Thanks, Nuwanw -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 -- Dharshana Warusavitharana Senior Software Engineer , Test Automation WSO2 Inc. http://wso2.com email : dharsha...@wso2.com dharsha...@wso2.com Tel : +94 11 214 5345 Fax :+94 11 2145300 cell : +94772202595 blog : http://dharshanaw.blogspot.com lean . enterprise . middleware -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Making Listner Extension class to work with the parameters defined in automation.xml
Hi Krishantha Please merge the pull request [1] and [2] for $subject. Please note that all the product integration test which use Test Framework 4.3.0, need to update(only the listenerExtensions element) the automation.xml and automationXMLSchema.xsd as [3] and [4]. [1] https://github.com/wso2/carbon-platform-integration/pull/10 [2] https://github.com/wso2/carbon-platform-integration-utils/pull/13 [3] https://github.com/wso2-dev/carbon-platform-integration/blob/master/test-automation-framework/org.wso2.carbon.automation.engine/src/main/resources/automation.xml [4] https://github.com/wso2-dev/carbon-platform-integration/blob/master/test-automation-framework/org.wso2.carbon.automation.engine/src/main/resources/automationXMLSchema.xsd Thanks, Nuwanw On Wed, Aug 13, 2014 at 12:54 PM, Nuwan Wimalasekara nuw...@wso2.com wrote: Hi I have created a redmine entry[1] and finished the initial phase of the implementation to support $subject. [1] https://redmine.wso2.com/issues/3149 Thanks, Nuwanw On Tue, Aug 12, 2014 at 11:18 AM, Dharshana Warusavitharana dharsha...@wso2.com wrote: +1 , Implemetation is on the way will add to the redmine . This is a required scenario On Tue, Aug 12, 2014 at 11:15 AM, Nuwan Wimalasekara nuw...@wso2.com wrote: Hi Current implementation of the extension class is designed not to refer any parameters outside. Ex : CarbonServerExtension class starts the carbon server with default configuration for the integration test. extentionClasses className org.wso2.carbon.integration.common.extensions.carbonserver.CarbonServerExtension/ className /extentionClasses But we need to pass some parameters into those extension classes to improve the flexibility of those extensions as below. Then we can refer those parameters inside the extension class and make those classes more flexible. Then we can start the carbon server with dynamic configuration. extentionClasses class name org.wso2.carbon.integration.common.extensions.carbonserver.CarbonServerExtension/name parameter name=portOffSet value=2 / parameter name=cmdArg value=debug 5005 / /class /extentionClasses Currently those extension classes implement ExecutionListenerExtension class. But in order to implement $subject we need to change ExecutionListenerExtension interface to abstract class and make some changes to automation.xml. Then we can provide the parameter list into the actual class extends the ExecutionListenerExtension. Thanks, Nuwanw -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 -- Dharshana Warusavitharana Senior Software Engineer , Test Automation WSO2 Inc. http://wso2.com email : dharsha...@wso2.com dharsha...@wso2.com Tel : +94 11 214 5345 Fax :+94 11 2145300 cell : +94772202595 blog : http://dharshanaw.blogspot.com lean . enterprise . middleware -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Making Listner Extension class to work with the parameters defined in automation.xml
Hi I have created a redmine entry[1] and finished the initial phase of the implementation to support $subject. [1] https://redmine.wso2.com/issues/3149 Thanks, Nuwanw On Tue, Aug 12, 2014 at 11:18 AM, Dharshana Warusavitharana dharsha...@wso2.com wrote: +1 , Implemetation is on the way will add to the redmine . This is a required scenario On Tue, Aug 12, 2014 at 11:15 AM, Nuwan Wimalasekara nuw...@wso2.com wrote: Hi Current implementation of the extension class is designed not to refer any parameters outside. Ex : CarbonServerExtension class starts the carbon server with default configuration for the integration test. extentionClasses className org.wso2.carbon.integration.common.extensions.carbonserver.CarbonServerExtension/ className /extentionClasses But we need to pass some parameters into those extension classes to improve the flexibility of those extensions as below. Then we can refer those parameters inside the extension class and make those classes more flexible. Then we can start the carbon server with dynamic configuration. extentionClasses class name org.wso2.carbon.integration.common.extensions.carbonserver.CarbonServerExtension/name parameter name=portOffSet value=2 / parameter name=cmdArg value=debug 5005 / /class /extentionClasses Currently those extension classes implement ExecutionListenerExtension class. But in order to implement $subject we need to change ExecutionListenerExtension interface to abstract class and make some changes to automation.xml. Then we can provide the parameter list into the actual class extends the ExecutionListenerExtension. Thanks, Nuwanw -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 -- Dharshana Warusavitharana Senior Software Engineer , Test Automation WSO2 Inc. http://wso2.com email : dharsha...@wso2.com dharsha...@wso2.com Tel : +94 11 214 5345 Fax :+94 11 2145300 cell : +94772202595 blog : http://dharshanaw.blogspot.com lean . enterprise . middleware -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Making Listner Extension class to work with the parameters defined in automation.xml
Hi Current implementation of the extension class is designed not to refer any parameters outside. Ex : CarbonServerExtension class starts the carbon server with default configuration for the integration test. extentionClasses className org.wso2.carbon.integration.common.extensions.carbonserver.CarbonServerExtension/ className /extentionClasses But we need to pass some parameters into those extension classes to improve the flexibility of those extensions as below. Then we can refer those parameters inside the extension class and make those classes more flexible. Then we can start the carbon server with dynamic configuration. extentionClasses class name org.wso2.carbon.integration.common.extensions.carbonserver.CarbonServerExtension/name parameter name=portOffSet value=2 / parameter name=cmdArg value=debug 5005 / /class /extentionClasses Currently those extension classes implement ExecutionListenerExtension class. But in order to implement $subject we need to change ExecutionListenerExtension interface to abstract class and make some changes to automation.xml. Then we can provide the parameter list into the actual class extends the ExecutionListenerExtension. Thanks, Nuwanw -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Making Listner Extension class to work with the parameters defined in automation.xml
+1 , Implemetation is on the way will add to the redmine . This is a required scenario On Tue, Aug 12, 2014 at 11:15 AM, Nuwan Wimalasekara nuw...@wso2.com wrote: Hi Current implementation of the extension class is designed not to refer any parameters outside. Ex : CarbonServerExtension class starts the carbon server with default configuration for the integration test. extentionClasses className org.wso2.carbon.integration.common.extensions.carbonserver.CarbonServerExtension/ className /extentionClasses But we need to pass some parameters into those extension classes to improve the flexibility of those extensions as below. Then we can refer those parameters inside the extension class and make those classes more flexible. Then we can start the carbon server with dynamic configuration. extentionClasses class name org.wso2.carbon.integration.common.extensions.carbonserver.CarbonServerExtension/name parameter name=portOffSet value=2 / parameter name=cmdArg value=debug 5005 / /class /extentionClasses Currently those extension classes implement ExecutionListenerExtension class. But in order to implement $subject we need to change ExecutionListenerExtension interface to abstract class and make some changes to automation.xml. Then we can provide the parameter list into the actual class extends the ExecutionListenerExtension. Thanks, Nuwanw -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 -- Dharshana Warusavitharana Senior Software Engineer , Test Automation WSO2 Inc. http://wso2.com email : dharsha...@wso2.com dharsha...@wso2.com Tel : +94 11 214 5345 Fax :+94 11 2145300 cell : +94772202595 blog : http://dharshanaw.blogspot.com lean . enterprise . middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
