from:"Krishantha Samaraweera"

Hi Waruna,

On Wed, May 6, 2015 at 9:12 AM, Waruna Perera waru...@wso2.com wrote:

 Hi Krishantha,

 And we need to update Automation.xml to use following class instead of one
 from utils.


Please remove the CarbonServerExtension class at utils. Its was deprecated
in last release and moved to test extensions to support for carbon kernel
startup.

Need to completely get rid of this extension class and its dependencies.

Thanks,
Krishantha.




 org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension

 Thanks

 On Tue, May 5, 2015 at 6:29 PM, Nuwan Wimalasekara nuw...@wso2.com
 wrote:

 Hi Krishantha,
 I tried generating coverage in ESB. It is working fine and Coverage
 reports generated. However the coverage report aggregation seems not
 working when there are multiple tests modules. We need to fix the issue.

 test-automation-framework - 4.3.2-SNAPSHOT
 carbon-platform-integration-utils - 4.3.1-SNAPSHOT

 Thanks,
 Nuwanw

 On Wed, Apr 29, 2015 at 10:41 PM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 Correction : Step #1 configuration should be as follows.

 execution
 idcopy-jacoco-dependencies/id
 phasecompile/phase
 goals
 goalcopy-dependencies/goal
 /goals
 configuration

 outputDirectory${project.build.directory}/jacoco/outputDirectory
 includeTypesjar/includeTypes
 includeArtifactIdsorg.jacoco.agent/includeArtifactIds
 /configuration
 /execution

 Thanks,
 Krishantha.

 On Thu, Apr 30, 2015 at 2:50 AM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 Hi all,

 New coverage implementation using Jacoco has been committed to master
 branch of carbon-platform-integration. I tried my best to adhere to
 existing Emma based design and reuse same instrumentation and filters text
 files. Note that this new coverage implementation was done to support for
 JDK 1.7 and 1.8. We need to test the new implementation thoroughly before
 the release.

 I've done initial testing with AS and everything seems to work.
 Automation team will start verifying coverage with products already
 migrated JDK 1.7. Specially products with multiple test modules (ESB, G-Reg
  BPS)

 Lets focus on testing following scenarios before the release.

 Test Scenarios for coverage :

 1. Coverage generation with patches applied.
 2. Merge coverage reports in multiple test modules.
 3. WebApp class coverage.
 4. Coverage generation after restart and impact to coverage numbers.

 To get started with Jacoco coverage :

 1. Edit your test module pom and replace emma copy dependency execution
 configuration with below.

 execution
 idcopy-emma-dependencies/id
 phasecompile/phase
 goals
 goalcopy-dependencies/goal
 /goals
 configuration

 outputDirectory${project.build.directory}/emma/outputDirectory
 includeTypesjar/includeTypes
 includeArtifactIdsemma
 /includeArtifactIds
 /configuration
 /execution

 2. Include jacoco argent as a dependency to root pom.

 dependency
 groupIdorg.jacoco/groupId
 artifactIdorg.jacoco.agent/artifactId
 version${jacoco.agent.version}/version
 /dependency

 jacoco.agent.version0.7.4.201502262128/jacoco.agent.version

 3. Remove following system properties from surefire plugin.

 emma.home${basedir}/target/emma/emma.home
 emma.output${basedir}/target/emma/emma.output

 You will find following log entries in console with required details to
 view the report once coverage generation completed. Available report
 formats are XML, HTML and CSV

 INFO
  
 [org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerManager]
 - Jacoco coverage dump file path :
 /Users/krishantha/git/wso2/product-as/modules/integration/tests-integration/tests/target/jacoco.exec
 INFO
  
 [org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerManager]
 - Jacoco class file path :
 /Users/xxx/product-as/modules/integration/tests-integration/tests/target/wso2as-6.0.0-NAPSHOT/repository/components/plugins
 INFO
  
 [org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerManager]
 - Jacoco coverage report path :
 /Users/krishantha/git/wso2/product-as/modules/integration/tests-integration/tests/target/jacoco/coverage

 Thanks,
 Krishantha.

 --
 Krishantha Samaraweera
 Senior Technical Lead - Test Automation
 Mobile: +94 77 7759918
 WSO2, Inc.; http://wso2.com/
 lean . enterprise . middlewear.




 --
 Krishantha Samaraweera
 Senior Technical Lead - Test Automation
 Mobile: +94 77 7759918
 WSO2, Inc.; http://wso2.com/
 lean . enterprise . middlewear.




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

 phone: +94 71 668 4620






 --
 Waruna Perera
 Senior Software Engineer - Test Automation
 Mobile: +94 77 3867037
 WSO2, Inc.; http://wso2.com/
 lean . enterprise . middlewear.




-- 
Krishantha Samaraweera
Senior Technical Lead - Test Automation

Re: [Dev] Testing Jacoco based code coverage genration

Hi Nuwan,

May be we can think of introducing pom file to do merging. If this option
is not user friendly.

Thanks,
Krishantha.

On Wed, May 6, 2015 at 10:24 AM, Nuwan Wimalasekara nuw...@wso2.com wrote:

Thanks,
Nuwanw

On Tue, May 5, 2015 at 9:47 PM, Nuwan Wimalasekara nuw...@wso2.com
wrote:

Yes. The correct implementation
is
org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension.
We will remove the CarbonServerExtension from utils to get rid of
conflicts.

Thanks,
Nuwanw

On Tue, May 5, 2015 at 9:27 PM, Krishantha Samaraweera
krishan...@wso2.com wrote:

Hi Nuwan,

You should remove
org.wso2.carbon.integration.common.extensions.carbonserver.CarbonServerExtension
not the
org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension.

Thanks,
Krishantha.

On Wed, May 6, 2015 at 9:47 AM, Nuwan Wimalasekara nuw...@wso2.com
wrote:

Hi
We should
remove
org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension
from extensions. Then all the tests module should refer the correct class.

Thanks,
Nuwanw

On Tue, May 5, 2015 at 8:49 PM, Krishantha Samaraweera
krishan...@wso2.com wrote:

Hi Waruna,

On Wed, May 6, 2015 at 9:12 AM, Waruna Perera waru...@wso2.com
wrote:

Hi Krishantha,

And we need to update Automation.xml to use following class instead
of one from utils.

Please remove the CarbonServerExtension class at utils. Its was
deprecated in last release and moved to test extensions to support for
carbon kernel startup.

Need to completely get rid of this extension class and its
dependencies.

Thanks,
Krishantha.

org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension

Thanks

On Tue, May 5, 2015 at 6:29 PM, Nuwan Wimalasekara nuw...@wso2.com
wrote:

test-automation-framework - 4.3.2-SNAPSHOT
carbon-platform-integration-utils - 4.3.1-SNAPSHOT

Thanks,
Nuwanw

On Wed, Apr 29, 2015 at 10:41 PM, Krishantha Samaraweera
krishan...@wso2.com wrote:

Correction : Step #1 configuration should be as follows.

execution
idcopy-jacoco-dependencies/id
phasecompile/phase
goals
goalcopy-dependencies/goal
/goals
configuration

outputDirectory${project.build.directory}/jacoco/outputDirectory
includeTypesjar/includeTypes
includeArtifactIdsorg.jacoco.agent/includeArtifactIds
/configuration
/execution

Thanks,
Krishantha.

On Thu, Apr 30, 2015 at 2:50 AM, Krishantha Samaraweera
krishan...@wso2.com wrote:

Hi all,

New coverage implementation using Jacoco has been committed to
master branch of carbon-platform-integration. I tried my best to
adhere to
existing Emma based design and reuse same instrumentation and filters
text
files. Note that this new coverage implementation was done to support
for
JDK 1.7 and 1.8. We need to test the new implementation thoroughly
before
the release.

Lets focus on testing following scenarios before the release.

Test Scenarios for coverage :

1. Coverage generation with patches applied.
2. Merge coverage reports in multiple test modules.
3. WebApp class coverage.
4. Coverage generation after restart and impact to coverage
numbers.

To get started with Jacoco coverage :

1. Edit your test module pom and replace emma copy dependency
execution configuration with below.

execution
idcopy-emma-dependencies/id
phasecompile/phase
goals
goalcopy-dependencies/goal
/goals
configuration

