[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:
-----------------------------
Issue Type: Bug (was: Enhancement)
> 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
10 years, 5 months
[JBoss JIRA] (ARQ-1586) ClassContextImpl is not active during TestNG @BeforeMethod
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/ARQ-1586?page=com.atlassian.jira.plugin.s... ]
Juraj Húska commented on ARQ-1586:
----------------------------------
IMHO the _ClassContext_ should be available.
This is the arquillian.debug output when running with testNG: (see the TestContextHandler.createClassContext)
{noformat:title=TESTNG debug}
(E) Before
(I) TestContextHandler.createSuiteContext
(I) TestContextHandler.createClassContext
(E) TestClass
(I) TestContextHandler.createTestContext
(I) ContainerEventController.createBeforeContext
(O) TestInstanceEnricher.enrich
(E) BeforeEnrichment
(O) ContextRootStoreInitializer.setupLocationForClass
(E) ContextRootStore
(E) DroneLifecycleEvent
(O) DroneInstanceCreator.createDroneInstance
(E) DroneLifecycleEvent
(O) WindowResizer.resizeBrowserWindow
(O) DroneEnhancer.enhanceDrone
(E) DroneEnhancementEvent
(E) DroneEnhancementEvent
(O) WindowResizer.resizeBrowserWindow
(E) AfterEnrichment
(O) DroneConfigurator.configureDrone
(O) ClientBeforeAfterLifecycleEventExecuter.on
{noformat}
These are the active contexts in {{Before}}: {{[org.jboss.arquillian.core.impl.context.ApplicationContextImpl@d4ec36]}}
This is the output when running with junit:
{noformat:title=JUNIT debug}
(E) Before
(I) TestContextHandler.createSuiteContext
(I) TestContextHandler.createClassContext
(E) TestClass
(I) TestContextHandler.createTestContext
(I) ContainerEventController.createBeforeContext
(O) DroneConfigurator.configureDrone
(O) TestInstanceEnricher.enrich
(E) BeforeEnrichment
(O) ContextRootStoreInitializer.setupLocationForClass
(E) ContextRootStore
(E) DroneLifecycleEvent
(O) DroneInstanceCreator.createDroneInstance
(E) DroneLifecycleEvent
(O) DroneEnhancer.enhanceDrone
(E) DroneEnhancementEvent
(E) DroneEnhancementEvent
(O) WindowResizer.resizeBrowserWindow
(O) WindowResizer.resizeBrowserWindow
(E) AfterEnrichment
(O) ClientBeforeAfterLifecycleEventExecuter.on
{noformat}
These are the active contexts: {{[org.jboss.arquillian.core.impl.context.ApplicationContextImpl@62b3beda, org.jboss.arquillian.test.impl.context.ClassContextImpl@6b70cd6, org.jboss.arquillian.container.impl.context.ContainerContextImpl@5babb90b, org.jboss.arquillian.container.impl.context.DeploymentContextImpl@6701b031, org.jboss.arquillian.test.impl.context.TestContextImpl@1fd695cc, org.jboss.arquillian.test.impl.context.SuiteContextImpl@41049468]}}
Other ideas:
* ClassContextImpl is available _(E) After_
* The JUnit part contains _(O) DroneConfigurator.configureDrone_, the testng not.
> 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
10 years, 5 months
[JBoss JIRA] (ARQGRA-397) Add support for host (ActiveX) objects
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-397?page=com.atlassian.jira.plugin... ]
Lukáš Fryč updated ARQGRA-397:
------------------------------
Status: Resolved (was: Pull Request Sent)
Assignee: Petr Andreev (was: Lukáš Fryč)
Resolution: Done
Thanks Petr, I have merged the pull requests which is fixing guards for IE9 and lower.
> Add support for host (ActiveX) objects
> --------------------------------------
>
> Key: ARQGRA-397
> URL: https://issues.jboss.org/browse/ARQGRA-397
> Project: Arquillian Graphene
> Issue Type: Feature Request
> Components: core
> Affects Versions: 2.0.0.CR2
> Environment: WIn7 x64, msxml3.dll (8.110.7601.17988), msxml6.dll (6.30.7601.17988)
> IE9 (IE9 in compat mode->IE7)
> Richfaces 3.3.4 (Sarissa 0.9.9.3)
> Reporter: Petr Andreev
> Assignee: Petr Andreev
> Fix For: 2.0.1.Final
>
> Attachments: Graphene.Page.RequestGuard.js.patch, Graphene.xhrInterception.js.patch, IE10-ARQGRA-397.png, test_ActiveXObject.js, test_setTimeout.js
>
>
> Graphene JavaScript RequestGuard interceptors cause failure of all AJAX requests with Richfaces 3 on InternetExplorer with ActiveXObject version of XMLHttpRequest (overriden by Sarissa included in RF3). There are several issues:
> 1. While wrapping the underlying XMLHttpRequest (provided by Sarissa and being actually the ActiveXObject) the InterceptedXMLHttpRequest accesses the response fields of XHR, which is illegal for windows-host objects. I.e. responseText throws an error '#575: This method cannot be called until the send method has been called.' The solution would be to not to read the response properties in constructor of InterceptedXMLHttpRequest since at this phase it makes no sense.
> 2. The bracket- style calls (xhr['send']) on host objects lead to immediate invocation of affected functions without any parameters. Therefore it is impossible to make any reflection-like invocations or checks for existence on them (i.e. if(xhr['send']) or xhr['send'].apply(.....)). The proposed solution is to wrap the host and native objects before 'apply' calls and expand argument list, in that way avoiding failures and ugly browser detection. On the other hand, the invocation of interceptor chain could be refactored (but there could be still problems passing function pointers of host objects: needs to be checked).
> IE9 errors: "#450: Wrong number of arguments or invalid property assignment" or "#87: The parameter is incorrect."
> 3. The scoping of "this" while attaching "onreadystatchange" callback to original (host) XHR is unspecified in contrary to the case with native JS objects. That`s why the interceptors and RF components don`t get notified about completed AJAX request .The solution is simple - just use the wrappers member variable.
> 4. Overriding the "window.setTimeout" method in RequestGuard causes JS error in IE9 + IE compat mode since there are no 'apply' and 'call' functions defined on window`s host object. The solution is to borrow both functions from Function.prototype- works for native objects too.
> Test cases attached (can be ran in http://jsfiddle.net)
> Proposed patches attached.
--
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, 5 months
[JBoss JIRA] (ARQGRA-397) Guards: Add support for host (ActiveX) objects
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-397?page=com.atlassian.jira.plugin... ]
Lukáš Fryč updated ARQGRA-397:
------------------------------
Summary: Guards: Add support for host (ActiveX) objects (was: Add support for host (ActiveX) objects)
> Guards: Add support for host (ActiveX) objects
> ----------------------------------------------
>
> Key: ARQGRA-397
> URL: https://issues.jboss.org/browse/ARQGRA-397
> Project: Arquillian Graphene
> Issue Type: Feature Request
> Components: core
> Affects Versions: 2.0.0.CR2
> Environment: WIn7 x64, msxml3.dll (8.110.7601.17988), msxml6.dll (6.30.7601.17988)
> IE9 (IE9 in compat mode->IE7)
> Richfaces 3.3.4 (Sarissa 0.9.9.3)
> Reporter: Petr Andreev
> Assignee: Petr Andreev
> Fix For: 2.0.1.Final
>
> Attachments: Graphene.Page.RequestGuard.js.patch, Graphene.xhrInterception.js.patch, IE10-ARQGRA-397.png, test_ActiveXObject.js, test_setTimeout.js
>
>
> Graphene JavaScript RequestGuard interceptors cause failure of all AJAX requests with Richfaces 3 on InternetExplorer with ActiveXObject version of XMLHttpRequest (overriden by Sarissa included in RF3). There are several issues:
> 1. While wrapping the underlying XMLHttpRequest (provided by Sarissa and being actually the ActiveXObject) the InterceptedXMLHttpRequest accesses the response fields of XHR, which is illegal for windows-host objects. I.e. responseText throws an error '#575: This method cannot be called until the send method has been called.' The solution would be to not to read the response properties in constructor of InterceptedXMLHttpRequest since at this phase it makes no sense.
> 2. The bracket- style calls (xhr['send']) on host objects lead to immediate invocation of affected functions without any parameters. Therefore it is impossible to make any reflection-like invocations or checks for existence on them (i.e. if(xhr['send']) or xhr['send'].apply(.....)). The proposed solution is to wrap the host and native objects before 'apply' calls and expand argument list, in that way avoiding failures and ugly browser detection. On the other hand, the invocation of interceptor chain could be refactored (but there could be still problems passing function pointers of host objects: needs to be checked).
> IE9 errors: "#450: Wrong number of arguments or invalid property assignment" or "#87: The parameter is incorrect."
> 3. The scoping of "this" while attaching "onreadystatchange" callback to original (host) XHR is unspecified in contrary to the case with native JS objects. That`s why the interceptors and RF components don`t get notified about completed AJAX request .The solution is simple - just use the wrappers member variable.
> 4. Overriding the "window.setTimeout" method in RequestGuard causes JS error in IE9 + IE compat mode since there are no 'apply' and 'call' functions defined on window`s host object. The solution is to borrow both functions from Function.prototype- works for native objects too.
> Test cases attached (can be ran in http://jsfiddle.net)
> Proposed patches attached.
--
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, 5 months
[JBoss JIRA] (ARQGRA-410) NPE when calling Graphene#createPageFragment inside TestNG @BeforeMethod or @AfterMethod
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-410?page=com.atlassian.jira.plugin... ]
Juraj Húska edited comment on ARQGRA-410 at 11/28/13 6:29 AM:
--------------------------------------------------------------
IMHO this issue is caused by ARQ-1586.
I will wait for an answer on that issue, and then proceed with resolution of this one.
was (Author: jhuska):
IMHO this issue is caused by ARQ-1586.
I would wait for an answer on that issue, and then proceed with resolution of this one.
> 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
10 years, 5 months
[JBoss JIRA] (ARQGRA-410) NPE when calling Graphene#createPageFragment inside TestNG @BeforeMethod or @AfterMethod
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-410?page=com.atlassian.jira.plugin... ]
Juraj Húska commented on ARQGRA-410:
------------------------------------
IMHO this issue is caused by ARQ-1586.
I would wait for an answer on that issue, and then proceed with resolution of this one.
> 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
10 years, 5 months
[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 reassigned ARQ-1583:
--------------------------------
Assignee: Karel Piwko
> Emulator does not figure out process had died
> ---------------------------------------------
>
> Key: ARQ-1583
> URL: https://issues.jboss.org/browse/ARQ-1583
> Project: Arquillian
> Issue Type: Enhancement
> 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
10 years, 5 months