from:"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.

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.

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.

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.

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

Re: [Carbon-dev] Event broker is registered after the message "WSO2 Carbon started in ...." when starting DSS in trunk build

2012-01-18 Thread Krishantha Samaraweera

Hi,

This is specific to DSS, I don't see the same behavior with other products.
Some DSS automation test fail because of this inconsistent start-up order.
We can add a delay to automation tests and over come the failures. But it
is better to check why we see this only with DSS trunk build.

Can someone from DSS team please help..

Thanks,
Krishantha.

On Tue, Jan 17, 2012 at 6:44 PM, Nuwan Wimalasekara  wrote:

> Hi
> There is a issue in server start up sequence. even if message is log
> "WSO2 Carbon started in 38 sec". HTTPS port is not listening until event
> broker is registered. that scenario found with carbon trunk build.
> it takes 3 to 6 seconds to up HTTPS port after message "WSO2 Carbon
> started in 38 sec".
>
> Environment : wso2dataservices-2.6.0-SNAPSHOT
>
> Refer : https://wso2.org/jira/browse/CARBON-12227
>
>
> Server log:
>
> [2012-01-17 11:09:36,423]  INFO {org.quartz.impl.StdSchedulerFactory} -
>  Quartz scheduler 'DefaultQuartzScheduler' initialized from default
> resource file in Quartz package: 'quartz.properties'
> [2012-01-17 11:09:36,423]  INFO {org.quartz.impl.StdSchedulerFactory} -
>  Quartz scheduler version: 2.1.1
> [2012-01-17 11:09:36,423]  INFO {org.quartz.core.QuartzScheduler} -
>  Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
> [2012-01-17 11:09:36,641]  INFO
> {org.wso2.carbon.ntask.core.internal.TasksDSComponent} -  Task service
> started
> [2012-01-17 11:09:36,892]  INFO
> {org.wso2.carbon.core.init.CarbonServerManager} -
>  ConfigurationContextService registered in 591ms
> [2012-01-17 11:09:36,905]  INFO
> {org.wso2.carbon.core.transports.http.HttpsTransportListener} -  HTTPS port
>   : 9446
> [2012-01-17 11:09:36,905]  INFO
> {org.wso2.carbon.core.transports.http.HttpTransportListener} -  HTTP port
>  : 9766
> [2012-01-17 11:09:37,124]  INFO
> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -  Started
> Transport Listener Manager
> [2012-01-17 11:09:37,124]  INFO
> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -  Server
>   :  WSO2 Data Services Server-2.6.0-SNAPSHOT
> [2012-01-17 11:09:37,125]  INFO
> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -  WSO2
> Carbon started in 34 sec
> [Broker] BRK-1006 : Using configuration :
> /home/nuwanw/svn/deployment-framework/SNAPSHOT/wso2dataservices-2.6.0-SNAPSHOT/repository/conf/advanced/qpid-config.xml
> [2012-01-17 11:09:39,555]  INFO {qpid.message.broker.listening} -
>  [Broker] BRK-1002 : Starting : Listening on TCP port 5675
> [2012-01-17 11:09:39,558]  INFO {qpid.message.broker.listening} -
>  [Broker] BRK-1002 : Starting : Listening on TCP/SSL port 8675
> [2012-01-17 11:09:39,559]  INFO
> {org.wso2.carbon.qpid.internal.QpidServiceComponent} -  Successfully
> connected to the server on port 5675
> [2012-01-17 11:09:39,784]  INFO
> {org.wso2.carbon.registry.eventing.internal.RegistryEventingServiceComponent}
> -  Successfully Initialized Eventing on Registry
> [2012-01-17 11:09:39,801]  INFO
> {org.wso2.carbon.event.core.internal.builder.EventBrokerHandler} -
>  Successfully registered the event broker
> [2012-01-17 11:09:40,056]  INFO
> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} -  Mgt Console URL
>  : https://10.100.3.39:9446/carbon/
>
>
> Thanks
> NuwanW
>
> --
> Nuwan Wimalasekara
> Software Engineer - Test Automation
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> phone: +94 71 668 4620
>
>
>
>
> ___
> 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] Bamboo scheduled build for trunk will be not available today.

Hi Charith,

Will let you know once we finish with test framework deployment.

Thanks,
Krishantha.

On Wed, Jan 18, 2012 at 11:52 AM, Charith Wickramarachchi
wrote:

> Hi ,
>
> I've disabled the Bamboo scheduled build for trunk till we get the
> Automation test to work with the trunk .
>
> thanks,
> Charith
>
> --
> Charith Dhanushka Wickramarachchi
> Software Engineer
> WSO2 Inc
> http://wso2.com/
> http://wso2.org/
>
> blog
> http://charithwiki.blogspot.com/
>
> twitter
> http://twitter.com/charithwiki
>
> Mobile : 0776706568
>
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] system test framework and product integration tests

Your are correct. We came across the same issue when designing the
framework. Since system tests runs with different configurations (e.g with
registry mounts and different DBs) we need to run all most all
product integration tests on top of product platform as well. We can not
directly have dependencies to product integration tests because of the way
we have written those tests. And, The tests architecture is also differ. We
have written the system-test-framework to address the distributed nature of
a platform deployment. Currently as what we can do is to duplicate
integration tests inside system tests. May be in future we can find a
better way to do it.

Thanks,
Krishantha.

On Wed, Jan 18, 2012 at 10:57 AM, KasunG Gajasinghe  wrote:

>  I have a little question about System-Test-Framework. Does the objective
 of it is to complement the integration tests of products,
 or will it be integrated in to the product integration tests in future?

>>>
>>> What current integration test does is test the individual components
>>> combined and grouped into a so called product. It doesn't have platform
>>> wide tests cases. For an example, It doesn't test a scenario run on ESB,
>>> BPS and G-Reg with registry mounts and clustering. What we does in
>>> system-test-framework is test the platform as a whole.
>>>
>>
>>> Nope system-test-framework will not be integrated in to integration
>>> tests.
>>>
>>
>> Understood. But, talking from viewpoint of AS, it seems that the boundary
>> of this framework's tests and product intg tests is somewhat blur. For
>> example, AS needs to test the security scenarios of Axis2 services
>> something which also done by the system-test-framework. May be we need to
>> come to a common ground on this.
>>
>
>
>
> We are going off the topic here. Lets discuss this on carbon-dev. Please
>> ask all the question you have in there.
>
>
> +1. forwarded to carbon-dev.
>
>
>> Thanks,
>> --KasunG
>>
>>
>>>
>>> Thanks,
>>> Krishantha.
>>>
>>>
>>>

 I'm asking this because I feel like things may get duplicated between
 product integration tests, and STF!

 Thanks,
 --KasunG


>
> Thanks,
> Krishantha.
>



 --
 *Kasun Gajasinghe*
 Software Engineer; WSO2 Inc.; http://wso2.com

 ,
 *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
 *blog: **http://blog.kasunbg.org* 

 *
 twitter: **http://twitter.com/kasunbg* 

 *
 *


>>>
>>
>>
>> --
>> *Kasun Gajasinghe*
>> Software Engineer; WSO2 Inc.; http://wso2.com
>>
>> ,
>> *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
>> *blog: **http://blog.kasunbg.org* 
>>
>> *
>> twitter: **http://twitter.com/kasunbg* 
>>
>> *
>> *
>>
>>
>
>
>
> --
> *Kasun Gajasinghe*
> Software Engineer; WSO2 Inc.; http://wso2.com
>
> ,
> *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
> *blog: **http://blog.kasunbg.org* 
>
> *
> twitter: **http://twitter.com/kasunbg* 
>
> *
> *
>
>
> ___
> 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] Unable to start BPS server when set offset value - trunk build

On Tue, Jan 17, 2012 at 3:15 PM, Waruna Ranasinghe  wrote:

> Hi krishantha,
>
> this happens when the Registry and the BPEL databases are out of sync.
>

Thanks Waruna, you are correct.

-Krishantha.

> sent from my mobile.
> On Jan 17, 2012 3:11 PM, "Krishantha Samaraweera" 
> wrote:
>
>> Hi,
>>
>> I see the following error when starting BPS trunk build with registry
>> mounts.
>>
>> [2012-01-17 14:53:51,247] ERROR - TenantProcessStoreImpl - Cannot find
>> DeploymentUnitDAO instance for package LoanService-8.
>> [2012-01-17 14:53:51,247] ERROR - BPELDeployer - Error deploying BPEL
>> package: LoanService.zip
>> org.wso2.carbon.bpel.core.ode.integration.store.BPELDeploymentException:
>> Cannot find DeploymentUnitDAO instance for package LoanService-8.
>>  at
>> org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl.loadExistingBPELPackage(TenantProcessStoreImpl.java:645)
>> at
>> org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl.reloadExistingVersionsOfBPELPackage(TenantProcessStoreImpl.java:506)
>>  at
>> org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl.deploy(TenantProcessStoreImpl.java:210)
>> at org.wso2.carbon.bpel.deployer.BPELDeployer.deploy(BPELDeployer.java:94)
>>  at
>> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
>> at
>> org.wso2.carbon.utils.deployment.GhostDeployer.deploy(GhostDeployer.java:126)
>>  at
>> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
>> at
>> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:810)
>>  at
>> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
>> at
>> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:371)
>>  at
>> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
>> at
>> org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:139)
>>  at
>> org.wso2.carbon.core.CarbonAxisConfigurator.loadServices(CarbonAxisConfigurator.java:434)
>> at
>> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:95)
>>  at
>> org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
>> at
>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:359)
>>  at
>> org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:257)
>> at
>> org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:117)
>>  at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:847)
>> at
>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>  at
>> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
>>
>> Thanks,
>> Krishantha.
>>
>>
>> On Tue, Jan 17, 2012 at 2:49 PM, Krishantha Samaraweera <
>> krishan...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> I was trying to start BPS server (trunk build) and got the following
>>> error. Further investigation reveals that issue caused after changing
>>> default offset value. Our system automation tests are failing due to this
>>> error. Please have a look.
>>>
>>> Exception
>>> =n
>>> [2012-01-17 14:40:35,699] ERROR - Database - Failed to resolved
>>> external DataSource at htds
>>> javax.naming.ServiceUnavailableException [Root exception is
>>> java.rmi.ConnectException: Connection refused to host: localhost; nested
>>> exception is:
>>>  java.net.ConnectException: Connection refused]
>>> at
>>> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:101)
>>>  at
>>> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:107)
>>> at
>>> org.wso2.carbon.utils.multitenancy.CarbonContextHolder$CarbonInitialJNDIContext.lookup(CarbonContextHolder.java:1034)
>>>  at javax.naming.InitialContext.lookup(InitialContext.java:392)
>>> at
>>> org.wso2.carbon.humantask.core.db.Database.lookupInJndi(Database.java:156)
>>>  at
>>> org.wso2.carbon.humantask.core.db.Database.initExternalDb(Database.java:127)
>>> at
>>> org.wso2.carbon

Re: [Carbon-dev] Unable to start BPS server when set offset value - trunk build

Hi,

I see the following error when starting BPS trunk build with registry
mounts.

[2012-01-17 14:53:51,247] ERROR - TenantProcessStoreImpl - Cannot find
DeploymentUnitDAO instance for package LoanService-8.
[2012-01-17 14:53:51,247] ERROR - BPELDeployer - Error deploying BPEL
package: LoanService.zip
org.wso2.carbon.bpel.core.ode.integration.store.BPELDeploymentException:
Cannot find DeploymentUnitDAO instance for package LoanService-8.
at
org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl.loadExistingBPELPackage(TenantProcessStoreImpl.java:645)
at
org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl.reloadExistingVersionsOfBPELPackage(TenantProcessStoreImpl.java:506)
at
org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl.deploy(TenantProcessStoreImpl.java:210)
at org.wso2.carbon.bpel.deployer.BPELDeployer.deploy(BPELDeployer.java:94)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at
org.wso2.carbon.utils.deployment.GhostDeployer.deploy(GhostDeployer.java:126)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:810)
at
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
at
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:371)
at
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
at
org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:139)
at
org.wso2.carbon.core.CarbonAxisConfigurator.loadServices(CarbonAxisConfigurator.java:434)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:95)
at
org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
at
org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:359)
at
org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:257)
at
org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:117)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:847)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)

Thanks,
Krishantha.

On Tue, Jan 17, 2012 at 2:49 PM, Krishantha Samaraweera  wrote:

> Hi,
>
> I was trying to start BPS server (trunk build) and got the following
> error. Further investigation reveals that issue caused after changing
> default offset value. Our system automation tests are failing due to this
> error. Please have a look.
>
> Exception
> =n
> [2012-01-17 14:40:35,699] ERROR - Database - Failed to resolved external
> DataSource at htds
> javax.naming.ServiceUnavailableException [Root exception is
> java.rmi.ConnectException: Connection refused to host: localhost; nested
> exception is:
>  java.net.ConnectException: Connection refused]
> at
> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:101)
>  at
> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:107)
> at
> org.wso2.carbon.utils.multitenancy.CarbonContextHolder$CarbonInitialJNDIContext.lookup(CarbonContextHolder.java:1034)
>  at javax.naming.InitialContext.lookup(InitialContext.java:392)
> at
> org.wso2.carbon.humantask.core.db.Database.lookupInJndi(Database.java:156)
>  at
> org.wso2.carbon.humantask.core.db.Database.initExternalDb(Database.java:127)
> at
> org.wso2.carbon.humantask.core.db.Database.initDataSource(Database.java:122)
>  at org.wso2.carbon.humantask.core.db.Database.start(Database.java:77)
> at
> org.wso2.carbon.humantask.core.HumanTaskServer.initDataSource(HumanTaskServer.java:92)
>  at
> org.wso2.carbon.humantask.core.HumanTaskServer.init(HumanTaskServer.java:61)
> at
> org.wso2.carbon.humantask.core.internal.HumanTaskServiceComponent.initHumanTaskServer(HumanTaskServiceComponent.java:83)
>  at
> org.wso2.carbon.humantask.core.internal.HumanTaskServiceComponent.activate(HumanTaskServiceComponent.java:63)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>  at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
>  at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activat

[Carbon-dev] Unable to start BPS server when set offset value - trunk build

Hi,

I was trying to start BPS server (trunk build) and got the following error.
Further investigation reveals that issue caused after changing default
offset value. Our system automation tests are failing due to this error.
Please have a look.

Exception
=

[2012-01-17 14:40:35,699] ERROR - Database - Failed to resolved external
DataSource at htds
javax.naming.ServiceUnavailableException [Root exception is
java.rmi.ConnectException: Connection refused to host: localhost; nested
exception is:
java.net.ConnectException: Connection refused]
at
com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:101)
at
com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:107)
at
org.wso2.carbon.utils.multitenancy.CarbonContextHolder$CarbonInitialJNDIContext.lookup(CarbonContextHolder.java:1034)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at
org.wso2.carbon.humantask.core.db.Database.lookupInJndi(Database.java:156)
at
org.wso2.carbon.humantask.core.db.Database.initExternalDb(Database.java:127)
at
org.wso2.carbon.humantask.core.db.Database.initDataSource(Database.java:122)
at org.wso2.carbon.humantask.core.db.Database.start(Database.java:77)
at
org.wso2.carbon.humantask.core.HumanTaskServer.initDataSource(HumanTaskServer.java:92)
at
org.wso2.carbon.humantask.core.HumanTaskServer.init(HumanTaskServer.java:61)
at
org.wso2.carbon.humantask.core.internal.HumanTaskServiceComponent.initHumanTaskServer(HumanTaskServiceComponent.java:83)
at
org.wso2.carbon.humantask.core.internal.HumanTaskServiceComponent.activate(HumanTaskServiceComponent.java:63)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
at
org.wso2.carbon.datasource.internal.DataSourceServiceComponent.activate(DataSourceServiceComponent.java:140)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatc

Re: [Carbon-dev] [Stratos-dev] System test framework progress update

2012-01-13 Thread Krishantha Samaraweera

On Fri, Jan 13, 2012 at 4:26 PM, Srinath Perera  wrote:

> just to confirm .. is this runs with trunk packs created from the build
> now?
>

Yes, we are setting the framework for trunk on bamboo machine.

Thanks,
Krishantha.

>
> On Fri, Jan 13, 2012 at 10:20 AM, Krishantha Samaraweera
>  wrote:
> >
> >
> > On Fri, Jan 13, 2012 at 8:12 AM, Afkham Azeez  wrote:
> >>
> >> Folks, It is better to start writing new tests using TestNG & gradually
> >> migrate the old tests.
> >
> >
> > +1, We are planning to hold test development and have a hackathon to
> migrate
> > into TestNG in next week.
> >
> > Thanks,
> > Krishantha.
> >>
> >> --
> >> Afkham Azeez
> >> Sent from my phone
> >>
> >> On Jan 12, 2012 8:09 PM, "Dharshana Warusavitharana" <
> dharsha...@wso2.com>
> >> wrote:
> >>>
> >>>
> >>>
> >>>
> >>> Hi,
> >>>
> >>> On BPS following scenarios are covered with sub scenarios. And It is
> >>> available for both local and stratos.
> >>>
> >>> Deployment of packages
> >>> Versioning
> >>> Package undeployment and redeployment
> >>> Deployment with active/retire set in deploy.xml
> >>> Running the processes in memory
> >>> Process instance cleanup
> >>> Event filtering at process level
> >>> Event filtering at scope level
> >>> Test with custom event listeners ( at process level)
> >>> Processes with basic activities
> >>> Processes with structured activities
> >>> Process activation and retire (manage processes)
> >>> Monitoring and managing process instances -
> >>> active/complete/failed/suspended/terminated (through process instances
> page)
> >>> - retry, delete, suspend
> >>> Bpel processes with external partner services
> >>> Xpath extentions and Other bpel activities (Xpath, XQuery, XSLT)
> >>> Xpath extentions and Other bpel activities (Xpath, XQuery, XSLT)
> >>>
> >>> The samples are available with the resources in system framework.
> >>>
> >>> Thank You,
> >>> Dharshana.
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> On Thu, Jan 12, 2012 at 5:44 PM, Nuwan Wimalasekara 
> >>> wrote:
> >>>>
> >>>> Hi
> >>>> Following scenarios have been covered in Data Service Server. All test
> >>>> can be run on Product or Stratos.
> >>>>
> >>>> 1) Data Service with CSV file which is on registry
> >>>> 2) Data Service with excel file which is on registry
> >>>>   XSLT transformation
> >>>> 3) Data Service with Google Spread Sheet
> >>>> 4) Data Service with MySql Database
> >>>>  INSERT, UPDATE, DELETE, and SELECT operation
> >>>> 5) Data Service with carbon data source
> >>>>  Data Source Creation
> >>>>  INSERT, UPDATE, DELETE, and SELECT operation
> >>>> 6) Distributed Transactions
> >>>> 7) Data Service Eventing
> >>>> 8) Nested Queries
> >>>> 9) Batch Request
> >>>> 10) File Service
> >>>> 11) REST Invocation
> >>>>  GET, POST, PUT, DELETE
> >>>> 12) Secure Service
> >>>>  Scenario no 1 to 15
> >>>> 13) Service Input parameter validation
> >>>>  length validation
> >>>>  pattern validation
> >>>> 14) MySql Stored procedure
> >>>>  IN params, OUT params, INOUT params
> >>>> 15) Faulty Service
> >>>>  Deploying faulty service
> >>>>  Edit and Redeploy faulty service
> >>>> 16) Data Service Schedule task
> >>>>  Add Schedule task
> >>>>  Reschedule Task
> >>>>  Verifying Task Repeat Count
> >>>>  Verifying Task Start Time
> >>>>
> >>>> Service uploading and data base creation for the service are also
> >>>> automated. MySql database is used for the data services.
> >>>>
> >>>>
> >>>> Thanks
> >>>> NuwanW
> >>>>
> >>>>
> >>>> On Thu, Jan 12, 2012 at 3:42 PM, Krish

Re: [Carbon-dev] [Stratos-dev] System test framework progress update

2012-01-12 Thread Krishantha Samaraweera

On Fri, Jan 13, 2012 at 8:12 AM, Afkham Azeez  wrote:

> Folks, It is better to start writing new tests using TestNG & gradually
> migrate the old tests.
>

+1, We are planning to hold test development and have a hackathon to
migrate into TestNG in next week.

Thanks,
Krishantha.

>  --
> Afkham Azeez
> Sent from my phone
> On Jan 12, 2012 8:09 PM, "Dharshana Warusavitharana" 
> wrote:
>
>>
>>
>>
>> Hi,
>>
>> On BPS following scenarios are covered with sub scenarios. And It is
>> available for both local and stratos.
>>
>>1.
>>2. Deployment of packages
>>3. Versioning
>>4. Package undeployment and redeployment
>>5. Deployment with active/retire set in deploy.xml
>>6. Running the processes in memory
>>7. Process instance cleanup
>>8. Event filtering at process level
>>9. Event filtering at scope level
>>10. Test with custom event listeners ( at process level)
>>11. Processes with basic activities
>>12. Processes with structured activities
>>13. Process activation and retire (manage processes)
>>14. Monitoring and managing process instances -
>>active/complete/failed/suspended/terminated (through process instances
>>page) - retry, delete, suspend
>>15. Bpel processes with external partner services
>>16. Xpath extentions and Other bpel activities (Xpath, XQuery, XSLT)
>>17. Xpath extentions and Other bpel activities (Xpath, XQuery, XSLT)
>>
>> The samples are available with the resources in system framework.
>>
>> Thank You,
>> Dharshana.
>>
>>
>>
>>
>>
>>
>> On Thu, Jan 12, 2012 at 5:44 PM, Nuwan Wimalasekara wrote:
>>
>>> Hi
>>> Following scenarios have been covered in Data Service Server. All test
>>> can be run on Product or Stratos.
>>>
>>> 1) Data Service with CSV file which is on registry
>>> 2) Data Service with excel file which is on registry
>>>   XSLT transformation
>>> 3) Data Service with Google Spread Sheet
>>> 4) Data Service with MySql Database
>>>  INSERT, UPDATE, DELETE, and SELECT operation
>>> 5) Data Service with carbon data source
>>>  Data Source Creation
>>>  INSERT, UPDATE, DELETE, and SELECT operation
>>> 6) Distributed Transactions
>>> 7) Data Service Eventing
>>> 8) Nested Queries
>>> 9) Batch Request
>>> 10) File Service
>>> 11) REST Invocation
>>>  GET, POST, PUT, DELETE
>>> 12) Secure Service
>>>  Scenario no 1 to 15
>>> 13) Service Input parameter validation
>>>  length validation
>>>  pattern validation
>>> 14) MySql Stored procedure
>>>  IN params, OUT params, INOUT params
>>> 15) Faulty Service
>>>  Deploying faulty service
>>>  Edit and Redeploy faulty service
>>> 16) Data Service Schedule task
>>>  Add Schedule task
>>>  Reschedule Task
>>>  Verifying Task Repeat Count
>>>  Verifying Task Start Time
>>>
>>> Service uploading and data base creation for the service are also
>>> automated. MySql database is used for the data services.
>>>
>>>
>>> Thanks
>>> NuwanW
>>>
>>>
>>> On Thu, Jan 12, 2012 at 3:42 PM, Krishantha Samaraweera <
>>> krishan...@wso2.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> System test framework [1] is capable of testing starots and product
>>>> platform. We already integrated Ravana, the perf test framewok into this
>>>> framework.  And it also contain test for G-Reg UI testing using
>>>> Selenium2/Webdriver. This framework uses perl based deployment framework
>>>> [2] to setup product platforms to be tested. From next week we will start
>>>> migrating system framework into TestNG. This is just an update of the
>>>> status.
>>>>
>>>> We have covered following functionalities releated to App Server. You
>>>> can run all these test on Products as well on Stratos.
>>>>
>>>> 1. Car file upload and multitenancy tests.
>>>> 2. Aar, Jar and spring service upload and multitenancy tests.
>>>> 3. SOAP tracer test.
>>>> 4. System level stat test.
>>>> 5. Faulty webapp test, web app redeployment,
>>>> 6. AAR load test n 100 c 100.
>>>> 7. We

[Carbon-dev] System test framework progress update

2012-01-12 Thread Krishantha Samaraweera

Hi,

System test framework [1] is capable of testing starots and product
platform. We already integrated Ravana, the perf test framewok into this
framework.  And it also contain test for G-Reg UI testing using
Selenium2/Webdriver. This framework uses perl based deployment framework
[2] to setup product platforms to be tested. From next week we will start
migrating system framework into TestNG. This is just an update of the
status.

We have covered following functionalities releated to App Server. You can
run all these test on Products as well on Stratos.

1. Car file upload and multitenancy tests.
2. Aar, Jar and spring service upload and multitenancy tests.
3. SOAP tracer test.
4. System level stat test.
5. Faulty webapp test, web app redeployment,
6. AAR load test n 100 c 100.
7. Web app deployment concurrency test using multiple tenants.

Automated scenarios of Stratos Manager

1. Add new tenant test.
2. Activate and deactivate tenants.
3. Usage plan update and downgrade test.
4. Tenant contact info update test.
5. Tenant info update tests.

Dharshana, Nuwan and Kishan please give updates on the areas you have been
automating.

Thanks,
Krishantha.

[1]
https://svn.wso2.org/repos/wso2/trunk/carbon/platform-integration/system-test-framework
[2]
https://svn.wso2.org/repos/wso2/trunk/carbon/platform-integration/deployment-framework
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Automation Tests for Mounting

2012-01-11 Thread Krishantha Samaraweera

+1, We have already configured test framework to setup product platform
with registry mounts and run test against the mounted product setup in
bamboo machine (only five products yet). But we don't have specific tests
for registry mounts. Normally we run governance API test on the setup. Lets
discuss this tomorrow.

Thanks,
Krishantha.

On Wed, Jan 11, 2012 at 6:13 PM, Senaka Fernando  wrote:

