September 2014 - arquillian-issues

[JBoss JIRA] (ARQ-1856) Remove dynamic import from arquillian-bundle

by Thomas Diesler (JIRA)

Thomas Diesler created ARQ-1856: ----------------------------------- Summary: Remove dynamic import from arquillian-bundle Key: ARQ-1856 URL: https://issues.jboss.org/browse/ARQ-1856 Project: Arquillian Issue Type: Feature Request Components: OSGi Containers Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: osgi_2.0.0.Final Currently, the arquillian bundle contains a dynamic import "*" which may lead to undesired package wiring. Theoretically, it should possible to embed all required dependencies in the arq-bundle and load the test classes from the test-bundle(s) via Bundle.loadClass(...) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-374) Allow to setup custom Location URL via arquillian.xml configuration with CustomizableURLResourceProvider

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-374?page=com.atlassian.jira.plugin... ] Stefan Miklosovic updated ARQGRA-374: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/123 > Allow to setup custom Location URL via arquillian.xml configuration with CustomizableURLResourceProvider > -------------------------------------------------------------------------------------------------------- > > Key: ARQGRA-374 > URL: https://issues.jboss.org/browse/ARQGRA-374 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Lukáš Fryč > Assignee: Stefan Miklosovic > Fix For: 2.1-Tracking > > > {code:xml} > <arquillian> > <extension name="graphene"> > <property name="url">http://localhost:8080/app/</property> > </extension> > </arquillian> > {code} > The provider will obtain URL from {{URLResourceProvider}} and use it if no other URL is provided. > Configuring this provider should also block deploying application, since its unnecessary. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1828) Replace Testrunner with a JUnit-Rule

