March 2014 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1615) Warp JSF: detect and sanitize FacesContextWrapper chain

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1615?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč reassigned ARQ-1615: ------------------------------- Assignee: Lukáš Fryč > Warp JSF: detect and sanitize FacesContextWrapper chain > ------------------------------------------------------- > > Key: ARQ-1615 > URL: https://issues.jboss.org/browse/ARQ-1615 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: warp_1.0.0.Alpha7 > > > When there is a chain of {{FacesContextWrapper}}s then Warp's WrappedFacesContext might fail to be detected and Warp itself may fail. > Use a while loop to iterate through wrappers in order to detect correct wrapper. > Needs to be accompanied with a ftest. -- 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

1
0
0 / 0

[JBoss JIRA] (ARQ-1615) Warp JSF: detect and sanitize FacesContextWrapper chain

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1615?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč resolved ARQ-1615. ----------------------------- Resolution: Done > Warp JSF: detect and sanitize FacesContextWrapper chain > ------------------------------------------------------- > > Key: ARQ-1615 > URL: https://issues.jboss.org/browse/ARQ-1615 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: warp_1.0.0.Alpha7 > > > When there is a chain of {{FacesContextWrapper}}s then Warp's WrappedFacesContext might fail to be detected and Warp itself may fail. > Use a while loop to iterate through wrappers in order to detect correct wrapper. > Needs to be accompanied with a ftest. -- 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

1
0
0 / 0

[JBoss JIRA] (ARQ-1535) Warp: getting intermittent issues in RichFaces tests

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1535?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč reassigned ARQ-1535: ------------------------------- Assignee: Lukáš Fryč > Warp: getting intermittent issues in RichFaces tests > ---------------------------------------------------- > > Key: ARQ-1535 > URL: https://issues.jboss.org/browse/ARQ-1535 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: warp_1.0.0.Alpha7 > > > See RF-13222 for issue details. -- 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

1
0
0 / 0

[JBoss JIRA] (ARQ-1703) Add annotation to add comments to test report

by Alex Soto (JIRA)

Alex Soto created ARQ-1703: ------------------------------ Summary: Add annotation to add comments to test report Key: ARQ-1703 URL: https://issues.jboss.org/browse/ARQ-1703 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Recorder Reporter: Alex Soto Priority: Minor Sometimes when you write some automatic tests, you also want that QA team execute them manually, maybe because that business case is critical or because automatic test can only cover one part. So it would be good if for example we could annotate test method with an annotation like: @Report("This test should be executed manually too") And then this message may be available on reporter class and could be written to report. -- 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

1
0
0 / 0

[JBoss JIRA] (ARQGRA-425) Allow @Location with relative URL when there is no deployment

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-425?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-425: ------------------------------ Fix Version/s: 2.1-Tracking > Allow @Location with relative URL when there is no deployment > ------------------------------------------------------------- > > Key: ARQGRA-425 > URL: https://issues.jboss.org/browse/ARQGRA-425 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj Húska > Fix For: 2.1-Tracking > > > There are some use cases when there is no {{@Deployment}} method, and we still need to treat {{URL}} in {{@Location}} as relative. > E.g. we are testing an application already deployed somewhere, but still the context root of the application can change, and we do not want to hardcode it. > As [~kpiwko] suggested, we can support his in Graphene like this: > # wrap {{org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider}} > # make it returns some default value of {{contextRoot}} if the {{contextRoot}} is null > # make that value configurable via Graphene configuration -- 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

1
0
0 / 0

[JBoss JIRA] (ARQGRA-425) Allow @Location with relative URL when there is no deployment

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-425?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-425: ----------------------------------- Right, we need to provide own wrapper for URLResourceProvider +1 this will be nice addition > Allow @Location with relative URL when there is no deployment > ------------------------------------------------------------- > > Key: ARQGRA-425 > URL: https://issues.jboss.org/browse/ARQGRA-425 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj Húska > > There are some use cases when there is no {{@Deployment}} method, and we still need to treat {{URL}} in {{@Location}} as relative. > E.g. we are testing an application already deployed somewhere, but still the context root of the application can change, and we do not want to hardcode it. > As [~kpiwko] suggested, we can support his in Graphene like this: > # wrap {{org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider}} > # make it returns some default value of {{contextRoot}} if the {{contextRoot}} is null > # make that value configurable via Graphene configuration -- 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

1
0
0 / 0

[JBoss JIRA] (ARQGRA-425) Allow @Location with relative URL when there is no deployment

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-425?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-425: ----------------------------------- I would vote for implementing it on 2.1 branch > Allow @Location with relative URL when there is no deployment > ------------------------------------------------------------- > > Key: ARQGRA-425 > URL: https://issues.jboss.org/browse/ARQGRA-425 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj Húska > > There are some use cases when there is no {{@Deployment}} method, and we still need to treat {{URL}} in {{@Location}} as relative. > E.g. we are testing an application already deployed somewhere, but still the context root of the application can change, and we do not want to hardcode it. > As [~kpiwko] suggested, we can support his in Graphene like this: > # wrap {{org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider}} > # make it returns some default value of {{contextRoot}} if the {{contextRoot}} is null > # make that value configurable via Graphene configuration -- 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

1
0
0 / 0

[JBoss JIRA] (ARQGRA-425) Allow @Location with relative URL when there is no deployment

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-425?page=com.atlassian.jira.plugin... ] Juraj Húska commented on ARQGRA-425: ------------------------------------ [~smikloso] is playing nicely with URL in https://github.com/smiklosovic/arquillian-smart-url. We might reuse something from that solution. > Allow @Location with relative URL when there is no deployment > ------------------------------------------------------------- > > Key: ARQGRA-425 > URL: https://issues.jboss.org/browse/ARQGRA-425 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj Húska > > There are some use cases when there is no {{@Deployment}} method, and we still need to treat {{URL}} in {{@Location}} as relative. > E.g. we are testing an application already deployed somewhere, but still the context root of the application can change, and we do not want to hardcode it. > As [~kpiwko] suggested, we can support his in Graphene like this: > # wrap {{org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider}} > # make it returns some default value of {{contextRoot}} if the {{contextRoot}} is null > # make that value configurable via Graphene configuration -- 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

1
0
0 / 0

[JBoss JIRA] (ARQ-1701) Allow possibility to resize screenshots

by Alex Soto (JIRA)

[ https://issues.jboss.org/browse/ARQ-1701?page=com.atlassian.jira.plugin.s... ] Alex Soto commented on ARQ-1701: -------------------------------- Ok I am not sure when I will have time to do it but I try it as soon as possible. Maybe for JavaLand hackergarten. > Allow possibility to resize screenshots > --------------------------------------- > > Key: ARQ-1701 > URL: https://issues.jboss.org/browse/ARQ-1701 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Priority: Minor > > When a screenshot is taken, user can decide if image is big enough to be added as link and not as embed image. Another approach that may find users useful is resize the image, so for example with a resize property you can decide that if an image is big enough instead of adding it as a link, resize the image to given percentage/fixed width, and embed inside the document. > In this case we should decide if image is resized and nothing more, or if it is resized and add an option to open the full screen. -- 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

1
0
0 / 0

[JBoss JIRA] (ARQ-1702) Add optional label for report title

by Alex Soto (JIRA)

Alex Soto created ARQ-1702: ------------------------------ Summary: Add optional label for report title Key: ARQ-1702 URL: https://issues.jboss.org/browse/ARQ-1702 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Recorder Reporter: Alex Soto Priority: Minor By default report title is fixed in xslt template or in AsciiDoc document. Allow users to define its own title may open the door to do something like: <extension> <property name="title">Tests results under ${env}</property> So the title can be for example "Test results under PRE environment", "Test results under QA environment", and so on, instead of fixed title. -- 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

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues March 2014