November 2013 - arquillian-issues

[JBoss JIRA] (ARQGRA-410) NPE when calling Graphene#createPageFragment inside TestNG @BeforeMethod or @AfterMethod

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-410?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-410: ----------------------------------- Thanks for investigations, Juraj, we will wait for clarification of ARQ-1586 then. > NPE when calling Graphene#createPageFragment inside TestNG @BeforeMethod or @AfterMethod > ---------------------------------------------------------------------------------------- > > Key: ARQGRA-410 > URL: https://issues.jboss.org/browse/ARQGRA-410 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Final > Reporter: Jiri Locker > Assignee: Juraj Húska > Fix For: 2.0.1.Final > > > Stack trace: > {noformat} > org.jboss.arquillian.graphene.enricher.exception.PageFragmentInitializationException: java.lang.NullPointerException > at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.createPageFragment(PageFragmentEnricher.java:171) > at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.createPageFragment(DefaultGrapheneRuntime.java:116) > at org.jboss.arquillian.graphene.Graphene.createPageFragment(Graphene.java:263) > at org.jboss.qa.brms.workbench.AbstractPerspective.<init>(AbstractPerspective.java:56) > at org.jboss.qa.brms.workbench.HomePerspective.<init>(HomePerspective.java:12) > at org.jboss.qa.brms.DesignerTestWrapper.login(DesignerTestWrapper.java:65) > at org.jboss.qa.brms.dashboard.DashboardsMenuTest.init(DashboardsMenuTest.java:20) > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.graphene.enricher.WebElementEnricher.enrich(WebElementEnricher.java:68) > at org.jboss.arquillian.graphene.enricher.AbstractSearchContextEnricher.enrichRecursively(AbstractSearchContextEnricher.java:74) > at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.createPageFragment(PageFragmentEnricher.java:156) > ... 36 more > ... Removed 30 stack frames > {noformat} -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQGRA-355) Allow to test on remote Internet Explorer

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-355?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-355: ------------------------------ Sprint: (was: Graphene 2.0.1) > Allow to test on remote Internet Explorer > ----------------------------------------- > > Key: ARQGRA-355 > URL: https://issues.jboss.org/browse/ARQGRA-355 > Project: Arquillian Graphene > Issue Type: Bug > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 2.0-Tracking > > -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQGRA-395) Graphene.guardAjax() doesn't work correctly in IE

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-395?page=com.atlassian.jira.plugin... ] Lukáš Fryč edited comment on ARQGRA-395 at 11/29/13 4:41 AM: ------------------------------------------------------------- Tests pass with IE9 since ARQGRA-397 was resolved. They fails with IE8 though. was (Author: lfryc): Tests pass with IE9 since ARQGRA-397 was resolved. > Graphene.guardAjax() doesn't work correctly in IE > ------------------------------------------------- > > Key: ARQGRA-395 > URL: https://issues.jboss.org/browse/ARQGRA-395 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.0.CR2 > Environment: IE 7, 8, 9 > Reporter: Jan Dosoudil > Assignee: Lukáš Fryč > Fix For: 2.0.1.Final > > > I have jsf page h:commandButton with f:ajax. Testing with Graphene.guardAjax(button).click(); works with Firefox, htmlUnit, phantomjs but doesn't with Internet Explorer (7, 8, 9). Internet explorer calls onclick function but without return false which causes full page submit. > button.click() works ok. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQGRA-355) Allow to test on remote Internet Explorer

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-355?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-355: ------------------------------ Fix Version/s: 2.0-Tracking (was: 2.0.1.Final) > Allow to test on remote Internet Explorer > ----------------------------------------- > > Key: ARQGRA-355 > URL: https://issues.jboss.org/browse/ARQGRA-355 > Project: Arquillian Graphene > Issue Type: Bug > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 2.0-Tracking > > -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQGRA-395) Graphene.guardAjax() doesn't work correctly in IE

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-395?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-395: ----------------------------------- Tests pass with IE9 since ARQGRA-397 was resolved. > Graphene.guardAjax() doesn't work correctly in IE > ------------------------------------------------- > > Key: ARQGRA-395 > URL: https://issues.jboss.org/browse/ARQGRA-395 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.0.CR2 > Environment: IE 7, 8, 9 > Reporter: Jan Dosoudil > Assignee: Lukáš Fryč > Fix For: 2.0.1.Final > > > I have jsf page h:commandButton with f:ajax. Testing with Graphene.guardAjax(button).click(); works with Firefox, htmlUnit, phantomjs but doesn't with Internet Explorer (7, 8, 9). Internet explorer calls onclick function but without return false which causes full page submit. > button.click() works ok. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQGRA-238) Catch client-side errors

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-238?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-238: ----------------------------------- PhantomJS has global onError handler: https://github.com/ariya/phantomjs/wiki/API-Reference-phantom > Catch client-side errors > ------------------------ > > Key: ARQGRA-238 > URL: https://issues.jboss.org/browse/ARQGRA-238 > Project: Arquillian Graphene > Issue Type: Feature Request > Affects Versions: 2.0.0.Alpha2 > Reporter: Lukáš Fryč > Fix For: 2.1-Tracking > > > Graphene should allow to inspect errors on client-side. > E.g. console.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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1583) Emulator does not figure out process had died

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1583?page=com.atlassian.jira.plugin.s... ] Karel Piwko edited comment on ARQ-1583 at 11/28/13 11:37 AM: ------------------------------------------------------------- Updated issue and bumped priority. The problem is that Droidium will not figure out emulator process is down and still waits for its output. was (Author: kpiwko): Updated issue and bumped priority. The problem is that Droidium will not figure out emulator process is down and still waits for it's output. > Emulator does not figure out process had died > --------------------------------------------- > > Key: ARQ-1583 > URL: https://issues.jboss.org/browse/ARQ-1583 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Critical > > *When*: > I let Droidium start emulator. > *Given*: > Emulator command fails, for instance when DISPLAY is not set. > *Then*: > Droidium waits up to emulator start time, then fails. > *Expected*: > Droidium will figure out command had failed - emulator actually outputs *SDL init failure, reason is: No available video device* and let user know what happened wrong. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1583) Emulator does not figure out process had died

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1583?page=com.atlassian.jira.plugin.s... ] Karel Piwko commented on ARQ-1583: ---------------------------------- Pushed upstream in https://github.com/arquillian/arquillian-droidium/commit/80b1f817b911d912... > Emulator does not figure out process had died > --------------------------------------------- > > Key: ARQ-1583 > URL: https://issues.jboss.org/browse/ARQ-1583 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Critical > > *When*: > I let Droidium start emulator. > *Given*: > Emulator command fails, for instance when DISPLAY is not set. > *Then*: > Droidium waits up to emulator start time, then fails. > *Expected*: > Droidium will figure out command had failed - emulator actually outputs *SDL init failure, reason is: No available video device* and let user know what happened wrong. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1586) ClassContextImpl is not active during TestNG @BeforeMethod

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1586?page=com.atlassian.jira.plugin.s... ] Karel Piwko commented on ARQ-1586: ---------------------------------- I think this is related to ARQ-1576. The problem is that even if ClassContext is available, it is a pretty new ClassContext - created in Before event - so anything that Graphene stored there is not available. > ClassContextImpl is not active during TestNG @BeforeMethod > ---------------------------------------------------------- > > Key: ARQ-1586 > URL: https://issues.jboss.org/browse/ARQ-1586 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.1.Final > Reporter: Juraj Húska > > When I call [this|https://github.com/arquillian/arquillian-graphene/blob/master/api/sr...] Arquillian Graphene's method in method annotated with TestNG {{@BeforeMethod}}, then it is not possible to get Graphene's configuration. > On this [line|https://github.com/arquillian/arquillian-graphene/blob/master/impl/s...], {{configuration.get()}} returns {{null}}. > The configuration should be retrieved from {{Instance<GrapheneConfiguration>}}. However, it is not. > When I compare this to JUnit {{@Before}}, I came to this: > At {{ManagerImpl.java}} [here|https://github.com/arquillian/arquillian-core/blob/master/core/impl-...], the configuration is retrieved from context {{ClassContextImpl}}. > However, that context is not marked as active when executing from TestNG (among the others contexts). -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1583) Emulator does not figure out process had died

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1583?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1583: ----------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-droidium/pull/8 > Emulator does not figure out process had died > --------------------------------------------- > > Key: ARQ-1583 > URL: https://issues.jboss.org/browse/ARQ-1583 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Critical > > *When*: > I let Droidium start emulator. > *Given*: > Emulator command fails, for instance when DISPLAY is not set. > *Then*: > Droidium waits up to emulator start time, then fails. > *Expected*: > Droidium will figure out command had failed - emulator actually outputs *SDL init failure, reason is: No available video device* and let user know what happened wrong. -- 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, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues November 2013