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
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]
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
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
+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
