January 2016 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQGRA-364) Allow for extensibility of GrapheneElement

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-364?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-364: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Allow for extensibility of GrapheneElement > ------------------------------------------ > > Key: ARQGRA-364 > URL: https://issues.jboss.org/browse/ARQGRA-364 > Project: Arquillian Graphene > Issue Type: Enhancement > Reporter: Lukáš Fryč > Fix For: 2.2-Tracking > > > Implement GrapheneElement#as(Class<?> type) method which will do a coercion to the given type. > If the given type is not implemented by wrapped WebElement, the service which implements this method will be called instead. This allows for simple extensibility mechanism: > {code} > @FindBy > GrapheneElement element; > @Test test() { > element.as(ValidableElement).checkValidity(); > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

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č updated ARQGRA-238: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > 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.2-Tracking > > > Graphene should allow to inspect errors on client-side. > E.g. console.log output. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-389) Improve Usability

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-389?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-389: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Improve Usability > ----------------- > > Key: ARQGRA-389 > URL: https://issues.jboss.org/browse/ARQGRA-389 > Project: Arquillian Graphene > Issue Type: Epic > Reporter: Lukáš Fryč > Fix For: 2.2-Tracking > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-388) Use Proxy between the server and client to enhance Graphene's functionality

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-388?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-388: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Use Proxy between the server and client to enhance Graphene's functionality > --------------------------------------------------------------------------- > > Key: ARQGRA-388 > URL: https://issues.jboss.org/browse/ARQGRA-388 > Project: Arquillian Graphene > Issue Type: Epic > Reporter: Lukáš Fryč > Fix For: 2.2-Tracking > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-318) Allow to select a code to execute based on a type of browser, its version, etc.

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-318?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-318: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Allow to select a code to execute based on a type of browser, its version, etc. > ------------------------------------------------------------------------------- > > Key: ARQGRA-318 > URL: https://issues.jboss.org/browse/ARQGRA-318 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Lukáš Fryč > Fix For: 2.2-Tracking > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-303) Improve failure messages in a fluent waiting API

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-303?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-303: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Improve failure messages in a fluent waiting API > ------------------------------------------------ > > Key: ARQGRA-303 > URL: https://issues.jboss.org/browse/ARQGRA-303 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Lukáš Fryč > Priority: Minor > Fix For: 2.2-Tracking > > > Test can currently fail with this message: > {code} > org.openqa.selenium.TimeoutException: Timed out after 2 seconds waiting for wrapped: text ('script executed') to be present in element found by By.tagName: title > {code} > We should: > * provide user with current value (last known value before the test failed) > * remove the "wrapped:" keyword, since it's misleading -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-79) Migrate command interceptors to Selenium 2

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-79?page=com.atlassian.jira.plugin.... ] Lukáš Fryč updated ARQGRA-79: ----------------------------- Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Migrate command interceptors to Selenium 2 > ------------------------------------------ > > Key: ARQGRA-79 > URL: https://issues.jboss.org/browse/ARQGRA-79 > Project: Arquillian Graphene > Issue Type: Epic > Components: api, core > Reporter: Lukáš Fryč > Priority: Optional > Fix For: 2.2-Tracking > > > There is listener capability in Selenium 2, it could by used in place of interceptors from Ajocado 1. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-329) Add support for HTML5 form validation API

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-329?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-329: ------------------------------ Fix Version/s: 2.2-Tracking (was: 2.1-Tracking) > Add support for HTML5 form validation API > ----------------------------------------- > > Key: ARQGRA-329 > URL: https://issues.jboss.org/browse/ARQGRA-329 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.0.Alpha4 > Reporter: Oliver Kišš > Labels: padawan > Fix For: 2.2-Tracking > > > Add support for using HTML5 [form validation API|http://www.whatwg.org/specs/web-apps/current-work/#the-constraint-val...] from Graphene, {{checkValidity()}} method in particular. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-423) Provide a way to intercept in some order

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-423?page=com.atlassian.jira.plugin... ] Lukáš Fryč reassigned ARQGRA-423: --------------------------------- Assignee: Juraj Húska > Provide a way to intercept in some order > ---------------------------------------- > > Key: ARQGRA-423 > URL: https://issues.jboss.org/browse/ARQGRA-423 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj Húska > Assignee: Juraj Húska > Fix For: 2.1.0.Alpha1 > > > Currently all registered interceptors are invoked in non defined order. > It would be handy to provide a way how to define such order. > It is mainly because on of the Graphene interceptors: {{SearchContextInterceptor}} blocks intercepting of {{findBy}} method. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2008) Arquillian

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-2008?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen commented on ARQ-2008: ------------------------------------ What happens when you run "mvn clean install" from command line? > Arquillian > ---------- > > Key: ARQ-2008 > URL: https://issues.jboss.org/browse/ARQ-2008 > Project: Arquillian > Issue Type: Feature Request > Environment: Arquillian > Reporter: Sanket Patel > Attachments: pom.xml > > > I get the below error when i try to run: > I have also atttached my pom file > I am new and trying to learn Arquillian so forgive me if some major or useless mistake. > import static org.junit.Assert.*; > import org.jboss.arquillian.container.test.api.Deployment; > import org.jboss.arquillian.junit.Arquillian; > import org.jboss.shrinkwrap.api.ShrinkWrap; > import org.jboss.shrinkwrap.api.asset.EmptyAsset; > import org.jboss.shrinkwrap.api.spec.JavaArchive; > import org.junit.Assert; > import org.junit.Test; > import org.junit.runner.RunWith; > @RunWith(Arquillian.class) > public class GreeterTest { > @Deployment > public static JavaArchive createDeployment() > { return ShrinkWrap.create(JavaArchive.class) .addClass(Greeter.class) .addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml"); } > @Test > public void should_create_greeting() > { assertEquals("sanket","sanket"); } > } > java.lang.NullPointerException > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:390) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues January 2016