Re: [Carbon-dev] System Test Framework Integration with Bamboo trunk build.

[Muhammed Shariq]

On Tue, Jan 24, 2012 at 6:51 PM, Krishantha Samaraweera  wrote:

> Hi Shariq,
>
> IMO, we can think about Stratos deployment based on trunk builds after we
> finish with Stratos Services Deployment management tool.
>

Yes +1. I had a chat with Chamith and Sanjaya regarding how we can setup
the packs from bamboo to dev, and it seems we can use Puppet to handle
the deployment in an elegant manner. So lets go with that.

>
> At the moment what we can easily do is to, setting up the framework to
> monitor SL. We can configure it to run once per every two days. WDYT?
>

+1. For the moment I am building the stratos services locally and good news
is most of the services start up without any errors / exceptions :).
However there are a few issues, and I am working with the relevant teams to
fix those. Will update once done.

Thanks,
> Krishantha.
>
> On Mon, Jan 23, 2012 at 9:35 AM, Muhammed Shariq  wrote:
>
>> On Fri, Jan 20, 2012 at 12:59 PM, Krishantha Samaraweera <
>> krishan...@wso2.com> wrote:
>>
>>>
>>> On Fri, Jan 20, 2012 at 9:51 AM, Muhammed Shariq wrote:
>>>
 Hi Krishantha et al,

 If I am not mistaken we are running these test for products only right,
 at the moment? How about the possibility of running these test on the
 stratos services too ? I had a chat with Dhrashana and we most of the tests
 that covers multitenancy aspect, so its a matter of setting up a stratos
 deployment in the bamboo machins right? I can work with the automation team
 to get this running. IIRC we even used these test suite to smoke test SLive
 after migrations etc, so we already have it.

>>>
>>> +1, we have written automation test to run on Stratos services and
>>> products. These tests cover tenant and multi-tenancy aspects as well. Yes
>>> it is matter to setting the things in bamboo machine. But we need to solve
>>> resource problems first. You cannot run startos setup on a single machine.
>>>
>>
>> How about using the machines used to run the Dev environment to set up
>> the trunk stratos builds. If I am not mistaken we have the scripts etc for
>> Dev too. Now that we are moving to the trunk, the Dev environment should
>> run on the trunk builds right? Also it would be ideal since any failures
>> can be patched and verified then and there, so it will save cycles as well.
>>
>> Only issue is we need a to copy the packs to these machines and then set
>> it up (would some scripts, scp etc work ?). Its important to automate this
>> task, else we will be wasting cycles.! If we can somehow figure out a way
>> to set this packs up remotely (ideally in the dev setup) then we could run
>> the tests from the bamboo machines, and generate the results, notification
>> etc. Setting up the dev cloud once a week should be sufficient IMO?
>>
>>>
 My concern is that, once we start developing new features we usually do
 development and testing cycles with the product. Ultimately the services
 gets side lined until quite late in the release cycle. If we can run a full
 test round once a week maybe and get notifications of the failures (or on
 the build status dashboard itself), we wouldn't need to worry about the
 status of the trunk at any time. WDYT ?

>>>
>>> +1, As far as you admit that failures are not false positives :))
>>>
>> Of course I admit that there are issues ;))
>>
>>>
>>>

 On a related note, there was a thread on adding TestNG integration test
 to cover tenant aspects as well,  wonder if we have made any progress in
 that front? Thinking about it, we first need to create a tenant, and also
 some of the tenant related test would require a proper setup (with mounting
 etc) prior to running the tests. Guess we need to put more thought into
 that?

>>>
>>> Integration tests are different from platform tests. Integration test
>>> covers features that grouped in to products. But  Platform test covers
>>> integrated product deployment (whole platform). We already have test to
>>> check tenant aspects. Even you can specify your tenant on the
>>> test configuration and run tests on your tenant. Setting up stratos evn
>>> would be to call startos setup script though the automation framework. We
>>> may need to find a way for  distributed deployment of each service.
>>>
>>
>> Yes we need to test the status of the current trunk with exact setup,
>> configs etc. If not we can't be sure the trunks is stable in terms
>> of functionality.
>>
>> Shall we try to come up with a plan and set this up ASAP, as part of the
>> stabilization effort it self?
>>
>>
>>> Thanks,
>>> Krishantha.
>>>
>>>
 On Fri, Jan 20, 2012 at 12:23 AM, Krishantha Samaraweera <
 krishan...@wso2.com> wrote:

> Hi,
>
> We have done the $subject on Bamboo machine and it is working. You can
> find the last successful test build at [1].
>
> Test framework has been configured to use packs generated by trunk
> build. The test setup consi

Re: [Carbon-dev] System Test Framework Integration with Bamboo trunk build.

[Krishantha Samaraweera]

Hi Shariq,

IMO, we can think about Stratos deployment based on trunk builds after we
finish with Stratos Services Deployment management tool.

At the moment what we can easily do is to, setting up the framework to
monitor SL. We can configure it to run once per every two days. WDYT?

Thanks,
Krishantha.

On Mon, Jan 23, 2012 at 9:35 AM, Muhammed Shariq  wrote:

> On Fri, Jan 20, 2012 at 12:59 PM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>>
>> On Fri, Jan 20, 2012 at 9:51 AM, Muhammed Shariq  wrote:
>>
>>> Hi Krishantha et al,
>>>
>>> If I am not mistaken we are running these test for products only right,
>>> at the moment? How about the possibility of running these test on the
>>> stratos services too ? I had a chat with Dhrashana and we most of the tests
>>> that covers multitenancy aspect, so its a matter of setting up a stratos
>>> deployment in the bamboo machins right? I can work with the automation team
>>> to get this running. IIRC we even used these test suite to smoke test SLive
>>> after migrations etc, so we already have it.
>>>
>>
>> +1, we have written automation test to run on Stratos services and
>> products. These tests cover tenant and multi-tenancy aspects as well. Yes
>> it is matter to setting the things in bamboo machine. But we need to solve
>> resource problems first. You cannot run startos setup on a single machine.
>>
>
> How about using the machines used to run the Dev environment to set up the
> trunk stratos builds. If I am not mistaken we have the scripts etc for Dev
> too. Now that we are moving to the trunk, the Dev environment should run on
> the trunk builds right? Also it would be ideal since any failures can be
> patched and verified then and there, so it will save cycles as well.
>
> Only issue is we need a to copy the packs to these machines and then set
> it up (would some scripts, scp etc work ?). Its important to automate this
> task, else we will be wasting cycles.! If we can somehow figure out a way
> to set this packs up remotely (ideally in the dev setup) then we could run
> the tests from the bamboo machines, and generate the results, notification
> etc. Setting up the dev cloud once a week should be sufficient IMO?
>
>>
>>> My concern is that, once we start developing new features we usually do
>>> development and testing cycles with the product. Ultimately the services
>>> gets side lined until quite late in the release cycle. If we can run a full
>>> test round once a week maybe and get notifications of the failures (or on
>>> the build status dashboard itself), we wouldn't need to worry about the
>>> status of the trunk at any time. WDYT ?
>>>
>>
>> +1, As far as you admit that failures are not false positives :))
>>
> Of course I admit that there are issues ;))
>
>>
>>
>>>
>>> On a related note, there was a thread on adding TestNG integration test
>>> to cover tenant aspects as well,  wonder if we have made any progress in
>>> that front? Thinking about it, we first need to create a tenant, and also
>>> some of the tenant related test would require a proper setup (with mounting
>>> etc) prior to running the tests. Guess we need to put more thought into
>>> that?
>>>
>>
>> Integration tests are different from platform tests. Integration test
>> covers features that grouped in to products. But  Platform test covers
>> integrated product deployment (whole platform). We already have test to
>> check tenant aspects. Even you can specify your tenant on the
>> test configuration and run tests on your tenant. Setting up stratos evn
>> would be to call startos setup script though the automation framework. We
>> may need to find a way for  distributed deployment of each service.
>>
>
> Yes we need to test the status of the current trunk with exact setup,
> configs etc. If not we can't be sure the trunks is stable in terms
> of functionality.
>
> Shall we try to come up with a plan and set this up ASAP, as part of the
> stabilization effort it self?
>
>
>> Thanks,
>> Krishantha.
>>
>>
>>> On Fri, Jan 20, 2012 at 12:23 AM, Krishantha Samaraweera <
>>> krishan...@wso2.com> wrote:
>>>
 Hi,

 We have done the $subject on Bamboo machine and it is working. You can
 find the last successful test build at [1].

 Test framework has been configured to use packs generated by trunk
 build. The test setup consists of five products (ESB, G-Reg, AS, BPS and
 DSS) with registry mounts on top of Mysql. This include Selenium test for
 G-Reg as well. I had to exclude Ravana tests due to few issues after
 updating the Ravana framework. Will get them fix by tomorrow.

 Thanks,
 Krishantha.

 [1] http://wso2.org/bamboo/browse/WSO2CARBONTUNK-AUTOMATIONTEST-13/

 ___
 Carbon-dev mailing list
 Carbon-dev@wso2.org
 http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev


>>>
>>>
>>> --
>>> Thanks,
>>> Shariq.
>>> Phone: +94 777 202 225
>>>
>>>
>

Re: [Carbon-dev] System Test Framework Integration with Bamboo trunk build.

[Charitha Kankanamge]

We will have a separate Gdoc to capture the platform test scenarios.
See [1] (in progress version)
The test artifacts produced by us in these scenarios will be merged
into the system framework.

[1]https://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0Arh4GwhkOX3ndEZnRll4eFhjRjhqVGlJUEd1b0FsZ0E&hl=en_US#gid=0