> Hi Krishantha,
>
> We need to discuss this sometime this week. We have some issues related to
> mounting, and we need to write automation tests for those as well as
> several other aspects. I'd like to explain a nearly similar model which I
> have used to test caching. But mounting is a little complicated since it
> involves multiple instances of servers, and also reconfiguring some config
> files and all.
>
> Thanks,
> Senaka.
>
> --
> *Senaka Fernando*
> Product Manager - WSO2 Governance Registry;
> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
> Linked-In: http://linkedin.com/in/senakafernando
>
> *Lean . Enterprise . Middleware
>
>
> ___
> 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 status with trunk

2012-01-10 Thread Krishantha Samaraweera

On Tue, Jan 10, 2012 at 12:47 PM, Afkham Azeez  wrote:

> Do you manually startup the server, and then run the client? How is the
> test executed? Does a single process fork the server & client?


We start the servers programmatically and same process fork the server and
client.

Nuwan, Shall we try to use the method suggested by Azeez.  Since System
test framework is separate from trunk integration tests. We may need to
duplicated the test core to System test framework.

Thanks,
Krishantha.

>
>
> On Tue, Jan 10, 2012 at 12:44 PM, Nuwan Wimalasekara wrote:
>
>> is it not a server issue?
>>
>> Thanks
>> NuwanW
>>
>>
>> On Tue, Jan 10, 2012 at 12:10 PM, Afkham Azeez  wrote:
>>
>>> To overcome this, you can use the ClientConnectionUtil.waitForLog()
>>> method I recently introduced to the new integration testing API.
>>>
>>>
>>> On Tue, Jan 10, 2012 at 11:42 AM, Nuwan Wimalasekara wrote:
>>>
>>>> Server Authentication failed nearly 5 to 10 seconds even if message is
>>>> log "WSO2 Carbon started in 38 sec". HTTPS port is not listening until
>>>> event broker is registered.
>>>> until then server authentication failed.
>>>> Error message : https://localhost:9446/services/AuthenticationAdminLogin 
>>>> failed due to RemoteException :Transport error: 404 Error: Not Found
>>>>
>>>> DSS Server log
>>>>
>>>> [2012-01-10 10:00:06,833]  INFO
>>>> {org.wso2.carbon.core.init.CarbonServerManager} -
>>>>  ConfigurationContextService registered in 572ms
>>>> [2012-01-10 10:00:06,840]  INFO
>>>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} -  HTTPS port
>>>>   : 9446
>>>> [2012-01-10 10:00:06,841]  INFO
>>>> {org.wso2.carbon.core.transports.http.HttpTransportListener} -  HTTP port
>>>>  : 9766
>>>> [2012-01-10 10:00:07,203]  INFO
>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -  Started
>>>> Transport Listener Manager
>>>> [2012-01-10 10:00:07,203]  INFO
>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -  Server
>>>>   :  WSO2 Data Services Server-2.6.0-SNAPSHOT
>>>> [2012-01-10 10:00:07,204]  INFO
>>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -  WSO2
>>>> Carbon started in 38 sec
>>>> [Broker] BRK-1006 : Using configuration :
>>>> /home/nuwanw/svn/deployment-framework/SNAPSHOT/wso2dataservices-2.6.0-SNAPSHOT/repository/conf/advanced/qpid-config.xml
>>>> [2012-01-10 10:00:09,255]  INFO {org.quartz.utils.UpdateChecker} -
>>>>  New Quartz update(s) found: 2.1.2 [
>>>> http://www.terracotta.org/kit/reflector?kitID=default&pageID=QuartzChangeLog
>>>> ]
>>>> [2012-01-10 10:00:09,459]  INFO {qpid.message.broker.listening} -
>>>>  [Broker] BRK-1002 : Starting : Listening on TCP port 5675
>>>> [2012-01-10 10:00:09,494]  INFO {qpid.message.broker.listening} -
>>>>  [Broker] BRK-1002 : Starting : Listening on TCP/SSL port 8675
>>>> [2012-01-10 10:00:09,498]  INFO
>>>> {org.wso2.carbon.qpid.internal.QpidServiceComponent} -  Successfully
>>>> connected to the server on port 5675
>>>> [2012-01-10 10:00:10,051]  INFO
>>>> {org.wso2.carbon.registry.eventing.internal.RegistryEventingServiceComponent}
>>>> -  Successfully Initialized Eventing on Registry
>>>> [2012-01-10 10:00:10,063]  INFO
>>>> {org.wso2.carbon.event.core.internal.builder.EventBrokerHandler} -
>>>>  Successfully registered the event broker
>>>> [2012-01-10 10:00:10,559]  INFO
>>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} -  Mgt Console URL
>>>>  : https://10.100.3.192:9446/carbon/
>>>>
>>>>
>>>> Thanks
>>>> NuwanW
>>>>
>>>>
>>>>
>>>> On Mon, Jan 9, 2012 at 10:37 PM, Krishantha Samaraweera <
>>>> krishan...@wso2.com> wrote:
>>>>
>>>>> sending to carbon-dev
>>>>>
>>>>>
>>>>> -- Forwarded message --
>>>>> From: Nuwan Wimalasekara 
>>>>> Date: Mon, Jan 9, 2012 at 6:40 PM
>>>>> Subject: System test framework status with trunk
>>>>> To: Krishantha Samaraweera 
>>>>>
>>>>>
>>>>> Hi Krishantha
>>>>> I could not find the latest p

[Carbon-dev] System test framework status with trunk

2012-01-09 Thread Krishantha Samaraweera

sending to carbon-dev

-- Forwarded message --
From: Nuwan Wimalasekara 
Date: Mon, Jan 9, 2012 at 6:40 PM
Subject: System test framework status with trunk
To: Krishantha Samaraweera 

Hi Krishantha
I could not find the latest product binaries already built. therefore i had
to build the product.

some classes in Admin services needed to be update due to api changes in
trunk service stubs. other than  System test framework can be
run successfully.
while testing DSS i found that there is a Authentication delay after server
starting. Authentication failed for nearly 5 seconds just after starting
server. therefore some test were failed. I will try to figure out the issue
as soon as possible.

Thanks
NuwanW

-- 
Nuwan Wimalasekara
Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

phone: +94 71 668 4620
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Carbon 3.2.3 packs to be released

2011-12-22 Thread Krishantha Samaraweera

Are we going to update maven repo with 3.2.3 artifacts ?

Thanks,
Krishantha.

On Thu, Dec 22, 2011 at 6:20 PM, Sanjeewa Malalgoda wrote:

> RM's please sign with the same key that you used to sign packs.
> Thanks.
>
>
> On Thu, Dec 22, 2011 at 5:28 PM, Madhuka Udantha  wrote:
>
>> Hi,
>>
>> Source packs are available in following url[1].
>>
>> [1]
>> http://builder1.us1.wso2.org/~carbon320/releases/carbon/3.2.3/SourcePacks/
>>
>> Thank you
>>
>> On Wed, Dec 21, 2011 at 2:24 PM, Hasini Gunasinghe wrote:
>>
>>>
>>> On Wed, Dec 21, 2011 at 12:04 PM, Sanjeewa Malalgoda 
>>> wrote:
>>>
 yes dasunpriya completed hosting packs. RM's please download and verify
 the packs before you send release notes.

>>>
>>> Verified the hosted IS pack.
>>>
>>> Thanks,
>>> Hasini.
>>>

 Thanks.

 On Wed, Dec 21, 2011 at 12:01 PM, Fazlan Sabar  wrote:

> Shall we sent out the release notes?
>
>
> On Wed, Dec 21, 2011 at 11:58 AM, Dasunpriya Anuradha <
> anura...@wso2.com> wrote:
>
>> WSO2 ESB 4.0.3, IS 3.2.3, DSS 2.6.3, G-Reg 4.1.1 hosted on OxygenTank.
>>
>> Thanks.
>>
>>
>> On Tue, Dec 20, 2011 at 10:31 PM, Dasunpriya Anuradha <
>> anura...@wso2.com> wrote:
>>
>>> Packs hosting in progress...
>>>
>>> Thanks.
>>>
>>>
>>> On Tue, Dec 20, 2011 at 10:23 PM, Prabath Siriwardena <
>>> prab...@wso2.com> wrote:
>>>


 On Tue, Dec 20, 2011 at 6:11 PM, Prabath Siriwardena <
 prab...@wso2.com> wrote:

> We need to crate the source packs.. Madhuka.. can you please work
> on that.. Please talk to Senaka - he will help you..


 Tag : https://svn.wso2.org/repos/wso2/tags/carbon/3.2.3/

 Thanks & regards,
 -Prabath


>
> Thanks & regards,
> -Prabath
>
>
> On Tue, Dec 20, 2011 at 6:01 PM, Sanjeewa Malalgoda <
> sanje...@wso2.com> wrote:
>
>> Hi Dasunpriya,
>> You can get the signed packs from following url. you can host
>> them.
>>
>> http://builder1.us1.wso2.org/~carbon320/releases/carbon/3.2.3/latest/signed_packs/final-packs/
>>
>> Thanks.
>>
>>
>> On Tue, Dec 20, 2011 at 5:08 PM, Yumani Ranaweera <
>> yum...@wso2.com> wrote:
>>
>>>
>>>
>>> On Tue, Dec 20, 2011 at 5:03 PM, Sanjeewa Malalgoda <
>>> sanje...@wso2.com> wrote:
>>>
 Hope you have checked release data, licence, read me texts all.
 Else RMs please take some time and check it.
>>>
>>>
>>> This is done for G-Reg pack.
>>>
>>> Regards,
>>> Yumani
>>>
>>>
>>>
 Thanks.


 On Tue, Dec 20, 2011 at 4:58 PM, Sandapa Handakumbura <
 sand...@wso2.com> wrote:

> Hi,
>
> Smoke test done for ESB 4.0.3 (latest pack) and it's good to
> release.
>
> Regards,
> Sandapa
>
>
> On Tue, Dec 20, 2011 at 4:47 PM, Pavithra Madurangi <
> pavit...@wso2.com> wrote:
>
>> Hi,
>>
>> Did a smoke test to the IS pack found at [1] and it's okay to
>> be released.
>>
>> [1]
>> http://builder1.us1.wso2.org/~carbon320/releases/carbon/3.2.3/latest/
>>
>> Thanks,
>> Pavithra
>> On Tue, Dec 20, 2011 at 11:57 AM, Prabath Siriwardena <
>> prab...@wso2.com> wrote:
>>
>>> Hi Charitha,
>>>
>>> Can you please confirm whether we are okay to release...
>>>
>>>
>>> Thanks & regards,
>>> -Prabath
>>>
>>> On Tue, Dec 20, 2011 at 11:54 AM, Sanjeewa Malalgoda <
>>> sanje...@wso2.com> wrote:
>>>
 Latest packs available in following url. RM's please sign
 the packs.

 http://builder1.us1.wso2.org/~carbon320/releases/carbon/3.2.3/latest/

 Thanks.
 --
 *Sanjeewa Malalgoda*
 Software Engineer
 **
 *WSO2, Inc.*
 lean.enterprise.middleware.

 mobile : +94 713068779
 web: http://wso2.com
  blog
 :http://sanjeewamalalgoda.blogspot.com/

 [image:
 http://wso2.com/wp-content/themes/wso2ng-v2/images/logos/stratos_logo_h42.gif]
>>

Re: [Carbon-dev] Test Automation Progress and Plan

2011-12-22 Thread Krishantha Samaraweera

On Thu, Dec 22, 2011 at 8:55 AM, Srinath Perera  wrote:

> Hi Krishantha,
>
> Those tests are failing due to database permission issue with Ravana.
> Could you check that, most likely it matter of giving permissions to
> client. Try connecting to the DB using a mysql client from the same
> machine as we are running the tests.
>

All enabled tests are passing now. Please refer to
http://wso2.org/bamboo/browse/WSO2CARBON320-AUTOMATIONTEST-32. We will
enable other tests case by case after testing locally.

Thanks,
Krishantha.

>
> --Srinath
>
> On Wed, Dec 21, 2011 at 5:25 PM, Krishantha Samaraweera
>  wrote:
> >
> >
> > On Tue, Dec 20, 2011 at 1:35 PM, Srinath Perera 
> wrote:
> >>
> >> Goal is to get the Dashbaord working to build trunk, branch, and
> >> support as a thin slice  by Thursday with automation tests
> >> Today we (Azeez, Samisa, and others) met to discuss the progress and
> >> following are TODOs
> >>
> >> Dashboard is at http://builder4.us1.wso2.org:/allPlans.action
> >>
> >> Krishantha and Automation Team
> >> 
> >> Azeez will get the trunk build with integration excluded and products
> >> added back, and use pack generated from that to run the automation
> >> tests Get all automation tests to work (there was 2 failing in the
> >> morning)
> >> Integrate performance tests with automatio frameworl
> >
> >
> > We have integrated Ravana into automation framework. Also selenium UI
> tests
> > are running now. UI tests were configured to use remote web browser on
> > Windows builder machine (build.wso2.com).
> >
> > Transforming tests to run on trunk build is in progress.
> >
> > Thanks,
> > Krishantha.
> >
> >>
> >>
> >> Dushan
> >> ==fix the assembly error in branch build
> >> Make sure abdera build problems are fixed and raise any future build
> >> concerns
> >> run the trunk and branch builds every 8 hours using Bamboo
> >>
> >> Charith
> >> ==Get Sonar to work with trunk Bamboo build and add that to
> >> builder4.us1.wso2.orgGet Clover to work with trunk Bamboo build and
> >> add that to builder4.us1.wso2.orgCurrent support branch to build with
> >> the Bamboo build from carbon core
> >> Make sure all Bamboo machines have security policy files  and increase
> >> the ulimit
> >>
> >> Infra  (Yasith)
> >> Get licences for BambooRegister the domain name with
> >> builder4.us1.wso2.org
> >> New windows machine to use as a build server
> >>
> >> Sadeep
> >> ==
> >> Introp tests
> >>
> >> Anything I missed?
> >>
> >> --Srinath
> >>
> >> 
> >> 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] Test Automation Progress and Plan

