Hi, I currently have these files[1] versioned to be available whenever I deploy a new installation.
AFAIK JSON file validation schema are enabled now, so can't we make use of those components instead of using an end to end test with the REST api's? [1] - https://github.com/chamilad/stratos-policies Regards, Chamila de Alwis Software Engineer | WSO2 | +94772207163 Blog: code.chamiladealwis.com On Mon, Oct 6, 2014 at 10:27 AM, Shiroshica Kulatilake <sh...@wso2.com> wrote: > > We already have a set of scripts under the following location > stratos/tools/rest-api-client added by Imesh I think - Sorry for not > looking for this first > > So we could probably extend this set to cover all scenarios and first run > this in non-build mode and then take it to build mode ? > > IF we add this to the build we will also have to > 1. Set up Stratos with the required configurations > 2. Run the scenario scripts - including different flavours as suggested by > Manula > 3. Clean up as well - e.g. subscriptions that would spawn instances etc > > On Mon, Oct 6, 2014 at 10:18 AM, Manula Chathurika Thantriwatte < > manu...@wso2.com> wrote: > >> Hi, >> >> >> On Mon, Oct 6, 2014 at 10:06 AM, Shiroshica Kulatilake <sh...@wso2.com> >> wrote: >> >>> Hi, >>> >>> So - what is the guarantee that when something changes the relevant JSON >>> file will also be changed ? >>> >> >> Yes. This can be a problem. Because some of the configurations can be >> different among the IaaS such as zone and region. >> >>> >>> I am totally +1 for having these files plus including them in >>> documentation - however - not sure whether we will tend to not update these >>> again. >>> >> >> Yes. Having the common JSON files against the release. Already we have >> that in the wiki. >> >>> >>> So - how about having this in some format which breaks if the correct >>> JSON file is not there and the easiest example I can think of is tests. >>> >>> For starters can we have a simple script which would invoke all the REST >>> APIs using sample JSON files and add this to the build ? >>> >> >> +1 for add this to build. >> >>> >>> >>> WDYT ? >>> >>> Thank you, >>> Shiro >>> >>> >>> >>> On Mon, Oct 6, 2014 at 7:49 AM, Udara Liyanage <ud...@wso2.com> wrote: >>> >>>> >>>> +1 for the idea. Only basic samples are available in docs. >>>> Shall we have a sample directory in root level where it is easy to find >>>> , users might not search for samples in tools directory. >>>> >>>> >>>> Touched, not typed. Erroneous words are a feature, not a typo. >>>> >>> >>> >>> >>> -- >>> Shiroshica Kulatilake >>> >>> Architect, >>> WSO2, Inc. http://wso2.com/ >>> Phone: +94 776523867 >>> >> >> >> >> -- >> Regards, >> Manula Chathurika Thantriwatte >> Software Engineer >> WSO2 Inc. : http://wso2.com >> lean . enterprise . middleware >> >> email : manu...@wso2.com / man...@apache.org >> phone : +94 772492511 >> blog : http://manulachathurika.blogspot.com/ >> >> >> >> > > > -- > Shiroshica Kulatilake > > Architect, > WSO2, Inc. http://wso2.com/ > Phone: +94 776523867 >
