March 2012 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQAJO-129) Blog about renaming to Graphene

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQAJO-129: --------------------------------- Summary: Blog about renaming to Graphene Key: ARQAJO-129 URL: https://issues.jboss.org/browse/ARQAJO-129 Project: Arquillian Ajocado Issue Type: Sub-task Reporter: Lukáš Fryč Fix For: 1.0.0.CR3 -- 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

13 years, 12 months

1
3
0 / 0

[JBoss JIRA] (ARQ-688) Arquillian can't start EAP 5.1

by Tomáš Schlosser (Created) (JIRA)

Arquillian can't start EAP 5.1 ------------------------------ Key: ARQ-688 URL: https://issues.jboss.org/browse/ARQ-688 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Environment: Arquillian 1.0.0.CR6 JBoss EAP 5.1.1 Reporter: Tomáš Schlosser When using JBoss container in manual mode and try to start it, the command throw exception because JBoss EAP does not start within 30 seconds. No command response within timeout of 30000 ms. org.jboss.arquillian.protocol.servlet.runner.ServletCommandService.execute(ServletCommandService.java:60) at org.jboss.arquillian.container.test.impl.client.container.ContainerContainerController.start(ContainerContainerController.java:45) at org.jboss.qa.brms.bre.container.TransactionsTest.foo(TransactionsTest.java:16) 98 lines not shown -- 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

13 years, 12 months

4
3
0 / 0

[JBoss JIRA] (ARQ-748) Update Arquillian test dependencies to be able to do a clean build against Maven Central

by Karel Piwko (JIRA)

Karel Piwko created ARQ-748: ------------------------------- Summary: Update Arquillian test dependencies to be able to do a clean build against Maven Central Key: ARQ-748 URL: https://issues.jboss.org/browse/ARQ-748 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Build Infrastructure Affects Versions: 1.0.0.CR7 Reporter: Karel Piwko Assignee: Karel Piwko * CDI TestEnricher Current version 1.1.0.Final is not available in Maven Central. Note that the change would require an update to related slf4j bindings to 1.6.1. * Servlet Protocol jboss.web:servlet-api:jar:3.0.0.alpha-25 in not available in Maven Central to be replaced with {code:xml} <dependency> <groupId>org.jboss.spec.javax.servlet</groupId> <artifactId>jboss-servlet-api_3.0_spec</artifactId> <version>1.0.0.Final</version> </dependency> {code} * Arquillian Example Domain/JUnit/TestNG same as protocol and org.jboss.ejb3:jboss-ejb3-api:jar:3.1.0 replaced with {code:xml} <dependency> <groupId>org.jboss.spec.javax.ejb</groupId> <artifactId>jboss-ejb-api_3.1_spec</artifactId> <version>1.0.1.Final</version> </dependency> {code} and javax.jms:jms with {code:xml} <dependency> <groupId>org.jboss.spec.javax.jms</groupId> <artifactId>jboss-jms-api_1.1_spec</artifactId> <version>1.0.0.Final</version> </dependency> {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

14 years

2
6
0 / 0

[JBoss JIRA] (ARQ-715) Add a getter for ProtocolMetaData.contexts

by Alexis Hassler (Created) (JIRA)

Add a getter for ProtocolMetaData.contexts ------------------------------------------ Key: ARQ-715 URL: https://issues.jboss.org/browse/ARQ-715 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Base Implementation Reporter: Alexis Hassler Having a ProtocolMetaData.getContexts() method would help to safely clone (and rewrite) metadata in extensions. Without that method, we could forget some contexts. -- 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

14 years

4
5
0 / 0

[JBoss JIRA] (ARQ-792) Honor system property for debugging Arquillian internals

by Karel Piwko (JIRA)

Karel Piwko created ARQ-792: ------------------------------- Summary: Honor system property for debugging Arquillian internals Key: ARQ-792 URL: https://issues.jboss.org/browse/ARQ-792 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.0.0.CR7 Reporter: Karel Piwko Often an extension developer wants to know what's going in Arquillian. There is a way how to enable a debug mode, however it requires a complete build of Arquillian from source: It should honor a property instead: {code} mvn test -Darquillian.debug=true {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

14 years

2
4
0 / 0

