November 2012 - arquillian-issues

[JBoss JIRA] (ARQ-1216) More intelligent and flexible container and extension configuration

by Dan Allen (JIRA)

Dan Allen created ARQ-1216: ------------------------------ Summary: More intelligent and flexible container and extension configuration Key: ARQ-1216 URL: https://issues.jboss.org/browse/ARQ-1216 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Configuration, Deployable Containers SPI Reporter: Dan Allen Story: *In order to* make activating or selecting container configuration easier *As a* tester *I want to* be able to use ids, profiles and qualifiers in the configuration so Arquillian can automatically select the correct configuration in most cases Scenarios: *Given* that I specify an id in the container configuration *When* I use a container adapter *Then* Arquillian should be able to activate that configuration by matching the globally unique id for that container with the id of the container configuration *Given* that I define multiple container configurations with the same id, each with unique profile attributes : *And* I define the property active.container.profile in arquillian-activation.properties with a value equal to one of the profiles *When* I run the test *Then* Arquillian should select the container configuration for the profile that I activated *Given* specify a qualifier at a @Drone injection point : *And* I include a webdriver extension configuration with a qualifier attribute whose value matches the qualifier at the injection point *When* I run the test *Then* Arquillian Drone should select the extension configuration that uses that qualifier Rationale: First and foremost, container adapters should have globally unique ids. This allows Arquillian to be able to link a container configuration to the adapter in use automatically by matching the container adapter id with the id attribute on the container configuration node. If there are multiple configurations for the same adapter, then the configurations must each have a unique profile attribute value (excluding the profile attribute implies a default value). Therefore, it's only necessary to activate a container configuration when there are multiple configurations for the same adapter and you don't want to use the default selection. The default selection is either the container configuration which specifies default="true" or, if one is not explicitly marked, the container configuration without a profile attribute. If neither is the case, then an initialization error should be thrown. -- 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 month

3
2
0 / 0

[JBoss JIRA] (ARQ-1209) Abbreviate WebDriver configuration property browserCapabilities as browser

by Dan Allen (JIRA)

Dan Allen created ARQ-1209: ------------------------------ Summary: Abbreviate WebDriver configuration property browserCapabilities as browser Key: ARQ-1209 URL: https://issues.jboss.org/browse/ARQ-1209 Project: Arquillian Issue Type: Enhancement 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* save typing and make the WebDriver configuration more readable *As a* tester *I want to* be able to configure the browser using the property name "browser" instead of "browserCapabilities" Scenarios: *Given* I want to use the FirefoxDriver when running my Drone WebDriver tests *When* I set the browser (e.g., firefox) in the WebDriver configuration property named "browser" *Then* Drone should interpret the value of that property as the browserCapabilities ; *And* Drone should select and initialize the FirefoxDriver ; *And* Drone should inject the FirefoxDriver into the @Drone injection point in the test *Given* I want to use the FirefoxDriver when running my Drone WebDriver tests : *And* I have an existing Drone WebDriver configuration *When* I set the browser (e.g., firefox) in the WebDriver configuration property named "browserCapabilities" *Then* Drone should interpret the value of that property as the browserCapabilities ; *And* Drone should select and initialize the FirefoxDriver ; *And* Drone should inject the FirefoxDriver into the @Drone injection point in the test Rationale: While browserCapabilities is the official name for specifying the browser by its coordinates name, version and platform, we need not expose this formality to our users. We can honor both names for this property, perhaps throwing an exception if both are present. Once we sort that out, we should propose another scenario to cover it. -- 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 month

2
2
0 / 0

[JBoss JIRA] (ARQ-1207) Support arquillian. prefix in configuration properties

by Dan Allen (JIRA)

Dan Allen created ARQ-1207: ------------------------------ Summary: Support arquillian. prefix in configuration properties Key: ARQ-1207 URL: https://issues.jboss.org/browse/ARQ-1207 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 1.0.3.Final Reporter: Dan Allen Priority: Minor Story: *In order to* have more readable and intuitive property names *As a* tester *I want to* be able to use the arquillian. prefix to configure properties in the arquillian.properties file Scenario: *Given* that I define a property in arquillian.properties which uses the prefix arquillian. instead of arq. *When* Arquillian loads the configuration *Then* the property should be recognized Rationale: The arq. prefix may be convenient for some, but to newcomers it's cryptic. We should support both the shorthand (arq.) and the full prefix (arquillian.) when loading properties. Since the property matches are done using regular expressions, it should not be hard to add support for both prefixes. I also recommend allowing extension to be abbreviated "ext". Thus, to configure webdriver, I could use any of these property declarations: {code} arquillian.extension.webdriver.browserCapabilities=firefox arquillian.ext.webdriver.remoteReusable=true arq.ext.webdriver.remoteAddress=http://127.0.0.1:4444/wd/hub/ {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, 1 month

2
2
0 / 0

[JBoss JIRA] (ARQGRA-227) Support for injecting Actions builder

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQGRA-227: --------------------------------- Summary: Support for injecting Actions builder Key: ARQGRA-227 URL: https://issues.jboss.org/browse/ARQGRA-227 Project: Arquillian Graphene Issue Type: Feature Request Reporter: Lukáš Fryč http://code.google.com/p/selenium/wiki/AdvancedUserInteractions -- 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 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1215) Clean slf4j dependency

by Bartosz Majsak (JIRA)

Bartosz Majsak created ARQ-1215: ----------------------------------- Summary: Clean slf4j dependency Key: ARQ-1215 URL: https://issues.jboss.org/browse/ARQ-1215 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha5 Reporter: Bartosz Majsak Assignee: Bartosz Majsak Fix For: persistence_1.0.0.next Current dependency included to satisfy DBUnit is slf4j-jdk14 which is obviously potential source of classpath conflicts. Replace it with reference to API only, so the user can provide facade working with logging framework of his choice. -- 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 month

1
2
0 / 0

[JBoss JIRA] (ARQ-1211) Revisit the allowConnectToRunningServer flag for managed containers

by Vineet Reynolds (JIRA)

Vineet Reynolds created ARQ-1211: ------------------------------------ Summary: Revisit the allowConnectToRunningServer flag for managed containers Key: ARQ-1211 URL: https://issues.jboss.org/browse/ARQ-1211 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: GlassFish Containers, WebLogic Containers Reporter: Vineet Reynolds Assignee: Vineet Reynolds Based on the discussion [here|https://github.com/arquillian/arquillian-container-glassfish/pull/19] and on IRC, we need to review the Managed container implementations that use the {{allowConnectToRunningServer}} configuration property. If a managed container adapter connects to an already running instance, then it should not shut down that 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

12 years, 1 month

1
1
0 / 0

[JBoss JIRA] (ARQ-1180) Support @Drone enricher on Graphene page objects/fragments

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQ-1180: ------------------------------- Summary: Support @Drone enricher on Graphene page objects/fragments Key: ARQ-1180 URL: https://issues.jboss.org/browse/ARQ-1180 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_1.1.0.Final Reporter: Lukáš Fryč Assignee: Karel Piwko Drone's {{TestEnricher}} fails to work in page fragments. If I remember correctly, Drone tries to access or initialize context incorrectly (more information have Aslak). This issue is related to ARQGRA-191. -- 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 month

2
2
0 / 0

[JBoss JIRA] (ARQ-1213) Add support for GlassFish 3.0 container

by Vineet Reynolds (JIRA)

Vineet Reynolds created ARQ-1213: ------------------------------------ Summary: Add support for GlassFish 3.0 container Key: ARQ-1213 URL: https://issues.jboss.org/browse/ARQ-1213 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: GlassFish Containers Reporter: Vineet Reynolds Priority: Minor The RESTful admin API provided by GlassFish 3.0 has does not provide all the REST resources that are currently used by the GlassFish 3.1 adapter. Hence the 3.1 adapter, is not backward compatible with a GlassFish 3.0 instance. Additionally, the message formats returned by the REST resources of GF 3.0 are different from the ones returned by GF 3.1, hence requiring different parsing semantics. We must therefore implement a separate adapter to support GlassFish 3.0, that either uses the RESTful Admin APIs available in 3.0, or a supported API like JSR-88. -- 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 month

1
1
0 / 0

[JBoss JIRA] (ARQ-837) Managed GlassFish container does not shutdown when a test errors out

by Vineet Reynolds (JIRA)

Vineet Reynolds created ARQ-837: ----------------------------------- Summary: Managed GlassFish container does not shutdown when a test errors out Key: ARQ-837 URL: https://issues.jboss.org/browse/ARQ-837 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: GlassFish Containers Affects Versions: glassfish_1.0.0.CR3 Reporter: Vineet Reynolds When a test errors out, Arquillian does not invoke the {{DeployableContainer.stop()}} implementation of the managed GlassFish container. The GlassFish container started by Arquillian continues to run, and the subsequent test execution produces the expected error message: {{quote}} The server is already running! Managed containers does not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration {{quote}} The GlassFish container implementation should incorporate a mechanism similar to the JBoss AS 7 managed container implementation, to execute the {{asadmin stop-domain}} command in a shutdown hook. -- 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, 1 month

1
8
0 / 0

[JBoss JIRA] (ARQ-796) Remove the GlassFishRestDeploymentAppender from the GlassFish container adapter

by Vineet Reynolds (JIRA)

Vineet Reynolds created ARQ-796: ----------------------------------- Summary: Remove the GlassFishRestDeploymentAppender from the GlassFish container adapter Key: ARQ-796 URL: https://issues.jboss.org/browse/ARQ-796 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: GlassFish Containers Reporter: Vineet Reynolds Priority: Minor The GlassFishRestDeploymentAppender does not appear to serve any purpose. Although it is implemented as an auxiliary archive appender, it does not appear to be used to enhance the deployment archive. It assumes the responsibility of enhancing the archive with TestEnrichers, but this is already done by the TestEnricher extensions themselves. -- 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, 1 month

2
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues November 2012