outputDirectory${project.build.directory}/emma/outputDirectory
includeTypesjar/includeTypes
includeArtifactIdsemma
/includeArtifactIds
/configuration
/execution

2. Include jacoco argent as a dependency to root pom.

dependency

Re: [Dev] Testing Jacoco based code coverage genration

Hi Nuwan,

You should remove
org.wso2.carbon.integration.common.extensions.carbonserver.CarbonServerExtension
not the
org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension.

Thanks,
Krishantha.

On Wed, May 6, 2015 at 9:47 AM, Nuwan Wimalasekara nuw...@wso2.com wrote:

 Hi
 We should
 remove 
 org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension
 from extensions. Then all the tests module should refer the correct class.

 Thanks,
 Nuwanw

 On Tue, May 5, 2015 at 8:49 PM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 Hi Waruna,

 On Wed, May 6, 2015 at 9:12 AM, Waruna Perera waru...@wso2.com wrote:

 Hi Krishantha,

 And we need to update Automation.xml to use following class instead of
 one from utils.


 Please remove the CarbonServerExtension class at utils. Its was
 deprecated in last release and moved to test extensions to support for
 carbon kernel startup.

 Need to completely get rid of this extension class and its dependencies.

 Thanks,
 Krishantha.




 org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension

 Thanks

 On Tue, May 5, 2015 at 6:29 PM, Nuwan Wimalasekara nuw...@wso2.com
 wrote:

 Hi Krishantha,
 I tried generating coverage in ESB. It is working fine and Coverage
 reports generated. However the coverage report aggregation seems not
 working when there are multiple tests modules. We need to fix the issue.

 test-automation-framework - 4.3.2-SNAPSHOT
 carbon-platform-integration-utils - 4.3.1-SNAPSHOT

 Thanks,
 Nuwanw

 On Wed, Apr 29, 2015 at 10:41 PM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 Correction : Step #1 configuration should be as follows.

 execution
 idcopy-jacoco-dependencies/id
 phasecompile/phase
 goals
 goalcopy-dependencies/goal
 /goals
 configuration

 outputDirectory${project.build.directory}/jacoco/outputDirectory
 includeTypesjar/includeTypes
 includeArtifactIdsorg.jacoco.agent/includeArtifactIds
 /configuration
 /execution

 Thanks,
 Krishantha.

 On Thu, Apr 30, 2015 at 2:50 AM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 Hi all,

 New coverage implementation using Jacoco has been committed to master
 branch of carbon-platform-integration. I tried my best to adhere to
 existing Emma based design and reuse same instrumentation and filters 
 text
 files. Note that this new coverage implementation was done to support for
 JDK 1.7 and 1.8. We need to test the new implementation thoroughly before
 the release.

 I've done initial testing with AS and everything seems to work.
 Automation team will start verifying coverage with products already
 migrated JDK 1.7. Specially products with multiple test modules (ESB, 
 G-Reg
  BPS)

 Lets focus on testing following scenarios before the release.

 Test Scenarios for coverage :

 1. Coverage generation with patches applied.
 2. Merge coverage reports in multiple test modules.
 3. WebApp class coverage.
 4. Coverage generation after restart and impact to coverage numbers.

 To get started with Jacoco coverage :

 1. Edit your test module pom and replace emma copy dependency
 execution configuration with below.

 execution
 idcopy-emma-dependencies/id
 phasecompile/phase
 goals
 goalcopy-dependencies/goal
 /goals
 configuration

 outputDirectory${project.build.directory}/emma/outputDirectory
 includeTypesjar/includeTypes
 includeArtifactIdsemma
 /includeArtifactIds
 /configuration
 /execution

 2. Include jacoco argent as a dependency to root pom.

 dependency
 groupIdorg.jacoco/groupId
 artifactIdorg.jacoco.agent/artifactId
 version${jacoco.agent.version}/version
 /dependency

 jacoco.agent.version0.7.4.201502262128/jacoco.agent.version

 3. Remove following system properties from surefire plugin.

 emma.home${basedir}/target/emma/emma.home
 emma.output${basedir}/target/emma/emma.output

 You will find following log entries in console with required details
 to view the report once coverage generation completed. Available report
 formats are XML, HTML and CSV

 INFO
  
 [org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerManager]
 - Jacoco coverage dump file path :
 /Users/krishantha/git/wso2/product-as/modules/integration/tests-integration/tests/target/jacoco.exec
 INFO
  
 [org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerManager]
 - Jacoco class file path :
 /Users/xxx/product-as/modules/integration/tests-integration/tests/target/wso2as-6.0.0-NAPSHOT/repository/components/plugins
 INFO
  
 [org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerManager]
 - Jacoco coverage report path :
 /Users/krishantha/git/wso2/product-as/modules/integration/tests-integration/tests/target/jacoco/coverage

 Thanks,
 Krishantha.

 --
 Krishantha Samaraweera
 Senior Technical Lead - Test Automation
 Mobile: +94 77 7759918
 WSO2, Inc

Re: [Dev] Testing Jacoco based code coverage genration

Hi Nuwan,

What is the exact issue ?

Please check whether java.io.tmpdir directory is set to another in test
module pom files. Normally coverage data should be appended to jacoco.exec
file at tmp dir when running each test module.

Thanks,
Krishantha.

On Tue, May 5, 2015 at 6:29 PM, Nuwan Wimalasekara nuw...@wso2.com wrote:

test-automation-framework - 4.3.2-SNAPSHOT
carbon-platform-integration-utils - 4.3.1-SNAPSHOT

Thanks,
Nuwanw

On Wed, Apr 29, 2015 at 10:41 PM, Krishantha Samaraweera
krishan...@wso2.com wrote:

Correction : Step #1 configuration should be as follows.

execution
idcopy-jacoco-dependencies/id
phasecompile/phase
goals
goalcopy-dependencies/goal
/goals
configuration

outputDirectory${project.build.directory}/jacoco/outputDirectory
includeTypesjar/includeTypes
includeArtifactIdsorg.jacoco.agent/includeArtifactIds
/configuration
/execution

Thanks,
Krishantha.

On Thu, Apr 30, 2015 at 2:50 AM, Krishantha Samaraweera
krishan...@wso2.com wrote:

Hi all,

New coverage implementation using Jacoco has been committed to master
branch of carbon-platform-integration. I tried my best to adhere to
existing Emma based design and reuse same instrumentation and filters text
files. Note that this new coverage implementation was done to support for
JDK 1.7 and 1.8. We need to test the new implementation thoroughly before
the release.

Lets focus on testing following scenarios before the release.

Test Scenarios for coverage :

1. Coverage generation with patches applied.
2. Merge coverage reports in multiple test modules.
3. WebApp class coverage.
4. Coverage generation after restart and impact to coverage numbers.

To get started with Jacoco coverage :

1. Edit your test module pom and replace emma copy dependency execution
configuration with below.

execution
idcopy-emma-dependencies/id
phasecompile/phase
goals
goalcopy-dependencies/goal
/goals
configuration

outputDirectory${project.build.directory}/emma/outputDirectory
includeTypesjar/includeTypes
includeArtifactIdsemma
/includeArtifactIds
/configuration
/execution

2. Include jacoco argent as a dependency to root pom.

dependency
groupIdorg.jacoco/groupId
artifactIdorg.jacoco.agent/artifactId
version${jacoco.agent.version}/version
/dependency

jacoco.agent.version0.7.4.201502262128/jacoco.agent.version

3. Remove following system properties from surefire plugin.

emma.home${basedir}/target/emma/emma.home
emma.output${basedir}/target/emma/emma.output

You will find following log entries in console with required details to
view the report once coverage generation completed. Available report
formats are XML, HTML and CSV

INFO

[org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerManager]
- Jacoco coverage dump file path :
/Users/krishantha/git/wso2/product-as/modules/integration/tests-integration/tests/target/jacoco.exec
INFO

[org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerManager]
- Jacoco class file path :
/Users/xxx/product-as/modules/integration/tests-integration/tests/target/wso2as-6.0.0-NAPSHOT/repository/components/plugins
INFO

[org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerManager]
- Jacoco coverage report path :
/Users/krishantha/git/wso2/product-as/modules/integration/tests-integration/tests/target/jacoco/coverage

Thanks,
Krishantha.

--
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.

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

