Hi Charitha Automatic dbs deployer is design to deploy a data service quickly through the configuration with sql script or other data source(csv, excel, ...) for basic scenarios. therefore we assume there is only one data source configuration in dbs file. if there are more than data source configs, we have to replace those property values(jdbs url, user name, password) within the test class.
implementing multiple configuration is also possible using dbs deployer. if so we have to add those info to configuration file as well and configuration will be much complex. we will discuss this matter and find the best solution. Thanks for the feedback. Thanks Nuwanw On Mon, Mar 26, 2012 at 7:17 PM, Charitha Kankanamge <[email protected]>wrote: > Test automation folks, > > The automatic deployment of data services through the configuration given > in testconfig.xml is having some issues. > > 1. Deployer assumes there is one data source config in dbs (see > /home/charitha/projects/system-test-framework-trunk/system-test-framework/core/org.wso2.automation.platform.core/src/main/java/org/wso2/platform/test/core/utils/dssutils/SqlDataSourceUtil.java#createArtifact). > Therefore, if there are multiple data source configurations such as jdbc, > csv, gspread etc.. we cannot use auto deployer OOTB. > 2. In testconfig.xml, we can have only one dependency_location for a > particular data service. Therefore, when we have data services with > multiple data source configs, all dependent resources have to be included > in one artifact directory. In a way, this seems to be valid but we may need > to look if there is a better approach. > > On a separate note, we should have a JIRA project to report > issues/improvements related to Clarity (system-test-framework). > > Thanks! > Charitha > -- Nuwan Wimalasekara Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
