May 2013 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1341) Warp JAX-RS testing

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1341?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on ARQ-1341: --------------------------------- As Aslak [pointed out|https://community.jboss.org/message/809204#809204], the REST extension would be better fit for separate module: {quote} We could put this in the arquillian-extension-rest. What's there now is just an early prototype with very little movement. We could 'move' the master branch to a branch, replace master with warp-rest, then retro fit the old master branch if needed. {quote} What do you think, [~jmnarloch]? > Warp JAX-RS testing > ------------------- > > Key: ARQ-1341 > URL: https://issues.jboss.org/browse/ARQ-1341 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Jakub Narloch > Assignee: Lukáš Fryč > Fix For: warp_1.next > > > Testing JAX-RS compilant REST services through Warp extension. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-274) The request guard does timeout for delayed requests

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-274?page=com.atlassian.jira.plugin... ] Work on ARQGRA-274 started by Lukáš Fryč. > The request guard does timeout for delayed requests > --------------------------------------------------- > > Key: ARQGRA-274 > URL: https://issues.jboss.org/browse/ARQGRA-274 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Alpha3 > Reporter: Bernard Labno > Assignee: Lukáš Fryč > Priority: Critical > Fix For: 2.0.0.Alpha5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > In RichFaces, there is request queue which can delay a processing of an user action which avoids overwhelming communication channel. > This is simply the case where request guard should: > * wait specified timeout (by default type "Ajax" timeout) for user action to start AJAX request (xhr.open) > * then wait another timeout (by default type "Ajax" timeout) for AJAX action to complete the request (xhr.readyState == 4) -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1070) Arquillian JUnit Standalone doesn't execute methods annotated by @Before annotation

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1070?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-1070: ---------------------------- Workaround Description: *You can use {{arquillian-junit-container}} and do not provide {{@Deployment}}* (was: You can use {{arquillian-junit-container}} and do not provide {{@Deployment}}) > Arquillian JUnit Standalone doesn't execute methods annotated by @Before annotation > ----------------------------------------------------------------------------------- > > Key: ARQ-1070 > URL: https://issues.jboss.org/browse/ARQ-1070 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.0.2.Final > Environment: Java(TM) SE Runtime Environment (build 1.7.0_04-b20) > Reporter: Jan Papousek > Labels: junit > Attachments: junit-sample.zip > > > The following test doesn't pass: > {code} > @RunWith(Arquillian.class) > public class AppTest { > private boolean before = false; > @Before > public void before() { > this.before = true; > } > @Test > public void testBefore() { > Assert.assertTrue(before); > } > } > {code} > The same test without @RunWith annotation passes. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1070) Arquillian JUnit Standalone doesn't execute methods annotated by @Before annotation

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1070?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-1070: ---------------------------- Workaround Description: You can use {{arquillian-junit-container}} and do not provide {{@Deployment}} Workaround: Workaround Exists > Arquillian JUnit Standalone doesn't execute methods annotated by @Before annotation > ----------------------------------------------------------------------------------- > > Key: ARQ-1070 > URL: https://issues.jboss.org/browse/ARQ-1070 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.0.2.Final > Environment: Java(TM) SE Runtime Environment (build 1.7.0_04-b20) > Reporter: Jan Papousek > Labels: junit > Attachments: junit-sample.zip > > > The following test doesn't pass: > {code} > @RunWith(Arquillian.class) > public class AppTest { > private boolean before = false; > @Before > public void before() { > this.before = true; > } > @Test > public void testBefore() { > Assert.assertTrue(before); > } > } > {code} > The same test without @RunWith annotation passes. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1391) Proxy port not verified if already in use

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1391?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč resolved ARQ-1391. ----------------------------- Assignee: Lukáš Fryč Resolution: Duplicate Issue > Proxy port not verified if already in use > ----------------------------------------- > > Key: ARQ-1391 > URL: https://issues.jboss.org/browse/ARQ-1391 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: 1.0.0.Alpha2 > Reporter: Bartosz Majsak > Assignee: Lukáš Fryč > > When the 18080 port is already taken (eg. for application server using certain offset, like in my case for AS7 managed), Warp proxy is not checking its' availability, which results in [following exception being thrown|https://gist.github.com/bartoszmajsak/5630321], even if the test is not marked as @WarpTest. > As an improvement we could make it configurable or a bit smarter ;) -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1391) Proxy port not verified if already in use

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1391?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on ARQ-1391: --------------------------------- +1 I would use {{PortProber}} to avoid this issue. The issue is already reported as ARQ-1237. > Proxy port not verified if already in use > ----------------------------------------- > > Key: ARQ-1391 > URL: https://issues.jboss.org/browse/ARQ-1391 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: 1.0.0.Alpha2 > Reporter: Bartosz Majsak > > When the 18080 port is already taken (eg. for application server using certain offset, like in my case for AS7 managed), Warp proxy is not checking its' availability, which results in [following exception being thrown|https://gist.github.com/bartoszmajsak/5630321], even if the test is not marked as @WarpTest. > As an improvement we could make it configurable or a bit smarter ;) -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1392) Test pinging / pull configuration