/Charitha
On Fri, Jan 20, 2012 at 1:52 PM, Charitha Kankanamge  wrote:
>
> Hi Srinath,
>
> We already have TestPlan docs such as [1] which we maintain against each
> release. However we categorized them according to products. What we can do
> is, add an additional sheet with "platform test scenarios" and include the
> cases which needs to be done, which has already been automated etc..
>
> [1]https://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0AvhVRxNoCg0KdDJPY2RMN0xncTFPM1h5Y3NOblVCOEE&hl=en_US&pli=1#gid=27
>
> /Charitha
>
>
> On Fri, Jan 20, 2012 at 1:28 PM, Srinath Perera  wrote:
>>
>> Shall we have a test metric defined in a google doc and keep track of
>> what to be done etc through that test matrix?
>> --Srinath
>>
>> On Fri, Jan 20, 2012 at 1:00 PM, Charitha Kankanamge 
>> wrote:
>> >
>> > On Fri, Jan 20, 2012 at 11:44 AM, Krishantha Samaraweera
>> >  wrote:
>> >>
>> >> Hi Srinath,
>> >>
>> >> On Fri, Jan 20, 2012 at 5:28 AM, Srinath Perera 
>> >> wrote:
>> >>>
>> >>> Thanks Krishantha!!
>> >>>
>> >>> How good are we with test coverage (including introps and perf)? Can
>> >>> you send the current status and plan to cover other products?
>> >>
>> >>
>> >> As I mentioned in the earlier mail, there were few issue with Ravana,
>> >> the
>> >> perf test framework. Recent updates to the framework causing some
>> >> troubles
>> >> with integration. I will work with Damitha to find possible solution.
>> >>
>> >> Sorry I forgot to mention about the interops tests. We haven't
>> >> integrate
>> >> interop tests to framework trunk yet. Dharshana is working on it. Will
>> >> update the status once it is done.
>> >>
>> >> We may need to have a distributed product setup if we are going to
>> >> cover
>> >> other products. Since running 13 products on the same machine will not
>> >> be
>> >> practical. Currently automation team is more focusing on our main
>> >> products.
>> >> And, the plan is to automate system/platform test plans that is going
>> >> to
>> >> prepared by QA team.
>> >
>> >
>> > +1. Our plan is to come up with various test scenarios which involves
>> > multiple product interactions. These test artifacts will be checked-in
>> > to
>> > test artifacts directory of svn and automation team and QA team will
>> > integrate it with the system test framework.
>> >
>> >
>> >>
>> >> And, also includes automation fixes done for external issues.
>> >>
>> >>>
>> >>> Did we start running Bamboo again since this is fixed?
>> >>
>> >>
>> >> Bamboo scheduled builds are running now.
>> >>
>> >>>
>> >>> Do we run introps and perf tests with this?
>> >>>
>> >>>
>> >>> --Srinath
>> >>>
>> >>> On Fri, Jan 20, 2012 at 12:28 AM, Krishantha Samaraweera
>> >>>  wrote:
>> >>> > We need to monitor how this works for few days.
>> >>> > If everything runs smoothly then we can enable test failure
>> >>> > notifications.
>> >>> >
>> >>> > Thanks,
>> >>> > Krishantha.
>> >>> >
>> >>> >
>> >>> > On Fri, Jan 20, 2012 at 12:23 AM, Krishantha Samaraweera
>> >>> >  wrote:
>> >>> >>
>> >>> >> Hi,
>> >>> >>
>> >>> >> We have done the $subject on Bamboo machine and it is working. You
>> >>> >> can
>> >>> >> find the last successful test build at [1].
>> >>> >>
>> >>> >> Test framework has been configured to use packs generated by trunk
>> >>> >> build.
>> >>> >> The test setup consists of five products (ESB, G-Reg, AS, BPS and
>> >>> >> DSS) with
>> >>> >> registry mounts on top of Mysql. This include Selenium test for
>> >>> >> G-Reg
>> >>> >> as
>> >>> >> well. I had to exclude Ravana tests due to few issues after
>> >>> >> updating
>> >>> >> the
>> >>> >> Ravana framework. Will get them fix by tomorrow.
>> >>> >>
>> >>> >> Thanks,
>> >>> >> Krishantha.
>> >>> >>
>> >>> >> [1] http://wso2.org/bamboo/browse/WSO2CARBONTUNK-AUTOMATIONTEST-13/
>> >>> >
>> >>> >
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> 
>> >>> Srinath Perera, Ph.D.
>> >>>   Senior Software Architect, WSO2 Inc.
>> >>>   Visiting Faculty, University of Moratuwa
>> >>>   Member, Apache Software Foundation
>> >>>   Research Scientist, Lanka Software Foundation
>> >>>   Blog: http://srinathsview.blogspot.com/
>> >>>   Photos: http://www.flickr.com/photos/hemapani/
>> >>>  Phone: 0772360902
>> >>
>> >>
>> >>
>> >> ___
>> >> Carbon-dev mailing list
>> >> Carbon-dev@wso2.org
>> >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> >>
>> >
>>
>>
>>
>> --
>> 
>> Srinath Perera, Ph.D.
>>   Senior Software Architect, WSO2 Inc.
>>   Visiting Faculty, University of Moratuwa
>>   Member, Apache Software Foundation
>>   Research Scientist, Lanka Software Foundation
>>   Bl

Re: [Carbon-dev] System Test Framework Integration with Bamboo trunk build.

[Muhammed Shariq]

On Fri, Jan 20, 2012 at 12:59 PM, Krishantha Samaraweera <
krishan...@wso2.com> wrote:

>
> On Fri, Jan 20, 2012 at 9:51 AM, Muhammed Shariq  wrote:
>
>> Hi Krishantha et al,
>>
>> If I am not mistaken we are running these test for products only right,
>> at the moment? How about the possibility of running these test on the
>> stratos services too ? I had a chat with Dhrashana and we most of the tests
>> that covers multitenancy aspect, so its a matter of setting up a stratos
>> deployment in the bamboo machins right? I can work with the automation team
>> to get this running. IIRC we even used these test suite to smoke test SLive
>> after migrations etc, so we already have it.
>>
>
> +1, we have written automation test to run on Stratos services and
> products. These tests cover tenant and multi-tenancy aspects as well. Yes
> it is matter to setting the things in bamboo machine. But we need to solve
> resource problems first. You cannot run startos setup on a single machine.
>

How about using the machines used to run the Dev environment to set up the
trunk stratos builds. If I am not mistaken we have the scripts etc for Dev
too. Now that we are moving to the trunk, the Dev environment should run on
the trunk builds right? Also it would be ideal since any failures can be
patched and verified then and there, so it will save cycles as well.

Only issue is we need a to copy the packs to these machines and then set it
up (would some scripts, scp etc work ?). Its important to automate this
task, else we will be wasting cycles.! If we can somehow figure out a way
to set this packs up remotely (ideally in the dev setup) then we could run
the tests from the bamboo machines, and generate the results, notification
etc. Setting up the dev cloud once a week should be sufficient IMO?

>
>> My concern is that, once we start developing new features we usually do
>> development and testing cycles with the product. Ultimately the services
>> gets side lined until quite late in the release cycle. If we can run a full
>> test round once a week maybe and get notifications of the failures (or on
>> the build status dashboard itself), we wouldn't need to worry about the
>> status of the trunk at any time. WDYT ?
>>
>
> +1, As far as you admit that failures are not false positives :))
>
Of course I admit that there are issues ;))

>
>
>>
>> On a related note, there was a thread on adding TestNG integration test
>> to cover tenant aspects as well,  wonder if we have made any progress in
>> that front? Thinking about it, we first need to create a tenant, and also
>> some of the tenant related test would require a proper setup (with mounting
>> etc) prior to running the tests. Guess we need to put more thought into
>> that?
>>
>
> Integration tests are different from platform tests. Integration test
> covers features that grouped in to products. But  Platform test covers
> integrated product deployment (whole platform). We already have test to
> check tenant aspects. Even you can specify your tenant on the
> test configuration and run tests on your tenant. Setting up stratos evn
> would be to call startos setup script though the automation framework. We
> may need to find a way for  distributed deployment of each service.
>

Yes we need to test the status of the current trunk with exact setup,
configs etc. If not we can't be sure the trunks is stable in terms
of functionality.

Shall we try to come up with a plan and set this up ASAP, as part of the
stabilization effort it self?


