[JBoss JIRA] (ARQ-868) Update Selenium version to 2.21.0
by Karel Piwko (JIRA)
Karel Piwko created ARQ-868:
-------------------------------
Summary: Update Selenium version to 2.21.0
Key: ARQ-868
URL: https://issues.jboss.org/browse/ARQ-868
Project: Arquillian
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Extension - Drone
Affects Versions: drone_1.0.0.Final
Reporter: Karel Piwko
Assignee: Karel Piwko
Update Arquillian Drone to reflect new changes in Selenium 2.21.0.
* Update version
* Add support for new parameters of Selenium Server
* Add support for Safari driver
From: http://selenium.googlecode.com/svn/trunk/java/CHANGELOG
{code}
WebDriver:
* Safaridriver has now been added !
* Issue 3489, maximize the browser window
* Significant stability improvements in firefoxdriver.
* Issue 3357 log-path for chromedriver
* IE driver issue 3360
* Android driver issue 3504
* Firefox issue 3559, max-connections-per-server
* Issue 3520
* Issue 2826
* Native events support for Firefox 11
* Dropped native events support for Firefoxes 4-9
Grid:
* Significant changes in the timeout strategy0 between hub, nodes and browser.
See http://code.google.com/p/selenium/wiki/Grid2 section on timeouts.
Compatibility note: It is recommended to at least update the nodes
to 2.21. Upgrading only the hub will effectively disable the
browser-death timeout and is *not* recommended.
* Improved error messages on console
* Content length issue solved, Issue 2362
* Issues 3328,3366
* Improvements in thread dumps in both hub and node,
possible to corrolate the two.
* Added hub api to query parameters
Server:
* -browserTimeout <timeoutInSeconds> added to
differentiate between browser hang and client gone (which is
-timeout <timeout>)
- System property -Dselenium.server.timeout removed, use -timeout instead.
See http://code.google.com/p/selenium/wiki/RemoteWebDriverServer
for further details.
* Issue 3577
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] Created: (ARQ-578) Create a Extension for handling Server State assertion during normal Servlet/JSF requests
by Aslak Knutsen (JIRA)
Create a Extension for handling Server State assertion during normal Servlet/JSF requests
-----------------------------------------------------------------------------------------
Key: ARQ-578
URL: https://issues.jboss.org/browse/ARQ-578
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Aslak Knutsen
The general requirements would be:
* hook into existing lifecycle callbacks from server (after_render, request_destory)
* inject and assert on state during request in container
** we want this to happen during request so all state is still available (@RequestScope)
* assert on output on client side
** this limits the need for incontianer deps / packaging
Rough API idea/draft:
https://gist.github.com/1184904
If we can piggyback the ServerState Assertion object to 'any' HTML request, we should be able to reuse existing tools for client testing like htmlunit / selenium, but with incontainer assertions.
This could be JSFUnit 3+ combined with a Serlvet Extension.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] Created: (ARQ-355) Support fluent API and @DeploymentTarget for Rules
by Aslak Knutsen (JIRA)
Support fluent API and @DeploymentTarget for Rules
--------------------------------------------------
Key: ARQ-355
URL: https://issues.jboss.org/browse/ARQ-355
Project: Arquillian
Issue Type: Feature Request
Components: Extension - Byteman
Reporter: Aslak Knutsen
Priority: Minor
With multi container support in arquillian, the byteman integration should support @DeploymentTarget for specifying which container a rule should be deployed on.
Byteman integration could follow the ShrinkWrap fluent API and make a API for rule creation, instead of having it only declarative via Annotaitons.
@BMRule @DeploymentTarget("name")
public static Rule createExceptionRule()
{
return Byteman.rule().....
}
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years