phone: +94 71 668 4620

Re: [Dev] How to assign java agent to carbon servers

Hi Nuwan,

Nope.. I had to edit wso2server.sh to attach java agent. The code is
committed to master branch.

Thanks,
Krishantha.

On Tue, May 5, 2015 at 4:22 PM, Nuwan Wimalasekara nuw...@wso2.com wrote:

 Hi Krishantha,
 Did you find a solution to set the agent without editing the wso2server.sh

 Thanks,
 Nuwanw


 On Wed, Apr 29, 2015 at 1:04 PM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:



 On Thu, Apr 30, 2015 at 1:31 AM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 Hi all,

 I'm trying to assign Jacoco (code coverage) java agent to our products
 and found it's not OOB supported though command line. So I had to edit the
 wso2server.sh and set it as JAVA_OPTS argument.

 sh wso2server.sh
 -javaagent:/Users/krishantha/xxx/agent/jacocoagent.jar=destfile=/Users/krishantha/xxx/target/jacoco.exec,append=true
 -* Not working*

 export
 JAVA_OPTS=-javaagent:/Users/krishantha/xxx/agent/jacocoagent.jar=destfile=/Users/krishantha/xxx/target/jacoco.exec,append=true
 sh wso2sever.sh - *Works*

 Is there any other way to achieve this without editing the shell script
 or exporting JAVA_OPTS. Since this a VM argument doesn't it need to be
 supported though command line ?

 Thanks,
 Krishantha.
 --
 Krishantha Samaraweera
 Senior Technical Lead - Test Automation
 Mobile: +94 77 7759918
 WSO2, Inc.; http://wso2.com/
 lean . enterprise . middlewear.




 --
 Krishantha Samaraweera
 Senior Technical Lead - Test Automation
 Mobile: +94 77 7759918
 WSO2, Inc.; http://wso2.com/
 lean . enterprise . middlewear.

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




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

 phone: +94 71 668 4620






-- 
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to assign java agent to carbon servers

2015-04-29 Thread Krishantha Samaraweera

On Thu, Apr 30, 2015 at 1:31 AM, Krishantha Samaraweera krishan...@wso2.com
 wrote:

 Hi all,

 I'm trying to assign Jacoco (code coverage) java agent to our products and
 found it's not OOB supported though command line. So I had to edit the
 wso2server.sh and set it as JAVA_OPTS argument.

 sh wso2server.sh
 -javaagent:/Users/krishantha/xxx/agent/jacocoagent.jar=destfile=/Users/krishantha/xxx/target/jacoco.exec,append=true
 -* Not working*

 export
 JAVA_OPTS=-javaagent:/Users/krishantha/xxx/agent/jacocoagent.jar=destfile=/Users/krishantha/xxx/target/jacoco.exec,append=true
 sh wso2sever.sh - *Works*

 Is there any other way to achieve this without editing the shell script or
 exporting JAVA_OPTS. Since this a VM argument doesn't it need to be
 supported though command line ?

 Thanks,
 Krishantha.
 --
 Krishantha Samaraweera
 Senior Technical Lead - Test Automation
 Mobile: +94 77 7759918
 WSO2, Inc.; http://wso2.com/
 lean . enterprise . middlewear.




-- 
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Testing Jacoco based code coverage genration

2015-04-29 Thread Krishantha Samaraweera

Hi all,

New coverage implementation using Jacoco has been committed to master
branch of carbon-platform-integration. I tried my best to adhere to
existing Emma based design and reuse same instrumentation and filters text
files. Note that this new coverage implementation was done to support for
JDK 1.7 and 1.8. We need to test the new implementation thoroughly before
the release.

I've done initial testing with AS and everything seems to work. Automation
team will start verifying coverage with products already migrated JDK 1.7.
Specially products with multiple test modules (ESB, G-Reg BPS)

Lets focus on testing following scenarios before the release.

Test Scenarios for coverage :

1. Coverage generation with patches applied.
2. Merge coverage reports in multiple test modules.
3. WebApp class coverage.
4. Coverage generation after restart and impact to coverage numbers.

To get started with Jacoco coverage :

1. Edit your test module pom and replace emma copy dependency execution
configuration with below.

execution
idcopy-emma-dependencies/id
phasecompile/phase
goals
goalcopy-dependencies/goal
/goals
configuration
outputDirectory${project.build.directory}/emma/outputDirectory
includeTypesjar/includeTypes
includeArtifactIdsemma
/includeArtifactIds
/configuration
/execution

2. Include jacoco argent as a dependency to root pom.

dependency
groupIdorg.jacoco/groupId
artifactIdorg.jacoco.agent/artifactId
version${jacoco.agent.version}/version
/dependency

jacoco.agent.version0.7.4.201502262128/jacoco.agent.version

3. Remove following system properties from surefire plugin.

emma.home${basedir}/target/emma/emma.home
emma.output${basedir}/target/emma/emma.output

You will find following log entries in console with required details to
view the report once coverage generation completed. Available report
formats are XML, HTML and CSV

INFO

Thanks,
Krishantha.

Re: [Dev] Testing Jacoco based code coverage genration

2015-04-29 Thread Krishantha Samaraweera

Correction : Step #1 configuration should be as follows.

execution
idcopy-jacoco-dependencies/id
phasecompile/phase
goals
goalcopy-dependencies/goal
/goals
configuration
outputDirectory${project.build.directory}/jacoco/outputDirectory
includeTypesjar/includeTypes
includeArtifactIdsorg.jacoco.agent/includeArtifactIds
/configuration
/execution

Thanks,
Krishantha.

On Thu, Apr 30, 2015 at 2:50 AM, Krishantha Samaraweera krishan...@wso2.com
wrote:

Hi all,

New coverage implementation using Jacoco has been committed to master
branch of carbon-platform-integration. I tried my best to adhere to
existing Emma based design and reuse same instrumentation and filters text
files. Note that this new coverage implementation was done to support for
JDK 1.7 and 1.8. We need to test the new implementation thoroughly before
the release.

I've done initial testing with AS and everything seems to work. Automation
team will start verifying coverage with products already migrated JDK 1.7.
Specially products with multiple test modules (ESB, G-Reg BPS)

Lets focus on testing following scenarios before the release.

Test Scenarios for coverage :

1. Coverage generation with patches applied.
2. Merge coverage reports in multiple test modules.
3. WebApp class coverage.
4. Coverage generation after restart and impact to coverage numbers.

To get started with Jacoco coverage :

1. Edit your test module pom and replace emma copy dependency execution
configuration with below.

2. Include jacoco argent as a dependency to root pom.

dependency
groupIdorg.jacoco/groupId
artifactIdorg.jacoco.agent/artifactId
version${jacoco.agent.version}/version
/dependency

jacoco.agent.version0.7.4.201502262128/jacoco.agent.version

3. Remove following system properties from surefire plugin.

emma.home${basedir}/target/emma/emma.home
emma.output${basedir}/target/emma/emma.output

You will find following log entries in console with required details to
view the report once coverage generation completed. Available report
formats are XML, HTML and CSV

INFO

Thanks,
Krishantha.

--
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.

Re: [Dev] Connection refused error on AM UI Integration Tests

2015-04-24 Thread Krishantha Samaraweera

On Sat, Apr 25, 2015 at 10:11 AM, Krishantha Samaraweera 
krishan...@wso2.com wrote:



 On Sat, Apr 25, 2015 at 9:09 AM, Rasika Perera rasi...@wso2.com wrote:

 According to the offline discussion I had with Krishantha, I was able to
 run the test case correctly. Followings are the concerns;

 mvn test -Dtest=TestCaseClassName is not running the test case with
 expected environment configurations. Hence you need to comment out other
 test cases in testng.xml or tesng-server-mgt.xml and execute mvn test.


  mvn test -Dtest=TestCaseClassName works only if you use include and
 exclude test case name pattern in surefire plugin. All integration tests
 are configured and managed though testng.xml as below in surefire.

  suiteXmlFiles
  suiteXmlFilesrc/test/resources/testng1.xml/suiteXmlFile
  suiteXmlFilesrc/test/resources/testng2.xml/suiteXmlFile
  /suiteXmlFiles

 The command you have tried will never execute any tests.


Note that this is the default behaviour of TestNG and Surefire.

