March 2011 - arquillian-issues - Jboss List Archives

[JBoss JIRA] Created: (ARQ-283) Support loading of configuration for Arquillian-Selenium

by Karel Piwko (JIRA)

Support loading of configuration for Arquillian-Selenium -------------------------------------------------------- Key: ARQ-283 URL: https://jira.jboss.org/browse/ARQ-283 Project: Arquillian Issue Type: Feature Request Components: Configuration Affects Versions: 1.0.0.Beta1 Reporter: Karel Piwko Assignee: Karel Piwko Fix For: 1.0.0.Beta1 At the moment, Arquillian Selenium extension does not support loading configuration through arquillian.xml, but only through System properties. Align configuration with the XML based one, developed within ARQ-215 and find a way how to leave System.properties configuration intact. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
5
0 / 0

[JBoss JIRA] Created: (ARQ-124) Move jndi.properties out as Configuration

by Aslak Knutsen (JIRA)

Move jndi.properties out as Configuration ----------------------------------------- Key: ARQ-124 URL: https://jira.jboss.org/jira/browse/ARQ-124 Project: Arquillian Issue Type: Task Components: Configuration, Documentation Affects Versions: 1.0.0.Alpha1, 1.0.0.Alpha2 Reporter: Aslak Knutsen When using multiple containers in the same project they might require different jndi.properties files. Since jndi.properties are sucked in by the InitialContext automagically, multiple resource folders has to be used to control which jndi.properties file is the active. Remove the need for jndi.properties by extending the Configuration module to support jndi properties pr container. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
6
0 / 0

[JBoss JIRA] Created: (ARQ-346) Create a GlassFish 3.1 Embedded Container

by Aslak Knutsen (JIRA)

Create a GlassFish 3.1 Embedded Container ----------------------------------------- Key: ARQ-346 URL: https://issues.jboss.org/browse/ARQ-346 Project: Arquillian Issue Type: Feature Request Components: GlassFish Containers Reporter: Aslak Knutsen Fix For: 1.0.0.Beta1 GlassFish 3.1 Embedded has a new API http://java.net/jira/browse/GLASSFISH-14638 http://java.net/jira/browse/GLASSFISH-13016 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
4
0 / 0

[JBoss JIRA] Created: (ARQ-393) Update Arquillian Drone Docbook

by Karel Piwko (JIRA)

Update Arquillian Drone Docbook ------------------------------- Key: ARQ-393 URL: https://issues.jboss.org/browse/ARQ-393 Project: Arquillian Issue Type: Task Components: Extension - Selenium Reporter: Karel Piwko Assignee: Karel Piwko Fix For: 1.0.0.Alpha5 Arquillian Drone had come a long way during Alpha5 release cycle. Update docbook to cover name change, new Drone SPI, Arquillian Ajocado support and multiple browsers per test. Also describe browser life cycle and its difference for Field/Argument enrichment. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
3
0 / 0

[JBoss JIRA] Created: (ARQ-387) Selenium extension should use the TestEnricher SPI to do injection into the test case

by Aslak Knutsen (JIRA)

Selenium extension should use the TestEnricher SPI to do injection into the test case ------------------------------------------------------------------------------------- Key: ARQ-387 URL: https://issues.jboss.org/browse/ARQ-387 Project: Arquillian Issue Type: Feature Request Components: Extension - Selenium Reporter: Aslak Knutsen Assignee: Karel Piwko Fix For: 1.0.0.Alpha5 Reimplement injection features to use the org.jboss.arquillian.spi.TestEnricher SPI. Adds support for TestMethod argument injection -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
3
0 / 0

[JBoss JIRA] Created: (ARQ-291) Create Selenium extension

by Karel Piwko (JIRA)

Create Selenium extension ------------------------- Key: ARQ-291 URL: https://jira.jboss.org/browse/ARQ-291 Project: Arquillian Issue Type: Task Components: Test Protocol SPIs and Implementation Affects Versions: 1.0.0.Beta1 Reporter: Karel Piwko Assignee: Karel Piwko Fix For: 1.0.0.Beta1 Create Selenium extension, which will make allow developer to test whole web application by Selenium in Arquillian's AS_CLIENT mode. Optionally, add a support for starting/stopping Selenium Server as a part of test lifecycle. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
5
0 / 0

[JBoss JIRA] Created: (ARQ-377) Reloaded Container test is failing; MCServer and ShrinkWrapDeployer can't bind to correct scope

by Andrew Rubinger (JIRA)