> Thanks,
> Krishantha.
>
>
>> On Fri, Jan 20, 2012 at 12:23 AM, Krishantha Samaraweera <
>> krishan...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> We have done the $subject on Bamboo machine and it is working. You can
>>> find the last successful test build at [1].
>>>
>>> Test framework has been configured to use packs generated by trunk
>>> build. The test setup consists of five products (ESB, G-Reg, AS, BPS and
>>> DSS) with registry mounts on top of Mysql. This include Selenium test for
>>> G-Reg as well. I had to exclude Ravana tests due to few issues after
>>> updating the Ravana framework. Will get them fix by tomorrow.
>>>
>>> Thanks,
>>> Krishantha.
>>>
>>> [1] http://wso2.org/bamboo/browse/WSO2CARBONTUNK-AUTOMATIONTEST-13/
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> Thanks,
>> Shariq.
>> Phone: +94 777 202 225
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Thanks,
Shariq.
Phone: +94 777 202 225
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mai

Re: [Carbon-dev] System Test Framework Integration with Bamboo trunk build.

[Charitha Kankanamge]

Hi Srinath,

We already have TestPlan docs such as [1] which we maintain against each
release. However we categorized them according to products. What we can do
is, add an additional sheet with "platform test scenarios" and include the
cases which needs to be done, which has already been automated etc..

[1]
https://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0AvhVRxNoCg0KdDJPY2RMN0xncTFPM1h5Y3NOblVCOEE&hl=en_US&pli=1#gid=27

/Charitha

On Fri, Jan 20, 2012 at 1:28 PM, Srinath Perera  wrote:

> Shall we have a test metric defined in a google doc and keep track of
> what to be done etc through that test matrix?
> --Srinath
>
> On Fri, Jan 20, 2012 at 1:00 PM, Charitha Kankanamge 
> wrote:
> >
> > On Fri, Jan 20, 2012 at 11:44 AM, Krishantha Samaraweera
> >  wrote:
> >>
> >> Hi Srinath,
> >>
> >> On Fri, Jan 20, 2012 at 5:28 AM, Srinath Perera 
> wrote:
> >>>
> >>> Thanks Krishantha!!
> >>>
> >>> How good are we with test coverage (including introps and perf)? Can
> >>> you send the current status and plan to cover other products?
> >>
> >>
> >> As I mentioned in the earlier mail, there were few issue with Ravana,
> the
> >> perf test framework. Recent updates to the framework causing some
> troubles
> >> with integration. I will work with Damitha to find possible solution.
> >>
> >> Sorry I forgot to mention about the interops tests. We haven't integrate
> >> interop tests to framework trunk yet. Dharshana is working on it. Will
> >> update the status once it is done.
> >>
> >> We may need to have a distributed product setup if we are going to cover
> >> other products. Since running 13 products on the same machine will not
> be
> >> practical. Currently automation team is more focusing on our main
> products.
> >> And, the plan is to automate system/platform test plans that is going to
> >> prepared by QA team.
> >
> >
> > +1. Our plan is to come up with various test scenarios which involves
> > multiple product interactions. These test artifacts will be checked-in to
> > test artifacts directory of svn and automation team and QA team will
> > integrate it with the system test framework.
> >
> >
> >>
> >> And, also includes automation fixes done for external issues.
> >>
> >>>
> >>> Did we start running Bamboo again since this is fixed?
> >>
> >>
> >> Bamboo scheduled builds are running now.
> >>
> >>>
> >>> Do we run introps and perf tests with this?
> >>>
> >>>
> >>> --Srinath
> >>>
> >>> On Fri, Jan 20, 2012 at 12:28 AM, Krishantha Samaraweera
> >>>  wrote:
> >>> > We need to monitor how this works for few days.
> >>> > If everything runs smoothly then we can enable test failure
> >>> > notifications.
> >>> >
> >>> > Thanks,
> >>> > Krishantha.
> >>> >
> >>> >
> >>> > On Fri, Jan 20, 2012 at 12:23 AM, Krishantha Samaraweera
> >>> >  wrote:
> >>> >>
> >>> >> Hi,
> >>> >>
> >>> >> We have done the $subject on Bamboo machine and it is working. You
> can
> >>> >> find the last successful test build at [1].
> >>> >>
> >>> >> Test framework has been configured to use packs generated by trunk
> >>> >> build.
> >>> >> The test setup consists of five products (ESB, G-Reg, AS, BPS and
> >>> >> DSS) with
> >>> >> registry mounts on top of Mysql. This include Selenium test for
> G-Reg
> >>> >> as
> >>> >> well. I had to exclude Ravana tests due to few issues after updating
> >>> >> the
> >>> >> Ravana framework. Will get them fix by tomorrow.
> >>> >>
> >>> >> Thanks,
> >>> >> Krishantha.
> >>> >>
> >>> >> [1] http://wso2.org/bamboo/browse/WSO2CARBONTUNK-AUTOMATIONTEST-13/
> >>> >
> >>> >
> >>>
> >>>
> >>>
> >>> --
> >>> 
> >>> Srinath Perera, Ph.D.
> >>>   Senior Software Architect, WSO2 Inc.
> >>>   Visiting Faculty, University of Moratuwa
> >>>   Member, Apache Software Foundation
> >>>   Research Scientist, Lanka Software Foundation
> >>>   Blog: http://srinathsview.blogspot.com/
> >>>   Photos: http://www.flickr.com/photos/hemapani/
> >>>  Phone: 0772360902
> >>
> >>
> >>
> >> ___
> >> Carbon-dev mailing list
> >> Carbon-dev@wso2.org
> >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >>
> >
>
>
>
> --
> 
> Srinath Perera, Ph.D.
>   Senior Software Architect, WSO2 Inc.
>   Visiting Faculty, University of Moratuwa
>   Member, Apache Software Foundation
>   Research Scientist, Lanka Software Foundation
>   Blog: http://srinathsview.blogspot.com/
>   Photos: http://www.flickr.com/photos/hemapani/
>  Phone: 0772360902
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] System Test Framework Integration with Bamboo trunk build.

[Srinath Perera]

Shall we have a test metric defined in a google doc and keep track of
what to be done etc through that test matrix?
--Srinath

