March 2013 - arquillian-issues - Jboss List Archives

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

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1352?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak updated ARQ-1352: -------------------------------- Assignee: Sandor Bodo-Merle (was: Bartosz Majsak) > 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: Sandor Bodo-Merle > Fix For: persistence_1.0.0.next > > Attachments: 0001-ScriptExecutor-fix-commit-parsing.patch > > > 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

[JBoss JIRA] (ARQ-1356) TestResult isn't updated correctly when TestNG is used

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/ARQ-1356?page=com.atlassian.jira.plugin.s... ] Jan Papousek updated ARQ-1356: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-core/pull/46 > TestResult isn't updated correctly when TestNG is used > ------------------------------------------------------ > > Key: ARQ-1356 > URL: https://issues.jboss.org/browse/ARQ-1356 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.0.3.Final > Environment: TestNG 6.1.1 > Reporter: Jan Papousek > Assignee: Jan Papousek > > When a test fails, the state of TestResult is still PASSED and therefore it can't be used in observer: > {code} > public class LifecycleObserver { > @Inject > private Instance<TestResult> result; > public void afterTest(@Observes After event) { > if (result.get().getStatus().equals(PASSED)) { > // something > } else { > // something else > } > } > } > {code} > The problem is [LocalTestExecutor|https://github.com/arquillian/arquillian-core/blob/mast...] updates the status to FAILED only if an [exception is thrown|https://github.com/arquillian/arquillian-core/blob/master/containe...], but [TestMethodExecutor|https://github.com/arquillian/arquillian-core/blob/mas...] from TestNG implemenation doesn't throw any exception when the test fails. It [memorizes it in ITestResult object|https://github.com/arquillian/arquillian-core/blob/master/testng/c...]. > I propose to throw an exception in [the end of test invocation|https://github.com/arquillian/arquillian-core/blob/master/test...], if the test fails. -- 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-1356) TestResult isn't updated correctly when TestNG is used

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/ARQ-1356?page=com.atlassian.jira.plugin.s... ] Jan Papousek reassigned ARQ-1356: --------------------------------- Assignee: Jan Papousek > TestResult isn't updated correctly when TestNG is used > ------------------------------------------------------ > > Key: ARQ-1356 > URL: https://issues.jboss.org/browse/ARQ-1356 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.0.3.Final > Environment: TestNG 6.1.1 > Reporter: Jan Papousek > Assignee: Jan Papousek > > When a test fails, the state of TestResult is still PASSED and therefore it can't be used in observer: > {code} > public class LifecycleObserver { > @Inject > private Instance<TestResult> result; > public void afterTest(@Observes After event) { > if (result.get().getStatus().equals(PASSED)) { > // something > } else { > // something else > } > } > } > {code} > The problem is [LocalTestExecutor|https://github.com/arquillian/arquillian-core/blob/mast...] updates the status to FAILED only if an [exception is thrown|https://github.com/arquillian/arquillian-core/blob/master/containe...], but [TestMethodExecutor|https://github.com/arquillian/arquillian-core/blob/mas...] from TestNG implemenation doesn't throw any exception when the test fails. It [memorizes it in ITestResult object|https://github.com/arquillian/arquillian-core/blob/master/testng/c...]. > I propose to throw an exception in [the end of test invocation|https://github.com/arquillian/arquillian-core/blob/master/test...], if the test fails. -- 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-1356) TestResult isn't updated correctly when TestNG is used

by Jan Papousek (JIRA)

Jan Papousek created ARQ-1356: --------------------------------- Summary: TestResult isn't updated correctly when TestNG is used Key: ARQ-1356 URL: https://issues.jboss.org/browse/ARQ-1356 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.0.3.Final Environment: TestNG 6.1.1 Reporter: Jan Papousek When a test fails, the state of TestResult is still PASSED and therefore it can't be used in observer: {code} public class LifecycleObserver { @Inject private Instance<TestResult> result; public void afterTest(@Observes After event) { if (result.get().getStatus().equals(PASSED)) { // something } else { // something else } } } {code} The problem is [LocalTestExecutor|https://github.com/arquillian/arquillian-core/blob/mast...] updates the status to FAILED only if an [exception is thrown|https://github.com/arquillian/arquillian-core/blob/master/containe...], but [TestMethodExecutor|https://github.com/arquillian/arquillian-core/blob/mas...] from TestNG implemenation doesn't throw any exception when the test fails. It [memorizes it in ITestResult object|https://github.com/arquillian/arquillian-core/blob/master/testng/c...]. I propose to throw an exception in [the end of test invocation|https://github.com/arquillian/arquillian-core/blob/master/test...], if the test fails. -- 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-1355) Access the DatabaseConnection for additional verifications in an arquillian test

by Dominik Grupp (JIRA)

Dominik Grupp created ARQ-1355: ---------------------------------- Summary: Access the DatabaseConnection for additional verifications in an arquillian test Key: ARQ-1355 URL: https://issues.jboss.org/browse/ARQ-1355 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Dominik Grupp Priority: Minor There should be a possibility in an arquillian test to access the DatabaseConnection for additional verifications using dbunit. Using @UsingDataSet and @ShouldMatchDataSet first the already provided verifications could be done but then additional verification with dbunit using the DatabaseConnection - e.g. verfiy with a rowcount to make sure not more entries than expected have been created by the test. Original post (with a code example): https://community.jboss.org/thread/222401?tstart=0 -- 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 Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1352?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak commented on ARQ-1352: ------------------------------------- Thank you very much for spotting this problem and providing the fix! Shame on me :) Would it be possible for you to fork the repository on github and send fix (maybe with the unit test?) through the pull request? Then you will be automatically recognized as a contributor on the Arquillian web site and will gain eternal fame :) If you are not that familiar with the workflow, please have a look at this [guide|http://community.jboss.org/wiki/ShrinkWrapDevelopmentAndContribution] or simply just ask. I'll be more than happy to help. > 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 > Fix For: persistence_1.0.0.next > > Attachments: 0001-ScriptExecutor-fix-commit-parsing.patch > > > 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

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

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1352?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak updated ARQ-1352: -------------------------------- Fix Version/s: persistence_1.0.0.next > 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 > Fix For: persistence_1.0.0.next > > Attachments: 0001-ScriptExecutor-fix-commit-parsing.patch > > > 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

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

by Sandor Bodo-Merle (JIRA)

[ https://issues.jboss.org/browse/ARQ-1352?page=com.atlassian.jira.plugin.s... ] Sandor Bodo-Merle updated ARQ-1352: ----------------------------------- Attachment: 0001-ScriptExecutor-fix-commit-parsing.patch fix pattern matching the /* */ SQL comment > 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 > Attachments: 0001-ScriptExecutor-fix-commit-parsing.patch > > > 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

[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... ] Lukáš Fryč updated ARQGRA-274: ------------------------------ Reporter: Bernard Labno (was: 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 > Fix For: 2.0.0.Beta1 > > > 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-275) Implement Guard observers which will filter out which request we want to intercept

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQGRA-275: --------------------------------- Summary: Implement Guard observers which will filter out which request we want to intercept Key: ARQGRA-275 URL: https://issues.jboss.org/browse/ARQGRA-275 Project: Arquillian Graphene Issue Type: Enhancement Reporter: Lukáš Fryč Fix For: 2.0.0.Beta1 When guardXhr is waiting for request, it may happen that another (unwanted) request comes and it will break our test. This is typically situation of polling data updates (a4j:poll) or server push method (long-polling/comet, a4j:push). -- 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