September 2015 - arquillian-issues

[JBoss JIRA] (ARQ-1979) Screenshot is not taken when a test fails

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQ-1979?page=com.atlassian.jira.plugin.s... ] Matous Jobanek updated ARQ-1979: -------------------------------- Description: The cause: There in the Arquillian-core 1.1.7.Final have been changed the workflow of events and the moment when the status of a test is set For more information see: https://github.com/arquillian/arquillian-core/commit/606b4b29a3a561bc0ea6... ARQ-1818 This change is not reflected there in the arquillian-recorder project - this causes that the screenshot is not taken when test fails: https://github.com/arquillian/arquillian-recorder/blob/master/arquillian-... was: The cause: There in the Arquillian-core 1.1.7.Final have been introduced new events: {{AfterTestLifecycleEvent}} {{BeforeTestLifecycleEvent}} that replaces the behaviour of predecessors {{After}} {{Before}} For more information see: https://github.com/arquillian/arquillian-core/commit/606b4b29a3a561bc0ea6... ARQ-1818 This change is not reflected there in the arquillian-recorder project - this causes that the screenshot is not taken when test fails: https://github.com/arquillian/arquillian-recorder/blob/master/arquillian-... > Screenshot is not taken when a test fails > ----------------------------------------- > > Key: ARQ-1979 > URL: https://issues.jboss.org/browse/ARQ-1979 > Project: Arquillian > Issue Type: Bug > Components: Extension - Recorder > Reporter: Matous Jobanek > Assignee: Matous Jobanek > > The cause: > There in the Arquillian-core 1.1.7.Final have been changed the workflow of events and the moment when the status of a test is set > For more information see: > https://github.com/arquillian/arquillian-core/commit/606b4b29a3a561bc0ea6... > ARQ-1818 > This change is not reflected there in the arquillian-recorder project - this causes that the screenshot is not taken when test fails: > https://github.com/arquillian/arquillian-recorder/blob/master/arquillian-... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1979) Screenshot is not taken when a test fails

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQ-1979?page=com.atlassian.jira.plugin.s... ] Matous Jobanek reassigned ARQ-1979: ----------------------------------- Assignee: Matous Jobanek > Screenshot is not taken when a test fails > ----------------------------------------- > > Key: ARQ-1979 > URL: https://issues.jboss.org/browse/ARQ-1979 > Project: Arquillian > Issue Type: Bug > Components: Extension - Recorder > Reporter: Matous Jobanek > Assignee: Matous Jobanek > > The cause: > There in the Arquillian-core 1.1.7.Final have been introduced new events: > {{AfterTestLifecycleEvent}} > {{BeforeTestLifecycleEvent}} > that replaces the behaviour of predecessors > {{After}} > {{Before}} > For more information see: > https://github.com/arquillian/arquillian-core/commit/606b4b29a3a561bc0ea6... > ARQ-1818 > This change is not reflected there in the arquillian-recorder project - this causes that the screenshot is not taken when test fails: > https://github.com/arquillian/arquillian-recorder/blob/master/arquillian-... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-479) Propagate xhr.response values in wrapper callback

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-479?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-479: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Propagate xhr.response values in wrapper callback > ------------------------------------------------- > > Key: ARQGRA-479 > URL: https://issues.jboss.org/browse/ARQGRA-479 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.3.Final, 2.1.0.Alpha2 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 2.0-Tracking, 2.1-Tracking > > > When the xhr wrapper is created the response property is copied but it isn't updated in the callback, which leads to the property values' being out of sync. Some frameworks (e.g. Angular) will use the xhr.response over xhr.responseText if it is present, which means that simply using a guardAjax in a Graphene test will cause all subsequent xhr calls to return invalid data. In my case (Firefox 38, Angular 1.4.4, Graphene 2.0.3.Final) all $http calls would return "" once a guardAjax was executed, despite valid data being shown in Firefox's request log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-479) Propagate xhr.response values in wrapper callback

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-479?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-479: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/137, https://github.com/arquillian/arquillian-graphene/pull/138 > Propagate xhr.response values in wrapper callback > ------------------------------------------------- > > Key: ARQGRA-479 > URL: https://issues.jboss.org/browse/ARQGRA-479 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.3.Final, 2.1.0.Alpha2 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 2.0-Tracking, 2.1-Tracking > > > When the xhr wrapper is created the response property is copied but it isn't updated in the callback, which leads to the property values' being out of sync. Some frameworks (e.g. Angular) will use the xhr.response over xhr.responseText if it is present, which means that simply using a guardAjax in a Graphene test will cause all subsequent xhr calls to return invalid data. In my case (Firefox 38, Angular 1.4.4, Graphene 2.0.3.Final) all $http calls would return "" once a guardAjax was executed, despite valid data being shown in Firefox's request log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-479) Propagate xhr.response values in wrapper callback

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-479?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-479: ------------------------------ Affects Version/s: 2.1.0.Alpha2 2.0.3.Final > Propagate xhr.response values in wrapper callback > ------------------------------------------------- > > Key: ARQGRA-479 > URL: https://issues.jboss.org/browse/ARQGRA-479 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.3.Final, 2.1.0.Alpha2 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 2.0-Tracking, 2.1-Tracking > > > When the xhr wrapper is created the response property is copied but it isn't updated in the callback, which leads to the property values' being out of sync. Some frameworks (e.g. Angular) will use the xhr.response over xhr.responseText if it is present, which means that simply using a guardAjax in a Graphene test will cause all subsequent xhr calls to return invalid data. In my case (Firefox 38, Angular 1.4.4, Graphene 2.0.3.Final) all $http calls would return "" once a guardAjax was executed, despite valid data being shown in Firefox's request log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-479) Propagate xhr.response values in wrapper callback

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQGRA-479: --------------------------------- Summary: Propagate xhr.response values in wrapper callback Key: ARQGRA-479 URL: https://issues.jboss.org/browse/ARQGRA-479 Project: Arquillian Graphene Issue Type: Bug Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 2.0-Tracking, 2.1-Tracking When the xhr wrapper is created the response property is copied but it isn't updated in the callback, which leads to the property values' being out of sync. Some frameworks (e.g. Angular) will use the xhr.response over xhr.responseText if it is present, which means that simply using a guardAjax in a Graphene test will cause all subsequent xhr calls to return invalid data. In my case (Firefox 38, Angular 1.4.4, Graphene 2.0.3.Final) all $http calls would return "" once a guardAjax was executed, despite valid data being shown in Firefox's request log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-478) Add support for multiple @InitialPage when using Qualifiers

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-478?page=com.atlassian.jira.plugin... ] Lukáš Fryč reassigned ARQGRA-478: --------------------------------- Assignee: Michael Irwin (was: Lukáš Fryč) > Add support for multiple @InitialPage when using Qualifiers > ----------------------------------------------------------- > > Key: ARQGRA-478 > URL: https://issues.jboss.org/browse/ARQGRA-478 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: core > Reporter: Michael Irwin > Assignee: Michael Irwin > Fix For: 2.1-Tracking > > > If using multiple browsers in a test, it would be nice to support multiple @InitialPage parameters in the method, each with a separate qualifier. > Obviously, if the same qualifier is applied to more than one @InitialPage, it should throw and prevent execution. > Pull-request incoming... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-478) Add support for multiple @InitialPage when using Qualifiers

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-478?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-478: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 2.1-Tracking Resolution: Done > Add support for multiple @InitialPage when using Qualifiers > ----------------------------------------------------------- > > Key: ARQGRA-478 > URL: https://issues.jboss.org/browse/ARQGRA-478 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: core > Reporter: Michael Irwin > Assignee: Michael Irwin > Fix For: 2.1-Tracking > > > If using multiple browsers in a test, it would be nice to support multiple @InitialPage parameters in the method, each with a separate qualifier. > Obviously, if the same qualifier is applied to more than one @InitialPage, it should throw and prevent execution. > Pull-request incoming... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-478) Add support for multiple @InitialPage when using Qualifiers

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-478?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-478: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/136 > Add support for multiple @InitialPage when using Qualifiers > ----------------------------------------------------------- > > Key: ARQGRA-478 > URL: https://issues.jboss.org/browse/ARQGRA-478 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: core > Reporter: Michael Irwin > > If using multiple browsers in a test, it would be nice to support multiple @InitialPage parameters in the method, each with a separate qualifier. > Obviously, if the same qualifier is applied to more than one @InitialPage, it should throw and prevent execution. > Pull-request incoming... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-478) Add support for multiple @InitialPage when using Qualifiers

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-478?page=com.atlassian.jira.plugin... ] Lukáš Fryč reassigned ARQGRA-478: --------------------------------- Assignee: Lukáš Fryč > Add support for multiple @InitialPage when using Qualifiers > ----------------------------------------------------------- > > Key: ARQGRA-478 > URL: https://issues.jboss.org/browse/ARQGRA-478 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: core > Reporter: Michael Irwin > Assignee: Lukáš Fryč > > If using multiple browsers in a test, it would be nice to support multiple @InitialPage parameters in the method, each with a separate qualifier. > Obviously, if the same qualifier is applied to more than one @InitialPage, it should throw and prevent execution. > Pull-request incoming... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues September 2015