2011-12-21 Thread Krishantha Samaraweera

On Thu, Dec 22, 2011 at 8:55 AM, Srinath Perera  wrote:

> Hi Krishantha,
>
> Those tests are failing due to database permission issue with Ravana.
> Could you check that, most likely it matter of giving permissions to
> client. Try connecting to the DB using a mysql client from the same
> machine as we are running the tests.
>

Will check.

Thanks,
Krishantha.

>
> --Srinath
>
> On Wed, Dec 21, 2011 at 5:25 PM, Krishantha Samaraweera
>  wrote:
> >
> >
> > On Tue, Dec 20, 2011 at 1:35 PM, Srinath Perera 
> wrote:
> >>
> >> Goal is to get the Dashbaord working to build trunk, branch, and
> >> support as a thin slice  by Thursday with automation tests
> >> Today we (Azeez, Samisa, and others) met to discuss the progress and
> >> following are TODOs
> >>
> >> Dashboard is at http://builder4.us1.wso2.org:/allPlans.action
> >>
> >> Krishantha and Automation Team
> >> 
> >> Azeez will get the trunk build with integration excluded and products
> >> added back, and use pack generated from that to run the automation
> >> tests Get all automation tests to work (there was 2 failing in the
> >> morning)
> >> Integrate performance tests with automatio frameworl
> >
> >
> > We have integrated Ravana into automation framework. Also selenium UI
> tests
> > are running now. UI tests were configured to use remote web browser on
> > Windows builder machine (build.wso2.com).
> >
> > Transforming tests to run on trunk build is in progress.
> >
> > Thanks,
> > Krishantha.
> >
> >>
> >>
> >> Dushan
> >> ==fix the assembly error in branch build
> >> Make sure abdera build problems are fixed and raise any future build
> >> concerns
> >> run the trunk and branch builds every 8 hours using Bamboo
> >>
> >> Charith
> >> ==Get Sonar to work with trunk Bamboo build and add that to
> >> builder4.us1.wso2.orgGet Clover to work with trunk Bamboo build and
> >> add that to builder4.us1.wso2.orgCurrent support branch to build with
> >> the Bamboo build from carbon core
> >> Make sure all Bamboo machines have security policy files  and increase
> >> the ulimit
> >>
> >> Infra  (Yasith)
> >> Get licences for BambooRegister the domain name with
> >> builder4.us1.wso2.org
> >> New windows machine to use as a build server
> >>
> >> Sadeep
> >> ==
> >> Introp tests
> >>
> >> Anything I missed?
> >>
> >> --Srinath
> >>
> >> 
> >> 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] Test Automation Progress and Plan

2011-12-21 Thread Krishantha Samaraweera

On Tue, Dec 20, 2011 at 1:35 PM, Srinath Perera  wrote:

> Goal is to get the Dashbaord working to build trunk, branch, and
> support as a thin slice  by Thursday with automation tests
> Today we (Azeez, Samisa, and others) met to discuss the progress and
> following are TODOs
>
> Dashboard is at http://builder4.us1.wso2.org:/allPlans.action
>
> Krishantha and Automation Team
> 
> Azeez will get the trunk build with integration excluded and products
> added back, and use pack generated from that to run the automation
> tests Get all automation tests to work (there was 2 failing in the
> morning)
> Integrate performance tests with automatio frameworl
>

We have integrated Ravana into automation framework. Also selenium UI tests
are running now. UI tests were configured to use remote web browser on
Windows builder machine (build.wso2.com).

Transforming tests to run on trunk build is in progress.

Thanks,
Krishantha.


>
> Dushan
> ==fix the assembly error in branch build
> Make sure abdera build problems are fixed and raise any future build
> concerns
> run the trunk and branch builds every 8 hours using Bamboo
>
> Charith
> ==Get Sonar to work with trunk Bamboo build and add that to
> builder4.us1.wso2.orgGet Clover to work with trunk Bamboo build and
> add that to builder4.us1.wso2.orgCurrent support branch to build with
> the Bamboo build from carbon core
> Make sure all Bamboo machines have security policy files  and increase
> the ulimit
>
> Infra  (Yasith)
> Get licences for BambooRegister the domain name with
> builder4.us1.wso2.org
> New windows machine to use as a build server
>
> Sadeep
> ==
> Introp tests
>
> Anything I missed?
>
> --Srinath
>
> 
> 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] Now we can start multiple Carbon servers within an integration TestSuite

2011-12-19 Thread Krishantha Samaraweera

On Mon, Dec 19, 2011 at 3:31 PM, Afkham Azeez  wrote:

> With the following commit, we can start a number of Carbon server
> instances from an integration TestSuite. Now it makes it very simple to
> write an integration test case which involves multiple Carbon products.
> Please take a look at the Javadocs of
> org.wso2.carbon.integration.framework.MultipleServersManager to see how
> this can be used. The automation team can use this  API for automation
> purposes too.
>

+1, Noted.

Thanks,
Krishantha.


>
> -- Forwarded message --
> From: 
> Date: Mon, Dec 19, 2011 at 3:18 PM
> Subject: [Carbon-commits] [Carbon] svn commit r118036 - in
> trunk/carbon/core/integration:
> framework/src/main/java/org/wso2/carbon/integration/framework
> framework/src/main/java/org/wso2/carbon/integration/framework/utils
> tests/src/test/java/org/wso2/carbon/integration/tests
> To: carbon-comm...@wso2.org
>
>
> Author: azeez
> Date: Mon Dec 19 01:48:32 2011
> New Revision: 118036
> URL: http://wso2.org/svn/browse/wso2?view=rev&revision=118036
>
> Log:
> Ability to start multiple Carbon servers inside an integration TestSuite
>
>
>
> Added:
>
> trunk/carbon/core/integration/tests/src/test/java/org/wso2/carbon/integration/tests/MultipleCarbonInstancesTestCase.java
> Modified:
>
> trunk/carbon/core/integration/framework/src/main/java/org/wso2/carbon/integration/framework/ClientConnectionUtil.java
>
> trunk/carbon/core/integration/framework/src/main/java/org/wso2/carbon/integration/framework/LoginLogoutUtil.java
>
> trunk/carbon/core/integration/framework/src/main/java/org/wso2/carbon/integration/framework/MultipleServersManager.java
>
> trunk/carbon/core/integration/framework/src/main/java/org/wso2/carbon/integration/framework/TestServerManager.java
>
> trunk/carbon/core/integration/framework/src/main/java/org/wso2/carbon/integration/framework/utils/ServerUtils.java
>
> trunk/carbon/core/integration/tests/src/test/java/org/wso2/carbon/integration/tests/CarbonTestServerManager.java
>
> Modified:
> trunk/carbon/core/integration/framework/src/main/java/org/wso2/carbon/integration/framework/ClientConnectionUtil.java
> URL:
> http://wso2.org/svn/browse/wso2/trunk/carbon/core/integration/framework/src/main/java/org/wso2/carbon/integration/framework/ClientConnectionUtil.java?rev=118036&r1=118035&r2=118036&view=diff
>
> ==
> ---
> trunk/carbon/core/integration/framework/src/main/java/org/wso2/carbon/integration/framework/ClientConnectionUtil.java
>   (original)
> +++
> trunk/carbon/core/integration/framework/src/main/java/org/wso2/carbon/integration/framework/ClientConnectionUtil.java
>   Mon Dec 19 01:48:32 2011
> @@ -72,6 +72,11 @@
> throw new RuntimeException("Port " + port + " is not open");
> }
>
> +/**
> + * Check whether the provided port is open
> + * @param port The port that needs to be checked
> + * @return true if the port is open & false otherwise
> + */
> public static boolean isPortOpen(int port) {
> Socket socket = null;
> boolean isPortOpen = false;
>
> Modified:
> trunk/carbon/core/integration/framework/src/main/java/org/wso2/carbon/integration/framework/LoginLogoutUtil.java
> URL:
> http://wso2.org/svn/browse/wso2/trunk/carbon/core/integration/framework/src/main/java/org/wso2/carbon/integration/framework/LoginLogoutUtil.java?rev=118036&r1=118035&r2=118036&view=diff
>
> ==
> ---
> trunk/carbon/core/integration/framework/src/main/java/org/wso2/carbon/integration/framework/LoginLogoutUtil.java
>(original)
> +++
> trunk/carbon/core/integration/framework/src/main/java/org/wso2/carbon/integration/framework/LoginLogoutUtil.java
>Mon Dec 19 01:48:32 2011
> @@ -30,18 +30,17 @@
>  import org.wso2.carbon.utils.NetworkUtils;
>
>  /**
> - * All tests which require logging in & logging out should extend this
> class
> + * A utility for logging into & logging out of Carbon servers
>  */
>  public final class LoginLogoutUtil {
> private static final Log log =
> LogFactory.getLog(LoginLogoutUtil.class);
> private String sessionCookie;
>
> /**
> - * This login method needs to be overridden in your TestNG test.
> Simply calling super.login()
> - * would be sufficient
> + * Log in to a Carbon server
>  *
>  * @return The session cookie on successful login
> - * @throws Exception If an error occurs while loggin in
> + * @throws Exception If an error occurs while logging in
>  */
> public String login() throws Exception {
>
> ClientConnectionUtil.waitForPort(Integer.parseInt(FrameworkSettings.HTTPS_PORT));
> @@ -52,8 +51,8 @@
> log.debug("UserName : " + FrameworkSettings.USER_NAME + "
> Password : " +
>   FrameworkSettings.PASSWORD + " HostName : " +
> hostName);
> }
> -boolean  isLoggedIn =
> authAdminStub.login(

Re: [Carbon-dev] [Architecture] Migrate to TestNG

2011-12-13 Thread Krishantha Samaraweera

On Tue, Dec 13, 2011 at 7:56 PM, Afkham Azeez  wrote:

> Folks,
> I was playing around a bit with TestNG (
> http://testng.org/doc/documentation-main.html#introduction) & it seems to
> be the way to go for the type of integration testing we are doing. This may
> involve major changes at the platform testing level but will be worth the
> investment.
>
> Here are some articles that compare TestNG with JUnit4. We are using JUnit
> 3.
>
> http://www.mkyong.com/unittest/junit-4-vs-testng-comparison/
> http://nelz.net/2010/10/06/testng-vs-junit4/
>
> I had a chat with Krishantha & he too agrees that TestNG is more suitable
> for the type of test automation we do. Does anybody have any concerns
> regarding this move?
>

+1, Just gone though the TestNG feature list. OOB support for, parallel
tests and rerunning failed test features are more promising. Selenium
framework also supports TestNG.

Junit 4.8 has introduced test grouping by using test categories [1]. But
this feature is undocumented and seems lot of work. Even I cannot find much
references on web.

You can find the feature matrix of Surefire plugin at [2] which has
extended support for TestNG [3].

Thanks,
Krishantha.

[1]http://www.wakaleo.com/blog/267-grouping-tests-using-junit-categories
[2]http://maven.apache.org/plugins/maven-surefire-plugin/featurematrix.html
[3]http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html

>
>
> --
> *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*
>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Discussion about changes to Carbon test framework in trunk

2011-12-12 Thread Krishantha Samaraweera

On Tue, Dec 13, 2011 at 8:41 AM, Senaka Fernando  wrote:

> +1. I'd like to see how we can make use of this framework to automate
> testing of concerns such as replicated caching, clustering, mounting and
> also to understand how this can eventually grow to automate the testing of
> multitenancy and related aspects.
>

In System test framework we have done some work to configure products with
mounts, clusters, different DBs etc.. And also we start multiple servers
with all configs etc to run automated tests. Anyway carbon test framework
and system test framework are two different things.

+1, for unified

Thanks,
Krishantha.


> Thanks,
> Senaka.
>
> On Tue, Dec 13, 2011 at 6:28 AM, Srinath Perera  wrote:
>
>> +1 .. Azeez talked to Krishantha as well, and we did some related work
>> for automation framework
>> --Srinath
>>
>> On Tue, Dec 13, 2011 at 12:11 AM, Charith Wickramarachchi
>>  wrote:
>> >
>> >
>> > On Mon, Dec 12, 2011 at 11:41 PM, Afkham Azeez  wrote:
>> >>
>> >> Folks,
>> >> I would like to review & make changes to the current Carbon integration
>> >> test framework we have in carbon core. It is a bit of a mess now with
>> people
>> >> doing artifact copying in various ways. I would like to introduce a
>> >> CarbonTestRunner. A server will be started per CarbonTestRunner
>> instance.
>> >> CarbonTestRunner is a TestSuite. In your Carbon test cases you will
>> >> implement the copyArtifacts method. CarbonTestRunner will first call
>> >> copyArtifacts on all test cases, start the server, and run the tests.
>> >> Different product teams are doing this in various hacky ways now, but
>> we
>> >> need to have a proper way of doing this.
>> >>
>> >> In addition, we have also think about starting up multiple Carbon
>> servers
>> >> per CarbonTestRunner.
>> >>
>> >> Can we have a short design discussion about this tomorrow at 10AM?
>> >
>> >
>> >
>> > +1
>> >
>> > For come up with a Unified  Framework.
>> >
>> > cheers,
>> > Charith
>> >
>> >
>> >>
>> >>
>> >>
>> >> --
>> >> 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
>> >>
>> >
>> >
>> >
>> > --
>> > Charith Dhanushka Wickramarachchi
>> > Software Engineer
>> > WSO2 Inc
>> > http://wso2.com/
>> > http://wso2.org/
>> >
>> > blog
>> > http://charithwiki.blogspot.com/
>> >
>> > twitter
>> > http://twitter.com/charithwiki
>> >
>> > Mobile : 0776706568
>> >
>> >
>>
>>
>>
>> --
>> 
>> 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/
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>
>
>
> --
> *Senaka Fernando*
> Product Manager - WSO2 Governance Registry;
> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
> Linked-In: http://linkedin.com/in/senakafernando
>
> *
> Lean . Enterprise . Middleware
>
>
> ___
> 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] Deployment configuration script - training

2011-10-18 Thread Krishantha Samaraweera

Great work Dharshana. Hope the Deployment framework will be helpful for QAs
to setup product platforms in future.

Following are to-do list that we have to complete. Lets try to finish this
before RC builds.

1. Option to configure cache.xml for product clusters.
2. Have a way to run DB script automatically (mysql, h2 etc..)
3. Option to enable/disble mounting
4. Configuration entry for NTTP and NTTPS ports on ESB cluster
5. Using another G-Reg instance as config registry.

Please update if I have missed anything.

Thanks,
Krishantha.

On Mon, Oct 17, 2011 at 8:25 PM, Dharshana Warusavitharana <
dharsha...@wso2.com> wrote:

> Hi Charitha,
>
> I think 10.30 AM will be comfortable time for all.  I will demonstrate a
> sample.
>
> Thank You,
> Dharshana.
>
>
> On Mon, Oct 17, 2011 at 5:51 PM, Charitha Kankanamge wrote:
>
>> Hi Dharshana,
>>
>> Please do @subject tomorrow morning @ #58 meeting room if you are
>> available to do so. It seems we need a quick training :)
>>
>> Please come up with a preferred time and reply to this thread.
>>
>> /Charitha
>>
>>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] G-Reg CarbonHome implementation issue in Test Automation Framework

2011-10-14 Thread Krishantha Samaraweera

On Fri, Oct 14, 2011 at 4:30 PM, Krishantha Samaraweera  wrote:

>
> Hi Senaka,
>
>
> On Fri, Oct 14, 2011 at 4:24 PM, Senaka Fernando  wrote:
>
>>
>>
>> On Fri, Oct 14, 2011 at 4:22 PM, Senaka Fernando  wrote:
>>
>>> Hi Kishan,
>>>
>>> Set -Dcarbon.repo.write.mode=true. This was an issue until very recently
>>> and was fixed.
>>>
>>
>> Adding more to this, since the carbon.xml is not accessible in a remote
>> client, for the exact same code to work at client side, we introduced the
>> above system property. Pleases note that this is only a requirement of the
>> standard Java clients.
>>
>
> How can we write test client for Stratos Governance. I think we cannot use
> the same approach you mentioned.
>

Thanks Senaka, test passed on Stratos/standalone product after
setting carbon.repo.write.mode as system property.

-Krishantha.


> Thanks,
> Krishantha.
>
>>
>> Thanks,
>> Senaka.
>>
>>
>>> Thanks,
>>> Senaka.
>>>
>>>
>>> On Fri, Oct 14, 2011 at 3:26 PM, Kishan Navaratne wrote:
>>>
>>>> Hi,
>>>>
>>>>  I tried to create a client to import a wsdl to G-Reg using WS-API +
>>>> Governance API. I have intentionally left setting carbon home parameter in
>>>> the test client. Since this client is going to be used inside automation
>>>> framework, keeping G-Reg build on client side and pointing the location is
>>>> not practical. So in order to continue with governance automation, Is there
>>>> any other way I can use Governance API without setting carbon home?
>>>>
>>>>
>>>>  Exception
>>>>
>>>> =
>>>>
>>>>
>>>>  Exception in thread "main" java.lang.NullPointerException
>>>>
>>>> at java.util.Hashtable.put(Hashtable.java:394)
>>>>
>>>> at java.util.Properties.setProperty(Properties.java:143)
>>>>
>>>> at java.lang.System.setProperty(System.java:729)
>>>>
>>>> at org.wso2.carbon.utils.CarbonUtils.getCarbonHome(CarbonUtils.java:178)
>>>>
>>>> at
>>>> org.wso2.carbon.utils.CarbonUtils.getCarbonConfigDirPath(CarbonUtils.java:204)
>>>>
>>>> at org.wso2.carbon.utils.CarbonUtils.getServerXml(CarbonUtils.java:169)
>>>>
>>>> at
>>>> org.wso2.carbon.utils.CarbonUtils.getServerConfiguration(CarbonUtils.java:465)
>>>>
>>>> at
>>>> org.wso2.carbon.registry.core.utils.RegistryUtils.isRegistryReadOnly(RegistryUtils.java:1053)
>>>>
>>>> at
>>>> org.wso2.carbon.registry.core.session.UserRegistry.importResource(UserRegistry.java:677)
>>>>
>>>> at
>>>> org.wso2.carbon.governance.api.wsdls.WsdlManager.addWsdl(WsdlManager.java:96)
>>>>
>>>> at SimpleWsdl_Upload.main(SimpleWsdl_Upload.java:37)
>>>>
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>
>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>
>>>> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:115)
>>>>
>>>>
>>>>  Once I set “*CarbonHome*” as a system property it worked perfectly,
>>>> wsdl was uploaded to Greg with no issues
>>>>
>>>>
>>>>  For your reference, client code is attached here with.
>>>>
>>>>
>>>>
>>>> Best Regards,
>>>>
>>>> Kishan
>>>>
>>>
>>>
>>>
>>> --
>>> *Senaka Fernando*
>>> Product Manager - WSO2 Governance Registry;
>>> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
>>> Member; Apache Software Foundation; http://apache.org
>>>
>>> E-mail: senaka AT wso2.com
>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
>>> Linked-In: http://linkedin.com/in/senakafernando
>>>
>>> *Lean . Enterprise . Middleware
>>>
>>>
>>
>>
>> --
>> *Senaka Fernando*
>> Product Manager - WSO2 Governance Registry;
>> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
>> Member; Apache Software Foundation; http://apache.org
>>
>> E-mail: senaka AT wso2.com
>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
>> Linked-In: http://linkedin.com/in/senakafernando
>>
>> *Lean . Enterprise . Middleware
>>
>>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] G-Reg CarbonHome implementation issue in Test Automation Framework

