March 2013 - arquillian-issues - Jboss List Archives

[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č commented on ARQ-1070: --------------------------------- Hey guys, does anyone from you wanna dive into that and find out why it happens? I can help you to dig into it on #arquillian @ irc.freenode.net > 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1320) Warp - The NonWrittingResponse does not override the flushBuffer() method allowing for committing response.

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1320?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on ARQ-1320: --------------------------------- Could you please open an issue which tracks concerns about sendError? > Warp - The NonWrittingResponse does not override the flushBuffer() method allowing for committing response. > ----------------------------------------------------------------------------------------------------------- > > Key: ARQ-1320 > URL: https://issues.jboss.org/browse/ARQ-1320 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Jakub Narloch > Assignee: Jakub Narloch > Priority: Blocker > Fix For: warp_1.0.0.Beta1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > The flushBuffer(http://docs.oracle.com/javaee/6/api/javax/servlet/ServletResp... which causes the response to be marked as commited. and Adding afterwards any headers to the response has no effect. > We should override the that method and prevent it's default behaviour. > Also, it would be good idea to check the specs for any other method that could commit the message and prevent from enriching it by Warp. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1320) Warp - The NonWrittingResponse does not override the flushBuffer() method allowing for committing response.

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1320?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on ARQ-1320: --------------------------------- Jakub, I must agree here - we are diving too deep into details of how response is handled here. The cleanest way to take care about problems with response wrapping is actually avoid it at all: ARQ-1325 > Warp - The NonWrittingResponse does not override the flushBuffer() method allowing for committing response. > ----------------------------------------------------------------------------------------------------------- > > Key: ARQ-1320 > URL: https://issues.jboss.org/browse/ARQ-1320 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Jakub Narloch > Priority: Blocker > Fix For: warp_1.0.0.Beta1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > The flushBuffer(http://docs.oracle.com/javaee/6/api/javax/servlet/ServletResp... which causes the response to be marked as commited. and Adding afterwards any headers to the response has no effect. > We should override the that method and prevent it's default behaviour. > Also, it would be good idea to check the specs for any other method that could commit the message and prevent from enriching it by Warp. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1320) Warp - The NonWrittingResponse does not override the flushBuffer() method allowing for committing response.

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1320?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-1320: ---------------------------- Status: Resolved (was: Pull Request Sent) Assignee: Jakub Narloch Resolution: Done > Warp - The NonWrittingResponse does not override the flushBuffer() method allowing for committing response. > ----------------------------------------------------------------------------------------------------------- > > Key: ARQ-1320 > URL: https://issues.jboss.org/browse/ARQ-1320 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Jakub Narloch > Assignee: Jakub Narloch > Priority: Blocker > Fix For: warp_1.0.0.Beta1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > The flushBuffer(http://docs.oracle.com/javaee/6/api/javax/servlet/ServletResp... which causes the response to be marked as commited. and Adding afterwards any headers to the response has no effect. > We should override the that method and prevent it's default behaviour. > Also, it would be good idea to check the specs for any other method that could commit the message and prevent from enriching it by Warp. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1320) Warp - The NonWrittingResponse does not override the flushBuffer() method allowing for committing response.

by Jakub Narloch (JIRA)

[ https://issues.jboss.org/browse/ARQ-1320?page=com.atlassian.jira.plugin.s... ] Jakub Narloch commented on ARQ-1320: ------------------------------------ On second thought, I think that adding the sendError methods to the pull request was a bad idea. In fact sending error on the response can redirect to other web page depending on the web.xml <errorPage> mapping, which we can not imitiate in any way through the proxy. The only solution would be to invoke the that method on the actual response, but that would end up in returning a non HTTP 200 code from the server. > Warp - The NonWrittingResponse does not override the flushBuffer() method allowing for committing response. > ----------------------------------------------------------------------------------------------------------- > > Key: ARQ-1320 > URL: https://issues.jboss.org/browse/ARQ-1320 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Jakub Narloch > Priority: Blocker > Fix For: warp_1.0.0.Beta1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > The flushBuffer(http://docs.oracle.com/javaee/6/api/javax/servlet/ServletResp... which causes the response to be marked as commited. and Adding afterwards any headers to the response has no effect. > We should override the that method and prevent it's default behaviour. > Also, it would be good idea to check the specs for any other method that could commit the message and prevent from enriching it by Warp. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1320) Warp - The NonWrittingResponse does not override the flushBuffer() method allowing for committing response.

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1320?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on ARQ-1320: --------------------------------- Hey Jakub, great job with investigations on how to make NonWritingResponse standard compliant. If you will be able to come up with the test cases / ftests for to further improve it, we can surely apply them. Otherwise we can solve that pro-actively when reflecting users' stories. > Warp - The NonWrittingResponse does not override the flushBuffer() method allowing for committing response. > ----------------------------------------------------------------------------------------------------------- > > Key: ARQ-1320 > URL: https://issues.jboss.org/browse/ARQ-1320 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Jakub Narloch > Priority: Blocker > Fix For: warp_1.0.0.Beta1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > The flushBuffer(http://docs.oracle.com/javaee/6/api/javax/servlet/ServletResp... which causes the response to be marked as commited. and Adding afterwards any headers to the response has no effect. > We should override the that method and prevent it's default behaviour. > Also, it would be good idea to check the specs for any other method that could commit the message and prevent from enriching it by Warp. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1319) Warp: Jacoco support

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1319?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč resolved ARQ-1319. ----------------------------- Resolution: Done > Warp: Jacoco support > -------------------- > > Key: ARQ-1319 > URL: https://issues.jboss.org/browse/ARQ-1319 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Lukáš Fryč > Assignee: Aris Tzoumas > Fix For: warp_1.0.0.Beta1 > > Attachments: ftest-coverage.jpg, jacoco.jpg, warp-jacoco.png > > Original Estimate: 2 days > Remaining Estimate: 2 days > > The support for CommandService was committed in ARQ-1027, which enabled us to run {{arquillian-extension-jacoco}}. > However as report from the Warp's build shows, the reporting isn't successful - report doesn't seem to contain any hits. > We need to investigate and once ready, we should use [{{check}}|http://www.eclemma.org/jacoco/trunk/doc/check-mojo.html] goal to be sure that coverage is reported successfully from Warp's tests. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-934) Warp: Reuse manager during whole test

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-934?page=com.atlassian.jira.plugin.sy... ] Lukáš Fryč updated ARQ-934: --------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Warp: Reuse manager during whole test > ------------------------------------- > > Key: ARQ-934 > URL: https://issues.jboss.org/browse/ARQ-934 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Lukáš Fryč > Assignee: Aris Tzoumas > Priority: Critical > Fix For: warp_1.0.0.Beta1 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Manager is created for each request independently: > https://github.com/arquillian/arquillian-extension-warp/blob/master/impl/... > {quote} > <aslak> Scopes a bound to ThreadLocals, so you'll need to 'reactivate' application scope pr request > {quote} -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1353) Warp: propagate manager's context to proxy correctly

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQ-1353: ------------------------------- Summary: Warp: propagate manager's context to proxy correctly Key: ARQ-1353 URL: https://issues.jboss.org/browse/ARQ-1353 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Warp Reporter: Lukáš Fryč Priority: Minor Fix For: warp_1.0.0.Beta1 Warp's proxy current serves in no context - we should use at least following hack to propagate context: https://github.com/arquillian/arquillian-extension-warp/blob/master/impl/... -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1352) Script can not insert unix path separator '/' into the DB

