December 2012 - arquillian-issues

[JBoss JIRA] (ARQ-1174) Warp: DeploymentEnricher should check whether current TestClass is annotated with WarpTest

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1174?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč resolved ARQ-1174. ----------------------------- Resolution: Done > Warp: DeploymentEnricher should check whether current TestClass is annotated with WarpTest > ------------------------------------------------------------------------------------------ > > Key: ARQ-1174 > URL: https://issues.jboss.org/browse/ARQ-1174 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2, 1.0.3.Final > Reporter: Anthony Patricio > Assignee: Lukáš Fryč > Priority: Critical > Fix For: warp_1.0.0.Alpha2 > > > Warp breaks all the deployments since it does not check if it is WarpTest. > In other words, some tests requires to be shipped with the deployed archive and warp is disabling this aspect. > This is impacting non @WarpTest test classes. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-937) Add usage examples to API/SPI classes

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-937?page=com.atlassian.jira.plugin.sy... ] Lukáš Fryč resolved ARQ-937. ---------------------------- Resolution: Done Polished SPI and its documentation. > Add usage examples to API/SPI classes > ------------------------------------- > > Key: ARQ-937 > URL: https://issues.jboss.org/browse/ARQ-937 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Aslak Knutsen > Assignee: Lukáš Fryč > Fix For: warp_1.0.0.Alpha2 > > > We should start adding Usage Examples to API and SPIs with a Description of the Concept this represent. > The future usage is to build up a reference dictionary, see current version: > https://github.com/arquillian/arquillian-core/blob/master/container/test-... > Example: > http://staging-arquilliandev.rhcloud.com/code/reference/#org.jboss.arquil... > Arquillian.org issue: https://github.com/arquillian/arquillian.github.com/issues/87 -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQGRA-232) Enriched WebElement cannot be converted to JSON without manual unwrapping

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-232?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-232: ------------------------------ Fix Version/s: 2.0.0.Alpha3 > Enriched WebElement cannot be converted to JSON without manual unwrapping > ------------------------------------------------------------------------- > > Key: ARQGRA-232 > URL: https://issues.jboss.org/browse/ARQGRA-232 > Project: Arquillian Graphene > Issue Type: Bug > Reporter: Jiří Štefek > Priority: Critical > Fix For: 2.0.0.Alpha3 > > > When you use something like this, WebElementToJsonConverter cannot convert enriched input: > {code} > @FindBy(css="input[id$=input]") > WebElement input; > public void blurInput(){ > JavascriptExecutor js = (JavascriptExecutor) GrapheneContext.getProxy(); > >>> js.executeScript("jQuery(arguments[0]).trigger('blur')", input); <<< > } > {code} > error: > {code} > java.lang.IllegalArgumentException: Argument is of an illegal type: $Proxy37 > at org.openqa.selenium.remote.internal.WebElementToJsonConverter.apply(WebElementToJsonConverter.java:78) > at com.google.common.collect.Iterators$8.next(Iterators.java:730) > at com.google.common.collect.Lists.newArrayList(Lists.java:136) > at com.google.common.collect.Lists.newArrayList(Lists.java:117) > at org.openqa.selenium.remote.RemoteWebDriver.executeScript(RemoteWebDriver.java:437) > 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:601) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.invokeReal(GrapheneProxyHandler.java:200) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler$1.invoke(GrapheneProxyHandler.java:134) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.invoke(GrapheneProxyHandler.java:164) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.intercept(GrapheneProxyHandler.java:172) > at org.openqa.selenium.firefox.FirefoxDriver$$EnhancerCGLIB$$cd9d0009.executeScript(<generated>) > {code} > Missing some interface in created proxy? -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQGRA-232) Enriched WebElement cannot be converted to JSON without manual unwrapping

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-232?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-232: ------------------------------ Priority: Critical (was: Major) > Enriched WebElement cannot be converted to JSON without manual unwrapping > ------------------------------------------------------------------------- > > Key: ARQGRA-232 > URL: https://issues.jboss.org/browse/ARQGRA-232 > Project: Arquillian Graphene > Issue Type: Bug > Reporter: Jiří Štefek > Priority: Critical > > When you use something like this, WebElementToJsonConverter cannot convert enriched input: > {code} > @FindBy(css="input[id$=input]") > WebElement input; > public void blurInput(){ > JavascriptExecutor js = (JavascriptExecutor) GrapheneContext.getProxy(); > >>> js.executeScript("jQuery(arguments[0]).trigger('blur')", input); <<< > } > {code} > error: > {code} > java.lang.IllegalArgumentException: Argument is of an illegal type: $Proxy37 > at org.openqa.selenium.remote.internal.WebElementToJsonConverter.apply(WebElementToJsonConverter.java:78) > at com.google.common.collect.Iterators$8.next(Iterators.java:730) > at com.google.common.collect.Lists.newArrayList(Lists.java:136) > at com.google.common.collect.Lists.newArrayList(Lists.java:117) > at org.openqa.selenium.remote.RemoteWebDriver.executeScript(RemoteWebDriver.java:437) > 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:601) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.invokeReal(GrapheneProxyHandler.java:200) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler$1.invoke(GrapheneProxyHandler.java:134) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.invoke(GrapheneProxyHandler.java:164) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.intercept(GrapheneProxyHandler.java:172) > at org.openqa.selenium.firefox.FirefoxDriver$$EnhancerCGLIB$$cd9d0009.executeScript(<generated>) > {code} > Missing some interface in created proxy? -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-710) Separated per-test and per-container log files.

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/ARQ-710?page=com.atlassian.jira.plugin.sy... ] Ondrej Zizka edited comment on ARQ-710 at 12/10/12 1:59 PM: ------------------------------------------------------------ About system properties: https://community.jboss.org/wiki/JBossAS7SystemProperties Writing a property: {code} /system-property=foo/:add(value=bar) {code} was (Author: ozizka): Reading system properties: https://community.jboss.org/wiki/JBossAS7OverviewOfAllSystemProperties > Separated per-test and per-container log files. > ----------------------------------------------- > > Key: ARQ-710 > URL: https://issues.jboss.org/browse/ARQ-710 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.0.0.CR7 > Reporter: Ondrej Zizka > > What's the best way to separate server and client log messages? > Currently, log messages can either go to the console, and Arquillian "forwards" them to Surefire, which causes mixed client and server messages. > Or, messages can go to the server log file as usually. Which ends up in tens of megabytes long log files. > So, either arq can log to an arbitrary file, or Surefire could have support for multiple logs. > The later won't happen any soon I guess Arq just forwards anything to surefire. > So, let's say I want to have separated log files in surefire-reports dir: > * org.jboss.FooBarTestCase-client, > * org.jboss.FooBarTestCase-server1, > * org.jboss.FooBarTestCase-server2, ... > This feature is quite important for large testsuites which produce tons of log messages, > and even more for multi-node tests. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-710) Separated per-test and per-container log files.

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/ARQ-710?page=com.atlassian.jira.plugin.sy... ] Ondrej Zizka edited comment on ARQ-710 at 12/10/12 1:53 PM: ------------------------------------------------------------ I've created a logger which would do that: https://github.com/OndraZizka/jboss-as/compare/TS-logPerTest (not tested) Now it's up to ARQ AS7 container to set the properties properly. was (Author: ozizka): I've created a logged which would do that: https://github.com/OndraZizka/jboss-as/compare/TS-logPerTest (not tested) Now it's up to ARQ AS7 container to set the properties properly. > Separated per-test and per-container log files. > ----------------------------------------------- > > Key: ARQ-710 > URL: https://issues.jboss.org/browse/ARQ-710 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.0.0.CR7 > Reporter: Ondrej Zizka > > What's the best way to separate server and client log messages? > Currently, log messages can either go to the console, and Arquillian "forwards" them to Surefire, which causes mixed client and server messages. > Or, messages can go to the server log file as usually. Which ends up in tens of megabytes long log files. > So, either arq can log to an arbitrary file, or Surefire could have support for multiple logs. > The later won't happen any soon I guess Arq just forwards anything to surefire. > So, let's say I want to have separated log files in surefire-reports dir: > * org.jboss.FooBarTestCase-client, > * org.jboss.FooBarTestCase-server1, > * org.jboss.FooBarTestCase-server2, ... > This feature is quite important for large testsuites which produce tons of log messages, > and even more for multi-node tests. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-710) Separated per-test and per-container log files.

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/ARQ-710?page=com.atlassian.jira.plugin.sy... ] Ondrej Zizka commented on ARQ-710: ---------------------------------- Reading system properties: https://community.jboss.org/wiki/JBossAS7OverviewOfAllSystemProperties > Separated per-test and per-container log files. > ----------------------------------------------- > > Key: ARQ-710 > URL: https://issues.jboss.org/browse/ARQ-710 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.0.0.CR7 > Reporter: Ondrej Zizka > > What's the best way to separate server and client log messages? > Currently, log messages can either go to the console, and Arquillian "forwards" them to Surefire, which causes mixed client and server messages. > Or, messages can go to the server log file as usually. Which ends up in tens of megabytes long log files. > So, either arq can log to an arbitrary file, or Surefire could have support for multiple logs. > The later won't happen any soon I guess Arq just forwards anything to surefire. > So, let's say I want to have separated log files in surefire-reports dir: > * org.jboss.FooBarTestCase-client, > * org.jboss.FooBarTestCase-server1, > * org.jboss.FooBarTestCase-server2, ... > This feature is quite important for large testsuites which produce tons of log messages, > and even more for multi-node tests. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1235) "@ArquillianResource URL contexPath" is resolved to "http:/0.0.0.0:8080/deploypath" when using -b 0.0.0.0

