call that a
general solution (wonderful though Jython 2.7b3 is).
From: Lakmal Warusawithana [mailto:lak...@wso2.com]
Sent: 25 September 2014 09:31
To: dev@stratos.apache.org
Cc: Chamila De Alwis
Subject: Re: MQTT Messaging + Python Cartridge Agent Testing Strategy
Hi Shaheed,
All 3 mention thread
Hi Shaheed,
All 3 mention thread has discussed lot of ideas. As far as my understand
all [1][2][3] will address eventually. As a first step we need to written
in python is very important, what i can see, when we moving to docker,
containers can boot up within 1,2 second and light weight agent is
I knew that there was a Python Cartridge Agent in the works, but did I miss any
recent
the discussion of it? I provided some details comments/requirements on some
related
discussions in May/June [1],[2] but got no responses to suggest if those would
be
considered or not.
In case I have been
Hi Chamila,
Artifact deployment scenarios such as auto_commit should also be tested.
On Wed, Sep 24, 2014 at 12:59 PM, Gayan Gunarathne 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
+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
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.
Regar
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
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
Nicely articulated Chamila! What's your plan to implement these tests?
On Tue, Sep 23, 2014 at 8:34 PM, Chamila De Alwis 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 publish
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.cham
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
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
12 matches
Mail list logo
