October 2013 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1514) Exceptions are swallowed and tests are not marked as failures/errors

by Tolis Emmanouilidis (JIRA)

[ https://issues.jboss.org/browse/ARQ-1514?page=com.atlassian.jira.plugin.s... ] Tolis Emmanouilidis resolved ARQ-1514. -------------------------------------- Fix Version/s: qunit_1.0.0.Alpha2 Resolution: Done > 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1510) Allow QUnit extension to pass deployment URL to the tests

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1510?page=com.atlassian.jira.plugin.s... ] Karel Piwko closed ARQ-1510. ---------------------------- Resolution: Rejected There is no need to do that. In javascript, you can get that information directly from browser, using: {code} window.location.host {code} > Allow QUnit extension to pass deployment URL to the tests > --------------------------------------------------------- > > Key: ARQ-1510 > URL: https://issues.jboss.org/browse/ARQ-1510 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - QUnit > Affects Versions: qunit_1.0.0.Alpha1 > Reporter: Karel Piwko > > Make possible for QUnit tests that require a deployed archive on server side to get URL of this deployment. > This should be a real advantage of bringing the tests into the container using 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-385) Unable to use Guards with AndroidDriver (again)

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-385?page=com.atlassian.jira.plugin... ] Lukáš Fryč resolved ARQGRA-385. ------------------------------- Assignee: Lukáš Fryč Resolution: Done > Unable to use Guards with AndroidDriver (again) > ----------------------------------------------- > > Key: ARQGRA-385 > URL: https://issues.jboss.org/browse/ARQGRA-385 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.0.CR1 > Environment: Selenium APK 2.32. > Reporter: Karel Piwko > Assignee: Lukáš Fryč > Priority: Critical > Fix For: 2.0.0.Final > > > It is not possible to use Guards on Android driver, it fails with following error: > {code} > java.lang.IllegalStateException: Can't invoke the javacript org.jboss.arquillian.graphene.guard.RequestGuardImpl#clearRequestDone() > at org.openqa.selenium.android.library.AndroidWebDriver.throwIfError(AndroidWebDriver.java:1024) > at org.openqa.selenium.android.library.AndroidWebDriver.executeRawScript(AndroidWebDriver.java:895) > at org.openqa.selenium.android.library.AndroidWebDriver.injectJavascript(AndroidWebDriver.java:930) > at org.openqa.selenium.android.library.AndroidWebDriver.executeScript(AndroidWebDriver.java:786) > at org.openqa.selenium.android.AndroidApkDriver.executeScript(AndroidApkDriver.java:106) > at java.lang.reflect.Method.invokeNative(Native Method) > at java.lang.reflect.Method.invoke(Method.java:511) > at org.openqa.selenium.support.events.EventFiringWebDriver$2.invoke(EventFiringWebDriver.java:101) > at $Proxy1.executeScript(Native Method) > at org.openqa.selenium.support.events.EventFiringWebDriver.executeScript(EventFiringWebDriver.java:209) > at org.openqa.selenium.remote.server.handler.ExecuteScript.call(ExecuteScript.java:55) > at org.openqa.selenium.remote.server.handler.ExecuteScript.call(ExecuteScript.java:1) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:305) > at java.util.concurrent.FutureTask.run(FutureTask.java:137) > at org.openqa.selenium.remote.server.DefaultSession$1.run(DefaultSession.java:169) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569) > at java.lang.Thread.run(Thread.java:856) > {code} > I've tested both *guardAjax(...)* and *guardNoRequest(...)* guards. > Together with ARQGRA-384, this significantly reduces usability of Graphene when combined with AndroidDriver. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-386) It should not be possible to place @InitialPage over field

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-386?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-386: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 2.0.0.Final Resolution: Done > It should not be possible to place @InitialPage over field > ---------------------------------------------------------- > > Key: ARQGRA-386 > URL: https://issues.jboss.org/browse/ARQGRA-386 > Project: Arquillian Graphene > Issue Type: Bug > Components: api > Affects Versions: 2.0.0.CR1 > Reporter: Juraj Húska > Assignee: Juraj Húska > Priority: Trivial > Fix For: 2.0.0.Final > > > {{@InitialPage}} annotation has accidentally also target: {{FIELD}}. > Currently there is no support for placing {{@InitialPage}} over field, thus it should be removed to avoid confusion. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-385) Unable to use Guards with AndroidDriver (again)

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-385?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-385: ----------------------------------- Thanks for verifying, Karel, I will merge it to master then! > Unable to use Guards with AndroidDriver (again) > ----------------------------------------------- > > Key: ARQGRA-385 > URL: https://issues.jboss.org/browse/ARQGRA-385 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.0.CR1 > Environment: Selenium APK 2.32. > Reporter: Karel Piwko > Priority: Critical > Fix For: 2.0.0.Final > > > It is not possible to use Guards on Android driver, it fails with following error: > {code} > java.lang.IllegalStateException: Can't invoke the javacript org.jboss.arquillian.graphene.guard.RequestGuardImpl#clearRequestDone() > at org.openqa.selenium.android.library.AndroidWebDriver.throwIfError(AndroidWebDriver.java:1024) > at org.openqa.selenium.android.library.AndroidWebDriver.executeRawScript(AndroidWebDriver.java:895) > at org.openqa.selenium.android.library.AndroidWebDriver.injectJavascript(AndroidWebDriver.java:930) > at org.openqa.selenium.android.library.AndroidWebDriver.executeScript(AndroidWebDriver.java:786) > at org.openqa.selenium.android.AndroidApkDriver.executeScript(AndroidApkDriver.java:106) > at java.lang.reflect.Method.invokeNative(Native Method) > at java.lang.reflect.Method.invoke(Method.java:511) > at org.openqa.selenium.support.events.EventFiringWebDriver$2.invoke(EventFiringWebDriver.java:101) > at $Proxy1.executeScript(Native Method) > at org.openqa.selenium.support.events.EventFiringWebDriver.executeScript(EventFiringWebDriver.java:209) > at org.openqa.selenium.remote.server.handler.ExecuteScript.call(ExecuteScript.java:55) > at org.openqa.selenium.remote.server.handler.ExecuteScript.call(ExecuteScript.java:1) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:305) > at java.util.concurrent.FutureTask.run(FutureTask.java:137) > at org.openqa.selenium.remote.server.DefaultSession$1.run(DefaultSession.java:169) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569) > at java.lang.Thread.run(Thread.java:856) > {code} > I've tested both *guardAjax(...)* and *guardNoRequest(...)* guards. > Together with ARQGRA-384, this significantly reduces usability of Graphene when combined with AndroidDriver. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1518) Replace arquillian-junit-container with arquiilian-junit-core dependency

