Hi Chamila, Artifact deployment scenarios such as auto_commit should also be tested.
On Wed, Sep 24, 2014 at 12:59 PM, Gayan Gunarathne <gay...@wso2.com> wrote: > +1 for this python cartridge testing > > But I guess for the future release testing it is really nice if we can > make some automation testing to some extend.It will ease our testing > workload and time. Also it will make sure our existing functionality not > affected with those new changes. > > IMO we can use following technologies as a start up > > - Use selenium based test automation with Stratos web interface. > - Use automation shell scripts for the back end API calls. > > Also for the REST API testing these are some frameworks exist as well > ex:frisby .I guess we can also look on to this as well. > > As a start,we won't be able to cover all the test scenarios at once. But I > suppose we will be able to cover some extend. WDYT? > > Please share your thoughts and suggestion on this. > > Thanks, > Gayan > > On Wed, Sep 24, 2014 at 12:33 PM, Chamila De Alwis <chami...@wso2.com> > wrote: > >> We are currently executing the tests manually, since we couldn't find any >> automation context in Stratos. >> >> As the initial test run, we are testing the event publishing and >> subscribing scopes, and consequently we are extending the scope to artifact >> management and health statistics publishing. >> >> >> Regards, >> Chamila de Alwis >> Software Engineer | WSO2 | +94772207163 >> Blog: code.chamiladealwis.com >> >> >> >> On Wed, Sep 24, 2014 at 12:07 PM, Nirmal Fernando <nirmal070...@gmail.com >> > wrote: >> >>> Nicely articulated Chamila! What's your plan to implement these tests? >>> >>> 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 >>>> >>>> >>>> >>> >>> >>> -- >>> Best Regards, >>> Nirmal >>> >>> Nirmal Fernando. >>> PPMC Member & Committer of Apache Stratos, >>> Senior Software Engineer, WSO2 Inc. >>> >>> Blog: http://nirmalfdo.blogspot.com/ >>> >> >> > > > -- > Best Regards, > > Gayan Gunarathne > Technical Lead > WSO2 Inc. (http://wso2.com) > email : gay...@wso2.com | mobile : +94 766819985 > > -- Udara Liyanage Software Engineer WSO2, Inc.: http://wso2.com lean. enterprise. middleware web: http://udaraliyanage.wordpress.com phone: +94 71 443 6897
