[JBoss JIRA] (ARQ-1221) Create a managed DeployableContainer integration for WAS Liberty Profile V8.5.Next
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1221?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen updated ARQ-1221:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: was_1.0.0.Alpha1
Resolution: Done
> Create a managed DeployableContainer integration for WAS Liberty Profile V8.5.Next
> ----------------------------------------------------------------------------------
>
> Key: ARQ-1221
> URL: https://issues.jboss.org/browse/ARQ-1221
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: WebSphere Containers
> Reporter: Gerhard Poul
> Assignee: Gerhard Poul
> Priority: Optional
> Fix For: was_1.0.0.Alpha1
>
>
> Create a managed DeployableContainer integration for WebSphere Application Server Liberty Profile V8.5.Next. The Alpha is currently available on wasdev.net.
> This implementation should allow complete lifecycle management of the liberty profile as part of the Arquillian test. A test should be implemented testing the ejblite compatibility.
> During implementation we should also investigate whether an integration with the new Maven support in liberty profile can be used in combination with Arquillian.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (ARQ-1432) Make Warp Airplane travel friendly
by Aslak Knutsen (JIRA)
Aslak Knutsen created ARQ-1432:
----------------------------------
Summary: Make Warp Airplane travel friendly
Key: ARQ-1432
URL: https://issues.jboss.org/browse/ARQ-1432
Project: Arquillian
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Extension - Warp
Affects Versions: warp_1.0.0.Alpha3
Reporter: Aslak Knutsen
When not connected to a network Warp throws this exception:
{code}
java.net.SocketException: Unresolved address
at java.net.DatagramSocket.connect(DatagramSocket.java:477)
at org.littleshoot.proxy.NetworkUtils.getLocalHostViaUdp(NetworkUtils.java:55)
at org.littleshoot.proxy.NetworkUtils.getLocalHost(NetworkUtils.java:46)
at org.littleshoot.proxy.ProxyUtils.<clinit>(ProxyUtils.java:67)
at org.littleshoot.proxy.LittleProxyConfig.<clinit>(LittleProxyConfig.java:44)
at org.jboss.arquillian.warp.impl.client.proxy.DefaultProxyService.startProxy(DefaultProxyService.java:75)
at org.jboss.arquillian.warp.impl.client.proxy.DefaultProxyService.startProxy(DefaultProxyService.java:46)
at org.jboss.arquillian.warp.impl.client.proxy.ProxyObserver.startProxy(ProxyObserver.java:71)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
at org.jboss.arquillian.warp.impl.client.proxy.ProxyObserver.requireProxy(ProxyObserver.java:66)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
at org.jboss.arquillian.warp.impl.client.proxy.ProxyURLProvider.getProxyUrl(ProxyURLProvider.java:82)
at org.jboss.arquillian.warp.impl.client.proxy.ProxyURLProvider.lookup(ProxyURLProvider.java:71)
at org.jboss.arquillian.test.impl.enricher.resource.ArquillianResourceTestEnricher.lookup(ArquillianResourceTestEnricher.java:112)
at org.jboss.arquillian.test.impl.enricher.resource.ArquillianResourceTestEnricher.enrich(ArquillianResourceTestEnricher.java:57)
at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52)
at org.jboss.arquillian.container.test.impl.ClientTestInstanceEnricher.enrich(ClientTestInstanceEnricher.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142)
at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.before(EventTestRunnerAdaptor.java:95)
at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:222)
at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185)
at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (ARQGRA-197) Support for Page Objects encapsulating location
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-197?page=com.atlassian.jira.plugin... ]
Juraj Húska commented on ARQGRA-197:
------------------------------------
I filed another pull request, which IMHO can be merged once reviewed.
> Support for Page Objects encapsulating location
> -----------------------------------------------
>
> Key: ARQGRA-197
> URL: https://issues.jboss.org/browse/ARQGRA-197
> Project: Arquillian Graphene
> Issue Type: Feature Request
> Affects Versions: 2.0.0.Alpha2
> Reporter: Lukáš Fryč
> Assignee: Juraj Húska
> Priority: Minor
> Fix For: 2.0.0.Alpha5
>
> Original Estimate: 6 hours
> Remaining Estimate: 6 hours
>
> {code:java|title=ConferencePage.java}
> @Location("view/conference/create.jsf")
> public class ConferencePage {
>
> @FindBy(id = "create")
> private ConferenceForm form;
>
> public ConferenceForm getForm() {
> return form;
> }
> }
> public class ConferencePage implements Bookmarkable {
>
> @FindBy(id = "create")
> private ConferenceForm form;
>
> public ConferenceForm getForm() {
> return form;
> }
> public String getLocation() {
> return "view/conference/create.jsf";
> }
> }
> {code}
> {code:java|title=Test.java}
> @Test
> public void test() {
> ConferencePage page = goTo(ConferencePage.class);
> ConferenceForm = page.getForm();
> }
> {code}
> The only issue is that it is not sure on which deployment and with what browser should given Page operate.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (ARQGRA-197) Support for Page Objects encapsulating location
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-197?page=com.atlassian.jira.plugin... ]
Juraj Húska updated ARQGRA-197:
-------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/82 (was: https://github.com/arquillian/arquillian-graphene/pull/79)
> Support for Page Objects encapsulating location
> -----------------------------------------------
>
> Key: ARQGRA-197
> URL: https://issues.jboss.org/browse/ARQGRA-197
> Project: Arquillian Graphene
> Issue Type: Feature Request
> Affects Versions: 2.0.0.Alpha2
> Reporter: Lukáš Fryč
> Assignee: Juraj Húska
> Priority: Minor
> Fix For: 2.0.0.Alpha5
>
> Original Estimate: 6 hours
> Remaining Estimate: 6 hours
>
> {code:java|title=ConferencePage.java}
> @Location("view/conference/create.jsf")
> public class ConferencePage {
>
> @FindBy(id = "create")
> private ConferenceForm form;
>
> public ConferenceForm getForm() {
> return form;
> }
> }
> public class ConferencePage implements Bookmarkable {
>
> @FindBy(id = "create")
> private ConferenceForm form;
>
> public ConferenceForm getForm() {
> return form;
> }
> public String getLocation() {
> return "view/conference/create.jsf";
> }
> }
> {code}
> {code:java|title=Test.java}
> @Test
> public void test() {
> ConferencePage page = goTo(ConferencePage.class);
> ConferenceForm = page.getForm();
> }
> {code}
> The only issue is that it is not sure on which deployment and with what browser should given Page operate.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (ARQ-1282) TestNG @DataProvider is fully invoked for each record
by Vitor Moraes (JIRA)
[ https://issues.jboss.org/browse/ARQ-1282?page=com.atlassian.jira.plugin.s... ]
Vitor Moraes commented on ARQ-1282:
-----------------------------------
[~karel.cemus] thank you very much
> TestNG @DataProvider is fully invoked for each record
> -----------------------------------------------------
>
> Key: ARQ-1282
> URL: https://issues.jboss.org/browse/ARQ-1282
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JBoss AS Containers
> Affects Versions: 1.0.3.Final
> Reporter: Karel Cemus
>
> h2. Expected behavior
> TestNG defines @DataProvider annotation to allow single method to perform multiple test cases. Provider method annotated with @DataProvider returns an array of arrays, each containing one test case. These parameters are given to the target method as input parameters. By the definition, the total count of performed test by single method is equal to number of test cases in related data provider.
> h2. Actual behavior
> Using TestNG under Arquillian framework makes this functionality buggy. Although the client (maven, IDE, etc.) thinks, that the total number of invoked test is correct, it is not. When we take a look into server's log, we can see that for each single test case it invoked full set of all test cases. It means, that in the end the amount of performed tests is equal to expected count squared. Such behaviour is not only slow but also in some cases it doesn't work and it makes tests to fail.
> h2. Example
> {code:java}
> @DataProvider
> public Object[][] sumProvider() {
> return new Object[][]{
> new Object[]{ 0, 0, 0 },
> new Object[]{ 1, 1, 2 },
> new Object[]{ 1, 5, 6 },
> new Object[]{ 5, 1, 6 }
> };
> }
> {code}
> h3. Expected output in server log
> {quote}
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> {quote}
> h3. Actual output
> {quote}
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (ARQ-1282) TestNG @DataProvider is fully invoked for each record
by Karel Cemus (JIRA)
[ https://issues.jboss.org/browse/ARQ-1282?page=com.atlassian.jira.plugin.s... ]
Karel Cemus edited comment on ARQ-1282 at 7/18/13 10:04 AM:
------------------------------------------------------------
[~vitornp] I have a personal hack of this issue, if you are interested. You can look [here on GitHub|https://github.com/KarelCemus/A4M36JEE/blob/master/src/test/java/c...] and there is an [example of usage|https://github.com/KarelCemus/A4M36JEE/blob/master/src/test/java/cz...]
was (Author: karel.cemus):
[@Vitor Moraes]
> TestNG @DataProvider is fully invoked for each record
> -----------------------------------------------------
>
> Key: ARQ-1282
> URL: https://issues.jboss.org/browse/ARQ-1282
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JBoss AS Containers
> Affects Versions: 1.0.3.Final
> Reporter: Karel Cemus
>
> h2. Expected behavior
> TestNG defines @DataProvider annotation to allow single method to perform multiple test cases. Provider method annotated with @DataProvider returns an array of arrays, each containing one test case. These parameters are given to the target method as input parameters. By the definition, the total count of performed test by single method is equal to number of test cases in related data provider.
> h2. Actual behavior
> Using TestNG under Arquillian framework makes this functionality buggy. Although the client (maven, IDE, etc.) thinks, that the total number of invoked test is correct, it is not. When we take a look into server's log, we can see that for each single test case it invoked full set of all test cases. It means, that in the end the amount of performed tests is equal to expected count squared. Such behaviour is not only slow but also in some cases it doesn't work and it makes tests to fail.
> h2. Example
> {code:java}
> @DataProvider
> public Object[][] sumProvider() {
> return new Object[][]{
> new Object[]{ 0, 0, 0 },
> new Object[]{ 1, 1, 2 },
> new Object[]{ 1, 5, 6 },
> new Object[]{ 5, 1, 6 }
> };
> }
> {code}
> h3. Expected output in server log
> {quote}
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> {quote}
> h3. Actual output
> {quote}
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (ARQ-1282) TestNG @DataProvider is fully invoked for each record
by Karel Cemus (JIRA)
[ https://issues.jboss.org/browse/ARQ-1282?page=com.atlassian.jira.plugin.s... ]
Karel Cemus commented on ARQ-1282:
----------------------------------
[@Vitor Moraes]
> TestNG @DataProvider is fully invoked for each record
> -----------------------------------------------------
>
> Key: ARQ-1282
> URL: https://issues.jboss.org/browse/ARQ-1282
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JBoss AS Containers
> Affects Versions: 1.0.3.Final
> Reporter: Karel Cemus
>
> h2. Expected behavior
> TestNG defines @DataProvider annotation to allow single method to perform multiple test cases. Provider method annotated with @DataProvider returns an array of arrays, each containing one test case. These parameters are given to the target method as input parameters. By the definition, the total count of performed test by single method is equal to number of test cases in related data provider.
> h2. Actual behavior
> Using TestNG under Arquillian framework makes this functionality buggy. Although the client (maven, IDE, etc.) thinks, that the total number of invoked test is correct, it is not. When we take a look into server's log, we can see that for each single test case it invoked full set of all test cases. It means, that in the end the amount of performed tests is equal to expected count squared. Such behaviour is not only slow but also in some cases it doesn't work and it makes tests to fail.
> h2. Example
> {code:java}
> @DataProvider
> public Object[][] sumProvider() {
> return new Object[][]{
> new Object[]{ 0, 0, 0 },
> new Object[]{ 1, 1, 2 },
> new Object[]{ 1, 5, 6 },
> new Object[]{ 5, 1, 6 }
> };
> }
> {code}
> h3. Expected output in server log
> {quote}
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> {quote}
> h3. Actual output
> {quote}
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months