On Fri, Jan 20, 2012 at 1:00 PM, Charitha Kankanamge  wrote:
>
> On Fri, Jan 20, 2012 at 11:44 AM, Krishantha Samaraweera
>  wrote:
>>
>> Hi Srinath,
>>
>> On Fri, Jan 20, 2012 at 5:28 AM, Srinath Perera  wrote:
>>>
>>> Thanks Krishantha!!
>>>
>>> How good are we with test coverage (including introps and perf)? Can
>>> you send the current status and plan to cover other products?
>>
>>
>> As I mentioned in the earlier mail, there were few issue with Ravana, the
>> perf test framework. Recent updates to the framework causing some troubles
>> with integration. I will work with Damitha to find possible solution.
>>
>> Sorry I forgot to mention about the interops tests. We haven't integrate
>> interop tests to framework trunk yet. Dharshana is working on it. Will
>> update the status once it is done.
>>
>> We may need to have a distributed product setup if we are going to cover
>> other products. Since running 13 products on the same machine will not be
>> practical. Currently automation team is more focusing on our main products.
>> And, the plan is to automate system/platform test plans that is going to
>> prepared by QA team.
>
>
> +1. Our plan is to come up with various test scenarios which involves
> multiple product interactions. These test artifacts will be checked-in to
> test artifacts directory of svn and automation team and QA team will
> integrate it with the system test framework.
>
>
>>
>> And, also includes automation fixes done for external issues.
>>
>>>
>>> Did we start running Bamboo again since this is fixed?
>>
>>
>> Bamboo scheduled builds are running now.
>>
>>>
>>> Do we run introps and perf tests with this?
>>>
>>>
>>> --Srinath
>>>
>>> On Fri, Jan 20, 2012 at 12:28 AM, Krishantha Samaraweera
>>>  wrote:
>>> > We need to monitor how this works for few days.
>>> > If everything runs smoothly then we can enable test failure
>>> > notifications.
>>> >
>>> > Thanks,
>>> > Krishantha.
>>> >
>>> >
>>> > On Fri, Jan 20, 2012 at 12:23 AM, Krishantha Samaraweera
>>> >  wrote:
>>> >>
>>> >> Hi,
>>> >>
>>> >> We have done the $subject on Bamboo machine and it is working. You can
>>> >> find the last successful test build at [1].
>>> >>
>>> >> Test framework has been configured to use packs generated by trunk
>>> >> build.
>>> >> The test setup consists of five products (ESB, G-Reg, AS, BPS and
>>> >> DSS) with
>>> >> registry mounts on top of Mysql. This include Selenium test for G-Reg
>>> >> as
>>> >> well. I had to exclude Ravana tests due to few issues after updating
>>> >> the
>>> >> Ravana framework. Will get them fix by tomorrow.
>>> >>
>>> >> Thanks,
>>> >> Krishantha.
>>> >>
>>> >> [1] http://wso2.org/bamboo/browse/WSO2CARBONTUNK-AUTOMATIONTEST-13/
>>> >
>>> >
>>>
>>>
>>>
>>> --
>>> 
>>> Srinath Perera, Ph.D.
>>>   Senior Software Architect, WSO2 Inc.
>>>   Visiting Faculty, University of Moratuwa
>>>   Member, Apache Software Foundation
>>>   Research Scientist, Lanka Software Foundation
>>>   Blog: http://srinathsview.blogspot.com/
>>>   Photos: http://www.flickr.com/photos/hemapani/
>>>  Phone: 0772360902
>>
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>



-- 

Srinath Perera, Ph.D.
  Senior Software Architect, WSO2 Inc.
  Visiting Faculty, University of Moratuwa
  Member, Apache Software Foundation
  Research Scientist, Lanka Software Foundation
  Blog: http://srinathsview.blogspot.com/
  Photos: http://www.flickr.com/photos/hemapani/
 Phone: 0772360902
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] System Test Framework Integration with Bamboo trunk build.

[Charitha Kankanamge]

On Fri, Jan 20, 2012 at 11:44 AM, Krishantha Samaraweera <
krishan...@wso2.com> wrote:

> Hi Srinath,
>
> On Fri, Jan 20, 2012 at 5:28 AM, Srinath Perera  wrote:
>
>> Thanks Krishantha!!
>>
>> How good are we with test coverage (including introps and perf)? Can
>> you send the current status and plan to cover other products?
>>
>
> As I mentioned in the earlier mail, there were few issue with Ravana, the
> perf test framework. Recent updates to the framework causing some troubles
> with integration. I will work with Damitha to find possible solution.
>
> Sorry I forgot to mention about the interops tests. We haven't integrate
> interop tests to framework trunk yet. Dharshana is working on it. Will
> update the status once it is done.
>
> We may need to have a distributed product setup if we are going to cover
> other products. Since running 13 products on the same machine will not be
> practical. Currently automation team is more focusing on our main products.
> And, the plan is to automate system/platform test plans that is going to
> prepared by QA team.
>

+1. Our plan is to come up with various test scenarios which involves
multiple product interactions. These test artifacts will be checked-in to
test artifacts directory of svn and automation team and QA team will
integrate it with the system test framework.



> And, also includes automation fixes done for external issues.
>
>
>> Did we start running Bamboo again since this is fixed?
>>
>
> Bamboo scheduled builds are running now.
>
>
>> Do we run introps and perf tests with this?
>
>
>> --Srinath
>>
>> On Fri, Jan 20, 2012 at 12:28 AM, Krishantha Samaraweera
>>  wrote:
>> > We need to monitor how this works for few days.
>> > If everything runs smoothly then we can enable test failure
>> notifications.
>> >
>> > Thanks,
>> > Krishantha.
>> >
>> >
>> > On Fri, Jan 20, 2012 at 12:23 AM, Krishantha Samaraweera
>> >  wrote:
>> >>
>> >> Hi,
>> >>
>> >> We have done the $subject on Bamboo machine and it is working. You can
>> >> find the last successful test build at [1].
>> >>
>> >> Test framework has been configured to use packs generated by trunk
>> build.
>> >> The test setup consists of five products (ESB, G-Reg, AS, BPS and
>> DSS) with
>> >> registry mounts on top of Mysql. This include Selenium test for G-Reg
>> as
>> >> well. I had to exclude Ravana tests due to few issues after updating
>> the
>> >> Ravana framework. Will get them fix by tomorrow.
>> >>
>> >> Thanks,
>> >> Krishantha.
>> >>
>> >> [1] http://wso2.org/bamboo/browse/WSO2CARBONTUNK-AUTOMATIONTEST-13/
>> >
>> >
>>
>>
>>
>> --
>> 
>> Srinath Perera, Ph.D.
>>   Senior Software Architect, WSO2 Inc.
>>   Visiting Faculty, University of Moratuwa
>>   Member, Apache Software Foundation
>>   Research Scientist, Lanka Software Foundation
>>   Blog: http://srinathsview.blogspot.com/
>>   Photos: http://www.flickr.com/photos/hemapani/
>>  Phone: 0772360902
>>
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] System Test Framework Integration with Bamboo trunk build.