by Sandor Bodo-Merle (JIRA)

Sandor Bodo-Merle created ARQ-1352: -------------------------------------- Summary: Script can not insert unix path separator '/' into the DB Key: ARQ-1352 URL: https://issues.jboss.org/browse/ARQ-1352 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha6 Reporter: Sandor Bodo-Merle Assignee: Bartosz Majsak I have a test class which try to insert a unix path value in the DB on schema creation: @CreateSchema({"setup.sql"}) public class UserTest { ... } Th the ScriptExecutor introduced in 1.0.0.Alpha6 will iron out the '/' character from the path on insert - like in the following small example: public class main { public static void main(String[] args) { final String ANSI_SQL_COMMENTS_PATTERN = "--.*|//.*|(?s)/\\\\*.*?\\\\*/|(?s)\\{.*?\\}"; String script = "INSERT INTO config (name, value) VALUES ('path', '/home/sbodo/test.txt');"; System.out.println(script.replaceAll(ANSI_SQL_COMMENTS_PATTERN, "")); } } Output is: INSERT INTO config (name, value) VALUES ('path', 'sbodo/test.txt'); instead of: INSERT INTO config (name, value) VALUES ('path', '/home/sbodo/test.txt'); Tested with Jboss 7.1.1 and Postgres 9.1. The test worked fine in 1.0.0.Alpha5. -- 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

11 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues March 2013