[JBoss JIRA] (ARQ-724) Upgrade to ShrinkWrap Resolver 1.1.0-alpha-2 in arquillian-parent.pom

by Juergen Zimmermann (Created) (JIRA)

Upgrade to ShrinkWrap Resolver 1.1.0-alpha-2 in arquillian-parent.pom --------------------------------------------------------------------- Key: ARQ-724 URL: https://issues.jboss.org/browse/ARQ-724 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Build Infrastructure Affects Versions: 1.0.0.CR7 Reporter: Juergen Zimmermann arquillian-parent.pom uses 1.0.0-beta-5. However, the current version is 1.1.0-alpha-2. -- 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

14 years

3
3
0 / 0

[JBoss JIRA] (ARQ-782) Document variable interpolation in arquillian.xml properties

by Dan Allen (JIRA)

Dan Allen created ARQ-782: ----------------------------- Summary: Document variable interpolation in arquillian.xml properties Key: ARQ-782 URL: https://issues.jboss.org/browse/ARQ-782 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Dan Allen I can't find anywhere in the documentation where it explains that interpolation of variables is supported in arquillian.xml properties. This should be added to the reference documentation in the "container configuration" chapter and/or in the getting started guides. -- 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

14 years

3
2
0 / 0

[JBoss JIRA] Created: (ARQ-473) DeployableContainer should not be restricted to only deploy Descriptors or Archives

by Aslak Knutsen (JIRA)

DeployableContainer should not be restricted to only deploy Descriptors or Archives ----------------------------------------------------------------------------------- Key: ARQ-473 URL: https://issues.jboss.org/browse/ARQ-473 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Base Implementation, Deployable Containers SPI Affects Versions: 1.0.0.CR1 Reporter: Aslak Knutsen Fix For: 1.1.0.CR1 To open up for more specialized Containers we should support some type of 'WildCard' Deploy. Possible by having a Annotation driven DeployableContainer, e.g. @Deploy public SomethingExposedInContext(SomeRandomOtherType type) This will let us e.g. deploy Files/ Images etc directly for non Java/EE type Containers. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
1
0 / 0

[JBoss JIRA] (ARQGRA-133) Firing events on inputs does not work on Chrome

by Juraj Huska (JIRA)

Juraj Huska created ARQGRA-133: ---------------------------------- Summary: Firing events on inputs does not work on Chrome Key: ARQGRA-133 URL: https://issues.jboss.org/browse/ARQGRA-133 Project: Arquillian Graphene Issue Type: Bug Components: core Affects Versions: 1.0.0.Final Environment: browser Chrome Reporter: Juraj Huska Assignee: Lukáš Fryč Priority: Critical The following code will not trigger the autocomplete suggestion list on the input, and it should: {code} selenium.type(input, "ska"); guardNoRequest(selenium).fireEvent(input, Event.KEYPRESS); {code} I also tried to use other type methods, other events and also keyPressNative, but unsuccessfully. Note that on Firefox it works just fine. -- 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

14 years

2
5
0 / 0

[JBoss JIRA] (ARQ-834) Executing Android packaged tests in Arquillian

by Karel Piwko (JIRA)

Karel Piwko created ARQ-834: ------------------------------- Summary: Executing Android packaged tests in Arquillian Key: ARQ-834 URL: https://issues.jboss.org/browse/ARQ-834 Project: Arquillian Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Karel Piwko Once the packaging problem is figured out, the next step consists of bringing user a way how to configure what should be tested in Arquillian test. More information about Android is here http://developer.android.com/guide/topics/testing/testing_android.html, focus on "Running Tests" section. Possible proposal {code} @RunWith(Arquillian.class) public class AndroidTest { @Test public void androidActivity(@AndroidActivity HelloAndroid helloAndroid) { mView = (TextView) mActivity.findViewById(com.example.helloandroid.R.id.textview); resourceString = mActivity.getString(com.example.helloandroid.R.string.hello); assertEquals(resourceString,(String)mView.getText()); } } {code} You can obviously inject into fields, make this a class scoped, not method scoped etc. Feel free to experiment and figure out what is the most convenient for users. Also note that your infrastructure should support Robotium in future. -- 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

14 years

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues March 2012