[JBoss JIRA] (ARQ-1517) QUnit extension does not distinguish between errors and failures
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/ARQ-1517?page=com.atlassian.jira.plugin.s... ]
Karel Piwko closed ARQ-1517.
----------------------------
> QUnit extension does not distinguish between errors and failures
> ----------------------------------------------------------------
>
> Key: ARQ-1517
> URL: https://issues.jboss.org/browse/ARQ-1517
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - QUnit
> Affects Versions: qunit_1.0.0.Alpha1
> Reporter: Karel Piwko
> Assignee: Tolis Emmanouilidis
> Fix For: qunit_1.0.0.Alpha2
>
>
> Suppose that assertion in QUnit test gets wrong. In such cases, it should be reported as failure, non as error.
> Tests run: 5, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 6.314 sec <<< FAILURE!
> module: Member Restful Calls test: Request current member list(com.acme.example.test.QUnitDroneTest) Time elapsed: 0.013 sec <<< ERROR!
> java.lang.Exception: Failed Initial member returned
> at org.jboss.arquillian.qunit.junit.core.QUnitJUnitReporter.report(QUnitJUnitReporter.java:135)
> at org.jboss.arquillian.qunit.junit.core.QUnitTestCase.executeQunitTestSuite(QUnitTestCase.java:107)
> at org.jboss.arquillian.qunit.junit.core.QUnitTestCase.executeQUnitTestSuites(QUnitTestCase.java:85)
> 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270)
> at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.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.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.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53)
> 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.createTestContext(ContainerEventController.java:129)
> 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.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111)
> at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263)
> at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226)
> 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.jboss.arquillian.qunit.junit.QUnitRunner.executeTests(QUnitRunner.java:95)
> at org.jboss.arquillian.qunit.junit.QUnitRunner.run(QUnitRunner.java:75)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:158)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:95)
> Results :
> Tests in error:
> » Failed Initial member returned
--
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
12 years, 6 months
[JBoss JIRA] (ARQ-1514) Exceptions are swallowed and tests are not marked as failures/errors
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/ARQ-1514?page=com.atlassian.jira.plugin.s... ]
Karel Piwko closed ARQ-1514.
----------------------------
> Exceptions are swallowed and tests are not marked as failures/errors
> --------------------------------------------------------------------
>
> Key: ARQ-1514
> URL: https://issues.jboss.org/browse/ARQ-1514
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - QUnit
> Affects Versions: qunit_1.0.0.Alpha1
> Reporter: Karel Piwko
> Assignee: Tolis Emmanouilidis
> Priority: Critical
> Fix For: qunit_1.0.0.Alpha2
>
>
> If something goes bad in Arquillian lifecycle out of test methods, like is not possible to connect Drone, QUnit will report it executed 0 tests and won't show user the exception at all.
> {code}
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.1 sec
> {code}
> QUnit should definitely output error and update tests as failure/errors in such cases.
--
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
12 years, 6 months
[JBoss JIRA] (ARQ-1500) Use nested Runner for QUnit test execution
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/ARQ-1500?page=com.atlassian.jira.plugin.s... ]
Karel Piwko reassigned ARQ-1500:
--------------------------------
Assignee: Karel Piwko
> Use nested Runner for QUnit test execution
> ------------------------------------------
>
> Key: ARQ-1500
> URL: https://issues.jboss.org/browse/ARQ-1500
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - QUnit
> Affects Versions: qunit_1.0.0.Alpha1
> Reporter: Karel Piwko
> Assignee: Karel Piwko
> Priority: Critical
> Fix For: qunit_1.0.0.Alpha2
>
>
> QUnit extension now wraps the code execution and executes QUnit methods using JUnitCore.
> However, JUnitCore creates a separate process, which:
> 1/ Prolongs the test execution
> 2/ Reduces information about current bootstrap path and classpath, leading to strange errors
> 3/ Creates another level of indirection, which is difficult to be debugged.
--
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
12 years, 6 months
[JBoss JIRA] (ARQ-1495) Support both serialId and avdName in arquillian.xml
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1495?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic resolved ARQ-1495.
------------------------------------
Resolution: Done
This issue was automatically resolved by ARQ-1511.
> Support both serialId and avdName in arquillian.xml
> ---------------------------------------------------
>
> Key: ARQ-1495
> URL: https://issues.jboss.org/browse/ARQ-1495
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
> Priority: Minor
>
> When serialId and avdName are both in arquillian.xml container configuration, try to firstly connect to physical device (according to serialId), when this fails, try to connect to avdName.
> Right now when serialId is used in connection with avdName and there is a failure to connect to physical device via serialId, the execution is aborted.
> This is not very comfortable from test execution point of view.
--
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
12 years, 6 months
[JBoss JIRA] (ARQ-1495) Support both serialId and avdName in arquillian.xml
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1495?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic updated ARQ-1495:
-----------------------------------
Fix Version/s: 1.0.0.Alpha2
> Support both serialId and avdName in arquillian.xml
> ---------------------------------------------------
>
> Key: ARQ-1495
> URL: https://issues.jboss.org/browse/ARQ-1495
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
> Priority: Minor
> Fix For: 1.0.0.Alpha2
>
>
> When serialId and avdName are both in arquillian.xml container configuration, try to firstly connect to physical device (according to serialId), when this fails, try to connect to avdName.
> Right now when serialId is used in connection with avdName and there is a failure to connect to physical device via serialId, the execution is aborted.
> This is not very comfortable from test execution point of view.
--
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
12 years, 6 months
[JBoss JIRA] (ARQ-1495) Support both serialId and avdName in arquillian.xml
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1495?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic closed ARQ-1495.
----------------------------------
> Support both serialId and avdName in arquillian.xml
> ---------------------------------------------------
>
> Key: ARQ-1495
> URL: https://issues.jboss.org/browse/ARQ-1495
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
> Priority: Minor
> Fix For: 1.0.0.Alpha2
>
>
> When serialId and avdName are both in arquillian.xml container configuration, try to firstly connect to physical device (according to serialId), when this fails, try to connect to avdName.
> Right now when serialId is used in connection with avdName and there is a failure to connect to physical device via serialId, the execution is aborted.
> This is not very comfortable from test execution point of view.
--
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
12 years, 6 months
[JBoss JIRA] (ARQ-1495) Support both serialId and avdName in arquillian.xml
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1495?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic reassigned ARQ-1495:
--------------------------------------
Assignee: Stefan Miklosovic
> Support both serialId and avdName in arquillian.xml
> ---------------------------------------------------
>
> Key: ARQ-1495
> URL: https://issues.jboss.org/browse/ARQ-1495
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
> Priority: Minor
>
> When serialId and avdName are both in arquillian.xml container configuration, try to firstly connect to physical device (according to serialId), when this fails, try to connect to avdName.
> Right now when serialId is used in connection with avdName and there is a failure to connect to physical device via serialId, the execution is aborted.
> This is not very comfortable from test execution point of view.
--
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
12 years, 6 months