[Krishantha Samaraweera]

On Fri, Jan 20, 2012 at 9:51 AM, Muhammed Shariq  wrote:

> Hi Krishantha et al,
>
> If I am not mistaken we are running these test for products only right, at
> the moment? How about the possibility of running these test on the stratos
> services too ? I had a chat with Dhrashana and we most of the tests that
> covers multitenancy aspect, so its a matter of setting up a stratos
> deployment in the bamboo machins right? I can work with the automation team
> to get this running. IIRC we even used these test suite to smoke test SLive
> after migrations etc, so we already have it.
>

+1, we have written automation test to run on Stratos services and
products. These tests cover tenant and multi-tenancy aspects as well. Yes
it is matter to setting the things in bamboo machine. But we need to solve
resource problems first. You cannot run startos setup on a single machine.


> My concern is that, once we start developing new features we usually do
> development and testing cycles with the product. Ultimately the services
> gets side lined until quite late in the release cycle. If we can run a full
> test round once a week maybe and get notifications of the failures (or on
> the build status dashboard itself), we wouldn't need to worry about the
> status of the trunk at any time. WDYT ?
>

+1, As far as you admit that failures are not false positives :))


>
> On a related note, there was a thread on adding TestNG integration test to
> cover tenant aspects as well,  wonder if we have made any progress in that
> front? Thinking about it, we first need to create a tenant, and also some
> of the tenant related test would require a proper setup (with mounting etc)
> prior to running the tests. Guess we need to put more thought into that?
>

Integration tests are different from platform tests. Integration test
covers features that grouped in to products. But  Platform test covers
integrated product deployment (whole platform). We already have test to
check tenant aspects. Even you can specify your tenant on the
test configuration and run tests on your tenant. Setting up stratos evn
would be to call startos setup script though the automation framework. We
may need to find a way for  distributed deployment of each service.

Thanks,
Krishantha.


> On Fri, Jan 20, 2012 at 12:23 AM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>> Hi,
>>
>> We have done the $subject on Bamboo machine and it is working. You can
>> find the last successful test build at [1].
>>
>> Test framework has been configured to use packs generated by trunk build.
>> The test setup consists of five products (ESB, G-Reg, AS, BPS and DSS) with
>> registry mounts on top of Mysql. This include Selenium test for G-Reg as
>> well. I had to exclude Ravana tests due to few issues after updating the
>> Ravana framework. Will get them fix by tomorrow.
>>
>> Thanks,
>> Krishantha.
>>
>> [1] http://wso2.org/bamboo/browse/WSO2CARBONTUNK-AUTOMATIONTEST-13/
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Thanks,
> Shariq.
> Phone: +94 777 202 225
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] System Test Framework Integration with Bamboo trunk build.

[Charitha Kankanamge]

On Fri, Jan 20, 2012 at 9:51 AM, Muhammed Shariq  wrote:

> Hi Krishantha et al,
>
> If I am not mistaken we are running these test for products only right, at
> the moment? How about the possibility of running these test on the stratos
> services too ? I had a chat with Dhrashana and we most of the tests that
> covers multitenancy aspect, so its a matter of setting up a stratos
> deployment in the bamboo machins right? I can work with the automation team
> to get this running. IIRC we even used these test suite to smoke test SLive
> after migrations etc, so we already have it.
>

+1.

>
> My concern is that, once we start developing new features we usually do
> development and testing cycles with the product. Ultimately the services
> gets side lined until quite late in the release cycle. If we can run a full
> test round once a week maybe and get notifications of the failures (or on
> the build status dashboard itself), we wouldn't need to worry about the
> status of the trunk at any time. WDYT ?
>
> On a related note, there was a thread on adding TestNG integration test to
> cover tenant aspects as well,  wonder if we have made any progress in that
> front? Thinking about it, we first need to create a tenant, and also some
> of the tenant related test would require a proper setup (with mounting etc)
> prior to running the tests. Guess we need to put more thought into that?
>
> On Fri, Jan 20, 2012 at 12:23 AM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>> Hi,
>>
>> We have done the $subject on Bamboo machine and it is working. You can
>> find the last successful test build at [1].
>>
>> Test framework has been configured to use packs generated by trunk build.
>> The test setup consists of five products (ESB, G-Reg, AS, BPS and DSS) with
>> registry mounts on top of Mysql. This include Selenium test for G-Reg as
>> well. I had to exclude Ravana tests due to few issues after updating the
>> Ravana framework. Will get them fix by tomorrow.
>>
>> Thanks,
>> Krishantha.
>>
>> [1] http://wso2.org/bamboo/browse/WSO2CARBONTUNK-AUTOMATIONTEST-13/
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Thanks,
> Shariq.
> Phone: +94 777 202 225
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] System Test Framework Integration with Bamboo trunk build.

[Afkham Azeez]

Excellent thoughts Shariq. Integration tests for Stratos are essential. I
guess what we should do is, do a full build, run the Stratos setup script,
create tenants, run some tenant management tests, run some tenant specific
tests, platform sample test etc.

Please consult your MC on working with the automation team to get this done.

On Fri, Jan 20, 2012 at 9:51 AM, Muhammed Shariq  wrote:

