July 2016 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-2038) Create Drone extension for Appium

by vinoth selvaraj (JIRA)

vinoth selvaraj created ARQ-2038: ------------------------------------ Summary: Create Drone extension for Appium Key: ARQ-2038 URL: https://issues.jboss.org/browse/ARQ-2038 Project: Arquillian Issue Type: Feature Request Components: Extension - Drone Reporter: vinoth selvaraj Appium is becoming an industry standard for mobile testing. Many large companies like Amazon, Zameron, Perfecto Mobile and others decided to put Appium into their clouds. Appium supports both andriod and ios automation. It would be nice to have a drone-extension for Appium. More Info on appium: *https://github.com/appium/appium* -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2037) Support additional browser capabilities for Chrome

by Matous Jobanek (JIRA)

Matous Jobanek created ARQ-2037: ----------------------------------- Summary: Support additional browser capabilities for Chrome Key: ARQ-2037 URL: https://issues.jboss.org/browse/ARQ-2037 Project: Arquillian Issue Type: Feature Request Components: Extension - Drone Affects Versions: drone_2.0.0.Final Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: drone_2.1.0.Final Support additional browser capabilities for Chrome & remove obsolete solution that uses chrome.switches https://github.com/arquillian/arquillian-extension-drone/blob/master/dron... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2034) Test enrichment and JUnit @Rule do not harmonize

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQ-2034?page=com.atlassian.jira.plugin.s... ] Matous Jobanek updated ARQ-2034: -------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-core/pull/110 > Test enrichment and JUnit @Rule do not harmonize > ------------------------------------------------ > > Key: ARQ-2034 > URL: https://issues.jboss.org/browse/ARQ-2034 > Project: Arquillian > Issue Type: Bug > Components: Base Implementation > Affects Versions: 1.1.11.Final > Environment: junit 4.11 > arquillian-junit-container 1.1.11.Final > wildfly-arquillian-container-remote 8.1.0.Final > Reporter: Björn Kautler > Assignee: Matous Jobanek > > We are starting with Arquillian tests on a remote WildFly instance. > I tried to write a JUnit {{@Rule}}, that can be used to make a login call for all test methods automatically, but I was not yet able to make it work, as I need an injected {{@Ejb}} instance for this. > I tried to add {{@EJB private InterfaceLoginManagement interfaceLoginManagement;}} to the {{TestRule}} implementation, but it stays {{null}}. I've read at ARQ-1954 that this should probably work, but unfortunately it is not, at least not with the remote container runner. {{org.jboss.arquillian.junit.extension.JUnitCoreExtension}} that should register {{org.jboss.arquillian.junit.extension.UpdateTestResultBeforeAfter}} and {{org.jboss.arquillian.junit.RulesEnricher}} is not even loaded on the container side. Maybe the {{META-INF/services/}} file is missing? > Then I tried to simply give the injected instance to the rule from the test class like > {code} > @EJB private InterfaceLoginManagement interfaceLoginManagement; > @Rule private LoginRule loginRule = new LoginRule(interfaceLoginManagement); > {code} > or even > {code} > @EJB private InterfaceLoginManagement interfaceLoginManagement; > @Rule public LoginRule getLoginRule() { > return new LoginRule(() -> { > return interfaceLoginManagement; > }); > } > {code} > with the {{LoginRule}} receiving a {{Supplier<InterfaceLoginManagement>}} and call it as late as possible, i. e. in the rules {{apply()}} method. But even this is still too early as the EJB is still {{null}} and the test enrichers are only run between the {{@Rule}} applying and {{@Before}} methods. > So I'd like to suggest two things: > # Fix the implementation of ARQ-1954 if it should work on container side which I assume it should > # Make the test enrichments earlier in the lifecycle, i. e. before the {{@Rule}} s are being applied, or rather even before the {{@Rule}} methods are called, so that you at least can use the injected instances in the {{@Rule}} annotated methods to forward them to a rule. This is necessary even if top 1 is taken care of, because you might want to use a 3rd Party rule the code of which you cannot change. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2034) Test enrichment and JUnit @Rule do not harmonize

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQ-2034?page=com.atlassian.jira.plugin.s... ] Matous Jobanek commented on ARQ-2034: ------------------------------------- Hi, good catch. Here is the fix https://github.com/arquillian/arquillian-core/pull/110 Regarding the second suggestion - I can see your point, but AFAIK this is the first event where I can get a reference to a test instance. There is maybe one possibility, I'll try my best a I'll let you know if I find any feasible solution. > Test enrichment and JUnit @Rule do not harmonize > ------------------------------------------------ > > Key: ARQ-2034 > URL: https://issues.jboss.org/browse/ARQ-2034 > Project: Arquillian > Issue Type: Bug > Components: Base Implementation > Affects Versions: 1.1.11.Final > Environment: junit 4.11 > arquillian-junit-container 1.1.11.Final > wildfly-arquillian-container-remote 8.1.0.Final > Reporter: Björn Kautler > Assignee: Matous Jobanek > > We are starting with Arquillian tests on a remote WildFly instance. > I tried to write a JUnit {{@Rule}}, that can be used to make a login call for all test methods automatically, but I was not yet able to make it work, as I need an injected {{@Ejb}} instance for this. > I tried to add {{@EJB private InterfaceLoginManagement interfaceLoginManagement;}} to the {{TestRule}} implementation, but it stays {{null}}. I've read at ARQ-1954 that this should probably work, but unfortunately it is not, at least not with the remote container runner. {{org.jboss.arquillian.junit.extension.JUnitCoreExtension}} that should register {{org.jboss.arquillian.junit.extension.UpdateTestResultBeforeAfter}} and {{org.jboss.arquillian.junit.RulesEnricher}} is not even loaded on the container side. Maybe the {{META-INF/services/}} file is missing? > Then I tried to simply give the injected instance to the rule from the test class like > {code} > @EJB private InterfaceLoginManagement interfaceLoginManagement; > @Rule private LoginRule loginRule = new LoginRule(interfaceLoginManagement); > {code} > or even > {code} > @EJB private InterfaceLoginManagement interfaceLoginManagement; > @Rule public LoginRule getLoginRule() { > return new LoginRule(() -> { > return interfaceLoginManagement; > }); > } > {code} > with the {{LoginRule}} receiving a {{Supplier<InterfaceLoginManagement>}} and call it as late as possible, i. e. in the rules {{apply()}} method. But even this is still too early as the EJB is still {{null}} and the test enrichers are only run between the {{@Rule}} applying and {{@Before}} methods. > So I'd like to suggest two things: > # Fix the implementation of ARQ-1954 if it should work on container side which I assume it should > # Make the test enrichments earlier in the lifecycle, i. e. before the {{@Rule}} s are being applied, or rather even before the {{@Rule}} methods are called, so that you at least can use the injected instances in the {{@Rule}} annotated methods to forward them to a rule. This is necessary even if top 1 is taken care of, because you might want to use a 3rd Party rule the code of which you cannot change. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2034) Test enrichment and JUnit @Rule do not harmonize

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQ-2034?page=com.atlassian.jira.plugin.s... ] Matous Jobanek reassigned ARQ-2034: ----------------------------------- Assignee: Matous Jobanek > Test enrichment and JUnit @Rule do not harmonize > ------------------------------------------------ > > Key: ARQ-2034 > URL: https://issues.jboss.org/browse/ARQ-2034 > Project: Arquillian > Issue Type: Bug > Components: Base Implementation > Affects Versions: 1.1.11.Final > Environment: junit 4.11 > arquillian-junit-container 1.1.11.Final > wildfly-arquillian-container-remote 8.1.0.Final > Reporter: Björn Kautler > Assignee: Matous Jobanek > > We are starting with Arquillian tests on a remote WildFly instance. > I tried to write a JUnit {{@Rule}}, that can be used to make a login call for all test methods automatically, but I was not yet able to make it work, as I need an injected {{@Ejb}} instance for this. > I tried to add {{@EJB private InterfaceLoginManagement interfaceLoginManagement;}} to the {{TestRule}} implementation, but it stays {{null}}. I've read at ARQ-1954 that this should probably work, but unfortunately it is not, at least not with the remote container runner. {{org.jboss.arquillian.junit.extension.JUnitCoreExtension}} that should register {{org.jboss.arquillian.junit.extension.UpdateTestResultBeforeAfter}} and {{org.jboss.arquillian.junit.RulesEnricher}} is not even loaded on the container side. Maybe the {{META-INF/services/}} file is missing? > Then I tried to simply give the injected instance to the rule from the test class like > {code} > @EJB private InterfaceLoginManagement interfaceLoginManagement; > @Rule private LoginRule loginRule = new LoginRule(interfaceLoginManagement); > {code} > or even > {code} > @EJB private InterfaceLoginManagement interfaceLoginManagement; > @Rule public LoginRule getLoginRule() { > return new LoginRule(() -> { > return interfaceLoginManagement; > }); > } > {code} > with the {{LoginRule}} receiving a {{Supplier<InterfaceLoginManagement>}} and call it as late as possible, i. e. in the rules {{apply()}} method. But even this is still too early as the EJB is still {{null}} and the test enrichers are only run between the {{@Rule}} applying and {{@Before}} methods. > So I'd like to suggest two things: > # Fix the implementation of ARQ-1954 if it should work on container side which I assume it should > # Make the test enrichments earlier in the lifecycle, i. e. before the {{@Rule}} s are being applied, or rather even before the {{@Rule}} methods are called, so that you at least can use the injected instances in the {{@Rule}} annotated methods to forward them to a rule. This is necessary even if top 1 is taken care of, because you might want to use a 3rd Party rule the code of which you cannot change. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1657) Inconsistency in usage of @OperateOnDeployment and OperatesOnDeployment

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1657?page=com.atlassian.jira.plugin.s... ] Karel Piwko closed ARQ-1657. ---------------------------- Resolution: Won't Fix > Inconsistency in usage of @OperateOnDeployment and OperatesOnDeployment > ----------------------------------------------------------------------- > > Key: ARQ-1657 > URL: https://issues.jboss.org/browse/ARQ-1657 > Project: Arquillian > Issue Type: Enhancement > Components: Base Implementation > Affects Versions: 1.1.3.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Minor > > In the past, @OperatesOnDeployment was renamed to @OperateOnDeployment. However, not all occurences of @OperatesOnDeployment were removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1657) Inconsistency in usage of @OperateOnDeployment and OperatesOnDeployment

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1657?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1657: ----------------------------- Status: Open (was: Pull Request Sent) > Inconsistency in usage of @OperateOnDeployment and OperatesOnDeployment > ----------------------------------------------------------------------- > > Key: ARQ-1657 > URL: https://issues.jboss.org/browse/ARQ-1657 > Project: Arquillian > Issue Type: Enhancement > Components: Base Implementation > Affects Versions: 1.1.3.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Minor > > In the past, @OperatesOnDeployment was renamed to @OperateOnDeployment. However, not all occurences of @OperatesOnDeployment were removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1470) Improve warning message for overriding browser

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1470?page=com.atlassian.jira.plugin.s... ] Karel Piwko closed ARQ-1470. ---------------------------- > Improve warning message for overriding browser > ---------------------------------------------- > > Key: ARQ-1470 > URL: https://issues.jboss.org/browse/ARQ-1470 > Project: Arquillian > Issue Type: Bug > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Minor > Fix For: drone_1.2.0.Beta2 > > > Current message about Arquillian configuration being ignored if "browser" property does not match Java type is confusing. > Configuration is not ignored, it's only browser property which is not honored. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1785) Update Selenium to 2.42.0

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1785?page=com.atlassian.jira.plugin.s... ] Karel Piwko closed ARQ-1785. ---------------------------- > Update Selenium to 2.42.0 > ------------------------- > > Key: ARQ-1785 > URL: https://issues.jboss.org/browse/ARQ-1785 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Drone > Affects Versions: drone_1.3.0.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.3.1.Final > > > Update to recent Selenium -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1469) Improve logging for AbstractWebDriverFactory

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1469?page=com.atlassian.jira.plugin.s... ] Karel Piwko closed ARQ-1469. ---------------------------- > Improve logging for AbstractWebDriverFactory > -------------------------------------------- > > Key: ARQ-1469 > URL: https://issues.jboss.org/browse/ARQ-1469 > Project: Arquillian > Issue Type: Bug > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Minor > Fix For: drone_1.2.0.Beta2 > > > Drone currently does not print available implementation classes when FINE level is enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues July 2016