Thanks,
Krishantha.


 Thanks,
 Krishantha.


 Further I downgraded into FF v.24.

 Thank you,
 Rasika

 On Mon, Apr 20, 2015 at 8:08 PM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 This seems to be firefox and selenium incompatibility issue. Can you try
 out with Firefox 21

 You can set the -Dwebdriver.firefox.bin=/path/to/firefox/binary property
 in order to set the selenium to use a different version of Firefox in your
 machine.

 e.g. mvn clean install
 -Dwebdriver.firefox.bin=/home/host/software/firefox/firefox-bin

 Thanks,

 Krishantha.

 On Mon, Apr 20, 2015 at 8:00 PM, Rasika Perera rasi...@wso2.com wrote:

 Hi Krishantha,

 Herewith attached the `automation.log`. I ran surefire plugin with
 debug mode. Complete terminal output is also attached.

 [2015-04-20 19:00:48,001]  INFO
 {org.wso2.carbon.automation.api.clients.authenticators.AuthenticatorClient}
 -  Login Successful
 [2015-04-20 19:00:48,007]  INFO
 {org.wso2.carbon.automation.core.BrowserManager} -  Test runs on
 firefoxbrowser
 org.openqa.selenium.firefox.NotConnectedException: Unable to connect to
 host 127.0.0.1 on port 7055 after 45000 ms.

 I am using firefox 36. When checking on
 Preferences-AddOns-Extensions-FireFox WebDriver v2.31 it was disabled
 mentioning This is incompatible with Firefox 36.

 Then I looked into selenium version on test automation pom.xml, and it
 was 2.37. Recommended FF version for this was FF v.24[1].

 Then downloaded FF v.24. Still couldn't get into it. It is redirecting
 to the correct publisher url but prompting security certificate exception
 infinitely(adding exception doesn't work).

 [1]. https://code.google.com/p/selenium/issues/detail?id=6780


 On Mon, Apr 20, 2015 at 11:43 AM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 Hi Rasika,

 Can you send the full automation log which is at
 /target/log/automation.log

 Did you debug the test case ? its seems admin user cannot login to the
 server, please check whether your server is started properly.

 Thanks,
 Krishantha.

 On Mon, Apr 20, 2015 at 11:29 AM, Rasika Perera rasi...@wso2.com
 wrote:

 Hi all,

 I am writing a test case[1] for ui integration in APIM. When running
 the test case, I am getting a connection refused error[2]. Any idea what
 could possibly go wrong?

 [1] TestCase.java
 public class TestCase  extends AMIntegrationUiTestBase{
   private WebDriver driver;
   private String baseUrl;
   private boolean acceptNextAlert = true;
   private StringBuffer verificationErrors = new StringBuffer();
   private WebDriverWait wait;

   @BeforeClass(alwaysRun = true)
   public void init() throws Exception {
 super.init(0);
 driver = BrowserManager.getWebDriver();
 wait = new WebDriverWait(driver, 60);
   }

   @Test(groups = wso2.am, description = Check for functionality
 A)
   public void testFunctionalityA() throws Exception {
 
 
 //
   }

   @AfterClass(alwaysRun = true)
   public void tearDown() throws Exception {
   if (driver != null) {
   driver.quit();
   }
   super.cleanup();
}

 [2] Error Log

 org.apache.axis2.AxisFault: Connection refused
 at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
 at
 org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:197)
 at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
 at
 org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:450)
 at
 org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:277)
 at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:443)
 at
 org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:406)
 at
 org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
 at
 org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
 at
 org.wso2

Re: [Dev] Connection refused error on AM UI Integration Tests

2015-04-24 Thread Krishantha Samaraweera

On Sat, Apr 25, 2015 at 9:09 AM, Rasika Perera rasi...@wso2.com wrote:

 According to the offline discussion I had with Krishantha, I was able to
 run the test case correctly. Followings are the concerns;

 mvn test -Dtest=TestCaseClassName is not running the test case with
 expected environment configurations. Hence you need to comment out other
 test cases in testng.xml or tesng-server-mgt.xml and execute mvn test.


 mvn test -Dtest=TestCaseClassName works only if you use include and
exclude test case name pattern in surefire plugin. All integration tests
are configured and managed though testng.xml as below in surefire.

 suiteXmlFiles
 suiteXmlFilesrc/test/resources/testng1.xml/suiteXmlFile
 suiteXmlFilesrc/test/resources/testng2.xml/suiteXmlFile
 /suiteXmlFiles

The command you have tried will never execute any tests.