by Tolis Emmanouilidis (JIRA)

[ https://issues.jboss.org/browse/ARQ-1518?page=com.atlassian.jira.plugin.s... ] Tolis Emmanouilidis commented on ARQ-1518: ------------------------------------------ https://github.com/arquillian/arquillian-extension-qunit/commit/2c46fa2a3... > Replace arquillian-junit-container with arquiilian-junit-core dependency > ------------------------------------------------------------------------ > > Key: ARQ-1518 > URL: https://issues.jboss.org/browse/ARQ-1518 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - QUnit > Reporter: Tolis Emmanouilidis > Assignee: Tolis Emmanouilidis > > Replace arquillian-junit-container with arquiilian-junit-core dependency -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1518) Replace arquillian-junit-container with arquiilian-junit-core dependency

by Tolis Emmanouilidis (JIRA)

Tolis Emmanouilidis created ARQ-1518: ---------------------------------------- Summary: Replace arquillian-junit-container with arquiilian-junit-core dependency Key: ARQ-1518 URL: https://issues.jboss.org/browse/ARQ-1518 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - QUnit Reporter: Tolis Emmanouilidis Assignee: Tolis Emmanouilidis Replace arquillian-junit-container with arquiilian-junit-core dependency -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1511) Wrong Android container identification in logs

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1511?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic updated ARQ-1511: ----------------------------------- Summary: Wrong Android container identification in logs (was: Wrong Android server identification in logs) > Wrong Android container identification in logs > ---------------------------------------------- > > Key: ARQ-1511 > URL: https://issues.jboss.org/browse/ARQ-1511 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha1 > Reporter: Karel Piwko > Priority: Minor > > Despite the fact I have physical device attached and tests are running on that device, Droidium logs following: > {code} > Sep 29, 2013 4:30:14 PM org.arquillian.droidium.container.configuration.AndroidContainerConfiguration validate > WARNING: Both "avdName" and "serialId" properties are defined, the device specified by "serialId" will get priority if connected. > Sep 29, 2013 4:30:14 PM org.arquillian.droidium.container.AndroidDeployableContainer start > INFO: Starting the container Nexus4. > Sep 29, 2013 4:30:14 PM org.arquillian.droidium.container.impl.AndroidBridgeConnector initAndroidDebugBridge > INFO: Initializing Android Debug Bridge. > Sep 29, 2013 4:30:14 PM org.arquillian.droidium.container.impl.AndroidBridgeImpl connect > INFO: Connecting to the Android Debug Bridge at /home/kpiwko/apps/android-sdk-linux_x86/platform-tools/adb forceNewBridge = true > Sep 29, 2013 4:30:14 PM org.arquillian.droidium.container.impl.AndroidBridgeConnector initAndroidDebugBridge > INFO: Android Debug Bridge was initialized in 323ms. > Sep 29, 2013 4:30:14 PM org.arquillian.droidium.container.impl.AndroidDeviceSelectorImpl getPhysicalDevice > INFO: Detected physical device with serial ID e8fd5c98. > {code} > *Starting the container Nexus4.* is a wrong log output. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1503) @QUnitResource and @QUnitTest usage is bit confusing

by Tolis Emmanouilidis (JIRA)

[ https://issues.jboss.org/browse/ARQ-1503?page=com.atlassian.jira.plugin.s... ] Tolis Emmanouilidis commented on ARQ-1503: ------------------------------------------ [~kpiwko]The QUnitResource value should be the path of a folder which contains all the resources needed for the QUnit Test Suites execution. In the mentioned example: src/test/qunit does not contain all the required resources. Probably some of your QUnit Suites are using resources (e.g jQuery, AeroGear JS libs) which are outside the src/test/qunit folder. That's why changing the QUnitResource value to src, fixed the issue. I would agree on changing the annotation names. However, I think it is well documented in the corresponding blog: > To create an Arquillian QUnit test class, annotate the test class with the @RunWith(QUnitRunner.class) and @QUnitResources annotations. The @QUnitResources annotation’s value should be the path of the folder which contains all the QUnit resources and dependencies which are required for your QUnit tests execution. For each QUnit Test Suite that you would like to execute, create a method and annotate it with the @QUnitTest annotation. The annotation’s value should be the QUnit Test Suite path, relative to the @QUnitResources path. On the below example, the src folder contains all the resources required from our QUnit tests in order to be executed and our QUnit Test Suite (qunit-tests.html) is included inside the src/test/resources/qunit-assets folder. > @QUnitResource and @QUnitTest usage is bit confusing > ---------------------------------------------------- > > Key: ARQ-1503 > URL: https://issues.jboss.org/browse/ARQ-1503 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - QUnit > Affects Versions: qunit_1.0.0.Alpha1 > Reporter: Karel Piwko > > It is difficult to figure out that: > @QUnitResource("src/test/qunit) > @QUnitTest("index.html") > and > @QUnitResource("src) > @QUnitTest("test/qunit/index.html") > will yield completely different results. It needs either a rework or definitely more documetation. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1501) ArquillianQUnitException should be unchecked and have richer API

by Tolis Emmanouilidis (JIRA)

[ https://issues.jboss.org/browse/ARQ-1501?page=com.atlassian.jira.plugin.s... ] Tolis Emmanouilidis commented on ARQ-1501: ------------------------------------------ [~kpiwko] removed ArquillianQUnitException since it was useless. https://github.com/arquillian/arquillian-extension-qunit/commit/3c73c699d... > ArquillianQUnitException should be unchecked and have richer API > ---------------------------------------------------------------- > > Key: ARQ-1501 > URL: https://issues.jboss.org/browse/ARQ-1501 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - QUnit > Affects Versions: qunit_1.0.0.Alpha1 > Reporter: Karel Piwko > > Current ArquillianQUnitException is not that useful, as it is checked and it is missing methods for setting exception cause. -- 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

11 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues October 2013