[JBoss JIRA] (ARQGRA-422) Regression in request guard
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-422?page=com.atlassian.jira.plugin... ]
Juraj Húska updated ARQGRA-422:
-------------------------------
Steps to Reproduce:
# git clone https://github.com/richfaces/richfaces-qa.git
# git checkout requestGuardReproducer
# cd metamer/ftest
# mvn clean verify -P jbossas-managed-7-1 -Dtest=TestRequestGuardWithNotifyMessage
was:
# git clone https://github.com/richfaces/richfaces-qa.git
# git checkout requestGuardReproducer
# mvn clean verify -P jbossas-managed-7-1 -Dtest=TestRequestGuardWithNotifyMessage
> Regression in request guard
> ---------------------------
>
> Key: ARQGRA-422
> URL: https://issues.jboss.org/browse/ARQGRA-422
> Project: Arquillian Graphene
> Issue Type: Bug
> Components: core
> Affects Versions: 2.0.1.Final
> Environment: RichFaces 5.0.0-SNAPSHOT
> Arquillian Core 1.1.2.Final
> Arquillian Drone 1.2.3.Final
> Arquillian Graphene 2.0.1.Final
> Selenium 2.39.0
> Reporter: Pavol Pitonak
> Assignee: Juraj Húska
> Priority: Blocker
>
> I have a simple page with two inputs, a submit button and two notify messages (one for each input) -
> https://github.com/richfaces/richfaces-qa/blob/requestGuardReproducer/met...
> When you guard ajax request when button is clicked, it fails with timeout:
> {code}
> org.openqa.selenium.TimeoutException: Timed out after 2 seconds waiting for org.jboss.arquillian.graphene.guard.RequestGuardFactory$RequestIsDone@19eda624
> {code}
> * when you run test (in Steps to Reproduce) all three tests fail on request guard (guarding Ajax request)
> * it doesn't matter how WebElement is obtained (WebDriver.find, \@FindBy or \@Page
> * these tests fail only when two validation errors are on page, i.e. when two notifyMessage components are displayed
> ** e.g. change value of second input from 888 to 8 in guardReproducer.xhtml and it will work
> * worked fine with Graphene 2.0.0.Final
--
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
[JBoss JIRA] (ARQ-1489) Warp Filter: prepend to all other filters in a chain & do not participate in forwarding
by Harald Albers (JIRA)
[ https://issues.jboss.org/browse/ARQ-1489?page=com.atlassian.jira.plugin.s... ]
Harald Albers commented on ARQ-1489:
------------------------------------
As the release was not available yet, I tried a local build of 1.0.0.Alpha7.
The issue is resolved in the demonstration project (which I updated) and in my production project.
Thanks a lot!
> Warp Filter: prepend to all other filters in a chain & do not participate in forwarding
> ---------------------------------------------------------------------------------------
>
> Key: ARQ-1489
> URL: https://issues.jboss.org/browse/ARQ-1489
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: 1.0.0.Alpha4
> Environment: Arquillian Warp 1.0.0.Alpha4 with Rewrite 2.0.7.Final in a JBoss AS 7.1.1.Final
> Reporter: Harald Albers
> Assignee: Lukáš Fryč
> Fix For: warp_1.0.0.Alpha7
>
>
> *Original title*: Warp: response payload was never registered when used with OCPsoft Rewrite
> I use OCPsoft Rewrite (http://ocpsoft.org/rewrite/) to add fancy URL aliases to my JSF webapp.
> Warp tests work as long as I use the original unaliased URLs.
> Warp tests using the aliased URLs fail with
> {quote}
> ClientWarpExecutionException: deenriching response failed: The response payload with serialId [...] was never registered
> {quote}
> I created a demonstration project, see README.md for details:
> https://github.com/albers/arquillian-showcase/tree/rewrite
--
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
[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:
--------------------------------
Interesting point about resizing, I think you are right I could do it from presentation point of view, only calculating the new resize width/height and set parameters to html.
Cool!! much less work to do.
> 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
[JBoss JIRA] (ARQ-1701) Allow possibility to resize screenshots
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1701?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic commented on ARQ-1701:
----------------------------------------
xuggler is what we use in desktop recorder implementation of video api, there are yet unreleased implementations here (1). Desktop video recorder will have its own repo, Droidium screenshooter will be part of Droidium alpha5 and browser screenshooter will be part of Graphene project.
When you talked about resizing, I was thinking that an image will be resized only from presentation point of view. That means an image would be unmodified as such but it would be "resized" in output HTML page when you set "width" and "hight" attributes to img tag. You would just displayed them differently but they would be just the same as they were.
Implementing this would mean you would hack that xsl template around to be able to resize them, from html / xsl point of view, dynamically.
(1) https://github.com/smiklosovic/recorder-implementations
> 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
[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:
--------------------------------
I have been doing some research about this topic. In case of images it is relatively simple, we can do it natively(http://stackoverflow.com/questions/244164/resize-an-image-in-jav... or by using an API (http://www.thebuzzmedia.com/software/imgscalr-java-image-scaling-library/) I think that using an API will be better because it deals with some problems of resizing, but if you this could be a problem then I implement with Java 2D natively.
The problem is with video resizing, I have only found one library to do it http://www.xuggle.com/xuggler/ but you need to install a software externally because it depends on ffmpeg (works in all OS anyway), so I think that resizing video it is a more complicated that simply calling an API. [~smikloso] Do you have any experience on video management?
> 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