Thanks,
Krishantha.


 Further I downgraded into FF v.24.

 Thank you,
 Rasika

 On Mon, Apr 20, 2015 at 8:08 PM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 This seems to be firefox and selenium incompatibility issue. Can you try
 out with Firefox 21

 You can set the -Dwebdriver.firefox.bin=/path/to/firefox/binary property
 in order to set the selenium to use a different version of Firefox in your
 machine.

 e.g. mvn clean install
 -Dwebdriver.firefox.bin=/home/host/software/firefox/firefox-bin

 Thanks,

 Krishantha.

 On Mon, Apr 20, 2015 at 8:00 PM, Rasika Perera rasi...@wso2.com wrote:

 Hi Krishantha,

 Herewith attached the `automation.log`. I ran surefire plugin with debug
 mode. Complete terminal output is also attached.

 [2015-04-20 19:00:48,001]  INFO
 {org.wso2.carbon.automation.api.clients.authenticators.AuthenticatorClient}
 -  Login Successful
 [2015-04-20 19:00:48,007]  INFO
 {org.wso2.carbon.automation.core.BrowserManager} -  Test runs on
 firefoxbrowser
 org.openqa.selenium.firefox.NotConnectedException: Unable to connect to
 host 127.0.0.1 on port 7055 after 45000 ms.

 I am using firefox 36. When checking on
 Preferences-AddOns-Extensions-FireFox WebDriver v2.31 it was disabled
 mentioning This is incompatible with Firefox 36.

 Then I looked into selenium version on test automation pom.xml, and it
 was 2.37. Recommended FF version for this was FF v.24[1].

 Then downloaded FF v.24. Still couldn't get into it. It is redirecting
 to the correct publisher url but prompting security certificate exception
 infinitely(adding exception doesn't work).

 [1]. https://code.google.com/p/selenium/issues/detail?id=6780


 On Mon, Apr 20, 2015 at 11:43 AM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 Hi Rasika,

 Can you send the full automation log which is at
 /target/log/automation.log

 Did you debug the test case ? its seems admin user cannot login to the
 server, please check whether your server is started properly.

 Thanks,
 Krishantha.

 On Mon, Apr 20, 2015 at 11:29 AM, Rasika Perera rasi...@wso2.com
 wrote:

 Hi all,

 I am writing a test case[1] for ui integration in APIM. When running
 the test case, I am getting a connection refused error[2]. Any idea what
 could possibly go wrong?

 [1] TestCase.java
 public class TestCase  extends AMIntegrationUiTestBase{
   private WebDriver driver;
   private String baseUrl;
   private boolean acceptNextAlert = true;
   private StringBuffer verificationErrors = new StringBuffer();
   private WebDriverWait wait;

   @BeforeClass(alwaysRun = true)
   public void init() throws Exception {
 super.init(0);
 driver = BrowserManager.getWebDriver();
 wait = new WebDriverWait(driver, 60);
   }

   @Test(groups = wso2.am, description = Check for functionality
 A)
   public void testFunctionalityA() throws Exception {
 
 
 //
   }

   @AfterClass(alwaysRun = true)
   public void tearDown() throws Exception {
   if (driver != null) {
   driver.quit();
   }
   super.cleanup();
}

 [2] Error Log

 org.apache.axis2.AxisFault: Connection refused
 at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
 at
 org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:197)
 at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
 at
 org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:450)
 at
 org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:277)
 at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:443)
 at
 org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:406)
 at
 org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
 at
 org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
 at
 org.wso2.carbon.authenticator.stub.AuthenticationAdminStub.login(AuthenticationAdminStub.java:659)
 at
 org.wso2.carbon.automation.api.clients.authenticators.AuthenticatorClient.login(AuthenticatorClient.java:59

Re: [Dev] How to change configuration file and run the integration tests?

Oder of method execution as follows.
Running TestSuite
BeforeMethod G1
test1()
test2()
AfterMethod G1

BeforeMethod G2
test1()
test2()
BeforeMethod G2

Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.593 sec

On Thu, Apr 23, 2015 at 11:38 AM, Krishantha Samaraweera 
krishan...@wso2.com wrote:

 Hi Sinthuja,

 As mentioned by Saneth you can use ServerConfigurationManager class to
 configure server.

 To execute same set of tests with different configuration you can use
 TestNG groups. Please see the example code below. You need to define two
 test blocks in testng.xml and execute each group separately.


 public class MainGroupClass {

 @BeforeTest(groups = {g1}, alwaysRun = false)
 public void setUpG1() {
 //configuration goes here
 sleep();
 System.out.println(BeforeMethod G1);
 }

 @AfterTest(groups = {g1}, alwaysRun = false)
 public void tearDownG1() {
 //revert configuration
 sleep();
 System.out.println(AfterMethod G1);
 }

 @BeforeTest(groups = {g2}, alwaysRun = false)
 public void setUpG2() {
 //configuration goes here
 sleep();
 System.out.println(BeforeMethod G2);
 }

 @AfterTest(groups = {g2}, alwaysRun = false)
 public void tearDownG2() {
 //revert Configuration
 sleep();
 System.out.println(BeforeMethod G2);
 }

 private void sleep() {
 try {
 Thread.sleep(500);
 } catch (InterruptedException e) {
 e.printStackTrace();
 }
 }

 }


 

 public class BeforeTestGroups {

 @Test(groups = {g1, g2})
 public void test1(){
 sleep();
 System.out.println(test1());
 }

 @Test(groups = {g1, g2})
 public void test2(){
 sleep();
 System.out.println(test2());
 }

 private void sleep(){
 try {
 Thread.sleep(500);
 } catch (InterruptedException ignored) {

 }
 }
 }


 ===

 suite name=Suite1 verbose=1 

 test name=TestG1
 groups
 run
 include name=g1/
 /run
 /groups

 classes
 class name=org.wso2.carbon.tests.BeforeTestGroups/
 class name=org.wso2.carbon.tests.MainGroupClass/
 /classes
 /test

 test name=TestG2
 groups
 run
 include name=g2/
 /run
 /groups

 classes
 class name=org.wso2.carbon.tests.BeforeTestGroups/
 class name=org.wso2.carbon.tests.MainGroupClass/
 /classes
 /test

 /suite

 ===


 Thanks,
 Krishantha.


 On Thu, Apr 23, 2015 at 8:03 AM, Saneth Dharmakeerthi sane...@wso2.com
 wrote:

 Hi Sinthuja,

 a)You can change the configuration by using
 applyConfigurationWithoutRestart()  methods in
 org.wso2.carbon.integration.common.utils.mgt.ServerConfigurationManager.java.
 For sample usage of ServerConfigurationManager [1] . You have to restart
 the server  like in the sample [1] to get the configaration to apply.

 b) I am not clear about your 2nd requirement, Do you want to run the same
 test case with 2 different configarations?

 [1]
 https://github.com/wso2/product-apim/blob/master/modules/integration/tests-integration/tests-backend/src/test/java/org/wso2/am/integration/tests/api/lifecycle/APIManagerConfigurationChangeTest.java


 Thanks and Best Regards,

 Saneth Dharmakeerthi
 Senior Software Engineer
 WSO2, Inc.
 Mobile: +94772325511

 On Wed, Apr 22, 2015 at 7:32 PM, Sinthuja Ragendran sinth...@wso2.com
 wrote:

 Hi QAA team,

 I have a requirement in DAS integration test to change a configuration
 file and run the whole integration tests again.

 Basically in DAS we have a core API which can run in LOCAL mode by using
 osgi services, and REMOTE mode by connecting to a remote services in a
 distributed setup. By default this configuration is LOCAL, and hence it
 just uses the osgi services. But I need to tests the REMOTE functionality
 as well by changing the configuration to REMOTE and point to localhost. And
 currently the file is loaded only in the server start up, therefore
 configuration fi. And I would prefer all the tests to be executed in both
 modes to make sure functionality.

 How can I achieve my requirement? Please advice.

 Thanks,
 Sinthuja.

 --
 *Sinthuja Rajendran*
 Senior Software Engineer http://wso2.com/
 WSO2, Inc.:http://wso2.com

 Blog: http://sinthu-rajan.blogspot.com/
 Mobile: +94774273955



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





 --
 Krishantha Samaraweera
 Senior Technical Lead - Test Automation
 Mobile: +94 77 7759918
 WSO2, Inc.; http://wso2.com/
 lean . enterprise . middlewear.




-- 
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise

Re: [Dev] How to change configuration file and run the integration tests?

Hi Sinthuja,

As mentioned by Saneth you can use ServerConfigurationManager class to
configure server.

To execute same set of tests with different configuration you can use
TestNG groups. Please see the example code below. You need to define two
test blocks in testng.xml and execute each group separately.


public class MainGroupClass {

@BeforeTest(groups = {g1}, alwaysRun = false)
public void setUpG1() {
//configuration goes here
sleep();
System.out.println(BeforeMethod G1);
}

@AfterTest(groups = {g1}, alwaysRun = false)
public void tearDownG1() {
//revert configuration
sleep();
System.out.println(AfterMethod G1);
}

@BeforeTest(groups = {g2}, alwaysRun = false)
public void setUpG2() {
//configuration goes here
sleep();
System.out.println(BeforeMethod G2);
}

@AfterTest(groups = {g2}, alwaysRun = false)
public void tearDownG2() {
//revert Configuration
sleep();
System.out.println(BeforeMethod G2);
}

private void sleep() {
try {
Thread.sleep(500);
} catch (InterruptedException e) {
e.printStackTrace();
}
}

}




public class BeforeTestGroups {

@Test(groups = {g1, g2})
public void test1(){
sleep();
System.out.println(test1());
}

@Test(groups = {g1, g2})
public void test2(){
sleep();
System.out.println(test2());
}

private void sleep(){
try {
Thread.sleep(500);
} catch (InterruptedException ignored) {

}
}
}


===

suite name=Suite1 verbose=1 

test name=TestG1
groups
run
include name=g1/
/run
/groups

classes
class name=org.wso2.carbon.tests.BeforeTestGroups/
class name=org.wso2.carbon.tests.MainGroupClass/
/classes
/test

test name=TestG2
groups
run
include name=g2/
/run
/groups

classes
class name=org.wso2.carbon.tests.BeforeTestGroups/
class name=org.wso2.carbon.tests.MainGroupClass/
/classes
/test

/suite

===


Thanks,
Krishantha.


On Thu, Apr 23, 2015 at 8:03 AM, Saneth Dharmakeerthi sane...@wso2.com
wrote:

 Hi Sinthuja,

 a)You can change the configuration by using
 applyConfigurationWithoutRestart()  methods in
 org.wso2.carbon.integration.common.utils.mgt.ServerConfigurationManager.java.
 For sample usage of ServerConfigurationManager [1] . You have to restart
 the server  like in the sample [1] to get the configaration to apply.

 b) I am not clear about your 2nd requirement, Do you want to run the same
 test case with 2 different configarations?

 [1]
 https://github.com/wso2/product-apim/blob/master/modules/integration/tests-integration/tests-backend/src/test/java/org/wso2/am/integration/tests/api/lifecycle/APIManagerConfigurationChangeTest.java


 Thanks and Best Regards,

 Saneth Dharmakeerthi
 Senior Software Engineer
 WSO2, Inc.
 Mobile: +94772325511

 On Wed, Apr 22, 2015 at 7:32 PM, Sinthuja Ragendran sinth...@wso2.com
 wrote:

 Hi QAA team,

 I have a requirement in DAS integration test to change a configuration
 file and run the whole integration tests again.

 Basically in DAS we have a core API which can run in LOCAL mode by using
 osgi services, and REMOTE mode by connecting to a remote services in a
 distributed setup. By default this configuration is LOCAL, and hence it
 just uses the osgi services. But I need to tests the REMOTE functionality
 as well by changing the configuration to REMOTE and point to localhost. And
 currently the file is loaded only in the server start up, therefore
 configuration fi. And I would prefer all the tests to be executed in both
 modes to make sure functionality.

 How can I achieve my requirement? Please advice.

 Thanks,
 Sinthuja.

 --
 *Sinthuja Rajendran*
 Senior Software Engineer http://wso2.com/
 WSO2, Inc.:http://wso2.com

 Blog: http://sinthu-rajan.blogspot.com/
 Mobile: +94774273955



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





