December 2012 - arquillian-issues

[JBoss JIRA] (ARQ-1236) Warp: filter favicon.ico requests by default

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1236?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč resolved ARQ-1236. ----------------------------- Resolution: Done > Warp: filter favicon.ico requests by default > -------------------------------------------- > > Key: ARQ-1236 > URL: https://issues.jboss.org/browse/ARQ-1236 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Critical > Fix For: warp_1.0.0.Alpha2 > > Original Estimate: 1 hour, 30 minutes > Remaining Estimate: 1 hour, 30 minutes > > Real browsers usually issue request for {{favicon.ico}} right after initial request for given domain. > This makes necessary to use filtering for each request with real browser. > Let's introduce default filter feature which will filter {{favicon.ico}} out. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1197) Warp: fails to deserialize assertion when it does not have serialVersionUID=1

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1197?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč reassigned ARQ-1197: ------------------------------- Assignee: Lukáš Fryč > Warp: fails to deserialize assertion when it does not have serialVersionUID=1 > ----------------------------------------------------------------------------- > > Key: ARQ-1197 > URL: https://issues.jboss.org/browse/ARQ-1197 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Blocker > Fix For: warp_1.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1246) Warp: single execution should observe only first request

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1246?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč reassigned ARQ-1246: ------------------------------- Assignee: Lukáš Fryč > Warp: single execution should observe only first request > -------------------------------------------------------- > > Key: ARQ-1246 > URL: https://issues.jboss.org/browse/ARQ-1246 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Critical > Fix For: warp_1.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Default Warp execution mode in Alpha1 was enhancing just first request in Warp execution cycle. > In Alpha2 with introduction of WarpGroups, this behavior was changed, so user needs to define observer for almost each request for complex pages which loads multiple requests, otherwise Warp fails with message that there are too much requests. > Default behavior in single execution scenario (which means without using request groups) is that only first request matching criteria is enhanced with Warp. > This will also preserve backward compatibility. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1246) Warp: single execution should observe only first request

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1246?page=com.atlassian.jira.plugin.s... ] Work on ARQ-1246 started by Lukáš Fryč. > Warp: single execution should observe only first request > -------------------------------------------------------- > > Key: ARQ-1246 > URL: https://issues.jboss.org/browse/ARQ-1246 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Critical > Fix For: warp_1.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Default Warp execution mode in Alpha1 was enhancing just first request in Warp execution cycle. > In Alpha2 with introduction of WarpGroups, this behavior was changed, so user needs to define observer for almost each request for complex pages which loads multiple requests, otherwise Warp fails with message that there are too much requests. > Default behavior in single execution scenario (which means without using request groups) is that only first request matching criteria is enhanced with Warp. > This will also preserve backward compatibility. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1236) Warp: filter favicon.ico requests by default

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1236?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-1236: ---------------------------- Summary: Warp: filter favicon.ico requests by default (was: Warp: filter favicon requests by default and use only first request for single executor) > Warp: filter favicon.ico requests by default > -------------------------------------------- > > Key: ARQ-1236 > URL: https://issues.jboss.org/browse/ARQ-1236 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Critical > Fix For: warp_1.0.0.Alpha2 > > Original Estimate: 1 hour, 30 minutes > Remaining Estimate: 1 hour, 30 minutes > > Real browsers usually issue request for {{favicon.ico}} right after initial request for given domain. > This makes necessary to use filtering for each request with real browser. > Let's introduce default filter feature which will filter {{favicon.ico}} out. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1246) Warp: single execution should observe only first request

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1246?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-1246: ---------------------------- Original Estimate: 2 hours Remaining Estimate: 2 hours > Warp: single execution should observe only first request > -------------------------------------------------------- > > Key: ARQ-1246 > URL: https://issues.jboss.org/browse/ARQ-1246 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Lukáš Fryč > Priority: Critical > Fix For: warp_1.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Default Warp execution mode in Alpha1 was enhancing just first request in Warp execution cycle. > In Alpha2 with introduction of WarpGroups, this behavior was changed, so user needs to define observer for almost each request for complex pages which loads multiple requests, otherwise Warp fails with message that there are too much requests. > Default behavior in single execution scenario (which means without using request groups) is that only first request matching criteria is enhanced with Warp. > This will also preserve backward compatibility. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1246) Warp: single execution should observe only first request

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1246?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-1246: ---------------------------- Sprint: Final Sprint > Warp: single execution should observe only first request > -------------------------------------------------------- > > Key: ARQ-1246 > URL: https://issues.jboss.org/browse/ARQ-1246 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Lukáš Fryč > Priority: Critical > Fix For: warp_1.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Default Warp execution mode in Alpha1 was enhancing just first request in Warp execution cycle. > In Alpha2 with introduction of WarpGroups, this behavior was changed, so user needs to define observer for almost each request for complex pages which loads multiple requests, otherwise Warp fails with message that there are too much requests. > Default behavior in single execution scenario (which means without using request groups) is that only first request matching criteria is enhanced with Warp. > This will also preserve backward compatibility. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1246) Warp: single execution should observe only first request

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQ-1246: ------------------------------- Summary: Warp: single execution should observe only first request Key: ARQ-1246 URL: https://issues.jboss.org/browse/ARQ-1246 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Warp Reporter: Lukáš Fryč Priority: Critical Fix For: warp_1.0.0.Alpha2 Default Warp execution mode in Alpha1 was enhancing just first request in Warp execution cycle. In Alpha2 with introduction of WarpGroups, this behavior was changed, so user needs to define observer for almost each request for complex pages which loads multiple requests, otherwise Warp fails with message that there are too much requests. Default behavior in single execution scenario (which means without using request groups) is that only first request matching criteria is enhanced with Warp. This will also preserve backward compatibility. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1245) Allow FirefoxDriver to pass profile as file

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1245: -------------------------------- Summary: Allow FirefoxDriver to pass profile as file Key: ARQ-1245 URL: https://issues.jboss.org/browse/ARQ-1245 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_1.1.0.Final Reporter: Karel Piwko By default, WebDriver capability uses JSON/Base64 formatted script, which is not easily usable by end users. Allow users to pass a path to Firefox Profile instead, as they are used from Selenium 1. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1244) Warp: shortcuts for defining WebDriver activities

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQ-1244: ------------------------------- Summary: Warp: shortcuts for defining WebDriver activities Key: ARQ-1244 URL: https://issues.jboss.org/browse/ARQ-1244 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Lukáš Fryč {code:java} @FindBy WebElement loginButton; Warp .initiate(drive(loginButton).click()) .inspect(new Inspect() { ... }); {code} -- 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, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues December 2012