by José Freitas (JIRA)

José Freitas created ARQ-1235: --------------------------------- Summary: "@ArquillianResource URL contexPath" is resolved to "http:/0.0.0.0:8080/deploypath" when using -b 0.0.0.0 Key: ARQ-1235 URL: https://issues.jboss.org/browse/ARQ-1235 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBoss AS Containers Affects Versions: 1.0.3.Final Environment: Windows 7 and AS7.1.1 with remote-container connector Reporter: José Freitas @ArquillianResource URL contextPath; gets resolved to: http://0.0.0.0:8080/15ff0138-935a-44be-a84f-73263a88df6a/ and it should return a public adress so it can connect to the server when @Deployment(testable = false) -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQGRA-232) Enriched WebElement cannot be converted to JSON without manual unwrapping

by Jiří Štefek (JIRA)

Jiří Štefek created ARQGRA-232: ---------------------------------- Summary: Enriched WebElement cannot be converted to JSON without manual unwrapping Key: ARQGRA-232 URL: https://issues.jboss.org/browse/ARQGRA-232 Project: Arquillian Graphene Issue Type: Bug Reporter: Jiří Štefek When you use something like this, WebElementToJsonConverter cannot convert enriched input: {code} @FindBy(css="input[id$=input]") WebElement input; public void blurInput(){ JavascriptExecutor js = (JavascriptExecutor) GrapheneContext.getProxy(); >>> js.executeScript("jQuery(arguments[0]).trigger('blur')", input); <<< } {code} error: {code} java.lang.IllegalArgumentException: Argument is of an illegal type: $Proxy37 at org.openqa.selenium.remote.internal.WebElementToJsonConverter.apply(WebElementToJsonConverter.java:78) at com.google.common.collect.Iterators$8.next(Iterators.java:730) at com.google.common.collect.Lists.newArrayList(Lists.java:136) at com.google.common.collect.Lists.newArrayList(Lists.java:117) at org.openqa.selenium.remote.RemoteWebDriver.executeScript(RemoteWebDriver.java:437) 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:601) at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.invokeReal(GrapheneProxyHandler.java:200) at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler$1.invoke(GrapheneProxyHandler.java:134) at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.invoke(GrapheneProxyHandler.java:164) at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.intercept(GrapheneProxyHandler.java:172) at org.openqa.selenium.firefox.FirefoxDriver$$EnhancerCGLIB$$cd9d0009.executeScript(<generated>) {code} Missing some interface in created proxy? -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1233) Warp: rename API according to results of survey

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1233?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-1233: ---------------------------- Priority: Blocker (was: Major) > Warp: rename API according to results of survey > ----------------------------------------------- > > Key: ARQ-1233 > URL: https://issues.jboss.org/browse/ARQ-1233 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Lukáš Fryč > Priority: Blocker > Fix For: warp_1.0.0.Alpha2 > > Attachments: warp-api-method-naming-survey-responses.pdf > > > There were discussion about Warp API method naming: > As a result, interesting options were selected and survey for choosing most natural and popular ones was opened: > https://docs.google.com/spreadsheet/viewform?formkey=dFlZeGI3ZklOUVlDX2M2... > As a response, we got 8 answers with following results: > {code} > most favorite: > option #1: Warp .initiate(Activity) .observe(What) .inspect(Inspection); > followed by: > option #5: Warp .execute(ClientAction) .filter(Filter) .inspect(ServerInspection); > {code} > The complete overview of responses is attached in PDF. -- 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, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues December 2012