-- 
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] APIM ui integration tests

On Thu, Apr 23, 2015 at 11:39 AM, Lakshman Udayakantha lakshm...@wso2.com
wrote:

 Hi Krishantha,

 How we can give a custom page in there. could you point me to an example?


Don't have example bit of RD but should be able to achieve. One option to
host webapp on tomcat server.

Thanks,
Krishantha.


 Thanks

 On Wed, Apr 22, 2015 at 4:32 PM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 Hi Lakshman,

 On Wed, Apr 22, 2015 at 4:11 PM, Lakshman Udayakantha lakshm...@wso2.com
  wrote:

 Hi Irham,

 in APIMANAGER3272ExternalLogoutPageTestCase, We have to give a custom
 logout page url. I put it in the comment.


 How can we ensure test case runs OOB without any human interaction. Need
 to provide logout URL properly and update the test.

 Thanks,
 Krishantha.


 Thanks

 On Wed, Apr 22, 2015 at 1:16 PM, Saneth Dharmakeerthi sane...@wso2.com
 wrote:

 Hi Irham,

 About YouTubeUIPagesTestCase failure,

 Check whether *apiAccessInfo.getAccessToken() *passing the correct
 access token.
  If the access token is different or empty, check the logic inside  
 doSubscribe()
 method in  org.wso2.am.integration.ui.tests.pages.store.StoreHomePage.java
 class.

 testAPIPage.testAPI(apiAccessInfo.getAccessURL() + API_METHOD, 
 *apiAccessInfo.getAccessToken()*);
 //Test response body
 assertTrue(testAPIPage.getTestResponseBody().contains(RESPONSE_BODY_TEST_STRING),
  RESPONSE_BODY_TEST_STRING +  should be in the respond body);




 Thanks and Best Regards,

 Saneth Dharmakeerthi
 Senior Software Engineer
 WSO2, Inc.
 Mobile: +94772325511

 On Wed, Apr 22, 2015 at 12:39 PM, Irham Iqbal iq...@wso2.com wrote:


 Hi,

 Currently I am fixing the following APIM UI integration tests failures.

 Results :

 Tests run: 26, Failures: 9, Errors: 0, Skipped: 1

 When i go through the code i found the following lines which may
 causing the test failures.

 APIMANAGER3272ExternalLogoutPageTestCase


- Getting an 404 when try to access
https://localhost:9443/store/site/pages/login.jag.
- In the code variable externalLogoutPage has assigned custom
logout page url.


 APIMANAGER3344ScopeSpecificTokenTestCase


- Searching Select Scopes link inside My Subscriptions page in the
store but i don't see any select scope link in that page.


 APIMANAGER3363StoreAPIConsoleWithReverseProxy


- When click on API Console tag getting an exception in log and
also bellowing exception under that tag - 500 : undefined

 https://localhost:9443/store/api-docs/admin%40apimanager3363.com/APIMANAGER3363/1.0.0
.


 APIMANAGER3366MultipleGatewayPublishTestCase

- In the publisher when adding the API in the manage state it's
expecting input.env css selector  but it's not in that page.


 APIMANAGER3371BusinessInformationClearedWhenAPISavedButton

- In the publisher when adding the API in the manage state it's
try to click on xpath //form[@id='manage_form']/fieldset[3]/legend
but it's not in that page.


 APIMANAGER3412DifferentRegistryContextPath


- In the publisher when adding the API in the design state it's
try to find a element by id jsonform-0-elt-production_endpoints but
it's not in that page.


 APIVersoinStatTestCase


- In the publisher in the all API page when it's empty it's trying
to find versionTxt by id but it's not in that page.


 TestNameLengthTestCase


- When running this test alone it's working. Some other test/tests
might be the reason of failure of this test case.


 YouTubeUIPagesTestCase

- testAPIPage.getTestResponseBody() gives ams:fault xmlns:ams=

 http://wso2.org/apimanager/security;ams:code900902/ams:codeams:messageMissing
Credentials/ams:messageams:descriptionRequired OAuth credentials 
 not
provided. Make sure your API invocation call has a header: 
 Authorization:
Bearer ACCESS_TOKEN/ams:description/ams:fault

 Thanks,
 Iqbal
 --
 Irham Iqbal
 Software Engineer - Test Automation
 WSO2, Inc.: http://wso2.com
 lean. enterprise. middleware
 phone: +94 777888452

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



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




 --
 Lakshman Udayakantha
 WSO2 Inc. www.wso2.com
 lean.enterprise.middleware
 Mobile: *0711241005 0711241005*


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




 --
 Krishantha Samaraweera
 Senior Technical Lead - Test Automation
 Mobile: +94 77 7759918
 WSO2, Inc.; http://wso2.com/
 lean . enterprise . middlewear.




 --
 Lakshman Udayakantha
 WSO2 Inc. www.wso2.com
 lean.enterprise.middleware
 Mobile: *0711241005 0711241005*




-- 
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear

Re: [Dev] Test case failure in AS

Please make sure to enable integration module which is commented ATM in
java8support branch.

Thanks,
Krishantha.

On Thu, Apr 23, 2015 at 11:54 AM, Waruna Perera waru...@wso2.com wrote:

 Hi Supun,

 Can you look at following which I came across running AS test cases for
 coverage  stats.

 java.lang.AssertionError: Unsatisfied components detected in server
 startup. [org.wso2.carbon.deployment.synchronizer.XXX] expected:0 but
 was:1 at
 org.wso2.carbon.integration.common.tests.OSGIServerBundleStatusTest.testOSGIUnsatisfiedComponents(OSGIServerBundleStatusTest.java:80)
 at
 org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:295)
 at
 org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:84)
 at
 org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:90)
 at
 org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
 at
 org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
 at
 org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
 ... Removed 26 stack frames

 org.wso2.carbon.deployment.synchronizer is in a unsatisfied state.

 Thanks,

 Waruna

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




-- 
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] APIM ui integration tests

2015-04-22 Thread Krishantha Samaraweera

Hi Lakshman,

On Wed, Apr 22, 2015 at 4:11 PM, Lakshman Udayakantha lakshm...@wso2.com
wrote:

 Hi Irham,

 in APIMANAGER3272ExternalLogoutPageTestCase, We have to give a custom
 logout page url. I put it in the comment.


How can we ensure test case runs OOB without any human interaction. Need to
provide logout URL properly and update the test.

Thanks,
Krishantha.


 Thanks

 On Wed, Apr 22, 2015 at 1:16 PM, Saneth Dharmakeerthi sane...@wso2.com
 wrote:

 Hi Irham,

 About YouTubeUIPagesTestCase failure,

 Check whether *apiAccessInfo.getAccessToken() *passing the correct
 access token.
  If the access token is different or empty, check the logic inside  
 doSubscribe()
 method in  org.wso2.am.integration.ui.tests.pages.store.StoreHomePage.java
 class.

 testAPIPage.testAPI(apiAccessInfo.getAccessURL() + API_METHOD, 
 *apiAccessInfo.getAccessToken()*);
 //Test response body
 assertTrue(testAPIPage.getTestResponseBody().contains(RESPONSE_BODY_TEST_STRING),
  RESPONSE_BODY_TEST_STRING +  should be in the respond body);




 Thanks and Best Regards,

 Saneth Dharmakeerthi
 Senior Software Engineer
 WSO2, Inc.
 Mobile: +94772325511

 On Wed, Apr 22, 2015 at 12:39 PM, Irham Iqbal iq...@wso2.com wrote:


 Hi,

 Currently I am fixing the following APIM UI integration tests failures.

 Results :

 Tests run: 26, Failures: 9, Errors: 0, Skipped: 1

 When i go through the code i found the following lines which may causing
 the test failures.

 APIMANAGER3272ExternalLogoutPageTestCase


- Getting an 404 when try to access
https://localhost:9443/store/site/pages/login.jag.
- In the code variable externalLogoutPage has assigned custom
logout page url.


 APIMANAGER3344ScopeSpecificTokenTestCase


