March 2016 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1952) Warp requests hit the application port instead of LittleProxy`s one

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1952?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč reassigned ARQ-1952: ------------------------------- Assignee: (was: Lukáš Fryč) > Warp requests hit the application port instead of LittleProxy`s one > ------------------------------------------------------------------- > > Key: ARQ-1952 > URL: https://issues.jboss.org/browse/ARQ-1952 > Project: Arquillian > Issue Type: Bug > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, warp_1.0.0.Beta1 > Environment: Linux x64, ChromeDriver , PhantomJSDriver, Wildfly 8.0 & 8.2, Mojarra 2.8 & 2.11 > Reporter: Pëtr Andreev > Fix For: warp_1.0.0.Beta1 > > Attachments: ARQ-1952-failure.log, ARQ-1952-success.log > > > Warp observer intermittently fails while inspecting the requests with: > "There were no requests matched by observer \[containsParameter(XXXX)\] ". > The technical reason for the failure is that the client request hits the original (application server) port and not the [LittleProxy`s|https://github.com/adamfisk/LittleProxy] one (HTTP successful and failed traffic is attached showing the HTTP requests going to the wrong port, i.e 8080). Since Warp hooks into the client/server conversation providing its own implementation of _HttpFiltersSourceAdapter_ in _DefaultHttpFiltersSource_, while expecting the payload request from client after setting up a WarpContext, the Warp runs into timeout because of the HTTP request never reaches the LittleProxy. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-2018) Upgrade Karaf to latest release for arquillian-container-karaf-managed

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/ARQ-2018?page=com.atlassian.jira.plugin.s... ] Thomas Diesler closed ARQ-2018. ------------------------------- Resolution: Duplicate Issue Duplicates ARQ-2019 > Upgrade Karaf to latest release for arquillian-container-karaf-managed > ---------------------------------------------------------------------- > > Key: ARQ-2018 > URL: https://issues.jboss.org/browse/ARQ-2018 > Project: Arquillian > Issue Type: Enhancement > Components: OSGi Containers > Affects Versions: osgi_2.1.0.Final > Reporter: Steve Storck > > The current version of the managed Karaf container is 2.3.3. This was released in 2013, so it is quite outdated. The latest release is 4.0.4, which was released in early 2016. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQRUSH-26) Support detection of changes in cases and tests (removals, additions, modifications)

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQRUSH-26?page=com.atlassian.jira.plugin... ] Lukáš Fryč reassigned ARQRUSH-26: --------------------------------- Assignee: (was: Lukáš Fryč) > Support detection of changes in cases and tests (removals, additions, modifications) > ------------------------------------------------------------------------------------ > > Key: ARQRUSH-26 > URL: https://issues.jboss.org/browse/ARQRUSH-26 > Project: Arquillian RushEye > Issue Type: Feature Request > Components: Core, Manager > Reporter: Lukáš Fryč > Fix For: 1.0.0.Alpha1 > > > {quote} > T 1341996997 31<lfryc>30 (5) problem of changes in test suite > T 1341997028 31<lfryc>30 basically what to do when "screenshots1" and "screenshots2" differs > T 1341997042 31<lfryc>30 in case of: > T 1341997047 31<lfryc>30 a) test additions > T 1341997050 31<lfryc>30 b) test removals > T 1341997055 31<lfryc>30 c) test modifications > T 1341997087 31<lfryc>30 the Manager should inteligently show the test case with matching images > T 1341997100 31<lfryc>30 and even allow context-menu resolution > T 1341997163 31<lfryc>30 we are currently investigating what's the stability of test suite (if the list of images doesn't differ between runs) > T 1341997163 18<fafnir88> if there is no corresponding image for test, this big image warning will be shown > T 1341997204 31<lfryc>30 yeah, this would need to be more smart.. > T 1341997220 31<lfryc>30 let's see this case, you get those tests (images): > T 1341997248 31<lfryc>30 00-open > T 1341997248 31<lfryc>30 01-click > T 1341997248 31<lfryc>30 02-click > T 1341997248 31<lfryc>30 03-type > T 1341997248 31<lfryc>30 04-click > T 1341997248 31<lfryc>30 05-click > T 1341997274 31<lfryc>30 but then you get other just those: > T 1341997279 31<lfryc>30 00-open > T 1341997283 31<lfryc>30 01-click > T 1341997285 31<lfryc>30 03-type > T 1341997304 31<lfryc>30 those images identifies all changes during the automated browser test > T 1341997316 31<lfryc>30 then you have problem > T 1341997321 31<lfryc>30 (sorry 02-type) > T 1341997337 31<lfryc>30 the Manager could fallback to heuristics > T 1341997359 31<lfryc>30 and in case of the images does not match in suite and samples.. > T 1341997378 18<fafnir88> so, you want to have a test pruning for missing cases? > T 1341997380 31<lfryc>30 it can offer alternative mode, when it could try determine what happened > T 1341997390 18<fafnir88> *test tree > T 1341997394 31<lfryc>30 yep > T 1341997402 31<lfryc>30 it should show something like: > T 1341997407 31<lfryc>30 OK 00-open > T 1341997412 31<lfryc>30 OK 01-click > T 1341997434 31<lfryc>30 02-click (missing sample) > T 1341997445 31<lfryc>30 02-type (missing pattern) > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQRUSH-43) Configure jenkins job running RushEye Core on current samples producing result.xml

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQRUSH-43?page=com.atlassian.jira.plugin... ] Lukáš Fryč reassigned ARQRUSH-43: --------------------------------- Assignee: (was: Lukáš Fryč) > Configure jenkins job running RushEye Core on current samples producing result.xml > ---------------------------------------------------------------------------------- > > Key: ARQRUSH-43 > URL: https://issues.jboss.org/browse/ARQRUSH-43 > Project: Arquillian RushEye > Issue Type: Sub-task > Components: Tests > Reporter: Lukáš Fryč > Fix For: 1.0.0.Alpha1 > > > The task is take the output of job ARQRUSH-42 and run the RushEye Core on it, so producing result.xml. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQRUSH-39) Enhance Positive/Negative buttons

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQRUSH-39?page=com.atlassian.jira.plugin... ] Lukáš Fryč reassigned ARQRUSH-39: --------------------------------- Assignee: (was: Lukáš Fryč) > Enhance Positive/Negative buttons > --------------------------------- > > Key: ARQRUSH-39 > URL: https://issues.jboss.org/browse/ARQRUSH-39 > Project: Arquillian RushEye > Issue Type: Enhancement > Components: Manager > Reporter: Lukáš Fryč > Fix For: 1.0.0.Alpha1 > > > The possitive button should be called "Accept changes". > Negative button can be removed, since its functionality would be duplicated with Next Case / Next Test. > ---- > "Accept changes" will actually act on what is selected: > 1. if Test is selected > * one particular test's pattern is accepted as new pattern, replacing the old one > 2. if Case is selected > * all the changes in underlying Case are accepted (adopted to current suite) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1923) Cannot build Warp 1.0.0.Alpha7 with OpenJDK 8

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1923?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-1923: ---------------------------- Status: Pull Request Sent (was: Open) > Cannot build Warp 1.0.0.Alpha7 with OpenJDK 8 > --------------------------------------------- > > Key: ARQ-1923 > URL: https://issues.jboss.org/browse/ARQ-1923 > Project: Arquillian > Issue Type: Bug > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7 > Reporter: Pavol Pitonak > Fix For: warp_1.0.0.Beta1 > > > # git clone https://github.com/arquillian/arquillian-extension-warp.git > # mvn clean install > result: > * when launched with OpenJDK 8, one test fails TestExecutedMethod.testSerializedAnnotation > {code} > java.lang.IllegalStateException: java.lang.IllegalStateException: Error instantiating proxy for annotation. Annotation type: interface org.jboss.arquillian.warp.impl.shared.TestingAnnotation > at org.jboss.arquillian.warp.impl.shared.SerializedAnnotation.getAnnotation(SerializedAnnotation.java:61) > at org.jboss.arquillian.warp.impl.shared.TestExecutedMethod.testSerializedAnnotation(TestExecutedMethod.java:49) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) > 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) > Caused by: java.lang.IllegalStateException: Error instantiating proxy for annotation. Annotation type: interface org.jboss.arquillian.warp.impl.shared.TestingAnnotation > at org.jboss.arquillian.warp.impl.utils.AnnotationInstanceProvider.get(AnnotationInstanceProvider.java:83) > at org.jboss.arquillian.warp.impl.shared.SerializedAnnotation.getAnnotation(SerializedAnnotation.java:59) > ... 24 more > Caused by: java.lang.IllegalAccessException: Class org.jboss.arquillian.warp.impl.utils.AnnotationInstanceProvider can not access a member of class org.jboss.arquillian.warp.impl.shared.$Proxy5 with modifiers "public" > at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:101) > at java.lang.reflect.AccessibleObject.slowCheckMemberAccess(AccessibleObject.java:295) > at java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:287) > at java.lang.reflect.Constructor.newInstance(Constructor.java:398) > at org.jboss.arquillian.warp.impl.utils.AnnotationInstanceProvider.get(AnnotationInstanceProvider.java:76) > ... 25 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1923) Cannot build Warp 1.0.0.Alpha7 with OpenJDK 8

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1923?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-1923: ---------------------------- Status: Resolved (was: Pull Request Sent) Assignee: Matous Jobanek Resolution: Done > Cannot build Warp 1.0.0.Alpha7 with OpenJDK 8 > --------------------------------------------- > > Key: ARQ-1923 > URL: https://issues.jboss.org/browse/ARQ-1923 > Project: Arquillian > Issue Type: Bug > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7 > Reporter: Pavol Pitonak > Assignee: Matous Jobanek > Fix For: warp_1.0.0.Beta1 > > > # git clone https://github.com/arquillian/arquillian-extension-warp.git > # mvn clean install > result: > * when launched with OpenJDK 8, one test fails TestExecutedMethod.testSerializedAnnotation > {code} > java.lang.IllegalStateException: java.lang.IllegalStateException: Error instantiating proxy for annotation. Annotation type: interface org.jboss.arquillian.warp.impl.shared.TestingAnnotation > at org.jboss.arquillian.warp.impl.shared.SerializedAnnotation.getAnnotation(SerializedAnnotation.java:61) > at org.jboss.arquillian.warp.impl.shared.TestExecutedMethod.testSerializedAnnotation(TestExecutedMethod.java:49) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) > 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) > Caused by: java.lang.IllegalStateException: Error instantiating proxy for annotation. Annotation type: interface org.jboss.arquillian.warp.impl.shared.TestingAnnotation > at org.jboss.arquillian.warp.impl.utils.AnnotationInstanceProvider.get(AnnotationInstanceProvider.java:83) > at org.jboss.arquillian.warp.impl.shared.SerializedAnnotation.getAnnotation(SerializedAnnotation.java:59) > ... 24 more > Caused by: java.lang.IllegalAccessException: Class org.jboss.arquillian.warp.impl.utils.AnnotationInstanceProvider can not access a member of class org.jboss.arquillian.warp.impl.shared.$Proxy5 with modifiers "public" > at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:101) > at java.lang.reflect.AccessibleObject.slowCheckMemberAccess(AccessibleObject.java:295) > at java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:287) > at java.lang.reflect.Constructor.newInstance(Constructor.java:398) > at org.jboss.arquillian.warp.impl.utils.AnnotationInstanceProvider.get(AnnotationInstanceProvider.java:76) > ... 25 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-2013) Update Arquillian, Drone, Resolver, JaCoCo and JUnit to newer version

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-2013?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-2013: ---------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: warp_1.0.0.Beta1 Resolution: Done > Update Arquillian, Drone, Resolver, JaCoCo and JUnit to newer version > --------------------------------------------------------------------- > > Key: ARQ-2013 > URL: https://issues.jboss.org/browse/ARQ-2013 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: warp_1.0.0.Beta1 > > > Please update to newer versions to use the latest and greatest implementations. > In case of JaCoCo - the current version {{0.6.0.201210061924}} is not compatible with JDK8 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-2013) Update Arquillian, Drone, Resolver, JaCoCo and JUnit to newer version

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-2013?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-2013: ---------------------------- Status: Pull Request Sent (was: Open) > Update Arquillian, Drone, Resolver, JaCoCo and JUnit to newer version > --------------------------------------------------------------------- > > Key: ARQ-2013 > URL: https://issues.jboss.org/browse/ARQ-2013 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: warp_1.0.0.Beta1 > > > Please update to newer versions to use the latest and greatest implementations. > In case of JaCoCo - the current version {{0.6.0.201210061924}} is not compatible with JDK8 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-2014) When warp is on classpath then almost every non-warp arquillian test fails

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-2014?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-2014: ---------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: warp_1.0.0.Beta1 Resolution: Done > When warp is on classpath then almost every non-warp arquillian test fails > -------------------------------------------------------------------------- > > Key: ARQ-2014 > URL: https://issues.jboss.org/browse/ARQ-2014 > Project: Arquillian > Issue Type: Bug > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: warp_1.0.0.Beta1 > > > Consider a test suite that contains a warp test (so you need to have the warp dependency on your classpath) and some other non-warp arquillian test. Then the non-warp tests fails with various exceptions depending on the type of the test. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues March 2016