Hi,

On Fri, Jan 16, 2015 at 10:37 AM, Dinesh J Weerakkody <[email protected]>
wrote:

> Hi,
>
> Following SVN External links are there in test module of APIManager 1.9.0.
>
>    - modules/integration/tests/src/test/resources
>    - modules/integration/tests-ui/src/test/resources
>
> both locations are pointed to
>
>
> https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/platform-integration/platform-automated-test-suite/
> *1.8.0*/org.wso2.carbon.automation.test.repo/src/main/resources/artifacts/AM
> artifacts/AM
>
> I'm curious to know followings. please help me to understand.
>
>    1. What is the reason for having a SVN external in these locations?
>
> This is to maintain centralised artefact repo to promote artefact
reusability among products and various test levels - e.g platform tests.
This concept is dropped in GIT based test suites and externals are no
longer required.

>
>    1. Please note that it is pointed to 1.8.0 location. Is this pointed
>    location is correct? I think it should be pointed to 1.9.0 location?
>
> You need to create next version of artefact repo.

>
>    1. There are several directories in
>    org.wso2.carbon.automation.test.repo/src/main/resources/artifacts/AM
>    artifacts/ location such as BAM, AS. if this location is for APIM what is
>    the reason for having other product folders?
>
>  Explained under #1

>
>    1. If this is a common place to have all the configuration files why
>    it is under 1.8.0? 1.8.0 is APIM version.
>
> It is PATS 1.8.0 (Platform Automated Test Suite) nothing related APIM 1.8.0

Thanks,
Krishantha.


> Thanks
>
> *Dinesh J. Weerakkody*
> Software Engineer
> WSO2 Inc.
> lean | enterprise | middleware
> M : +94 727 361788 | E : [email protected] | W : www.wso2.com
>



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

Reply via email to