September 2013 - arquillian-issues

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

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1514: -------------------------------- Summary: 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 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-382) @InitialPage does not work for Field

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-382?page=com.atlassian.jira.plugin... ] Karel Piwko commented on ARQGRA-382: ------------------------------------ Given that *initial ~ existing or occurring at the beginning*, this can be both understood as BeforeClass (my understanding) and Before (your understanding). However, all other fields in tests preserve the state among tests, so Before would be an exception. That said, I would either prefer to remove the possibility of annotating a field or making a paramater to @InitialPage, which would additionally alter it's behavior - e.g. where do you want URL to be fired, which some reasonable default identified by broader audience. Nice Enhancement for post 2.0.0.GA release? > @InitialPage does not work for Field > ------------------------------------ > > Key: ARQGRA-382 > URL: https://issues.jboss.org/browse/ARQGRA-382 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.0.CR1 > Reporter: Karel Piwko > Fix For: 2.0.0.Final > > > While @InitialPage allows to be used on test class field, it does not do anything. > {code} > @InitialPage AddUserPage page; > @Test > void test() { > page.foo() > } > {code} > raises > {code} > java.lang.NullPointerException: null > at com.acme.example.test.DroneTest.addUser(DroneTest.java:35) > {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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1513) Multicontainer extension should not log warnings about its property

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1513: -------------------------------- Summary: Multicontainer extension should not log warnings about its property Key: ARQ-1513 URL: https://issues.jboss.org/browse/ARQ-1513 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 All the time, following WARNING is present in the log: {code} Unused property entries: {adapterImplClass=org.arquillian.droidium.container.AndroidDeployableContainer} {code} As this property is required, the warning should be somehow suppressed. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-135) Helpers for writing browser specific code

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-135?page=com.atlassian.jira.plugin... ] Juraj Húska edited comment on ARQGRA-135 at 9/30/13 3:15 AM: ------------------------------------------------------------- If the resolution of ARQ-1179 would support injection of the {{BrowserType}}, so that a user will be able to use browser specific code also in his Page Objects etc, then I agree that we probably do not need this one. However, if it supports only denoting on which browsers a test should run, then we would probably need this issue. was (Author: jhuska): If the resolution of ARQ-1179 would support injection of the {{BrowserType}}, so that a user will be able to use browser specific code also in his Page Objects etc, then I agree that we probably do not need this one. > Helpers for writing browser specific code > ----------------------------------------- > > Key: ARQGRA-135 > URL: https://issues.jboss.org/browse/ARQGRA-135 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: api > Reporter: Lukáš Fryč > Priority: Minor > Fix For: 2.1-Tracking > > > Sometimes people need to deal with interoperability of the code between browsers. > It would be nice if Graphene 2 could provide nice way to handle that. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-135) Helpers for writing browser specific code

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-135?page=com.atlassian.jira.plugin... ] Juraj Húska commented on ARQGRA-135: ------------------------------------ If the resolution of ARQ-1179 would support injection of the {{BrowserType}}, so that a user will be able to use browser specific code also in his Page Objects etc, then I agree that we probably do not need this one. > Helpers for writing browser specific code > ----------------------------------------- > > Key: ARQGRA-135 > URL: https://issues.jboss.org/browse/ARQGRA-135 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: api > Reporter: Lukáš Fryč > Priority: Minor > Fix For: 2.1-Tracking > > > Sometimes people need to deal with interoperability of the code between browsers. > It would be nice if Graphene 2 could provide nice way to handle that. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-381) Support for robust and concise way of asserting instances of WebDriver

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-381?page=com.atlassian.jira.plugin... ] Juraj Húska closed ARQGRA-381. ------------------------------ > Support for robust and concise way of asserting instances of WebDriver > ---------------------------------------------------------------------- > > Key: ARQGRA-381 > URL: https://issues.jboss.org/browse/ARQGRA-381 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: core > Affects Versions: 2.0.0.CR1 > Reporter: Juraj Húska > > In the old days, it was possible to figure out which browser the test is running on by: > {code} > GrapheneContext.holdsInstanceOf(AndroidDriver.class) > {code} > In the current Graphene this information can be retrieved IMHO in quite verbose way. E.g. [this|https://github.com/richfaces/richfaces/blob/master/build/build-resou...] piece of code to find out whether the browser is {{PhnatomJS}}. > Can we provide some robust and concise shortcut for this ? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-381) Support for robust and concise way of asserting instances of WebDriver

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-381?page=com.atlassian.jira.plugin... ] Juraj Húska resolved ARQGRA-381. -------------------------------- Resolution: Duplicate Issue Yes Lukas, this is duplication of ARQGRA-135. I am closing this one. > Support for robust and concise way of asserting instances of WebDriver > ---------------------------------------------------------------------- > > Key: ARQGRA-381 > URL: https://issues.jboss.org/browse/ARQGRA-381 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: core > Affects Versions: 2.0.0.CR1 > Reporter: Juraj Húska > > In the old days, it was possible to figure out which browser the test is running on by: > {code} > GrapheneContext.holdsInstanceOf(AndroidDriver.class) > {code} > In the current Graphene this information can be retrieved IMHO in quite verbose way. E.g. [this|https://github.com/richfaces/richfaces/blob/master/build/build-resou...] piece of code to find out whether the browser is {{PhnatomJS}}. > Can we provide some robust and concise shortcut for this ? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1508) WindowResizer does not fail-safe on Android

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1508?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1508: ----------------------------- Fix Version/s: drone_1.2.0.Final > WindowResizer does not fail-safe on Android > ------------------------------------------- > > Key: ARQ-1508 > URL: https://issues.jboss.org/browse/ARQ-1508 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.CR1 > Reporter: Karel Piwko > Fix For: drone_1.2.0.Final > > > WindowResizer does fails when running on Android with > {code} > org.openqa.selenium.WebDriverException: Window handling not supported on Android > {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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1508) WindowResizer does not fail-safe on Android

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1508?page=com.atlassian.jira.plugin.s... ] Karel Piwko commented on ARQ-1508: ---------------------------------- Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/3d475572d... > WindowResizer does not fail-safe on Android > ------------------------------------------- > > Key: ARQ-1508 > URL: https://issues.jboss.org/browse/ARQ-1508 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.CR1 > Reporter: Karel Piwko > Fix For: drone_1.2.0.Final > > > WindowResizer does fails when running on Android with > {code} > org.openqa.selenium.WebDriverException: Window handling not supported on Android > {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, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1508) WindowResizer does not fail-safe on Android

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1508?page=com.atlassian.jira.plugin.s... ] Karel Piwko resolved ARQ-1508. ------------------------------ Assignee: Karel Piwko Resolution: Done > WindowResizer does not fail-safe on Android > ------------------------------------------- > > Key: ARQ-1508 > URL: https://issues.jboss.org/browse/ARQ-1508 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.CR1 > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.2.0.Final > > > WindowResizer does fails when running on Android with > {code} > org.openqa.selenium.WebDriverException: Window handling not supported on Android > {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, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues September 2013