- Searching Select Scopes link inside My Subscriptions page in the
store but i don't see any select scope link in that page.


 APIMANAGER3363StoreAPIConsoleWithReverseProxy


- When click on API Console tag getting an exception in log and also
bellowing exception under that tag - 500 : undefined

 https://localhost:9443/store/api-docs/admin%40apimanager3363.com/APIMANAGER3363/1.0.0
.


 APIMANAGER3366MultipleGatewayPublishTestCase

- In the publisher when adding the API in the manage state it's
expecting input.env css selector  but it's not in that page.


 APIMANAGER3371BusinessInformationClearedWhenAPISavedButton

- In the publisher when adding the API in the manage state it's try
to click on xpath //form[@id='manage_form']/fieldset[3]/legend  but
it's not in that page.


 APIMANAGER3412DifferentRegistryContextPath


- In the publisher when adding the API in the design state it's try
to find a element by id jsonform-0-elt-production_endpoints but it's
not in that page.


 APIVersoinStatTestCase


- In the publisher in the all API page when it's empty it's trying
to find versionTxt by id but it's not in that page.


 TestNameLengthTestCase


- When running this test alone it's working. Some other test/tests
might be the reason of failure of this test case.


 YouTubeUIPagesTestCase

- testAPIPage.getTestResponseBody() gives ams:fault xmlns:ams=

 http://wso2.org/apimanager/security;ams:code900902/ams:codeams:messageMissing
Credentials/ams:messageams:descriptionRequired OAuth credentials not
provided. Make sure your API invocation call has a header: 
 Authorization:
Bearer ACCESS_TOKEN/ams:description/ams:fault

 Thanks,
 Iqbal
 --
 Irham Iqbal
 Software Engineer - Test Automation
 WSO2, Inc.: http://wso2.com
 lean. enterprise. middleware
 phone: +94 777888452

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



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




 --
 Lakshman Udayakantha
 WSO2 Inc. www.wso2.com
 lean.enterprise.middleware
 Mobile: *0711241005 0711241005*


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




-- 
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] App Manager Integration tests are broken

2015-04-21 Thread Krishantha Samaraweera

Hi App Manager team,

Ui integration tests are broken heavily.

When running the UI tests more than 15 firefox instances get created. This
directly affect to test performance.  Can you arrange a review with
Automation team after fixing failures.

Also backend test module is excluded from build [1].  Aren't you guys add
test cases for new features ?

Failed tests:
init(org.wso2.carbon.appmanager.integration.ui.TestCases.SAMLtoBackendTestCase):
Change state failed

destroy(org.wso2.carbon.appmanager.integration.ui.TestCases.SAMLtoBackendTestCase)

init(org.wso2.carbon.appmanager.integration.ui.TestCases.JWTGenerationTestCase):
Change state failed

destroy(org.wso2.carbon.appmanager.integration.ui.TestCases.JWTGenerationTestCase)

init(org.wso2.carbon.appmanager.integration.ui.TestCases.ResourceAuthXCMLTestCase):
Change state failed

destroy(org.wso2.carbon.appmanager.integration.ui.TestCases.ResourceAuthXCMLTestCase)

init(org.wso2.carbon.appmanager.integration.ui.TestCases.ThrottlingTestCase):
Change state failed

destroy(org.wso2.carbon.appmanager.integration.ui.TestCases.ThrottlingTestCase)
  init(org.wso2.carbon.appmanager.integration.ui.TestCases.TagsTestCase):
Change state failed

init(org.wso2.carbon.appmanager.integration.ui.TestCases.ResourceAuthRolesTestCase):
Change state failed

destroy(org.wso2.carbon.appmanager.integration.ui.TestCases.ResourceAuthRolesTestCase)

init(org.wso2.carbon.appmanager.integration.ui.TestCases.LifeCycleTestCase):
Change state failed

destroy(org.wso2.carbon.appmanager.integration.ui.TestCases.LifeCycleTestCase)

testApplicationDeletion(org.wso2.carbon.appmanager.integration.ui.TestCases.AppDeleteTestCase):
App deletion failed

testSelfSignUp(org.wso2.carbon.appmanager.integration.ui.TestCases.SelfSignUpTestCase):
Timed out after 30 seconds waiting for visibility of element located by
By.id: inp-username(..)

init(org.wso2.carbon.appmanager.integration.ui.TestCases.DocumentTestCase):
Change state failed

init(org.wso2.carbon.appmanager.integration.ui.TestCases.GoogleAnalyticsTestCase):
Change state failed
  init(org.wso2.carbon.appmanager.integration.ui.TestCases.RatingTestCase):
Change state failed

*Tests run: 36, Failures: 18, Errors: 0, Skipped: 16*

[1]
https://github.com/wso2/product-app-manager/blob/master/modules/integration/tests/pom.xml

Thanks,
Krishantha.
-- 
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Enterprise Store - UI test failures

More test failures in tests-ui module.

Failed tests:
testESPublishToStore(org.wso2.es.ui.integration.test.common.ESPublishToStore):
Timed out after 30 seconds waiting for presence of element located by:
By.linkText: Add gadget(..)

setUp(org.wso2.es.ui.integration.test.notifications.ESPublisherNotificationTestCase):
Timed out after 30 seconds waiting for presence of element located by:
By.linkText: Add gadget(..)

tearDown(org.wso2.es.ui.integration.test.notifications.ESPublisherNotificationTestCase)

testAddAsset(org.wso2.es.ui.integration.test.publisher.ESPublisherTenantAddEditAssetTestCase):
Timed out after 30 seconds waiting for presence of element located by:
By.linkText: Add gadget(..)

testAddAsset(org.wso2.es.ui.integration.test.publisher.ESPublisherTenantAddEditAssetTestCase):
Timed out after 30 seconds waiting for presence of element located by:
By.linkText: Add gadget(..)

testSubscriptionCreation(org.wso2.es.ui.integration.test.notifications.ESPublisherSubscriptionTestCase):
Timed out after 30 seconds waiting for presence of element located by:
By.linkText: Add gadget(..)

testSubscriptionCreation(org.wso2.es.ui.integration.test.notifications.ESPublisherSubscriptionTestCase):
Timed out after 30 seconds waiting for presence of element located by:
By.linkText: Add gadget(..)

setUp(org.wso2.es.ui.integration.test.notifications.ESPublisherTenantNotificationTestCase):
Timed out after 30 seconds waiting for presence of element located by:
By.linkText: Add gadget(..)

setUp(org.wso2.es.ui.integration.test.store.ESStoreAnonCategorySortingTestCase):
Timed out after 30 seconds waiting for presence of element located by:
By.linkText: Add gadget(..)

tearDown(org.wso2.es.ui.integration.test.notifications.ESPublisherTenantNotificationTestCase)

testAnonHomePage(org.wso2.es.ui.integration.test.store.ESStoreAnonHomePageTestCase):
Timed out after 30 seconds waiting for presence of element located by:
By.selector: div.span3.store-right  div.row  div.span3(..)

testAnonNavigationLinks(org.wso2.es.ui.integration.test.store.ESStoreAnonHomePageTestCase):
Recent Gadgets link not working expected [Stacked Line Chart] but found
[Line Chart]

testSubscriptionCreation(org.wso2.es.ui.integration.test.notifications.ESPublisherTenantSubscriptionTestCase):
Timed out after 30 seconds waiting for presence of element located by:
By.linkText: Add gadget(..)

testSubscriptionCreation(org.wso2.es.ui.integration.test.notifications.ESPublisherTenantSubscriptionTestCase):
Timed out after 30 seconds waiting for presence of element located by:
By.linkText: Add gadget(..)

testAnonHomePage(org.wso2.es.ui.integration.test.store.ESStoreAnonSuperTenantHomePageTestCase):
Timed out after 30 seconds waiting for presence of element located by:
By.selector: div.span3.store-right  div.row  div.span3(..)

testAnonNavigationLinks(org.wso2.es.ui.integration.test.store.ESStoreAnonSuperTenantHomePageTestCase):
Recent Gadgets link not working expected [Stacked Line Chart] but found
[Line Chart]

testAddAsset(org.wso2.es.ui.integration.test.publisher.ESPublisherAddEditAssetTestCase):
Timed out after 30 seconds waiting for presence of element located by:
By.linkText: Add gadget(..)

