From issues at jboss.org Tue May 3 03:20:00 2016 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 3 May 2016 03:20:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2027) JDK 8 with wildfly failing for integration tests In-Reply-To: References: Message-ID: Bartosz Majsak created ARQ-2027: ----------------------------------- Summary: JDK 8 with wildfly failing for integration tests Key: ARQ-2027 URL: https://issues.jboss.org/browse/ARQ-2027 Project: Arquillian Issue Type: Bug Components: Extension - Persistence Reporter: Bartosz Majsak Assignee: Bartosz Majsak More details on discuss http://discuss.arquillian.org/t/help-running-arquillian-persistence-int-tests/307/9 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun May 8 07:28:00 2016 From: issues at jboss.org (Christian Schulz (JIRA)) Date: Sun, 8 May 2016 07:28:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2028) The precedence of ScreenshooterLifecycleObserver should be increased In-Reply-To: References: Message-ID: Christian Schulz created ARQ-2028: ------------------------------------- Summary: The precedence of ScreenshooterLifecycleObserver should be increased Key: ARQ-2028 URL: https://issues.jboss.org/browse/ARQ-2028 Project: Arquillian Issue Type: Enhancement Components: Extension - Recorder Affects Versions: recorder_1.1.0.Final Reporter: Christian Schulz Some people does cleanup after executing a test case which can lead into a blank page or similar, increasing the observer should prevent it. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun May 8 07:29:00 2016 From: issues at jboss.org (Christian Schulz (JIRA)) Date: Sun, 8 May 2016 07:29:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2028) The precedence of ScreenshooterLifecycleObserver should be increased In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulz updated ARQ-2028: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-recorder/pull/30 > The precedence of ScreenshooterLifecycleObserver should be increased > -------------------------------------------------------------------- > > Key: ARQ-2028 > URL: https://issues.jboss.org/browse/ARQ-2028 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Recorder > Affects Versions: recorder_1.1.0.Final > Reporter: Christian Schulz > > Some people does cleanup after executing a test case which can lead into a blank page or similar, increasing the observer should prevent it. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun May 8 18:53:00 2016 From: issues at jboss.org (Rafael Pestano (JIRA)) Date: Sun, 8 May 2016 18:53:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2027) JDK 8 with wildfly failing for integration tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13202379#comment-13202379 ] Rafael Pestano commented on ARQ-2027: ------------------------------------- I also happens on jboss-as-7 (default container in APE int-tests). To reproduce just use 'mvn clean verify' on APE parent module using jdk8. All it-tests will fail with the following exception: {noformat} java.lang.ClassCastException: org.jboss.arquillian.persistence.core.event.ApplyScriptsBeforeTest cannot be cast to org.jboss.arquillian.persistence.dbunit.event.CompareDBUnitData {noformat} The exception is [raised here|https://github.com/arquillian/arquillian-extension-persistence/blob/master/dbunit/src/main/java/org/jboss/arquillian/persistence/dbunit/lifecycle/DataSetHandler.java#L59] when the event below is fired: {noformat} prepareDataEvent.fire(new PrepareDBUnitData(dataSetProvider.getDescriptorsDefinedFor(beforePersistenceTest.getTestMethod()))); {noformat} > JDK 8 with wildfly failing for integration tests > ------------------------------------------------ > > Key: ARQ-2027 > URL: https://issues.jboss.org/browse/ARQ-2027 > Project: Arquillian > Issue Type: Bug > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > > More details on discuss > http://discuss.arquillian.org/t/help-running-arquillian-persistence-int-tests/307/9 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun May 8 18:54:00 2016 From: issues at jboss.org (Rafael Pestano (JIRA)) Date: Sun, 8 May 2016 18:54:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2027) JDK 8 with wildfly failing for integration tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13202379#comment-13202379 ] Rafael Pestano edited comment on ARQ-2027 at 5/8/16 6:53 PM: ------------------------------------------------------------- It also happens on jboss-as-7 (default container in APE int-tests). To reproduce just use 'mvn clean verify' on APE parent module using jdk8. All it-tests will fail with the following exception: {noformat} java.lang.ClassCastException: org.jboss.arquillian.persistence.core.event.ApplyScriptsBeforeTest cannot be cast to org.jboss.arquillian.persistence.dbunit.event.CompareDBUnitData {noformat} The exception is [raised here|https://github.com/arquillian/arquillian-extension-persistence/blob/master/dbunit/src/main/java/org/jboss/arquillian/persistence/dbunit/lifecycle/DataSetHandler.java#L59] when the event below is fired: {noformat} prepareDataEvent.fire(new PrepareDBUnitData(dataSetProvider.getDescriptorsDefinedFor(beforePersistenceTest.getTestMethod()))); {noformat} was (Author: kwintesencja): I also happens on jboss-as-7 (default container in APE int-tests). To reproduce just use 'mvn clean verify' on APE parent module using jdk8. All it-tests will fail with the following exception: {noformat} java.lang.ClassCastException: org.jboss.arquillian.persistence.core.event.ApplyScriptsBeforeTest cannot be cast to org.jboss.arquillian.persistence.dbunit.event.CompareDBUnitData {noformat} The exception is [raised here|https://github.com/arquillian/arquillian-extension-persistence/blob/master/dbunit/src/main/java/org/jboss/arquillian/persistence/dbunit/lifecycle/DataSetHandler.java#L59] when the event below is fired: {noformat} prepareDataEvent.fire(new PrepareDBUnitData(dataSetProvider.getDescriptorsDefinedFor(beforePersistenceTest.getTestMethod()))); {noformat} > JDK 8 with wildfly failing for integration tests > ------------------------------------------------ > > Key: ARQ-2027 > URL: https://issues.jboss.org/browse/ARQ-2027 > Project: Arquillian > Issue Type: Bug > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > > More details on discuss > http://discuss.arquillian.org/t/help-running-arquillian-persistence-int-tests/307/9 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun May 8 21:02:00 2016 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sun, 8 May 2016 21:02:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2027) JDK 8 with wildfly failing for integration tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13202388#comment-13202388 ] Bartosz Majsak commented on ARQ-2027: ------------------------------------- Are you sure jboss 7.x is working with jdk 8 at all? Maybe we have wrong setup compiling against jdk8 but running app server with the older java. This might be the reason why we are getting such strange errors. > JDK 8 with wildfly failing for integration tests > ------------------------------------------------ > > Key: ARQ-2027 > URL: https://issues.jboss.org/browse/ARQ-2027 > Project: Arquillian > Issue Type: Bug > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > > More details on discuss > http://discuss.arquillian.org/t/help-running-arquillian-persistence-int-tests/307/9 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 10 08:51:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Tue, 10 May 2016 08:51:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-467) Screenshooter: Tests fail when no Drone contexts exist In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek reopened ARQGRA-467: ----------------------------------- Assignee: Matous Jobanek (was: Stefan Miklosovic) > Screenshooter: Tests fail when no Drone contexts exist > ------------------------------------------------------ > > Key: ARQGRA-467 > URL: https://issues.jboss.org/browse/ARQGRA-467 > Project: Arquillian Graphene > Issue Type: Bug > Components: screenshooter > Affects Versions: 2.1.0.Alpha1, 2.1.0.CR1 > Reporter: Luk?? Fry? > Assignee: Matous Jobanek > Fix For: 2.1.0.Alpha2 > > > https://github.com/arquillian/arquillian-recorder/issues/10 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 10 08:51:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Tue, 10 May 2016 08:51:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-467) Screenshooter: Tests fail when no Drone contexts exist In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQGRA-467: ---------------------------------- Affects Version/s: 2.1.0.CR1 > Screenshooter: Tests fail when no Drone contexts exist > ------------------------------------------------------ > > Key: ARQGRA-467 > URL: https://issues.jboss.org/browse/ARQGRA-467 > Project: Arquillian Graphene > Issue Type: Bug > Components: screenshooter > Affects Versions: 2.1.0.Alpha1, 2.1.0.CR1 > Reporter: Luk?? Fry? > Assignee: Matous Jobanek > Fix For: 2.1.0.Alpha2 > > > https://github.com/arquillian/arquillian-recorder/issues/10 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 10 08:55:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Tue, 10 May 2016 08:55:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-467) Screenshooter: Tests fail when no Drone contexts exist In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQGRA-467: ---------------------------------- Fix Version/s: 2.1.0.CR2 (was: 2.1.0.Alpha2) > Screenshooter: Tests fail when no Drone contexts exist > ------------------------------------------------------ > > Key: ARQGRA-467 > URL: https://issues.jboss.org/browse/ARQGRA-467 > Project: Arquillian Graphene > Issue Type: Bug > Components: screenshooter > Affects Versions: 2.1.0.Alpha1, 2.1.0.CR1 > Reporter: Luk?? Fry? > Assignee: Matous Jobanek > Fix For: 2.1.0.CR2 > > > https://github.com/arquillian/arquillian-recorder/issues/10 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 10 09:57:00 2016 From: issues at jboss.org (Christian Schulz (JIRA)) Date: Tue, 10 May 2016 09:57:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2029) Tell us the HTTP method in debug mode In-Reply-To: References: Message-ID: Christian Schulz created ARQ-2029: ------------------------------------- Summary: Tell us the HTTP method in debug mode Key: ARQ-2029 URL: https://issues.jboss.org/browse/ARQ-2029 Project: Arquillian Issue Type: Enhancement Components: Extension - Warp Reporter: Christian Schulz Prints parallel to requestUri the method. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 10 09:57:00 2016 From: issues at jboss.org (Christian Schulz (JIRA)) Date: Tue, 10 May 2016 09:57:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2029) Tell us the HTTP method in debug mode In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulz updated ARQ-2029: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-warp/pull/34 > Tell us the HTTP method in debug mode > ------------------------------------- > > Key: ARQ-2029 > URL: https://issues.jboss.org/browse/ARQ-2029 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Warp > Reporter: Christian Schulz > > Prints parallel to requestUri the method. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 10 10:55:00 2016 From: issues at jboss.org (=?UTF-8?Q?Tom=C3=A1=C5=A1_Turek_=28JIRA=29?=) Date: Tue, 10 May 2016 10:55:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2030) Upgrade Karaf to version 4.0.4 broke comparability with JBoss Fuse In-Reply-To: References: Message-ID: Tom?? Turek created ARQ-2030: -------------------------------- Summary: Upgrade Karaf to version 4.0.4 broke comparability with JBoss Fuse Key: ARQ-2030 URL: https://issues.jboss.org/browse/ARQ-2030 Project: Arquillian Issue Type: Bug Components: OSGi Containers Reporter: Tom?? Turek Assignee: Thomas Diesler [Commit|https://github.com/arquillian/arquillian-container-osgi/commit/31157c2be1600929d47e79b7f4a15bc7b89f9bbd] which upgrade Karaf to version 4.0.4 for managed broke compatibility with JBoss Fuse 6.x. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 10 11:03:00 2016 From: issues at jboss.org (=?UTF-8?Q?Tom=C3=A1=C5=A1_Turek_=28JIRA=29?=) Date: Tue, 10 May 2016 11:03:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2030) Upgrade Karaf to version 4.0.4 broke comparability with JBoss Fuse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom?? Turek updated ARQ-2030: ----------------------------- Priority: Minor (was: Major) > Upgrade Karaf to version 4.0.4 broke comparability with JBoss Fuse > ------------------------------------------------------------------ > > Key: ARQ-2030 > URL: https://issues.jboss.org/browse/ARQ-2030 > Project: Arquillian > Issue Type: Bug > Components: OSGi Containers > Reporter: Tom?? Turek > Assignee: Thomas Diesler > Priority: Minor > > [Commit|https://github.com/arquillian/arquillian-container-osgi/commit/31157c2be1600929d47e79b7f4a15bc7b89f9bbd] which upgrade Karaf to version 4.0.4 for managed broke compatibility with JBoss Fuse 6.x. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 17 06:05:01 2016 From: issues at jboss.org (Jessica Streicher (JIRA)) Date: Tue, 17 May 2016 06:05:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2031) Test method missing in report In-Reply-To: References: Message-ID: Jessica Streicher created ARQ-2031: -------------------------------------- Summary: Test method missing in report Key: ARQ-2031 URL: https://issues.jboss.org/browse/ARQ-2031 Project: Arquillian Issue Type: Bug Components: Extension - Recorder Affects Versions: 1.1.10.Final Environment: Tests are run with Eclipse and JUnit plugin against an external Webserver (They're pure client UI tests) Reporter: Jessica Streicher Whenever a testmethod fails (assertion fail), the test method is not available in the report. I have tracked the Problem in the ReportLifecycleObserver class - it is caused because there are two BeforeTestLifeCycleEvents, but only one AfterTestLifecycleEvent. The passed test also has two AfterTestLifecycleEvents, so an event seems to be missing when the test fails? I'm afraid my current code cannot be posted publicly, but i'll try to recreate it later on in another setting. It would still be nice if anyone by chance knows what could be the cause of this situation. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 17 06:06:00 2016 From: issues at jboss.org (Jessica Streicher (JIRA)) Date: Tue, 17 May 2016 06:06:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2031) Test method missing in report In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Streicher updated ARQ-2031: ----------------------------------- Description: Whenever a testmethod fails (assertion fail), the test method is not available in the report. I have tracked the Problem in the ReportLifecycleObserver class - it is caused because there are two BeforeTestLifeCycleEvents, but only one AfterTestLifecycleEvent. The other "passed" test has two AfterTestLifecycleEvents, so an event seems to be missing when the test "fails"? I'm afraid my current code cannot be posted publicly, but i'll try to recreate it later on in another setting. It would still be nice if anyone by chance knows what could be the cause of this situation. was: Whenever a testmethod fails (assertion fail), the test method is not available in the report. I have tracked the Problem in the ReportLifecycleObserver class - it is caused because there are two BeforeTestLifeCycleEvents, but only one AfterTestLifecycleEvent. The passed test also has two AfterTestLifecycleEvents, so an event seems to be missing when the test fails? I'm afraid my current code cannot be posted publicly, but i'll try to recreate it later on in another setting. It would still be nice if anyone by chance knows what could be the cause of this situation. > Test method missing in report > ----------------------------- > > Key: ARQ-2031 > URL: https://issues.jboss.org/browse/ARQ-2031 > Project: Arquillian > Issue Type: Bug > Components: Extension - Recorder > Affects Versions: 1.1.10.Final > Environment: Tests are run with Eclipse and JUnit plugin against an external Webserver (They're pure client UI tests) > Reporter: Jessica Streicher > > Whenever a testmethod fails (assertion fail), the test method is not available in the report. > I have tracked the Problem in the ReportLifecycleObserver class - it is caused because there are two BeforeTestLifeCycleEvents, but only one AfterTestLifecycleEvent. > The other "passed" test has two AfterTestLifecycleEvents, so an event seems to be missing when the test "fails"? > I'm afraid my current code cannot be posted publicly, but i'll try to recreate it later on in another setting. It would still be nice if anyone by chance knows what could be the cause of this situation. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 17 07:46:01 2016 From: issues at jboss.org (Jessica Streicher (JIRA)) Date: Tue, 17 May 2016 07:46:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2031) Test method missing in report In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238579#comment-13238579 ] Jessica Streicher commented on ARQ-2031: ---------------------------------------- I did some more testing and it seems to be a matter about an action that is not possible during the @After execution. In the failed test i switched the browser to an inner frame in the test method, then i tried to execute a click on an element that is not available in that frame in the @after method (the logout button basically, this is executed for all tests). I assume this messes with the events somehow. Should executing UI tasks in the @After method be generally avoided or is this a problem with Arquillian/JUnit/Recorder? > Test method missing in report > ----------------------------- > > Key: ARQ-2031 > URL: https://issues.jboss.org/browse/ARQ-2031 > Project: Arquillian > Issue Type: Bug > Components: Extension - Recorder > Affects Versions: 1.1.10.Final > Environment: Tests are run with Eclipse and JUnit plugin against an external Webserver (They're pure client UI tests) > Reporter: Jessica Streicher > > Whenever a testmethod fails (assertion fail), the test method is not available in the report. > I have tracked the Problem in the ReportLifecycleObserver class - it is caused because there are two BeforeTestLifeCycleEvents, but only one AfterTestLifecycleEvent. > The other "passed" test has two AfterTestLifecycleEvents, so an event seems to be missing when the test "fails"? > I'm afraid my current code cannot be posted publicly, but i'll try to recreate it later on in another setting. It would still be nice if anyone by chance knows what could be the cause of this situation. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 17 07:55:00 2016 From: issues at jboss.org (Jessica Streicher (JIRA)) Date: Tue, 17 May 2016 07:55:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2031) Test method missing in report In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Streicher updated ARQ-2031: ----------------------------------- Attachment: TestTest.java SubTest.java > Test method missing in report > ----------------------------- > > Key: ARQ-2031 > URL: https://issues.jboss.org/browse/ARQ-2031 > Project: Arquillian > Issue Type: Bug > Components: Extension - Recorder > Affects Versions: 1.1.10.Final > Environment: Tests are run with Eclipse and JUnit plugin against an external Webserver (They're pure client UI tests) > Reporter: Jessica Streicher > Attachments: SubTest.java, TestTest.java > > > Whenever a testmethod fails (assertion fail), the test method is not available in the report. > I have tracked the Problem in the ReportLifecycleObserver class - it is caused because there are two BeforeTestLifeCycleEvents, but only one AfterTestLifecycleEvent. > The other "passed" test has two AfterTestLifecycleEvents, so an event seems to be missing when the test "fails"? > I'm afraid my current code cannot be posted publicly, but i'll try to recreate it later on in another setting. It would still be nice if anyone by chance knows what could be the cause of this situation. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 18 05:06:00 2016 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Wed, 18 May 2016 05:06:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2032) Do not start fragment bundles when property "autostartBundle" is true In-Reply-To: References: Message-ID: Martin Basovnik created ARQ-2032: ------------------------------------ Summary: Do not start fragment bundles when property "autostartBundle" is true Key: ARQ-2032 URL: https://issues.jboss.org/browse/ARQ-2032 Project: Arquillian Issue Type: Feature Request Components: OSGi Containers Reporter: Martin Basovnik Assignee: Thomas Diesler -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 18 05:06:00 2016 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Wed, 18 May 2016 05:06:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2032) Do not start fragment bundles when property "autostartBundle" is true In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239202#comment-13239202 ] Martin Basovnik commented on ARQ-2032: -------------------------------------- I will provide pull request. > Do not start fragment bundles when property "autostartBundle" is true > --------------------------------------------------------------------- > > Key: ARQ-2032 > URL: https://issues.jboss.org/browse/ARQ-2032 > Project: Arquillian > Issue Type: Feature Request > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 18 05:06:00 2016 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Wed, 18 May 2016 05:06:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2032) Do not start fragment bundles when property "autostartBundle" is true In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Basovnik updated ARQ-2032: --------------------------------- Priority: Minor (was: Major) > Do not start fragment bundles when property "autostartBundle" is true > --------------------------------------------------------------------- > > Key: ARQ-2032 > URL: https://issues.jboss.org/browse/ARQ-2032 > Project: Arquillian > Issue Type: Feature Request > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 18 05:13:00 2016 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Wed, 18 May 2016 05:13:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2032) Do not start fragment bundles when property "autostartBundle" is true In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Basovnik updated ARQ-2032: --------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-container-osgi/pull/49 > Do not start fragment bundles when property "autostartBundle" is true > --------------------------------------------------------------------- > > Key: ARQ-2032 > URL: https://issues.jboss.org/browse/ARQ-2032 > Project: Arquillian > Issue Type: Feature Request > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 18 07:04:00 2016 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Wed, 18 May 2016 07:04:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2032) Do not start fragment bundles when property "autostartBundle" is true In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239322#comment-13239322 ] Thomas Diesler commented on ARQ-2032: ------------------------------------- OSGi on WildFly is not supported any more. > Do not start fragment bundles when property "autostartBundle" is true > --------------------------------------------------------------------- > > Key: ARQ-2032 > URL: https://issues.jboss.org/browse/ARQ-2032 > Project: Arquillian > Issue Type: Feature Request > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 18 07:04:00 2016 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Wed, 18 May 2016 07:04:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2032) Do not start fragment bundles when property "autostartBundle" is true In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler reassigned ARQ-2032: ----------------------------------- Assignee: (was: Thomas Diesler) > Do not start fragment bundles when property "autostartBundle" is true > --------------------------------------------------------------------- > > Key: ARQ-2032 > URL: https://issues.jboss.org/browse/ARQ-2032 > Project: Arquillian > Issue Type: Feature Request > Components: OSGi Containers > Reporter: Martin Basovnik > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 18 07:51:00 2016 From: issues at jboss.org (Martin Basovnik (JIRA)) Date: Wed, 18 May 2016 07:51:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2032) Do not start fragment bundles when property "autostartBundle" is true In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239358#comment-13239358 ] Martin Basovnik commented on ARQ-2032: -------------------------------------- [~thomas.diesler], I do not understand how is this issue connected with Wildfly... I just wanted to track issue somewhere. Shall I rather use github issues? > Do not start fragment bundles when property "autostartBundle" is true > --------------------------------------------------------------------- > > Key: ARQ-2032 > URL: https://issues.jboss.org/browse/ARQ-2032 > Project: Arquillian > Issue Type: Feature Request > Components: OSGi Containers > Reporter: Martin Basovnik > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu May 19 14:52:00 2016 From: issues at jboss.org (Christian Schulz (JIRA)) Date: Thu, 19 May 2016 14:52:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2028) The precedence of ScreenshooterLifecycleObserver should be increased In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240220#comment-13240220 ] Christian Schulz commented on ARQ-2028: --------------------------------------- The PR is already merged. > The precedence of ScreenshooterLifecycleObserver should be increased > -------------------------------------------------------------------- > > Key: ARQ-2028 > URL: https://issues.jboss.org/browse/ARQ-2028 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Recorder > Affects Versions: recorder_1.1.0.Final > Reporter: Christian Schulz > > Some people does cleanup after executing a test case which can lead into a blank page or similar, increasing the observer should prevent it. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu May 19 14:56:02 2016 From: issues at jboss.org (Christian Schulz (JIRA)) Date: Thu, 19 May 2016 14:56:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2026) Client activity failures should have more priority over server activities In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulz updated ARQ-2026: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-warp/pull/35 > Client activity failures should have more priority over server activities > ------------------------------------------------------------------------- > > Key: ARQ-2026 > URL: https://issues.jboss.org/browse/ARQ-2026 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7 > Reporter: Christian Schulz > > I have noticed multiple times that my warp tests are failing caused by ServerWarpExecutionException. > In my research I found out that the DefaultWarpExecutor prefers to show server activity failures over client activity failures. > In my opinion client failures should be handled with higher priority, because in most cases the failing client activities is the reason for the server activity failure f.e. with asserts. > I would suggest to ignore AssertionErrors from server activities if there is a catched client exception. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu May 19 15:28:00 2016 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 19 May 2016 15:28:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2028) The precedence of ScreenshooterLifecycleObserver should be increased In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-2028: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > The precedence of ScreenshooterLifecycleObserver should be increased > -------------------------------------------------------------------- > > Key: ARQ-2028 > URL: https://issues.jboss.org/browse/ARQ-2028 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Recorder > Affects Versions: recorder_1.1.0.Final > Reporter: Christian Schulz > > Some people does cleanup after executing a test case which can lead into a blank page or similar, increasing the observer should prevent it. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 25 08:56:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 25 May 2016 08:56:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-467) Screenshooter: Tests fail when no Drone contexts exist In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQGRA-467. --------------------------------- Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-graphene/commit/3c17108227576d5f68f9be49a66c639ed3075311 > Screenshooter: Tests fail when no Drone contexts exist > ------------------------------------------------------ > > Key: ARQGRA-467 > URL: https://issues.jboss.org/browse/ARQGRA-467 > Project: Arquillian Graphene > Issue Type: Bug > Components: screenshooter > Affects Versions: 2.1.0.Alpha1, 2.1.0.CR1 > Reporter: Luk?? Fry? > Assignee: Matous Jobanek > Fix For: 2.1.0.CR2 > > > https://github.com/arquillian/arquillian-recorder/issues/10 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri May 27 15:40:00 2016 From: issues at jboss.org (Dave Levitt (JIRA)) Date: Fri, 27 May 2016 15:40:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2033) Managed Tomcat fails to launch on Windows during maven test phase In-Reply-To: References: Message-ID: Dave Levitt created ARQ-2033: -------------------------------- Summary: Managed Tomcat fails to launch on Windows during maven test phase Key: ARQ-2033 URL: https://issues.jboss.org/browse/ARQ-2033 Project: Arquillian Issue Type: Bug Components: Tomcat Containers Environment: Windows 7, jdk 8 [1.8.0_66], maven 3.3.9 Reporter: Dave Levitt The *TomcatManagedContainer* class assembles file system path parameters int its start tomcat command line by string concatenation, for example: {{ cmd.add("-Djava.endorsed.dirs=" + absoluteCatalinaHomePath + "/endorsed");}} This works fine on Linux and OSX but fails for those developers afflicted by Windows as their dev system. The '/' character embedded in several string fragments needs to be replaced by the localized *java.util.File.separator* field. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon May 30 08:43:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Mon, 30 May 2016 08:43:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1980) Add support for BrowserStack In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-1980: -------------------------------- Fix Version/s: drone_2.0.0.Final (was: drone_2.1.0.Final) > Add support for BrowserStack > ---------------------------- > > Key: ARQ-1980 > URL: https://issues.jboss.org/browse/ARQ-1980 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.0.0.Final > > > Add support for BrowserStack > see: https://github.com/MatousJobanek/arquillian-drone-browserstack-webdriver/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon May 30 08:43:01 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Mon, 30 May 2016 08:43:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1980) Add support for BrowserStack In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-1980. ------------------------------- Resolution: Duplicate Closing as it has been already fixed as part of this issue https://issues.jboss.org/browse/ARQ-2025 > Add support for BrowserStack > ---------------------------- > > Key: ARQ-1980 > URL: https://issues.jboss.org/browse/ARQ-1980 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.0.0.Final > > > Add support for BrowserStack > see: https://github.com/MatousJobanek/arquillian-drone-browserstack-webdriver/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 31 09:22:00 2016 From: issues at jboss.org (Dave Levitt (JIRA)) Date: Tue, 31 May 2016 09:22:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2033) Managed Tomcat fails to launch on Windows during maven test phase In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13245336#comment-13245336 ] Dave Levitt commented on ARQ-2033: ---------------------------------- Could not submit pull request :( > Managed Tomcat fails to launch on Windows during maven test phase > ----------------------------------------------------------------- > > Key: ARQ-2033 > URL: https://issues.jboss.org/browse/ARQ-2033 > Project: Arquillian > Issue Type: Bug > Components: Tomcat Containers > Environment: Windows 7, jdk 8 [1.8.0_66], maven 3.3.9 > Reporter: Dave Levitt > > The *TomcatManagedContainer* class assembles file system path parameters int its start tomcat command line by string concatenation, for example: > {{ cmd.add("-Djava.endorsed.dirs=" + absoluteCatalinaHomePath + "/endorsed");}} > > This works fine on Linux and OSX but fails for those developers afflicted by Windows as their dev system. The '/' character embedded in several string fragments needs to be replaced by the localized *java.util.File.separator* field. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 31 10:41:00 2016 From: issues at jboss.org (Dave Levitt (JIRA)) Date: Tue, 31 May 2016 10:41:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2033) Managed Tomcat fails to launch on Windows during maven test phase In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13245441#comment-13245441 ] Dave Levitt commented on ARQ-2033: ---------------------------------- Just 'read the fine manual' ;) and was able to make the pull request. > Managed Tomcat fails to launch on Windows during maven test phase > ----------------------------------------------------------------- > > Key: ARQ-2033 > URL: https://issues.jboss.org/browse/ARQ-2033 > Project: Arquillian > Issue Type: Bug > Components: Tomcat Containers > Environment: Windows 7, jdk 8 [1.8.0_66], maven 3.3.9 > Reporter: Dave Levitt > > The *TomcatManagedContainer* class assembles file system path parameters int its start tomcat command line by string concatenation, for example: > {{ cmd.add("-Djava.endorsed.dirs=" + absoluteCatalinaHomePath + "/endorsed");}} > > This works fine on Linux and OSX but fails for those developers afflicted by Windows as their dev system. The '/' character embedded in several string fragments needs to be replaced by the localized *java.util.File.separator* field. -- This message was sent by Atlassian JIRA (v6.4.11#64026)