by Moinz Moinzen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1828?page=com.atlassian.jira.plugin.s... ] Moinz Moinzen commented on ARQ-1828: ------------------------------------ A Junit Rule would also make it a lot easier to make some default setup, and then allowing the individual tests to add further information. Example: {code:java} private static class MyTestRule implements TestRule { ArquillianTestRule arquillianTestRule = new ArquillianTestRule(); private final WebArchive warModule = ShrinkWrap.create(WebArchive.class, "test.war") .addPackages(true, "some.default.package") .addAsManifestResource("MANIFEST.MF") .addAsWebResource(EmptyAsset.INSTANCE, "beans.xml") .addClass(ServerUserContext.class); private final JavaArchive beansModule = ShrinkWrap.create(JavaArchive.class).addClass(ApiProducer.class); public void addWarClass(Class clazz) { warModule.addClass(clazz); } @Override public Statement apply(Statement base, Description description) { arquillianTestRule.setArchive(ShrinkWrap.create(EnterpriseArchive.class, "test.ear") .addAsModule(warModule) .addAsModule(beansModule)); return arquillianTestRule.apply(base, description); } } {code} Usage: {code:java} public class MyTest { @Rule MyTestRule rule = new MyTestRule(); @Setup public void setup(){ rule.addWarClass(MyOtherClass.class); } @Test public void myTest() { //Go! } } {code} > Replace Testrunner with a JUnit-Rule > ------------------------------------ > > Key: ARQ-1828 > URL: https://issues.jboss.org/browse/ARQ-1828 > Project: Arquillian > Issue Type: Feature Request > Reporter: Niels Niels > > At the moment all tests must run with > @RunWith(Arquillian.class) > This makes trouble if you need a runner with add or remove tests like Parameterized. I can't see what Arquillian.class do which can not be done with a JUnit-Rule. JUnit-Rules can be easily combined. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-231) consider usage of javascript compressor/optimizer

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-231?page=com.atlassian.jira.plugin... ] Lukáš Fryč resolved ARQGRA-231. ------------------------------- Resolution: Deferred Fix Version/s: (was: 2.1-Tracking) > consider usage of javascript compressor/optimizer > ------------------------------------------------- > > Key: ARQGRA-231 > URL: https://issues.jboss.org/browse/ARQGRA-231 > Project: Arquillian Graphene > Issue Type: Enhancement > Reporter: Jan Papousek > > Javascript source executed on AndroidDriver can't contain line breaks, so they have to be eliminated. Consider the utility class for removing comments, line breaks and other optimization. > This issue should overcome upstream issue http://code.google.com/p/selenium/issues/detail?id=4816 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-361) Reimplement WebElement/PageFragment/ElementWrapper Enrichers to have one enrichment base which delegates to factories

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-361?page=com.atlassian.jira.plugin... ] Lukáš Fryč resolved ARQGRA-361. ------------------------------- Resolution: Deferred Fix Version/s: (was: 2.1-Tracking) > Reimplement WebElement/PageFragment/ElementWrapper Enrichers to have one enrichment base which delegates to factories > --------------------------------------------------------------------------------------------------------------------- > > Key: ARQGRA-361 > URL: https://issues.jboss.org/browse/ARQGRA-361 > Project: Arquillian Graphene > Issue Type: Bug > Reporter: Lukáš Fryč > > All of these enrichers scans for FindBy annotations: > * [WebElementEnricher|https://github.com/arquillian/arquillian-graphene/blob...] > * [PageFragmentEnricher|https://github.com/arquillian/arquillian-graphene/bl...] > * [WebElementWrapperEnricher|https://github.com/arquillian/arquillian-graphe...] > That leads into disambiguity since the solution is not readable. It also brings code duplication. > ---- > The suggested refactoring should lead into one enricher, which delegates to particular factories. > It will evaluate which type of injection should happen: > * interface / abstract class (needs to check newly created registry for implementation) > ** this is suitable for WebElement or GrapheneElement injections (GrapheneElement needs to be refactored to interface) > ** it's also case of page fragments with interface and implementation > * element wrapper: MyWrapper(WebElement) > ** this is case of e.g. Select(WebElement) > * page fragment implementation > When interface / abstract class doesn't find suitable implementation or it is a final class, exception should be thrown. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-280) Refactor handling of staleness to improve performance

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-280?page=com.atlassian.jira.plugin... ] Lukáš Fryč resolved ARQGRA-280. ------------------------------- Resolution: Deferred Fix Version/s: (was: 2.1-Tracking) > Refactor handling of staleness to improve performance > ----------------------------------------------------- > > Key: ARQGRA-280 > URL: https://issues.jboss.org/browse/ARQGRA-280 > Project: Arquillian Graphene > Issue Type: Task > Affects Versions: 2.0.0.Alpha3 > Reporter: Jan Papousek > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > The current situation of handling staleness is it works purely accidentally in some cases and it prevents any caching of web elements. > Imagine the following code: > {code} > Action action = new Actions(driver).moveToElement(element).build(); > ... // some action causing staleness > action.perform(); > {code} > The previous code doesn't throw StaleElementReferenceException only in the case when the action causing staleness finishes before the requested action starts performing and when there is no caching of web elements. Currently Graphene can't force the action to perform again when StaleElementReferenceException is thrown. > In the case of caching the scenerio would be: > # element is loaded and put to the cache > # ... some actions ... > # action causing staleness is performed > # the requested action starts performing > -- cached element is used => StaleElementReferenceException -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-292) Extend fluent wating API to support page fragments

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-292?page=com.atlassian.jira.plugin... ] Lukáš Fryč resolved ARQGRA-292. ------------------------------- Resolution: Deferred Fix Version/s: (was: 2.1-Tracking) > Extend fluent wating API to support page fragments > -------------------------------------------------- > > Key: ARQGRA-292 > URL: https://issues.jboss.org/browse/ARQGRA-292 > Project: Arquillian Graphene > Issue Type: Feature Request > Affects Versions: 2.0.0.Alpha4 > Reporter: Jan Papousek > > Provide reasonable interfaces for page fragments to be able to extend fluent API for them, e.g. _Visible_: > {code} > Visible pf = ...; > Graphene.waitAjax().until().pageFragment(pf).is().visible(); > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-314) Allow to reuse jQuery from the page for speeding up jquery location strategy

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-314?page=com.atlassian.jira.plugin... ] Lukáš Fryč resolved ARQGRA-314. ------------------------------- Resolution: Deferred Fix Version/s: (was: 2.1-Tracking) > Allow to reuse jQuery from the page for speeding up jquery location strategy > ---------------------------------------------------------------------------- > > Key: ARQGRA-314 > URL: https://issues.jboss.org/browse/ARQGRA-314 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Lukáš Fryč > > Currently JQuery needs to be checked for presense in the page and then injected when necessary to Graphene.jQuery object. > However we should allow to reuse jQuery and fall back to using own one when necessary. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-117) Create JBoss Forge plugin for Graphene

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-117?page=com.atlassian.jira.plugin... ] Lukáš Fryč resolved ARQGRA-117. ------------------------------- Resolution: Deferred Fix Version/s: (was: 2.1-Tracking) > Create JBoss Forge plugin for Graphene > -------------------------------------- > > Key: ARQGRA-117 > URL: https://issues.jboss.org/browse/ARQGRA-117 > Project: Arquillian Graphene > Issue Type: Task > Components: integration > Reporter: Lukáš Fryč > Priority: Critical > Labels: devconf > > This could be rather Arquillian/Drone plugin. > Requirements: > * scaffolding new Graphene project > * start remote selenium server (ARQ-1032) > * ability to export @Deployment > ** the export of deployment is afaik done in Arquillian Forge plugin > * ability to deploy @Deployment (export + deploy) (ARQGRA-213) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-196) Retrieve text/attribute of an element with @FindBy annotated fields of alternative types

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-196?page=com.atlassian.jira.plugin... ] Lukáš Fryč resolved ARQGRA-196. ------------------------------- Resolution: Deferred Fix Version/s: (was: 2.1-Tracking) > Retrieve text/attribute of an element with @FindBy annotated fields of alternative types > ---------------------------------------------------------------------------------------- > > Key: ARQGRA-196 > URL: https://issues.jboss.org/browse/ARQGRA-196 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.0.Alpha2 > Reporter: Aslak Knutsen > > {code} > @FindBy(xpath = "//a[@id='name']") > private String name; > {code} > When annotating a field of type String a WebElement.getText could be automatically invoked and the result set on the field. > Other possible supported types could be: Integer, int, Boolean, Date? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues September 2014