testAddAsset(org.wso2.es.ui.integration.test.publisher.ESPublisherAddEditAssetTestCase):
Timed out after 30 seconds waiting for presence of element located by:
By.linkText: Add gadget(..)

testESStoreBookmarkTestCase(org.wso2.es.ui.integration.test.store.ESStoreBookmarkTestCase):
Timed out after 30 seconds waiting for text ('Bookmarked') to be present in
element found by By.id: btn-add-gadget(..)

setUp(org.wso2.es.ui.integration.test.publisher.ESPublisherLCTransitionTestCase):
Timed out after 30 seconds waiting for presence of element located by:
By.linkText: Add gadget(..)

tearDown(org.wso2.es.ui.integration.test.publisher.ESPublisherLCTransitionTestCase)

testLoggedInHomePage(org.wso2.es.ui.integration.test.store.ESStoreCarbonSuperUserTUHomePageTestCase):
Timed out after 30 seconds waiting for presence of element located by:
By.selector: div.span3.store-right  div.row  div.span3(..)

testLoggedInNavigationLinks(org.wso2.es.ui.integration.test.store.ESStoreCarbonSuperUserTUHomePageTestCase):
Recent Gadgets link not working expected [Stacked Line Chart] but found
[Line Chart]

testGadgetPage(org.wso2.es.ui.integration.test.store.ESStoreGadgetPageTestCase):
Timed out after 30 seconds waiting for presence of element located by:
By.xpath: //a[contains(text(),'Line Plus Bar Chart')](..)

testAddAsset(org.wso2.es.ui.integration.test.store.ESStoreSearchGadgetListTestCase):
Timed out after 30 seconds waiting for presence of element located by:
By.linkText: Add gadget(..)

Tests run: 88, Failures: 25, Errors: 0, Skipped: 31


Thanks,
Krishantha.

On Mon, Apr 20, 2015 at 3:29 PM, Krishantha Samaraweera krishan...@wso2.com
 wrote:

 Hi all,

 I see following UI failures in master branch. Please have a look.

 Failed tests:
 testESPublisherAddedAssetTestCase(org.wso2

[Dev] Enterprise Store - UI test failures

Hi all,

I see following UI failures in master branch. Please have a look.

Failed tests:
testESPublisherAddedAssetTestCase(org.wso2.es.ui.integration.extension.test.publisher.ESPublisherAddedAssetTestCase):
Timed out after 30 seconds waiting for presence of element located by:
By.linkText: Services(..)

testESPublisherAssetCaramelPageTestCase(org.wso2.es.ui.integration.extension.test.publisher.ESPublisherAssetCaramelPageTestCase):
Timed out after 30 seconds waiting for presence of element located by:
By.linkText: Overview(..)


setUp(org.wso2.es.ui.integration.extension.test.publisher.ESPublisherAssetOverridePartialTestCase):
Timed out after 30 seconds waiting for presence of element located by:
By.linkText: Add servicex(..)


setUp(org.wso2.es.ui.integration.extension.test.publisher.ESPublisherAssetOverrideRendererTestCase):
Timed out after 30 seconds waiting for presence of element located by:
By.linkText: Add servicex(..)

*Tests run: 15, Failures: 4, Errors: 0, Skipped: 2*

Thanks,
Krishantha.

-- 
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Connection refused error on AM UI Integration Tests

This seems to be firefox and selenium incompatibility issue. Can you try
out with Firefox 21

You can set the -Dwebdriver.firefox.bin=/path/to/firefox/binary property in
order to set the selenium to use a different version of Firefox in your
machine.

e.g. mvn clean install
-Dwebdriver.firefox.bin=/home/host/software/firefox/firefox-bin

Thanks,

Krishantha.

On Mon, Apr 20, 2015 at 8:00 PM, Rasika Perera rasi...@wso2.com wrote:

 Hi Krishantha,

 Herewith attached the `automation.log`. I ran surefire plugin with debug
 mode. Complete terminal output is also attached.

 [2015-04-20 19:00:48,001]  INFO
 {org.wso2.carbon.automation.api.clients.authenticators.AuthenticatorClient}
 -  Login Successful
 [2015-04-20 19:00:48,007]  INFO
 {org.wso2.carbon.automation.core.BrowserManager} -  Test runs on
 firefoxbrowser
 org.openqa.selenium.firefox.NotConnectedException: Unable to connect to
 host 127.0.0.1 on port 7055 after 45000 ms.

 I am using firefox 36. When checking on
 Preferences-AddOns-Extensions-FireFox WebDriver v2.31 it was disabled
 mentioning This is incompatible with Firefox 36.

 Then I looked into selenium version on test automation pom.xml, and it was
 2.37. Recommended FF version for this was FF v.24[1].

 Then downloaded FF v.24. Still couldn't get into it. It is redirecting to
 the correct publisher url but prompting security certificate exception
 infinitely(adding exception doesn't work).

 [1]. https://code.google.com/p/selenium/issues/detail?id=6780


 On Mon, Apr 20, 2015 at 11:43 AM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 Hi Rasika,

 Can you send the full automation log which is at
 /target/log/automation.log

 Did you debug the test case ? its seems admin user cannot login to the
 server, please check whether your server is started properly.

 Thanks,
 Krishantha.

 On Mon, Apr 20, 2015 at 11:29 AM, Rasika Perera rasi...@wso2.com wrote:

 Hi all,

 I am writing a test case[1] for ui integration in APIM. When running
 the test case, I am getting a connection refused error[2]. Any idea what
 could possibly go wrong?

 [1] TestCase.java
 public class TestCase  extends AMIntegrationUiTestBase{
   private WebDriver driver;
   private String baseUrl;
   private boolean acceptNextAlert = true;
   private StringBuffer verificationErrors = new StringBuffer();
   private WebDriverWait wait;

   @BeforeClass(alwaysRun = true)
   public void init() throws Exception {
 super.init(0);
 driver = BrowserManager.getWebDriver();
 wait = new WebDriverWait(driver, 60);
   }

   @Test(groups = wso2.am, description = Check for functionality A)
   public void testFunctionalityA() throws Exception {
 
 
 //
   }

   @AfterClass(alwaysRun = true)
   public void tearDown() throws Exception {
   if (driver != null) {
   driver.quit();
   }
   super.cleanup();
}

 [2] Error Log

 org.apache.axis2.AxisFault: Connection refused
 at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
 at
 org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:197)
 at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
 at
 org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:450)
 at
 org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:277)
 at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:443)
 at
 org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:406)
 at
 org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
 at
 org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
 at
 org.wso2.carbon.authenticator.stub.AuthenticationAdminStub.login(AuthenticationAdminStub.java:659)
 at
 org.wso2.carbon.automation.api.clients.authenticators.AuthenticatorClient.login(AuthenticatorClient.java:59)
 at
 org.wso2.carbon.automation.core.utils.environmentutils.EnvironmentBuilder.loginSetup(EnvironmentBuilder.java:520)
 at
 org.wso2.carbon.automation.core.utils.environmentutils.EnvironmentBuilder.am
 (EnvironmentBuilder.java:453)
 at
 org.wso2.carbon.am.integration.ui.AMIntegrationUiTestBase.init(AMIntegrationUiTestBase.java:44)
 at
 org.wso2.carbon.am.integration.ui.APIMANAGER3452IncorrectMethodInfoThrottlingTab.init(
 
 TestCase
 .java:47)
 Caused by: java.net.ConnectException: Connection refused
 at java.net.PlainSocketImpl.socketConnect(Native Method)


 --
 With Regards,

 *Rasika Perera*
 Software Engineer
 M: +94 71 680 9060 E: rasi...@wso2.com
 LinkedIn: http://lk.linkedin.com/in/rasika90

 WSO2 Inc. www.wso2.com
 lean.enterprise.middleware




 --
 Krishantha Samaraweera
 Senior Technical Lead - Test Automation
 Mobile: +94 77 7759918
 WSO2, Inc.; http://wso2.com/
 lean . enterprise . middlewear.




 --
 With Regards,

 *Rasika Perera*
 Software Engineer
 M: +94 71 680 9060 E: rasi...@wso2.com
 LinkedIn: http

Re: [Dev] Connection refused error on AM UI Integration Tests