2011-10-14 Thread Krishantha Samaraweera

Hi Senaka,


On Fri, Oct 14, 2011 at 4:24 PM, Senaka Fernando  wrote:

>
>
> On Fri, Oct 14, 2011 at 4:22 PM, Senaka Fernando  wrote:
>
>> Hi Kishan,
>>
>> Set -Dcarbon.repo.write.mode=true. This was an issue until very recently
>> and was fixed.
>>
>
> Adding more to this, since the carbon.xml is not accessible in a remote
> client, for the exact same code to work at client side, we introduced the
> above system property. Please note that this is only a requirement of the
> standard Java clients.
>

How can we write test client for Stratos Governance. I think we cannot use
the same approach you mentioned.

Thanks,
Krishantha.

>
> Thanks,
> Senaka.
>
>
>> Thanks,
>> Senaka.
>>
>>
>> On Fri, Oct 14, 2011 at 3:26 PM, Kishan Navaratne wrote:
>>
>>> Hi,
>>>
>>>  I tried to create a client to import a wsdl to G-Reg using WS-API +
>>> Governance API. I have intentionally left setting carbon home parameter in
>>> the test client. Since this client is going to be used inside automation
>>> framework, keeping G-Reg build on client side and pointing the location is
>>> not practical. So in order to continue with governance automation, Is there
>>> any other way I can use Governance API without setting carbon home?
>>>
>>>
>>>  Exception
>>>
>>> =
>>>
>>>
>>>  Exception in thread "main" java.lang.NullPointerException
>>>
>>> at java.util.Hashtable.put(Hashtable.java:394)
>>>
>>> at java.util.Properties.setProperty(Properties.java:143)
>>>
>>> at java.lang.System.setProperty(System.java:729)
>>>
>>> at org.wso2.carbon.utils.CarbonUtils.getCarbonHome(CarbonUtils.java:178)
>>>
>>> at
>>> org.wso2.carbon.utils.CarbonUtils.getCarbonConfigDirPath(CarbonUtils.java:204)
>>>
>>> at org.wso2.carbon.utils.CarbonUtils.getServerXml(CarbonUtils.java:169)
>>>
>>> at
>>> org.wso2.carbon.utils.CarbonUtils.getServerConfiguration(CarbonUtils.java:465)
>>>
>>> at
>>> org.wso2.carbon.registry.core.utils.RegistryUtils.isRegistryReadOnly(RegistryUtils.java:1053)
>>>
>>> at
>>> org.wso2.carbon.registry.core.session.UserRegistry.importResource(UserRegistry.java:677)
>>>
>>> at
>>> org.wso2.carbon.governance.api.wsdls.WsdlManager.addWsdl(WsdlManager.java:96)
>>>
>>> at SimpleWsdl_Upload.main(SimpleWsdl_Upload.java:37)
>>>
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>
>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>
>>> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:115)
>>>
>>>
>>>  Once I set “*CarbonHome*” as a system property it worked perfectly,
>>> wsdl was uploaded to Greg with no issues
>>>
>>>
>>>  For your reference, client code is attached here with.
>>>
>>>
>>>
>>> Best Regards,
>>>
>>> Kishan
>>>
>>
>>
>>
>> --
>> *Senaka Fernando*
>> Product Manager - WSO2 Governance Registry;
>> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
>> Member; Apache Software Foundation; http://apache.org
>>
>> E-mail: senaka AT wso2.com
>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
>> Linked-In: http://linkedin.com/in/senakafernando
>>
>> *Lean . Enterprise . Middleware
>>
>>
>
>
> --
> *Senaka Fernando*
> Product Manager - WSO2 Governance Registry;
> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
> Linked-In: http://linkedin.com/in/senakafernando
>
> *Lean . Enterprise . Middleware
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] [QA] Use Jmeter heavily in test automation

2011-10-08 Thread Krishantha Samaraweera

On Sat, Oct 8, 2011 at 2:06 PM, Charitha Kankanamge wrote:

> Apache Jmeter is a very useful tool for both functional and performance
> testing. At the moment, we use Jmeter in HB checker app to test console
> level login for all Stratos services as well as Jmeter is used to test
> concurrent login to management console,  webapp uploads etc.
>
> Similarly, Jmeter can be used for trivial functional testing in our
> products/stratos services.
>
> The attached Jmeter test has been written to test AAR services which does
> the following automatically.
>
> 1. Log in to AS management console
> 2. Upload an AAR service
> 3. Assert to check whether the service appears in service list
> 4. Invoke the service by sending both POST and GET requests
> 5. Sign out
>
> Jmeter does all these things very nicely. The beauty of Jmeter is, the same
> test can be converted to a load test by increasing the thread count. The
> possiblity of breaking tests due to UI changes is also minimum.
>
> Krishantha and automation team, please look at the attached test script and
> modify/add to relevant svn location and invoke this automatically through
> test framework. Similarly, we can produce tests for other services too.
>

Great stuff Charitha, We will work on adding this to our automation
framework.

Thanks,
Krishantha.

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

[Carbon-dev] Snapshot repo required for automation work

2011-09-12 Thread Krishantha Samaraweera

Hi,

Currently, automation team is using snapshot dependencies for ongoing
automation work. The automation team have build the trunk and using
artifacts at local repo. This approach doesn't scale when we are going to
deliver the work to QA or Devs. And, our initial plan is to maintain maven
based system-test-framework separately from trunk. So we cannot expect
others to build trunk or branch in order to use the framework.So snapshot
maven repo is required for automation work. Since we are going to run the
automation frameworks against each releases, this has to be online repo
associated with current trunk or branch.

Our standard snapshot repo at [1] haven't been updated since Feb 2010.
AFAIK, trunk is unstable now. So is there any way to deploy at least
required artifacts to our repo.

How about maintaning staging snapshot repo for on going dev/automation work?

Your comments and suggestions are welcome.

Thanks,
Krishantha.

