Hi all, I'm till trying to figure out how Clarity modules should map to trunk svn structure.
Clarity has following modules 1. API - contains clients written using service stubs. 2. Core - (Artifact deployer, User populator, Report generator, Selenium etc..) 3. Tools Core - Jmeter and Soup UI test runners. 4. Scenarios - Test case/scenarios module. 5. Tools Scenarios - Test cases written using tools (Selenium, Ravana, Jmeter and SoupUi) API is the top most module and core depends on it. In order to deploy artifacts and populate users Clarity needs to have dependency to Integration tests. IMO, artifact deployer should be separate out from Clarity core and place somewhere below component level. Clarity maintain Artifact repo [1] which need be placed in a common location which can be accessed by giving relative paths from product level. What is the best place to put that test artifacts repo? current integration tests use different place to keep test artifacts and some tests generate artifacts while building. The plan is to pack automation tests as a distribution and make available for Straos and Product platform testing. Having a common place to keep all test artifacts would be helpful when wring platform scenarios in future. Thanks, Krishantha. [1] https://svn.wso2.org/repos/wso2/carbon/platform/trunk/platform-integration/system-test-framework/core/org.wso2.automation.platform.core/src/main/resources/artifacts
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
