Hi Manula,

Currently there's no plan to test auto scaling. The method, as we've
planned, is to test the publishing side of the health topic. Autoscaling as
an end to end test case will not be included in our scope.


Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com



On Tue, Sep 23, 2014 at 9:25 PM, Manula Chathurika Thantriwatte <
manu...@wso2.com> wrote:

> Hi Chamila,
>
> +1 for test cases. Are you going to test auto-scaling as well ? What I
> mean here is publishing summarize health stats from python cartridge agent
> and according to those health stats we have to check whether the
> auto-scaling is functioning as expected.
>
> Thanks !
>
> On Tue, Sep 23, 2014 at 8:34 PM, Chamila De Alwis <chami...@wso2.com>
> wrote:
>
>> Hi,
>>
>> For $subject, we decided to implement the following steps.
>>
>> Following aspects need to be tested from agent's point of view.
>>
>> 1) Listening to and publishing instance related events
>> 2) Managing artifacts
>> 3) Managing tenants based on tenant related events
>> 4) Managing log publishing
>>
>> We chose the following three cartridge types to cover the above basic
>> scenarios.
>>
>> 1) PHP - Single tenant framework cartridge
>> 2) MySQL - Single tenant data cartridge
>> 3) WSO2AS - Multi tenant cartridge
>>
>> The initial test cases are as follows.It is a work in progress, however
>> further test cases will be added in the future.
>>
>> Please add your suggestions on any improvements.
>>
>>
>> Cartridge Agent successfully publishes instance status events
>> Prerequisites
>> Stratos InstalledPuppet master configuredStratos policies deployedA base
>> cartridge configuredMySQL cartridge definition deployed
>>
>> Steps
>> StepExpected resultLog in to Stratos admin consoleMy Cartridges page
>> will be displayedSubscribe to MySQL cartridgeMySQL subscription page
>> will be loadedEnter a name for the cartridge and click SubscribeSubscription
>> page will be displayed with MySQL cartridge marked as subscribedWait
>> until cartridge is spawnedwso2carbon.log will output "Instance is
>> successfully starting up." when the instance is spawning.SSH in to the
>> spawned instance Successfully SSH in to the instanceCheck the log file,
>> /tmp/puppet_log /tmp/puppet_log will out put "Initialization completed
>> successfully." after puppet has successfully configured the instanceCheck
>> the wso2carbon.log for the InstanceStartedEvent published from the
>> cartridge agentwso2carbon.log will output the received event details.Check
>> the wso2carbon.log for the InstanceActivatedEvent published from the
>> cartridge agentwso2carbon.log will output the received event details.
>>
>>
>>
>>
>>
>> Cartridge Agent successfully listenes to instance notifier events
>> Prerequisites
>> Stratos InstalledPuppet master configuredStratos policies deployedA base
>> cartridge configuredPHP cartridge definition deployed
>>
>> Steps
>> StepExpected resultLog in to Stratos admin consoleMy Cartridges page
>> will be displayedSubscribe to PHP cartridgePHP subscription page will be
>> loadedEnter a name and the repository for the cartridge and click
>> SubscribeSubscription page will be displayed with PHP cartridge marked
>> as subscribedWait until cartridge is spawnedwso2carbon.log will output
>> "Instance is successfully starting up." when the instance is spawning.SSH
>> in to the spawned instance Successfully SSH in to the instanceCheck the
>> log file, /tmp/puppet_log /tmp/puppet_log will out put "Initialization
>> completed successfully." after puppet has successfully configured the
>> instanceCheck for CompleteTopologyEvent and CompleteTenantEvent being
>> listened to by the 
>> agent/var/log/apache-stratos/cartridge-agent-extensions.log
>> file will out put information received with the mentioned eventsUpdate
>> the remote repository with new files and check if the ArtifactUpdatedEvent
>> was received by the cartridge 
>> agent/var/log/apache-stratos/cartridge-agent-extensions.log
>> file will out put information received with the mentioned eventsRefresh
>> the served pages and check if the updated pages are servedWeb
>> application is updated with the new artifacts
>>
>> Regards,
>> Chamila de Alwis
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>
>
> --
> 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/
>
>
>
>

Reply via email to