[1]http://dist.wso2.org/snapshots/maven2/
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Has the Carbon 3.2.0 P2 repo been updated with 3.2.1 features?

2011-08-02 Thread Krishantha Samaraweera

On Wed, Aug 3, 2011 at 10:34 AM, Pradeep Fernando  wrote:

> Hi,
>
> On Tue, Aug 2, 2011 at 3:49 PM, Supun Malinga  wrote:
> > Hi azeez,
> > Not yet. Will do this by tomorrow.
> > For now you can use, [1]
> > [1]
> http://builder1.us1.wso2.org/~carbon320/releases/carbon/3.2.1/2011-07-14_09-56-52/p2-repo/
>
>
> QA team please do a smoke test for 3.2.0/3.2.1 products using the
> above repo. We are going to host it afterwards.
>

Nirodha will carry out smoke testing on the repo.

Thanks,
Krishantha.

>
> thanks,
> --Pradeep
> ___
> 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] Does HTTP/REST work with Registry WS API

2011-06-29 Thread Krishantha Samaraweera

On Thu, Jun 30, 2011 at 7:27 AM, Sumedha Rubasinghe wrote:

>
>
> On Thu, Jun 30, 2011 at 6:59 AM, Samisa Abeysinghe wrote:
>
>> $subject?
>>
>> Can I use only HTTP style calls without SOAP with the same API?
>>
>
> Nope. We haven't enabled REST for the same services exposed by WS API.
> However, SOAP HTTP Bindings should work by default.
>
> When Registry work started, we used to support REST style of invocation for
> all Registry operations. But this aspect hasn't been tested (Krishantha did
> some work) or developed for a long time.
>

As I could remember only basic operations were supported by registry REST
API [1]. There was discussion at Architecture list with the subject "Rejuvenate
REST-API in Registry or Drop it?".

Thanks,
Krishantha

[1]https://wso2.org/wiki/display/registry/Registry+Protocol

>
> /sumedha
>
>> Thanks,
>> Samisa...
>>
>> Samisa Abeysinghe
>> VP Engineering
>> WSO2 Inc.
>> http://wso2.com
>> http://wso2.org
>>
>>
>>
>> ___
>> 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
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Problem with Monitoring WSO2 ESB using JConsole

2011-06-10 Thread Krishantha Samaraweera

Hi Jorge,

Edit jmx.xml at CRBON_HOME/repository/conf/advanced and set your IP as the
host name.

localhost

Thanks,
Krishantha.

On Fri, Jun 10, 2011 at 9:04 PM, Jorge Infante Osorio wrote:

> Hi folks.
>
> I read this interesting article
> http://wso2.org/library/knowledge-base/2011/04/monitoring-wso2-esb-using-jconsole
>
> And I test the  access to a local server successfully, but in a remote
> server I can´t not access yet.
>
>
>
> I uncomment the RMIRegistryPort in carbon.xml in ESB and open the port  in
> the iptables config , I use Centos, and my service url is show in console
> when the server start:
>
>
>
> CarbonServerManager JMX Service URL  : service:jmx:rmi:///jndi/rmi://
> 10.3.10.74:/jmxrmi
>
>
>
> But in the Jconsole I receive this:
>
>
>
>
>
> Any idea?
>
>
>
> Saludos,
>
> Ing. Jorge Infante Osorio.
>
> J´Dpto Soluciones SOA.
>
> CDAE.
>
> Fac. 5.
>
> UCI.
>
>
>
> ___
> 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] RC3 Packs - 3.2.0

2011-05-30 Thread Krishantha Samaraweera

Hi Amila,

Can you copy p2-repo as well. BTW in builder machine p2-repo.zip is
148 bytes, please check.

Thanks,
Krishantha.

On Mon, May 30, 2011 at 7:02 PM, Charitha Kankanamge  wrote:
>
> On Mon, May 30, 2011 at 5:49 PM, Amila Maha Arachchi 
> wrote:
>>
>>
>> On Mon, May 30, 2011 at 5:25 PM, Amila Maha Arachchi 
>> wrote:
>>>
>>>
>>> On Mon, May 30, 2011 at 4:24 PM, Amila Maha Arachchi 
>>> wrote:


 On Mon, May 30, 2011 at 3:22 PM, Amila Maha Arachchi 
 wrote:
>
>
> On Mon, May 30, 2011 at 1:45 PM, Amila Maha Arachchi 
> wrote:
>>
>>
>> On Mon, May 30, 2011 at 11:55 AM, Amila Maha Arachchi
>>  wrote:
>>>
>>>
>>> On Mon, May 30, 2011 at 10:59 AM, Amila Maha Arachchi
>>>  wrote:

 Hi,

 I started downloading packs from the EC2 builder to local builder.
 You can find them at [2]. At the moment only AS is downloaded. G-Reg 
 and IS
 are being downloaded. I'll update as the packs are available.

 [2] http://10.100.1.43/~carbon/releases/carbon/3.2.0/rc3/products/

>>>
>>> G-Reg and IS packs are available locally at [2].
>>
>> GS and MS packs are available locally [2].
>
> DSS and BAM packs are available locally at [2]

 ESB and BPS packs are available locally.
>>>
>>> BRS, CEP and MB packs are available locally now.
>>
>> WSF and LB packs are also available locally now (i.e. All the product
>> packs are available locally). Will be downloading services now.
>
> Thank you very much Amila!
> /Charitha
>
> ___
> 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] Context root disappearing in Websphere

2011-05-12 Thread Krishantha Samaraweera

Hi all,

The same issue [1] has been raised sometime back and it has been resolved
without doing a proper fix.

Thanks
Krishantha

[1] https://wso2.org/jira/browse/CARBON-7371

On Thu, May 12, 2011 at 2:21 PM, Nuwan Bandara  wrote:

> Surprisingly this does not happen in other app servers (Tomcat etc),
> according to pradeep he has seen this when there are relative URLs, But
> there are many places in our UI bundles that we do redirection to relative
> URLs.
>
> Regards,
> /Nuwan
>
>
> On Thu, May 12, 2011 at 2:15 PM, Milinda Pathirage wrote:
>
>> This could be due to recent changes we done to facilitate custom home page
>> URLs. Will look into this.
>>
>> Thanks
>> Milinda
>>
>> On Thu, May 12, 2011 at 1:56 PM, Chamara Ariyarathne 
>> wrote:
>>
>>> Following are the places which Browser redirect with wrong context root
>>> when server deployed in Websphere. I'm sending this for the request made by
>>> Pradeep and Nuwan, and according to the offline chat I had with them, there
>>> will be a similar solution for this.
>>>
>>> *Mashup Server;*
>>> Home button
>>> Upload Module; Modules -> Add Modules -> Upoload
>>> Upload JavaScript services -> Upload
>>> *
>>> Gadget Server;*
>>> Add Gadgets
>>>
>>>
>>> *Chamara Ariyarathne*
>>> Software Engineer - QA;
>>> WSO2 Inc; http://www.wso2.com/.
>>> Mobile; *0772786766*
>>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> Milinda Pathirage
>> Technical Lead and Product Manager, Business Process Server - WSO2 Inc;
>> http://wso2.com
>> Blog: http://blog.mpathirage.com
>>
>> Lean Enterprise Middleware
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> *Thanks & Regards,
>
> Nuwan Bandara
> Senior Software Engineer
>
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>
> http://nuwan.bandara.co
> *
> 
>
> ___
> 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] Question on Integration Tests

2011-05-03 Thread Krishantha Samaraweera

On Wed, May 4, 2011 at 10:50 AM, Isuru Suriarachchi  wrote:

>
>
> On Wed, May 4, 2011 at 10:33 AM, Hiranya Jayathilaka wrote:
>
>> Hi,
>>
>> In our integration tests, is it possible to make a few modifications to
>> the product installation before it starts up? For an example can I replace
>> the axis2.xml of the ESB before it boots up for the test?
>>
>
> I've done something similar in the AS where all the needed artifacts are
> copied into the server before it starts up. I've written a ASTestTemplate to
> do that. May be you can use the same technique to override the axis2.xml.
>

Yes, I have used same technique to copy keystores and services in to
BPS/Axis2Sever. This can be easily extend to copy axis2.xml in your case.

Thanks,
Krishantha.

>
> Thanks,
> ~Isuru
>
>
>>
>> Thanks
>> --
>> Hiranya Jayathilaka
>> Senior Software Engineer;
>> WSO2 Inc.;  http://wso2.org
>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>> Blog: http://techfeast-hiranya.blogspot.com
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Isuru Suriarachchi
> Technical Lead & Product Manager, WSO2 Application Server
> WSO2 Inc. http://wso2.com
> email : is...@wso2.com
> blog : http://isurues.wordpress.com/
>
> lean . enterprise . middleware
>
>
> ___
> 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] G-Reg Test Coverage in Automated Test Framework: ~ 50%

2011-03-07 Thread Krishantha Samaraweera

On Mon, Mar 7, 2011 at 1:40 PM, Senaka Fernando  wrote:

>
>
> On Sun, Mar 6, 2011 at 3:28 PM, Thilini Ishaka  wrote:
>
>> Yes Chamara.
>> Attached the latest coverage report.
>> Increased from 5% and now it is 52%.
>>
>
> Nice, let's the get others done as well. I'm sure we can get over 67%
> coverage, once those are done.
>

+1 for maintaining all G-Reg test frameworks under our main Test Automation
framework. We can easily add them to our test framework and improve the code
coverage. But IMHO we need to improve the test coverage though admin
services. The mentioned frameworks have been using by QA for each product
release for years. Theoretically adding them to framework doesn't improve
anything.. We need to improve those framework or write more test to cover
admin services.

Thanks,
Krishantha.


>
> Thilini, by the way, why aren't the bean classes counted? Is that an EMMA
> bug, or do we need to annotate them or something? If those are counted as
> well, the numbers should be even higher.
>
> Thanks,
> Senaka.
>
>>
>> Thanks.
>>
>> --
>> Thilini
>>
>>
>>
>> On Fri, Mar 4, 2011 at 9:45 PM, Chamara Silva  wrote:
>>
>>> Thilini can we have test coverage now?
>>>
>>> Regards,
>>> Chamara
>>>
>>> On Fri, Mar 4, 2011 at 9:40 PM, Krishantha Samaraweera <
>>> krishan...@wso2.com> wrote:
>>>
>>>>
>>>>
>>>> On Wed, Mar 2, 2011 at 1:23 PM, Krishantha Samaraweera <
>>>> krishan...@wso2.com> wrote:
>>>>
>>>>>
>>>>>>
>>>>>> I believe that the reports are correct. But, you need to run the
>>>>>> governance API, WS Client and the JCR Client, Check-in Check-out client 
>>>>>> as
>>>>>> well, which will improve the coverage. I'm not sure why the bean classes
>>>>>> were not covered. Ideally, if you used the service, the bean classes 
>>>>>> would
>>>>>> be used. So, its kind of strange.
>>>>>>
>>>>>>
>>>>> We don't have tests for governance API, excepts the tests in carbon
>>>>> trunk. We will write some tests for governance API as well. I am in the
>>>>> process of integrating ws-api to test framework it will available within a
>>>>> day.  Checkin/out client tests only support on Linux we will add that to 
>>>>> the
>>>>> framework and will be executed only on Linux environments.
>>>>>
>>>>
>>>> G-Reg WS-API test framework has been integrated with test automation
>>>> framework now.
>>>>
>>>> Thanks,
>>>> Krishantha.
>>>>
>>>>>
>>>>> Thanks,
>>>>> Krishantha.
>>>>>
>>>>
>>>>
>>>> ___
>>>> Carbon-dev mailing list
>>>> Carbon-dev@wso2.org
>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Suminda Chamara Silva
>>> WSO2 Inc.
>>> Mobile: +94 718 302858
>>> blog: http://chamaras.blogspot.com
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> Thilini Ishaka
>> email: thil...@wso2.com
>> mobile: +94 718408171
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> *Senaka Fernando*
> Product Manager - WSO2 Governance Registry;
> Associate Technical Lead; WSO2, Inc.; http://wso2.com*
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
> Linked-In: http://www.linkedin.com/in/senakafernando
>
> *Lean . Enterprise . Middleware
>
>
> ___
> 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] G-Reg Test Coverage in Automated Test Framework: ~ 50%

2011-03-04 Thread Krishantha Samaraweera

On Wed, Mar 2, 2011 at 1:23 PM, Krishantha Samaraweera
wrote:

>
>>
>> I believe that the reports are correct. But, you need to run the
>> governance API, WS Client and the JCR Client, Check-in Check-out client as
>> well, which will improve the coverage. I'm not sure why the bean classes
>> were not covered. Ideally, if you used the service, the bean classes would
>> be used. So, its kind of strange.
>>
>>
> We don't have tests for governance API, excepts the tests in carbon trunk.
> We will write some tests for governance API as well. I am in the process of
> integrating ws-api to test framework it will available within a day.
> Checkin/out client tests only support on Linux we will add that to the
> framework and will be executed only on Linux environments.
>

G-Reg WS-API test framework has been integrated with test automation
framework now.

Thanks,
Krishantha.

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

Re: [Carbon-dev] G-Reg Test Coverage in Automated Test Framework: ~ 50%

2011-03-01 Thread Krishantha Samaraweera

>
>
>
> I believe that the reports are correct. But, you need to run the governance
> API, WS Client and the JCR Client, Check-in Check-out client as well, which
> will improve the coverage. I'm not sure why the bean classes were not
> covered. Ideally, if you used the service, the bean classes would be used.
> So, its kind of strange.
>
>
We don't have tests for governance API, excepts the tests in carbon trunk.
We will write some tests for governance API as well. I am in the process of
integrating ws-api to test framework it will available within a day.
Checkin/out client tests only support on Linux we will add that to the
framework and will be executed only on Linux environments.

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

Re: [Carbon-dev] [QA Test Framework] Focus on functional coverage across more features instead of covering all possible scenarios related to a particular use case

2011-02-20 Thread Krishantha Samaraweera

On Mon, Feb 21, 2011 at 10:31 AM, Charitha Kankanamge wrote:

> I had an offline chat with Samisa last friday regarding the current test
> coverage. We understood that it is essential to have a horizontal coverage
> across features instead of spending time on automating all possible
> scenarios related to a particular functionality. We can fill the gaps later
> on after we completing all features. Therefore, please focus on covering all
> features first.
>

++ 1,  We will go though all admin services and come up with relevant
command classes with few test cases for each admin service. so the gaps can
be filled later by referring to guiding tests.

Thanks,
Krishantha.

>
> Regards
> Charitha
>
> ___
> 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] Fwd: Greg Test Automation Hackathon

2011-02-15 Thread Krishantha Samaraweera

On Tue, Feb 15, 2011 at 4:20 PM, Samisa Abeysinghe  wrote:

>
>
> On Tue, Feb 15, 2011 at 4:03 PM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>>
>>
>> On Tue, Feb 15, 2011 at 3:50 PM, Samisa Abeysinghe wrote:
>>
>>> What is the % coverage of functionality now?
>>>
>>>
>> I would say it is 35%.
>>
>
> Guys, we need to finish this. We need to have a roadmap on this. We need to
> hist 80% at least.
>
> I still see only ESB and G-Reg being covered with test framework. We need
> to get past.
>
> Please work on a roadmap ASAP, as we also need to start looking into other
> products. The next in line should be DS and BPS
>

+1, sure will do

Thanks,
Krishantha.

>
>
>>
>> Thanks
>> Krishantha.
>>
>>>
>>> On Tue, Feb 15, 2011 at 1:59 PM, Krishantha Samaraweera <
>>> krishan...@wso2.com> wrote:
>>>
>>>> Hi Samisa,
>>>>
>>>> On Tue, Feb 15, 2011 at 1:17 PM, Samisa Abeysinghe wrote:
>>>>
>>>>> What happened to this Hackathon? What do we have now??
>>>>
>>>>
>>>> We were able to cover the following tasks.
>>>>
>>>> 1. G-Reg meta data management tests including WSDL, Schema, Policies.
>>>> 2. Done with command classes for add service. In the process of
>>>> integrating FE service XML generation logic to automation framework. Have 
>>>> to
>>>> write tests.
>>>> 3. Started resource versioning tests. Not yet finished.
>>>> 4. Done with command classes for content search, have to write tests.
>>>> 4. Used maven site plugin to view integrated test results.
>>>> 5. Fixed remote registry tests and other test failures.
>>>> 6. Fixed framework related issues on windows environment.
>>>>
>>>> Thanks,
>>>> Krishantha.
>>>>
>>>>>
>>>>>
>>>>> On Thu, Feb 10, 2011 at 9:50 AM, Thilini Ishaka wrote:
>>>>>
>>>>>> +1
>>>>>>
>>>>>>
>>>>>> On Thu, Feb 10, 2011 at 6:34 AM, Chamara Silva wrote:
>>>>>>
>>>>>>> Most probably we can double our automation speed if we can have
>>>>>>> contact person in greg development team instead of disturbing to all the
>>>>>>> people.because sometimes we take long times to understand greg code.
>>>>>>>
>>>>>>>  Regards,
>>>>>>> Chamara
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Feb 9, 2011 at 10:49 PM, Krishantha Samaraweera <
>>>>>>> krishan...@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> We are still on automating SOA meta data management which is the
>>>>>>>> most highest priority functional area. As per todays progress, we will 
>>>>>>>> not
>>>>>>>> be able to finish with all missing functionalities on Friday. However, 
>>>>>>>> We
>>>>>>>> will try to cover the highest priority functional areas as much as 
>>>>>>>> possible
>>>>>>>> before Friday.
>>>>>>>>
>>>>>>>> We may need another few days from next week to have decent amount of
>>>>>>>> G-Reg test coverage.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Krishantha.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Feb 8, 2011 at 12:37 PM, Krishantha Samaraweera <
>>>>>>>> krishan...@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> We have gone though the existing tests and identified following
>>>>>>>>> functional areas which are not covered adequately. We will start work 
>>>>>>>>> on
>>>>>>>>> those areas by given order.
>>>>>>>>>
>>>>>>>>> 1. SOA meta data management - WSDLS, XSDs, Policies, Services and
>>>>>>>>> validation policies.
>>>>>>>>> 2. Content search.
>>>>>>>>> 3. Resource versioning.
>

Re: [Carbon-dev] Fwd: Greg Test Automation Hackathon

2011-02-15 Thread Krishantha Samaraweera

On Tue, Feb 15, 2011 at 3:50 PM, Samisa Abeysinghe  wrote:

> What is the % coverage of functionality now?
>
>
I would say it is 35%.

Thanks
Krishantha.

>
> On Tue, Feb 15, 2011 at 1:59 PM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>> Hi Samisa,
>>
>> On Tue, Feb 15, 2011 at 1:17 PM, Samisa Abeysinghe wrote:
>>
>>> What happened to this Hackathon? What do we have now??
>>
>>
>> We were able to cover the following tasks.
>>
>> 1. G-Reg meta data management tests including WSDL, Schema, Policies.
>> 2. Done with command classes for add service. In the process of
>> integrating FE service XML generation logic to automation framework. Have to
>> write tests.
>> 3. Started resource versioning tests. Not yet finished.
>> 4. Done with command classes for content search, have to write tests.
>> 4. Used maven site plugin to view integrated test results.
>> 5. Fixed remote registry tests and other test failures.
>> 6. Fixed framework related issues on windows environment.
>>
>> Thanks,
>> Krishantha.
>>
>>>
>>>
>>> On Thu, Feb 10, 2011 at 9:50 AM, Thilini Ishaka wrote:
>>>
>>>> +1
>>>>
>>>>
>>>> On Thu, Feb 10, 2011 at 6:34 AM, Chamara Silva wrote:
>>>>
>>>>> Most probably we can double our automation speed if we can have contact
>>>>> person in greg development team instead of disturbing to all the
>>>>> people.because sometimes we take long times to understand greg code.
>>>>>
>>>>>  Regards,
>>>>> Chamara
>>>>>
>>>>>
>>>>> On Wed, Feb 9, 2011 at 10:49 PM, Krishantha Samaraweera <
>>>>> krishan...@wso2.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> We are still on automating SOA meta data management which is the most
>>>>>> highest priority functional area. As per todays progress, we will not be
>>>>>> able to finish with all missing functionalities on Friday. However, We 
>>>>>> will
>>>>>> try to cover the highest priority functional areas as much as possible
>>>>>> before Friday.
>>>>>>
>>>>>> We may need another few days from next week to have decent amount of
>>>>>> G-Reg test coverage.
>>>>>>
>>>>>> Thanks,
>>>>>> Krishantha.
>>>>>>
>>>>>>
>>>>>> On Tue, Feb 8, 2011 at 12:37 PM, Krishantha Samaraweera <
>>>>>> krishan...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> We have gone though the existing tests and identified following
>>>>>>> functional areas which are not covered adequately. We will start work on
>>>>>>> those areas by given order.
>>>>>>>
>>>>>>> 1. SOA meta data management - WSDLS, XSDs, Policies, Services and
>>>>>>> validation policies.
>>>>>>> 2. Content search.
>>>>>>> 3. Resource versioning.
>>>>>>> 4. Custom Queries.
>>>>>>> 5. Registry handers.
>>>>>>> 6. Life cycles - promote, demote
>>>>>>> 7. Eventing and Notification.
>>>>>>> 8. Registry mounting.
>>>>>>> 9. Authentication and authorization on resources.
>>>>>>> 10. C-App deployment.
>>>>>>> 11. Tag/Comment/Rating
>>>>>>> 12. Symlinks
>>>>>>> 13. More test for dependencies
>>>>>>> 14. Activity search.
>>>>>>>
>>>>>>> Please let us know, if there are any other high priority functional
>>>>>>> areas that we need look at first.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Krishantha.
>>>>>>>
>>>>>>> On Tue, Feb 8, 2011 at 11:43 AM, Chamara Silva wrote:
>>>>>>>
>>>>>>>> Forwarded.
>>>>>>>> /chamara
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> -- Forwarded message --
>>>>>>>> From: Chamara Silva 
>>>>>>>> Date: Tue, Feb 8, 2011 at 11:41 AM
>>>

Re: [Carbon-dev] Fwd: Greg Test Automation Hackathon

2011-02-15 Thread Krishantha Samaraweera

Hi Samisa,

On Tue, Feb 15, 2011 at 1:17 PM, Samisa Abeysinghe  wrote:

> What happened to this Hackathon? What do we have now??


We were able to cover the following tasks.

1. G-Reg meta data management tests including WSDL, Schema, Policies.
2. Done with command classes for add service. In the process of integrating
FE service XML generation logic to automation framework. Have to write
tests.
3. Started resource versioning tests. Not yet finished.
4. Done with command classes for content search, have to write tests.
4. Used maven site plugin to view integrated test results.
5. Fixed remote registry tests and other test failures.
6. Fixed framework related issues on windows environment.

Thanks,
Krishantha.

>
>
> On Thu, Feb 10, 2011 at 9:50 AM, Thilini Ishaka  wrote:
>
>> +1
>>
>>
>> On Thu, Feb 10, 2011 at 6:34 AM, Chamara Silva  wrote:
>>
>>> Most probably we can double our automation speed if we can have contact
>>> person in greg development team instead of disturbing to all the
>>> people.because sometimes we take long times to understand greg code.
>>>
>>>  Regards,
>>> Chamara
>>>
>>>
>>> On Wed, Feb 9, 2011 at 10:49 PM, Krishantha Samaraweera <
>>> krishan...@wso2.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> We are still on automating SOA meta data management which is the most
>>>> highest priority functional area. As per todays progress, we will not be
>>>> able to finish with all missing functionalities on Friday. However, We will
>>>> try to cover the highest priority functional areas as much as possible
>>>> before Friday.
>>>>
>>>> We may need another few days from next week to have decent amount of
>>>> G-Reg test coverage.
>>>>
>>>> Thanks,
>>>> Krishantha.
>>>>
>>>>
>>>> On Tue, Feb 8, 2011 at 12:37 PM, Krishantha Samaraweera <
>>>> krishan...@wso2.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> We have gone though the existing tests and identified following
>>>>> functional areas which are not covered adequately. We will start work on
>>>>> those areas by given order.
>>>>>
>>>>> 1. SOA meta data management - WSDLS, XSDs, Policies, Services and
>>>>> validation policies.
>>>>> 2. Content search.
>>>>> 3. Resource versioning.
>>>>> 4. Custom Queries.
>>>>> 5. Registry handers.
>>>>> 6. Life cycles - promote, demote
>>>>> 7. Eventing and Notification.
>>>>> 8. Registry mounting.
>>>>> 9. Authentication and authorization on resources.
>>>>> 10. C-App deployment.
>>>>> 11. Tag/Comment/Rating
>>>>> 12. Symlinks
>>>>> 13. More test for dependencies
>>>>> 14. Activity search.
>>>>>
>>>>> Please let us know, if there are any other high priority functional
>>>>> areas that we need look at first.
>>>>>
>>>>> Thanks,
>>>>> Krishantha.
>>>>>
>>>>> On Tue, Feb 8, 2011 at 11:43 AM, Chamara Silva wrote:
>>>>>
>>>>>> Forwarded.
>>>>>> /chamara
>>>>>>
>>>>>>
>>>>>>
>>>>>> -- Forwarded message --
>>>>>> From: Chamara Silva 
>>>>>> Date: Tue, Feb 8, 2011 at 11:41 AM
>>>>>> Subject: Greg Test Automation Hackathon
>>>>>> To: strategy-group 
>>>>>>
>>>>>>
>>>>>> Following are the task we need to do in Greg automation hackathon.
>>>>>>
>>>>>> 1. Need to update QA repository with latest dependency jars.
>>>>>> 2. Add latest admin service test cases.
>>>>>> 3. Functionality test cases automation - Krishantha will reply what
>>>>>> are the functionalities need to automate.
>>>>>>
>>>>>> Thank you,
>>>>>> Chamara
>>>>>>
>>>>>> --
>>>>>> Suminda Chamara Silva
>>>>>> WSO2 Inc.
>>>>>> Mobile: <+94718302858>+94 718 302858 <+94718302858>
>>>>>> blog: http://chamaras.blogspot.com
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Suminda Chamara Silv