Reloaded Container test is failing; MCServer and ShrinkWrapDeployer can't bind to correct scope ----------------------------------------------------------------------------------------------- Key: ARQ-377 URL: https://issues.jboss.org/browse/ARQ-377 Project: Arquillian Issue Type: Bug Reporter: Andrew Rubinger Assignee: Aslak Knutsen java.lang.IllegalArgumentException: No active DeploymentScoped Context to bind to Both the instance members of the ReloadedContainer are set to @DeploymentScoped, though they're not part of the deployment state. The above error is resulting, blocking the build. This is currently tracked in upstream/next. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
4
0 / 0

[JBoss JIRA] Created: (ARQ-389) Rename @Target, @Expected, @Run and @DeploymentTarget annotations

by Aslak Knutsen (JIRA)

Rename @Target, @Expected, @Run and @DeploymentTarget annotations ----------------------------------------------------------------- Key: ARQ-389 URL: https://issues.jboss.org/browse/ARQ-389 Project: Arquillian Issue Type: Feature Request Components: Base Implementation Affects Versions: 1.0.0.Alpha4 Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: 1.0.0.Alpha5 For better consistent naming, we should rename the API annotations: * @Run(RunModeType) = @RunAsClient ** InContainer is extracted from @Deployment(testable) and only possible to override with AS_CLIENT * @Expected = @ShouldThrowException * @Target = @TargetsContainer("x") ** Clearify meaning * @DeploymentTarget = @OperateOnDeployment ** Clearify that this test will operate within the context of the @Deployment {code} public class TestClass { @Deployment(name = "dep", testable=false) @ShouldThrowException(Exception.class) @TargetsContainer("x") public JavaArchive create() {} container x{ deployment dep{ @Test @RunAsClient @OperateOnDeployment("dep") public void shouldBe() {} container x{ @Test @OperateOnContainer("x") public void shouldBe() {} } {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
7
0 / 0

[JBoss JIRA] Created: (ARQ-290) performence/pom.xml references WELD-1.0.1

by steven verborgh (JIRA)

performence/pom.xml references WELD-1.0.1 ----------------------------------------- Key: ARQ-290 URL: https://jira.jboss.org/browse/ARQ-290 Project: Arquillian Issue Type: Bug Components: Build Infrastructure Environment: Mac OS, Maven 3, using jboss-repository-public as in JBoss maven Getting started wiki Reporter: steven verborgh build fails with: [ERROR] The build could not read 1 project -> [Help 1] [ERROR] The project org.jboss.arquillian.extension:arquillian-performance:1.0.0-SNAPSHOT (/Users/verborghs/Documents/Repositories/arquilian/arquillian/arquillian/extensions/performance/pom.xml) has 4 errors [ERROR] Non-resolvable import POM org.jboss.weld:weld-core-bom:1.0.2-SNAPSHOT: Failed to resolve POM for org.jboss.weld:weld-core-bom:1.0.2-SNAPSHOT due to The following artifacts could not be resolved: org.jboss.weld:weld-core-bom:pom:1.0.2-SNAPSHOT: Could not find artifact org.jboss.weld:weld-core-bom:pom:1.0.2-SNAPSHOT in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public-jboss/, releases=true, snapshots=true, managed=false) @ line 105, column 26 -> [Help 2] [ERROR] 'dependencies.dependency.version' for org.jboss.weld:weld-core:jar is missing. @ line 84, column 25 [ERROR] 'dependencies.dependency.version' for org.jboss.weld:weld-api:jar is missing. @ line 88, column 25 [ERROR] 'dependencies.dependency.version' for org.slf4j:slf4j-simple:jar is missing. @ line 92, column 25 [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException Solved by replacing 1.0.2-SNAPSHOT which is no longer in https://repository.jboss.org/nexus/content/groups/public-jboss/ to 1.1.0-SNAPSHOT -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
10
0 / 0

[JBoss JIRA] Created: (ARQ-323) Implement a GlassFish 3.1 remote container based on REST API

by Dan Allen (JIRA)

Implement a GlassFish 3.1 remote container based on REST API ------------------------------------------------------------ Key: ARQ-323 URL: https://jira.jboss.org/browse/ARQ-323 Project: Arquillian Issue Type: Feature Request Components: GlassFish Containers Affects Versions: 1.0.0.Alpha4 Reporter: Dan Allen Priority: Minor The GlassFish 3 remote container is based on JMX. GlassFish 3.1 has a much more powerful REST administration API. This API should be leveraged to create the GlassFish 3.1 remote and managed container. @see http://wikis.sun.com/display/GlassFish/V3.1RESTfulApiOnePager @see http://blogs.steeplesoft.com/2010/08/glassfish-administration-the-rest-of... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
8
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues March 2011