by Ales Justin (JIRA)

Ales Justin created ARQ-1392: -------------------------------- Summary: Test pinging / pull configuration Key: ARQ-1392 URL: https://issues.jboss.org/browse/ARQ-1392 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration Reporter: Ales Justin Assignee: Aslak Knutsen It should be fairly easy to add a configuration option to control the pull interval. We could e.g. say 0 to disable it. It does have consequences disabling it, since some features might not work. But you can at least increase the frequency of the pulling. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1391) Proxy port not verified if already in use

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1391?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak updated ARQ-1391: -------------------------------- Summary: Proxy port not verified if already in use (was: Proxy port not verified is already in use) > Proxy port not verified if already in use > ----------------------------------------- > > Key: ARQ-1391 > URL: https://issues.jboss.org/browse/ARQ-1391 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: 1.0.0.Alpha2 > Reporter: Bartosz Majsak > > When the 18080 port is already taken (eg. for application server using certain offset, like in my case for AS7 managed), Warp proxy is not checking its' availability, which results in [following exception being thrown|https://gist.github.com/bartoszmajsak/5630321], even if the test is not marked as @WarpTest. > As an improvement we could make it configurable or a bit smarter ;) -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1391) Proxy port not verified is already in use

by Bartosz Majsak (JIRA)

Bartosz Majsak created ARQ-1391: ----------------------------------- Summary: Proxy port not verified is already in use Key: ARQ-1391 URL: https://issues.jboss.org/browse/ARQ-1391 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Warp Affects Versions: 1.0.0.Alpha2 Reporter: Bartosz Majsak When the 18080 port is already taken (eg. for application server using certain offset, like in my case for AS7 managed), Warp proxy is not checking its' availability, which results in [following exception being thrown|https://gist.github.com/bartoszmajsak/5630321], even if the test is not marked as @WarpTest. As an improvement we could make it configurable or a bit smarter ;) -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1390) @ArquillianResource URL contextPath is malformed if the web archive name contains dots

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1390?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak edited comment on ARQ-1390 at 5/22/13 2:14 PM: -------------------------------------------------------------- Then this might be a [problem|https://github.com/wildfly/wildfly/blob/master/arquillian/common/...]. I will have a look. was (Author: bmajsak): Then this might be a [problem|https://github.com/wildfly/wildfly/blob/master/arquillian/common/...]. > @ArquillianResource URL contextPath is malformed if the web archive name contains dots > -------------------------------------------------------------------------------------- > > Key: ARQ-1390 > URL: https://issues.jboss.org/browse/ARQ-1390 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.0.3.Final > Reporter: Ron Šmeral > Attachments: arq-1390-reproducer.zip > > > If a WAR with dots in the name is deployed, the context path returned using {{@ArquillianResource URL contextPath}} is incorrect, as it has the segment after the last dot stripped off. > For example, deploying an archive called {{this.archive.has.dots.war}}, the real context path reported by the server is {{/this.archive.has.dots}} but {{@ArquillianResource URL}} points to {{/this.archive.has}}. -- 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

12 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues May 2013