January 2017 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-2012) Warnings when test runs as client without @RunAsClient

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2012?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak resolved ARQ-2012. --------------------------------- Fix Version/s: 1.1.12.Final Resolution: Done > Warnings when test runs as client without @RunAsClient > ------------------------------------------------------ > > Key: ARQ-2012 > URL: https://issues.jboss.org/browse/ARQ-2012 > Project: Arquillian > Issue Type: Bug > Components: Deployable Containers SPI > Affects Versions: 1.1.11.Final > Reporter: Ladislav Thon > Assignee: Matous Jobanek > Fix For: 1.1.12.Final > > > When I moved to Arquillian 1.1.11.Final, I started getting warnings when my tests run as client but don't use the {{@RunAsClient}} annotation. The cause is ARQ-1937. > I'll just reiterate that I actually never ever use the {{@RunAsClient}} annotation because it's superfluous. I simply set my {{@Deployment}} to {{testable = false}} or I have no {{@Deployment}} at all. I do that intentionally and I _expect_ that the test will run as client, so the warning doesn't make much sense for me. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2012) Warnings when test runs as client without @RunAsClient

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2012?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak reopened ARQ-2012: --------------------------------- > Warnings when test runs as client without @RunAsClient > ------------------------------------------------------ > > Key: ARQ-2012 > URL: https://issues.jboss.org/browse/ARQ-2012 > Project: Arquillian > Issue Type: Bug > Components: Deployable Containers SPI > Affects Versions: 1.1.11.Final > Reporter: Ladislav Thon > Assignee: Matous Jobanek > > When I moved to Arquillian 1.1.11.Final, I started getting warnings when my tests run as client but don't use the {{@RunAsClient}} annotation. The cause is ARQ-1937. > I'll just reiterate that I actually never ever use the {{@RunAsClient}} annotation because it's superfluous. I simply set my {{@Deployment}} to {{testable = false}} or I have no {{@Deployment}} at all. I do that intentionally and I _expect_ that the test will run as client, so the warning doesn't make much sense for me. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

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

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2034?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak resolved ARQ-2034. --------------------------------- Resolution: Done > 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 > Fix For: 1.1.12.Final > > > 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 (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

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

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2034?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak updated ARQ-2034: -------------------------------- Fix Version/s: 1.1.12.Final > 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 > Fix For: 1.1.12.Final > > > 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 (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2065) Combine multiple test results

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2065?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak updated ARQ-2065: -------------------------------- Fix Version/s: 1.1.12.Final > Combine multiple test results > ----------------------------- > > Key: ARQ-2065 > URL: https://issues.jboss.org/browse/ARQ-2065 > Project: Arquillian > Issue Type: Feature Request > Components: core > Affects Versions: 1.1.11.Final > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Priority: Minor > Fix For: 1.1.12.Final > > > With the current implementation in place splitting single test in several executions can only happen from within Arquillian events (so we run n tests from within single test). This in particular happens for running contract tests for Pact, where one test spawns several verifications based on the content of the contract itself. > Even though the {{List<TestResult>}} is used as a container object for TestResult instance passed along when Test event is fired, it can happen one test can be fired multiple times (for example in arquillian-algeron). > The temporary solution for this problem could be that all the results are collected into one instance of TestResult. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2067) Can't use the Arquillian Karaf Extension with a remote container

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/ARQ-2067?page=com.atlassian.jira.plugin.s... ] Thomas Diesler closed ARQ-2067. ------------------------------- Resolution: Rejected > Can't use the Arquillian Karaf Extension with a remote container > ---------------------------------------------------------------- > > Key: ARQ-2067 > URL: https://issues.jboss.org/browse/ARQ-2067 > Project: Arquillian > Issue Type: Bug > Components: OSGi Containers > Affects Versions: osgi_2.1.0.Final > Reporter: Cristina González castellano > > I have been trying to use the Arquillian OSGi extension with a Docker container, but I have found the next issue: > - When we use JMXDeployableContainer, to deploy a OSGi Bundle to a remote OSGi Karaf, we use a local URL, of the type: file:/var/folders/nq/p1_j3ycj169dzl1ypg8d5zhh0000gn/T/vfs/osgitmp-8888e08d9dca9b47/urlstream-d8ff47698b0d2150/253ae58a-4ad3-4077-b049-281ef1b9d3eb.jar. > - Of course this URL doesn't exist in the remote Docker container. > - So I get the exception: > Caused by: java.io.IOException: Installation of a bundle with location 253ae58a-4ad3-4077-b049-281ef1b9d3eb.jar failed with the message: /var/folders/nq/p1_j3ycj169dzl1ypg8d5zhh0000gn/T/vfs/osgitmp-8888e08d9dca9b47/urlstream-d8ff47698b0d2150/253ae58a-4ad3-4077-b049-281ef1b9d3eb.jar (No such file or directory) > Have you faced this issue before? What do you think is the best solution? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2067) Can't use the Arquillian Karaf Extension with a remote container

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/ARQ-2067?page=com.atlassian.jira.plugin.s... ] Thomas Diesler reassigned ARQ-2067: ----------------------------------- Assignee: (was: Thomas Diesler) We have no plans to support in-container testing with Docker. > Can't use the Arquillian Karaf Extension with a remote container > ---------------------------------------------------------------- > > Key: ARQ-2067 > URL: https://issues.jboss.org/browse/ARQ-2067 > Project: Arquillian > Issue Type: Bug > Components: OSGi Containers > Affects Versions: osgi_2.1.0.Final > Reporter: Cristina González castellano > > I have been trying to use the Arquillian OSGi extension with a Docker container, but I have found the next issue: > - When we use JMXDeployableContainer, to deploy a OSGi Bundle to a remote OSGi Karaf, we use a local URL, of the type: file:/var/folders/nq/p1_j3ycj169dzl1ypg8d5zhh0000gn/T/vfs/osgitmp-8888e08d9dca9b47/urlstream-d8ff47698b0d2150/253ae58a-4ad3-4077-b049-281ef1b9d3eb.jar. > - Of course this URL doesn't exist in the remote Docker container. > - So I get the exception: > Caused by: java.io.IOException: Installation of a bundle with location 253ae58a-4ad3-4077-b049-281ef1b9d3eb.jar failed with the message: /var/folders/nq/p1_j3ycj169dzl1ypg8d5zhh0000gn/T/vfs/osgitmp-8888e08d9dca9b47/urlstream-d8ff47698b0d2150/253ae58a-4ad3-4077-b049-281ef1b9d3eb.jar (No such file or directory) > Have you faced this issue before? What do you think is the best solution? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1264) Drone: provide Chrome driver binary from Maven

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQ-1264?page=com.atlassian.jira.plugin.s... ] Matous Jobanek updated ARQ-1264: -------------------------------- Fix Version/s: (was: drone_2.1.0.Final) > Drone: provide Chrome driver binary from Maven > ---------------------------------------------- > > Key: ARQ-1264 > URL: https://issues.jboss.org/browse/ARQ-1264 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Reporter: Lukáš Fryč > Assignee: Matous Jobanek > Labels: usability > > It should be packaged in JAR and installed to drive similarly how we do it with PhantomJS. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1264) Drone: provide Chrome driver binary from Maven

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQ-1264?page=com.atlassian.jira.plugin.s... ] Matous Jobanek reopened ARQ-1264: --------------------------------- > Drone: provide Chrome driver binary from Maven > ---------------------------------------------- > > Key: ARQ-1264 > URL: https://issues.jboss.org/browse/ARQ-1264 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Reporter: Lukáš Fryč > Assignee: Matous Jobanek > Labels: usability > > It should be packaged in JAR and installed to drive similarly how we do it with PhantomJS. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1826) Download Explorer binary for Drone

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQ-1826?page=com.atlassian.jira.plugin.s... ] Matous Jobanek resolved ARQ-1826. --------------------------------- Resolution: Done Is part of the whole Spacelift solution: https://github.com/arquillian/arquillian-extension-drone/commit/fb36d41af... > Download Explorer binary for Drone > ---------------------------------- > > Key: ARQ-1826 > URL: https://issues.jboss.org/browse/ARQ-1826 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Matous Jobanek > Fix For: drone_2.1.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 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 2017