> Hi Krishantha et al,
>
> If I am not mistaken we are running these test for products only right, at
> the moment? How about the possibility of running these test on the stratos
> services too ? I had a chat with Dhrashana and we most of the tests that
> covers multitenancy aspect, so its a matter of setting up a stratos
> deployment in the bamboo machins right? I can work with the automation team
> to get this running. IIRC we even used these test suite to smoke test SLive
> after migrations etc, so we already have it.
>
> My concern is that, once we start developing new features we usually do
> development and testing cycles with the product. Ultimately the services
> gets side lined until quite late in the release cycle. If we can run a full
> test round once a week maybe and get notifications of the failures (or on
> the build status dashboard itself), we wouldn't need to worry about the
> status of the trunk at any time. WDYT ?
>
> On a related note, there was a thread on adding TestNG integration test to
> cover tenant aspects as well,  wonder if we have made any progress in that
> front? Thinking about it, we first need to create a tenant, and also some
> of the tenant related test would require a proper setup (with mounting etc)
> prior to running the tests. Guess we need to put more thought into that?
>
> On Fri, Jan 20, 2012 at 12:23 AM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>> Hi,
>>
>> We have done the $subject on Bamboo machine and it is working. You can
>> find the last successful test build at [1].
>>
>> Test framework has been configured to use packs generated by trunk build.
>> The test setup consists of five products (ESB, G-Reg, AS, BPS and DSS) with
>> registry mounts on top of Mysql. This include Selenium test for G-Reg as
>> well. I had to exclude Ravana tests due to few issues after updating the
>> Ravana framework. Will get them fix by tomorrow.
>>
>> Thanks,
>> Krishantha.
>>
>> [1] http://wso2.org/bamboo/browse/WSO2CARBONTUNK-AUTOMATIONTEST-13/
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Thanks,
> Shariq.
> Phone: +94 777 202 225
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] System Test Framework Integration with Bamboo trunk build.

[Krishantha Samaraweera]

Hi Srinath,

On Fri, Jan 20, 2012 at 5:28 AM, Srinath Perera  wrote:

> Thanks Krishantha!!
>
> How good are we with test coverage (including introps and perf)? Can
> you send the current status and plan to cover other products?
>

As I mentioned in the earlier mail, there were few issue with Ravana, the
perf test framework. Recent updates to the framework causing some troubles
with integration. I will work with Damitha to find possible solution.

Sorry I forgot to mention about the interops tests. We haven't integrate
interop tests to framework trunk yet. Dharshana is working on it. Will
update the status once it is done.

We may need to have a distributed product setup if we are going to cover
other products. Since running 13 products on the same machine will not be
practical. Currently automation team is more focusing on our main products.
And, the plan is to automate system/platform test plans that is going to
prepared by QA team. And, also includes automation fixes done for external
issues.


> Did we start running Bamboo again since this is fixed?
>

Bamboo scheduled builds are running now.


> Do we run introps and perf tests with this?


> --Srinath
>
> On Fri, Jan 20, 2012 at 12:28 AM, Krishantha Samaraweera
>  wrote:
> > We need to monitor how this works for few days.
> > If everything runs smoothly then we can enable test failure
> notifications.
> >
> > Thanks,
> > Krishantha.
> >
> >
> > On Fri, Jan 20, 2012 at 12:23 AM, Krishantha Samaraweera
> >  wrote:
> >>
> >> Hi,
> >>
> >> We have done the $subject on Bamboo machine and it is working. You can
> >> find the last successful test build at [1].
> >>
> >> Test framework has been configured to use packs generated by trunk
> build.
> >> The test setup consists of five products (ESB, G-Reg, AS, BPS and
> DSS) with
> >> registry mounts on top of Mysql. This include Selenium test for G-Reg as
> >> well. I had to exclude Ravana tests due to few issues after updating the
> >> Ravana framework. Will get them fix by tomorrow.
> >>
> >> Thanks,
> >> Krishantha.
> >>
> >> [1] http://wso2.org/bamboo/browse/WSO2CARBONTUNK-AUTOMATIONTEST-13/
> >
> >
>
>
>
> --
> 
> Srinath Perera, Ph.D.
>   Senior Software Architect, WSO2 Inc.
>   Visiting Faculty, University of Moratuwa
>   Member, Apache Software Foundation
>   Research Scientist, Lanka Software Foundation
>   Blog: http://srinathsview.blogspot.com/
>   Photos: http://www.flickr.com/photos/hemapani/
>  Phone: 0772360902
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] System Test Framework Integration with Bamboo trunk build.

[Muhammed Shariq]

Hi Krishantha et al,

If I am not mistaken we are running these test for products only right, at
the moment? How about the possibility of running these test on the stratos
services too ? I had a chat with Dhrashana and we most of the tests that
covers multitenancy aspect, so its a matter of setting up a stratos
deployment in the bamboo machins right? I can work with the automation team
to get this running. IIRC we even used these test suite to smoke test SLive
after migrations etc, so we already have it.

My concern is that, once we start developing new features we usually do
development and testing cycles with the product. Ultimately the services
gets side lined until quite late in the release cycle. If we can run a full
test round once a week maybe and get notifications of the failures (or on
the build status dashboard itself), we wouldn't need to worry about the
status of the trunk at any time. WDYT ?

On a related note, there was a thread on adding TestNG integration test to
cover tenant aspects as well,  wonder if we have made any progress in that
front? Thinking about it, we first need to create a tenant, and also some
of the tenant related test would require a proper setup (with mounting etc)
prior to running the tests. Guess we need to put more thought into that?

On Fri, Jan 20, 2012 at 12:23 AM, Krishantha Samaraweera <
krishan...@wso2.com> wrote:

> Hi,
>
> We have done the $subject on Bamboo machine and it is working. You can
> find the last successful test build at [1].
>
> Test framework has been configured to use packs generated by trunk build.
> The test setup consists of five products (ESB, G-Reg, AS, BPS and DSS) with
> registry mounts on top of Mysql. This include Selenium test for G-Reg as
> well. I had to exclude Ravana tests due to few issues after updating the
> Ravana framework. Will get them fix by tomorrow.
>
> Thanks,
> Krishantha.
>
> [1] http://wso2.org/bamboo/browse/WSO2CARBONTUNK-AUTOMATIONTEST-13/
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Thanks,
Shariq.
Phone: +94 777 202 225
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] System Test Framework Integration with Bamboo trunk build.

[Srinath Perera]

Thanks Krishantha!!

How good are we with test coverage (including introps and perf)? Can
you send the current status and plan to cover other products?

Did we start running Bamboo again since this is fixed?

Do we run introps and perf tests with this?

--Srinath

