[JBoss JIRA] (ARQ-1212) Add support for GlassFish 2.x containers
by Vineet Reynolds (JIRA)
Vineet Reynolds created ARQ-1212:
------------------------------------
Summary: Add support for GlassFish 2.x containers
Key: ARQ-1212
URL: https://issues.jboss.org/browse/ARQ-1212
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: GlassFish Containers
Reporter: Vineet Reynolds
Priority: Minor
There has been atleast one request to support the GlassFish 2.x container. Since the RESTful admin API used by the current GlassFish adapter is available only since 3.0, we'll need to implement support for 2.x using a different mechanism (possibly using JSR-88 APIs).
--
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
11 years, 7 months
[JBoss JIRA] (ARQ-1206) Configuration option to delete all cookies on reusable browser instance
by Dan Allen (JIRA)
Dan Allen created ARQ-1206:
------------------------------
Summary: Configuration option to delete all cookies on reusable browser instance
Key: ARQ-1206
URL: https://issues.jboss.org/browse/ARQ-1206
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Drone
Affects Versions: drone_1.1.0.Final
Reporter: Dan Allen
Assignee: Karel Piwko
Story:
*In order* to avoid false results from state leaking between deployments when using a reusable browser instance
*As a* tester
*I want* to be able to specify that Drone delete all cookies after reconnecting the the resuable browser instance
Scenario:
*Given* that I've configured the WebDriver extension to use a remote reusable instance
: *And* I configure the WebDriver extension to deleteAllCookies
*When* I inject WebDriver into my test at a @Drone injection point
*Then* The browser should have no cookies
Rationale:
The deleteAllCookies configuration option eliminates potential side effects of using a remote reusable browser instance.
--
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
11 years, 7 months
[JBoss JIRA] (ARQ-1205) Expose a resolver in the SPI to lookup the deploymentUrl easily from an extension
by Dan Allen (JIRA)
Dan Allen created ARQ-1205:
------------------------------
Summary: Expose a resolver in the SPI to lookup the deploymentUrl easily from an extension
Key: ARQ-1205
URL: https://issues.jboss.org/browse/ARQ-1205
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Base Implementation
Affects Versions: 1.0.3.Final
Reporter: Dan Allen
Priority: Minor
Story:
*In order* to initialize clients to conveniently access URLs in the deployed application
*As an* extension writer
*I want* to be able to use an SPI to calculate the deployment URL (consistent with the [URLResourceProvider|http://docs.jboss.org/arquillian/aggregate/1.0.3.Fina...])
Scenarios:
*Given* that I need to access the deployment URL from an extension
*When* I invoke a public SPI method that resolves the deployment URL
: *And* the test case only has one deployment
*Then* the SPI method should return the URL to that deployment
*Given* that I need to access the deployment URL from an extension
*When* I invoke a public SPI method that resolves the deployment URL
: *And* the test case has multiple deployments
: *And* I specify a string-based deployment name as an argument
*Then* the SPI method should return the URL to that deployment
Rationale:
Extensions may need access to the deploymentUrl for setting up resources, such as a client. However, there is quite a bit of logic necessary to resolve the deploymentUrl properly, especially when multiple deployments are in use.
Therefore, I propose adding an SPI that exposes the logic in the URLResourceProvider. Here's a rough sketch of the SPI:
{code}
public interface DeploymentURLResolver {
public URL resolveURL();
public URL resolveURL(String deploymentName);
}
{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
11 years, 7 months