Re: [Carbon-dev] G-Reg checkin/out client automation

2011-02-03 Thread Krishantha Samaraweera

Hi Samisa,

On Thu, Feb 3, 2011 at 9:02 AM, Samisa Abeysinghe  wrote:

> Um, it has to work across platforms. Can we not use something like
> ant/maven for this rather than a script?


Yes, I thought of using ant initially. But even with ant I cannot write
platform independent script. Please refer the ant script [1] which I used to
test G-Reg with different DBs options. Even in this script I had to check
the OS before executing certain system calls. I selected Perl since I was
able to reuse XML processing model written by C team. And, perl library
functions provide all most all features I require. My plan was to write the
script for Linux and extend it to support windows later.

To be frank, I am not familiar much with maven. And my initial impression on
maven was based on our build scripts, which we use ant scripts inside maven
to make the build. So I under the impression that maven can not do much
things when it comes to automating command line tool.

Thanks,
Krishantha

[1]
https://wso2.org/repos/wso2/trunk/commons/qa/db-configuration-scripts/build.xml



>
>
> On Thu, Feb 3, 2011 at 7:58 AM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>> Hi Sumedha,
>>
>> On 2/3/11, Sumedha Rubasinghe  wrote:
>> > Hi Kris,
>> > This is excellent work. I tried checking out, but it failed giving
>> following
>> > error.
>> >
>> > "svn: URL '
>> >
>> https://wso2.org/repos/wso2/trunk/commons/qa/registry/checkin-checkout-script/src/main/resources/governance/services/http/www/webserviceX
>> '
>> > of existing directory
>> >
>> 'checkin-checkout-script/src/main/resources/governance/services/http/www/webservicex'
>> > does not match expected URL '
>> >
>> https://wso2.org/repos/wso2/trunk/commons/qa/registry/checkin-checkout-script/src/main/resources/governance/services/http/www/webservicex
>> > '
>> > "
>>
>> Thanks for your inputs, I think you are on Mac or Windows. Linux users
>> will not find this problem. Here is the reason.
>>
>> When you have two directories like
>> /src/main/resources/governance/services/http/www/webservicex
>> and
>> /src/main/resources/governance/services/http/www/webserviceX
>>
>> on Linux, they are different directories. So you import like this to
>> subversion without any issues.
>>
>> But when you try to checkout on Windows/Mac, since these are same
>> directories on the environment, you get that error message.
>>
>> I will fix this checkout problem and update you.
>>
>> Thanks,
>> Krishantha.
>>
>> >
>> > Anyway, talk with Damitha & make the result output file format
>> compatible
>> > with what our performance testing framework can read in.  That way, we
>> can
>> > directly use the output from this to generate statistics using
>> performance
>> > testing framework.
>> >
>> > /sumedha
>> >
>> > On Thu, Feb 3, 2011 at 1:58 AM, Krishantha Samaraweera
>> > wrote:
>> >
>> >> Hi all,
>> >>
>> >> I have improved the perl script which I have been using to test G-Reg
>> >> checkin/out client as a test framework. Currently, the framework has
>> >> around 36 test cases and covers 80% of the checkin/out
>> >> functionalities, including some customer scenarios. I will be able to
>> >> add more tests once G-Reg team finish with redesigning REST-API in
>> >> Registry. And, also I wil check the possibility of using remote
>> >> registry APIs to cater some registry operation requirements for
>> >> pending functinalities.
>> >>
>> >> Hopefully, this framework will save at least five hours of testing
>> effort.
>> >>
>> >> Source code and the the framework distribution can be found at [1] and
>> >> [2]. Instructions to run the framework is available in the README of
>> >> given distribution. the framework runs based on the parameters given
>> >> in greg_test.xml file, To add more test, you may have to write a Perl
>> >> subroutine and customized the tests defined.
>> >>
>> >> A sample result file is also attached.
>> >>
>> >> Todo:
>> >> ===
>> >> 1. Write a windows version (if required)
>> >> 2. Resource meta data checkin/out.
>> >> 3. cyclic symlink handling.
>> >> 4. checkin/out based on resource permission levels.
>> >> 5. Add more test to cover service meta data checkin/out
>> >>

Re: [Carbon-dev] G-Reg checkin/out client automation

>
> I will fix this checkout problem and update you.
>

Fixed now, Please check.

Thanks,
Krishantha.


> Thanks,
> Krishantha.
>
> >
> > Anyway, talk with Damitha & make the result output file format compatible
> > with what our performance testing framework can read in.  That way, we
> can
> > directly use the output from this to generate statistics using
> performance
> > testing framework.
> >
> > /sumedha
> >
> > On Thu, Feb 3, 2011 at 1:58 AM, Krishantha Samaraweera
> > wrote:
> >
> >> Hi all,
> >>
> >> I have improved the perl script which I have been using to test G-Reg
> >> checkin/out client as a test framework. Currently, the framework has
> >> around 36 test cases and covers 80% of the checkin/out
> >> functionalities, including some customer scenarios. I will be able to
> >> add more tests once G-Reg team finish with redesigning REST-API in
> >> Registry. And, also I wil check the possibility of using remote
> >> registry APIs to cater some registry operation requirements for
> >> pending functinalities.
> >>
> >> Hopefully, this framework will save at least five hours of testing
> effort.
> >>
> >> Source code and the the framework distribution can be found at [1] and
> >> [2]. Instructions to run the framework is available in the README of
> >> given distribution. the framework runs based on the parameters given
> >> in greg_test.xml file, To add more test, you may have to write a Perl
> >> subroutine and customized the tests defined.
> >>
> >> A sample result file is also attached.
> >>
> >> Todo:
> >> ===
> >> 1. Write a windows version (if required)
> >> 2. Resource meta data checkin/out.
> >> 3. cyclic symlink handling.
> >> 4. checkin/out based on resource permission levels.
> >> 5. Add more test to cover service meta data checkin/out
> >> 6. Checkin/out between different instances.
> >>
> >> I look forward to your feedbacks for improvements.
> >>
> >> Thanks,
> >> Krishantha.
> >>
> >> [1]
> >>
> https://wso2.org/repos/wso2/trunk/commons/qa/registry/checkin-checkout-script
> >> [2]
> >>
> http://ww2.wso2.org/~qa/test_framework_builds/registry/wso2carbon-checkin-checkout-1.0.zip<http://ww2.wso2.org/%7Eqa/test_framework_builds/registry/wso2carbon-checkin-checkout-1.0.zip>
> <
> http://ww2.wso2.org/%7Eqa/test_framework_builds/registry/wso2carbon-checkin-checkout-1.0.zip
> >
> >>
> >> ___
> >> 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] G-Reg checkin/out client automation

Hi Sumedha,

On 2/3/11, Sumedha Rubasinghe  wrote:
> Hi Kris,
> This is excellent work. I tried checking out, but it failed giving following
> error.
>
> "svn: URL '
> https://wso2.org/repos/wso2/trunk/commons/qa/registry/checkin-checkout-script/src/main/resources/governance/services/http/www/webserviceX'
> of existing directory
> 'checkin-checkout-script/src/main/resources/governance/services/http/www/webservicex'
> does not match expected URL '
> https://wso2.org/repos/wso2/trunk/commons/qa/registry/checkin-checkout-script/src/main/resources/governance/services/http/www/webservicex
> '
> "

Thanks for your inputs, I think you are on Mac or Windows. Linux users
will not find this problem. Here is the reason.

When you have two directories like
/src/main/resources/governance/services/http/www/webservicex
and
/src/main/resources/governance/services/http/www/webserviceX

on Linux, they are different directories. So you import like this to
subversion without any issues.

But when you try to checkout on Windows/Mac, since these are same
directories on the environment, you get that error message.

I will fix this checkout problem and update you.

Thanks,
Krishantha.

>
> Anyway, talk with Damitha & make the result output file format compatible
> with what our performance testing framework can read in.  That way, we can
> directly use the output from this to generate statistics using performance
> testing framework.
>
> /sumedha
>
> On Thu, Feb 3, 2011 at 1:58 AM, Krishantha Samaraweera
> wrote:
>
>> Hi all,
>>
>> I have improved the perl script which I have been using to test G-Reg
>> checkin/out client as a test framework. Currently, the framework has
>> around 36 test cases and covers 80% of the checkin/out
>> functionalities, including some customer scenarios. I will be able to
>> add more tests once G-Reg team finish with redesigning REST-API in
>> Registry. And, also I wil check the possibility of using remote
>> registry APIs to cater some registry operation requirements for
>> pending functinalities.
>>
>> Hopefully, this framework will save at least five hours of testing effort.
>>
>> Source code and the the framework distribution can be found at [1] and
>> [2]. Instructions to run the framework is available in the README of
>> given distribution. the framework runs based on the parameters given
>> in greg_test.xml file, To add more test, you may have to write a Perl
>> subroutine and customized the tests defined.
>>
>> A sample result file is also attached.
>>
>> Todo:
>> ===
>> 1. Write a windows version (if required)
>> 2. Resource meta data checkin/out.
>> 3. cyclic symlink handling.
>> 4. checkin/out based on resource permission levels.
>> 5. Add more test to cover service meta data checkin/out
>> 6. Checkin/out between different instances.
>>
>> I look forward to your feedbacks for improvements.
>>
>> Thanks,
>> Krishantha.
>>
>> [1]
>> https://wso2.org/repos/wso2/trunk/commons/qa/registry/checkin-checkout-script
>> [2]
>> http://ww2.wso2.org/~qa/test_framework_builds/registry/wso2carbon-checkin-checkout-1.0.zip<http://ww2.wso2.org/%7Eqa/test_framework_builds/registry/wso2carbon-checkin-checkout-1.0.zip>
>>
>> ___
>> 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

[Carbon-dev] G-Reg checkin/out client automation

Hi all,

I have improved the perl script which I have been using to test G-Reg
checkin/out client as a test framework. Currently, the framework has
around 36 test cases and covers 80% of the checkin/out
functionalities, including some customer scenarios. I will be able to
add more tests once G-Reg team finish with redesigning REST-API in
Registry. And, also I wil check the possibility of using remote
registry APIs to cater some registry operation requirements for
pending functinalities.

Hopefully, this framework will save at least five hours of testing effort.

Source code and the the framework distribution can be found at [1] and
[2]. Instructions to run the framework is available in the README of
given distribution. the framework runs based on the parameters given
in greg_test.xml file, To add more test, you may have to write a Perl
subroutine and customized the tests defined.

A sample result file is also attached.

Todo:
===
1. Write a windows version (if required)
2. Resource meta data checkin/out.
3. cyclic symlink handling.
4. checkin/out based on resource permission levels.
5. Add more test to cover service meta data checkin/out
6. Checkin/out between different instances.

I look forward to your feedbacks for improvements.

Thanks,
Krishantha.

[1]https://wso2.org/repos/wso2/trunk/commons/qa/registry/checkin-checkout-script
[2]http://ww2.wso2.org/~qa/test_framework_builds/registry/wso2carbon-checkin-checkout-1.0.zip
Total test cases: 36
Successful test cases: 36
Failed test cases: 0
Presenatage of failure cases: 0 %

Passed Test Cases
===
test1 -- chekout registry root
test2 -- update registry root
test3 -- checkin to registry root
test4 -- chekout a registry collection
test5 -- chekout registry root to a dump file
test6 -- chekout registry collection to a dump file
test7 -- checkin dump file to registry root - depends on test5
test8 -- checkin dump file to registry collection - depends on test6
test9 -- update registry collection - depends on test4
test10 -- checkin new file to registry root
test11 -- checkout updates to registry root- depends on test10
test12 -- update a file and checkin to registry root - depends on test11
test13 -- checkout updated content of root - depends on test12
test14 -- checkin file with colon to registry root
test15 -- checkout resources with colon in name- depends on test14
test16 -- checkin file names with spaces to registry root
test17 -- checkout file with spaces- depends on test16
test18 -- checkin files to a collection - depends on test17
test19 -- checkin after file deletion - depends on test18
test20 -- checkout after file deletion - depends on test19
test21 -- checkin collection
test22 -- checkout collection - depends on test21
test23 -- checkin collection after updating- depends on test22
test24 -- checkout collection after updating- depends on test23
test25 -- checkin collection after deleting - depends on test24
test26 -- checkout collection after deleting - depends on test25
test27 -- checkin WSDLS, Schemas, Endpoints, Policies, Services
test28 -- checkout WSDLS, Schemas, Endpoints, Policies, Services
test29 -- checkin a collection with symlinks
test30 -- checkout a collection with symlinks
test31 -- checkout registry root with incorrect user credentials
test32 -- checkout from invalid resource path
test33 -- checkin to registry root with invalid user credentials
test34 -- Update registry root with invalid user credentials
test35 -- checkout with conflicting resources
test36 -- update with conflicting resources - depends test35

Failed Test Cases
===

cat: filename-fail.out: No such file or directory
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Invitation: Group B : Code review (Registry Search Service) @ Thu Feb 3 2pm - 3pm (carbon-dev@wso2.org)