On Fri, Jan 20, 2012 at 12:28 AM, Krishantha Samaraweera
 wrote:
> We need to monitor how this works for few days.
> If everything runs smoothly then we can enable test failure notifications.
>
> Thanks,
> Krishantha.
>
>
> On Fri, Jan 20, 2012 at 12:23 AM, Krishantha Samaraweera
>  wrote:
>>
>> Hi,
>>
>> We have done the $subject on Bamboo machine and it is working. You can
>> find the last successful test build at [1].
>>
>> Test framework has been configured to use packs generated by trunk build.
>> The test setup consists of five products (ESB, G-Reg, AS, BPS and DSS) with
>> registry mounts on top of Mysql. This include Selenium test for G-Reg as
>> well. I had to exclude Ravana tests due to few issues after updating the
>> Ravana framework. Will get them fix by tomorrow.
>>
>> Thanks,
>> Krishantha.
>>
>> [1] http://wso2.org/bamboo/browse/WSO2CARBONTUNK-AUTOMATIONTEST-13/
>
>



-- 

Srinath Perera, Ph.D.
  Senior Software Architect, WSO2 Inc.
  Visiting Faculty, University of Moratuwa
  Member, Apache Software Foundation
  Research Scientist, Lanka Software Foundation
  Blog: http://srinathsview.blogspot.com/
  Photos: http://www.flickr.com/photos/hemapani/
 Phone: 0772360902
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] System Test Framework Integration with Bamboo trunk build.

[Krishantha Samaraweera]

Framework users maven as the builder. Hence, it uses dependencies relevant
to carbon version under test. Support for multiple carbon versions will be
a good additions to the framework. When consider test architecture, having
support for multiple carbon versions, will add extra complexity to
the framework in terms of maintainability. I'm still not sure whether it is
feasible to implement. May be we can come up with separate test framework
for BAM scenario testing.

Thanks,
Krishantha.

On Fri, Jan 20, 2012 at 12:43 AM, Tharindu Mathew  wrote:

> Hi Kris,
>
> I was wondering whether there is a possibility of testing different carbon
> versions of products, such as ESB 3.0.1 with BAM 2.0.0?
>
> On Fri, Jan 20, 2012 at 12:28 AM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>> We need to monitor how this works for few days.
>> If everything runs smoothly then we can enable test failure notifications.
>>
>> Thanks,
>> Krishantha.
>>
>>
>> On Fri, Jan 20, 2012 at 12:23 AM, Krishantha Samaraweera <
>> krishan...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> We have done the $subject on Bamboo machine and it is working. You can
>>> find the last successful test build at [1].
>>>
>>> Test framework has been configured to use packs generated by trunk
>>> build. The test setup consists of five products (ESB, G-Reg, AS, BPS and
>>> DSS) with registry mounts on top of Mysql. This include Selenium test for
>>> G-Reg as well. I had to exclude Ravana tests due to few issues after
>>> updating the Ravana framework. Will get them fix by tomorrow.
>>>
>>> Thanks,
>>> Krishantha.
>>>
>>> [1] http://wso2.org/bamboo/browse/WSO2CARBONTUNK-AUTOMATIONTEST-13/
>>>
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Regards,
>
> Tharindu
>
> blog: http://mackiemathew.com/
> M: +9459908
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] System Test Framework Integration with Bamboo trunk build.

[Tharindu Mathew]

Hi Kris,

I was wondering whether there is a possibility of testing different carbon
versions of products, such as ESB 3.0.1 with BAM 2.0.0?

On Fri, Jan 20, 2012 at 12:28 AM, Krishantha Samaraweera <
krishan...@wso2.com> wrote:

> We need to monitor how this works for few days.
> If everything runs smoothly then we can enable test failure notifications.
>
> Thanks,
> Krishantha.
>
>
> On Fri, Jan 20, 2012 at 12:23 AM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>> Hi,
>>
>> We have done the $subject on Bamboo machine and it is working. You can
>> find the last successful test build at [1].
>>
>> Test framework has been configured to use packs generated by trunk build.
>> The test setup consists of five products (ESB, G-Reg, AS, BPS and DSS) with
>> registry mounts on top of Mysql. This include Selenium test for G-Reg as
>> well. I had to exclude Ravana tests due to few issues after updating the
>> Ravana framework. Will get them fix by tomorrow.
>>
>> Thanks,
>> Krishantha.
>>
>> [1] http://wso2.org/bamboo/browse/WSO2CARBONTUNK-AUTOMATIONTEST-13/
>>
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Regards,

Tharindu

blog: http://mackiemathew.com/
M: +9459908
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] System Test Framework Integration with Bamboo trunk build.

[Krishantha Samaraweera]

We need to monitor how this works for few days.
If everything runs smoothly then we can enable test failure notifications.

Thanks,
Krishantha.

On Fri, Jan 20, 2012 at 12:23 AM, Krishantha Samaraweera <
krishan...@wso2.com> wrote:

> Hi,
>
> We have done the $subject on Bamboo machine and it is working. You can
> find the last successful test build at [1].
>
> Test framework has been configured to use packs generated by trunk build.
> The test setup consists of five products (ESB, G-Reg, AS, BPS and DSS) with
> registry mounts on top of Mysql. This include Selenium test for G-Reg as
> well. I had to exclude Ravana tests due to few issues after updating the
> Ravana framework. Will get them fix by tomorrow.
>
> Thanks,
> Krishantha.
>
> [1] http://wso2.org/bamboo/browse/WSO2CARBONTUNK-AUTOMATIONTEST-13/
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] System Test Framework Integration with Bamboo trunk build.

[Krishantha Samaraweera]

Hi,

We have done the $subject on Bamboo machine and it is working. You can find
the last successful test build at [1].

Test framework has been configured to use packs generated by trunk build.
The test setup consists of five products (ESB, G-Reg, AS, BPS and DSS) with
registry mounts on top of Mysql. This include Selenium test for G-Reg as
well. I had to exclude Ravana tests due to few issues after updating the
Ravana framework. Will get them fix by tomorrow.

Thanks,
Krishantha.

[1] http://wso2.org/bamboo/browse/WSO2CARBONTUNK-AUTOMATIONTEST-13/
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev