February 2014 - arquillian-issues

[JBoss JIRA] (ARQGRA-422) Regression in request guard

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-422?page=com.atlassian.jira.plugin... ] Work on ARQGRA-422 started by Lukáš Fryč. > Regression in request guard > --------------------------- > > Key: ARQGRA-422 > URL: https://issues.jboss.org/browse/ARQGRA-422 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.1.Final > Environment: RichFaces 5.0.0-SNAPSHOT > Arquillian Core 1.1.2.Final > Arquillian Drone 1.2.3.Final > Arquillian Graphene 2.0.1.Final > Selenium 2.39.0 > Reporter: Pavol Pitonak > Assignee: Lukáš Fryč > > I have a simple page with two inputs, a submit button and two notify messages (one for each input) - > https://github.com/richfaces/richfaces-qa/blob/requestGuardReproducer/met... > When you guard ajax request when button is clicked, it fails with timeout: > {code} > org.openqa.selenium.TimeoutException: Timed out after 2 seconds waiting for org.jboss.arquillian.graphene.guard.RequestGuardFactory$RequestIsDone@19eda624 > {code} > * when you run test (in Steps to Reproduce) all three tests fail on request guard (guarding Ajax request) > * it doesn't matter how WebElement is obtained (WebDriver.find, \@FindBy or \@Page > * these tests fail only when two validation errors are on page, i.e. when two notifyMessage components are displayed > ** e.g. change value of second input from 888 to 8 in guardReproducer.xhtml and it will work > * worked fine with Graphene 2.0.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-422) Regression in request guard

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-422?page=com.atlassian.jira.plugin... ] Lukáš Fryč reassigned ARQGRA-422: --------------------------------- Assignee: Lukáš Fryč > Regression in request guard > --------------------------- > > Key: ARQGRA-422 > URL: https://issues.jboss.org/browse/ARQGRA-422 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.1.Final > Environment: RichFaces 5.0.0-SNAPSHOT > Arquillian Core 1.1.2.Final > Arquillian Drone 1.2.3.Final > Arquillian Graphene 2.0.1.Final > Selenium 2.39.0 > Reporter: Pavol Pitonak > Assignee: Lukáš Fryč > > I have a simple page with two inputs, a submit button and two notify messages (one for each input) - > https://github.com/richfaces/richfaces-qa/blob/requestGuardReproducer/met... > When you guard ajax request when button is clicked, it fails with timeout: > {code} > org.openqa.selenium.TimeoutException: Timed out after 2 seconds waiting for org.jboss.arquillian.graphene.guard.RequestGuardFactory$RequestIsDone@19eda624 > {code} > * when you run test (in Steps to Reproduce) all three tests fail on request guard (guarding Ajax request) > * it doesn't matter how WebElement is obtained (WebDriver.find, \@FindBy or \@Page > * these tests fail only when two validation errors are on page, i.e. when two notifyMessage components are displayed > ** e.g. change value of second input from 888 to 8 in guardReproducer.xhtml and it will work > * worked fine with Graphene 2.0.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-422) Regression in request guard

by Pavol Pitonak (JIRA)

Pavol Pitonak created ARQGRA-422: ------------------------------------ Summary: Regression in request guard Key: ARQGRA-422 URL: https://issues.jboss.org/browse/ARQGRA-422 Project: Arquillian Graphene Issue Type: Bug Components: core Affects Versions: 2.0.1.Final Environment: RichFaces 5.0.0-SNAPSHOT Arquillian Core 1.1.2.Final Arquillian Drone 1.2.3.Final Arquillian Graphene 2.0.1.Final Selenium 2.39.0 Reporter: Pavol Pitonak I have a simple page with two inputs, a submit button and two notify messages (one for each input) - https://github.com/richfaces/richfaces-qa/blob/requestGuardReproducer/met... When you guard ajax request when button is clicked, it fails with timeout: {code} org.openqa.selenium.TimeoutException: Timed out after 2 seconds waiting for org.jboss.arquillian.graphene.guard.RequestGuardFactory$RequestIsDone@19eda624 {code} * when you run test (in Steps to Reproduce) all three tests fail on request guard (guarding Ajax request) * it doesn't matter how WebElement is obtained (WebDriver.find, \@FindBy or \@Page * these tests fail only when two validation errors are on page, i.e. when two notifyMessage components are displayed ** e.g. change value of second input from 888 to 8 in guardReproducer.xhtml and it will work * worked fine with Graphene 2.0.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-628) Tomcat managed throws NullPointerException when application under test brings weld-servlet dependency

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-628?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen updated ARQ-628: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: tomcat_1.0.0.Final Resolution: Done > Tomcat managed throws NullPointerException when application under test brings weld-servlet dependency > ----------------------------------------------------------------------------------------------------- > > Key: ARQ-628 > URL: https://issues.jboss.org/browse/ARQ-628 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR2 > Environment: tomcat-managed-7 > application - richfaces-showcase-4.1.0-20111011-M3-tomcat6.war > Reporter: Juraj Húska > Fix For: tomcat_1.0.0.Final > > > I have encountered this issue when I was testing richfaces-showcase application. It seems that tomcat-managed-7 has problem with applications which bring own weld-servlet dependency. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1650) Managed container bypasses tomcat jul setup

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1650?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen resolved ARQ-1650. -------------------------------- Resolution: Done pushed upstream https://github.com/arquillian/arquillian-container-tomcat/commit/b0bca68d... > Managed container bypasses tomcat jul setup > ------------------------------------------- > > Key: ARQ-1650 > URL: https://issues.jboss.org/browse/ARQ-1650 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR5 > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: tomcat_1.0.0.Final > > > This code from the catalina startup script is not done in the manged deployable container > {code} > # Set juli LogManager config file if it is present and an override has not been issued > if [ -z "$LOGGING_CONFIG" ]; then > if [ -r "$CATALINA_BASE"/conf/logging.properties ]; then > LOGGING_CONFIG="-Djava.util.logging.config.file=$CATALINA_BASE/conf/logging.properties" > else > # Bugzilla 45585 > LOGGING_CONFIG="-Dnop" > fi > fi > if [ -z "$LOGGING_MANAGER" ]; then > LOGGING_MANAGER="-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager" > fi > {code} > As a result, tomcat logging does not work -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1652) Cannot auto install arquillian-bundle on windows

by Thomas Diesler (JIRA)

Thomas Diesler created ARQ-1652: ----------------------------------- Summary: Cannot auto install arquillian-bundle on windows Key: ARQ-1652 URL: https://issues.jboss.org/browse/ARQ-1652 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: OSGi Containers Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: osgi_2.0.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1071) NullPointerException when timeout is set in @Test when using JUnit

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1071?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen edited comment on ARQ-1071 at 2/19/14 9:43 AM: ------------------------------------------------------------- ReOpened since applied fix was causing multiple other problems and has been reverted. (ARQ-1458 ) was (Author: aslak): ReOpened since applied fix was causing multiple other problems and has been reverted. > NullPointerException when timeout is set in @Test when using JUnit > ------------------------------------------------------------------ > > Key: ARQ-1071 > URL: https://issues.jboss.org/browse/ARQ-1071 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.0.Final, 1.0.1.Final > Reporter: Rick-Rainer Ludwig > > When defining a timeout in @Test of JUnit Arquillian throws a NullPointerException: > {code} > java.lang.NullPointerException > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) > at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOfTimeout.java:62) > {code} > The code to reproduce this: > {code} > import org.jboss.arquillian.junit.Arquillian; > import org.junit.Test; > import org.junit.runner.RunWith; > @RunWith(Arquillian.class) > public class TestTimeout { > @Test(timeout = 3000) > public void test() throws Exception { > Thread.sleep(1000); > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1071) NullPointerException when timeout is set in @Test when using JUnit

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1071?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1071: ------------------------------- Affects Version/s: 1.1.3.Final > NullPointerException when timeout is set in @Test when using JUnit > ------------------------------------------------------------------ > > Key: ARQ-1071 > URL: https://issues.jboss.org/browse/ARQ-1071 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.0.Final, 1.0.1.Final, 1.1.3.Final > Reporter: Rick-Rainer Ludwig > > When defining a timeout in @Test of JUnit Arquillian throws a NullPointerException: > {code} > java.lang.NullPointerException > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) > at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOfTimeout.java:62) > {code} > The code to reproduce this: > {code} > import org.jboss.arquillian.junit.Arquillian; > import org.junit.Test; > import org.junit.runner.RunWith; > @RunWith(Arquillian.class) > public class TestTimeout { > @Test(timeout = 3000) > public void test() throws Exception { > Thread.sleep(1000); > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1071) NullPointerException when timeout is set in @Test when using JUnit

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1071?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen commented on ARQ-1071: ------------------------------------ ReOpened since applied fix was causing multiple other problems and has been reverted. > NullPointerException when timeout is set in @Test when using JUnit > ------------------------------------------------------------------ > > Key: ARQ-1071 > URL: https://issues.jboss.org/browse/ARQ-1071 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.0.Final, 1.0.1.Final > Reporter: Rick-Rainer Ludwig > > When defining a timeout in @Test of JUnit Arquillian throws a NullPointerException: > {code} > java.lang.NullPointerException > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) > at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOfTimeout.java:62) > {code} > The code to reproduce this: > {code} > import org.jboss.arquillian.junit.Arquillian; > import org.junit.Test; > import org.junit.runner.RunWith; > @RunWith(Arquillian.class) > public class TestTimeout { > @Test(timeout = 3000) > public void test() throws Exception { > Thread.sleep(1000); > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1071) NullPointerException when timeout is set in @Test when using JUnit

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1071?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1071: ------------------------------- Fix Version/s: (was: 1.0.4.Final) > NullPointerException when timeout is set in @Test when using JUnit > ------------------------------------------------------------------ > > Key: ARQ-1071 > URL: https://issues.jboss.org/browse/ARQ-1071 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.0.Final, 1.0.1.Final > Reporter: Rick-Rainer Ludwig > > When defining a timeout in @Test of JUnit Arquillian throws a NullPointerException: > {code} > java.lang.NullPointerException > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) > at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOfTimeout.java:62) > {code} > The code to reproduce this: > {code} > import org.jboss.arquillian.junit.Arquillian; > import org.junit.Test; > import org.junit.runner.RunWith; > @RunWith(Arquillian.class) > public class TestTimeout { > @Test(timeout = 3000) > public void test() throws Exception { > Thread.sleep(1000); > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues February 2014