April 2011 - arquillian-issues - Jboss List Archives

[JBoss JIRA] Created: (ARQ-287) Add support for filtering tests based on required execution environment

by Dan Allen (JIRA)

Add support for filtering tests based on required execution environment ----------------------------------------------------------------------- Key: ARQ-287 URL: https://jira.jboss.org/browse/ARQ-287 Project: Arquillian Issue Type: Feature Request Components: Configuration Affects Versions: 1.0.0.Alpha4 Reporter: Dan Allen Assignee: Dan Allen Fix For: 1.0.0.Beta1 Allow the developer to declaratively specify the execution environment required for a given test to function. Then, Arquillian should filter out tests that require an execution environment that the target container doesn't provide. (In other words, only execute a test case if the target container provides the execution environment the test requires). To support this feature, we need to introduce the concept of an execution environment definition into the API and a mechanism for indicating which containers provide a given execution environment. The developer experience will be something like: @RunWith(Arquillian.class) @RequiresJavaEE6 public class MyTestCase { ... } or @RunWith(Arquillian.class) @RequiresEnvironment(JavaEE6Container.class) public class MyTestCase { ... } Formal proposals and prototypes will be submitted as branches in github. -- 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

13 years

2
11
0 / 0

[JBoss JIRA] Created: (ARQ-277) Use consistent naming, in consistent use of Executor vs Executer

by Aslak Knutsen (JIRA)

Use consistent naming, in consistent use of Executor vs Executer ---------------------------------------------------------------- Key: ARQ-277 URL: https://jira.jboss.org/browse/ARQ-277 Project: Arquillian Issue Type: Feature Request Components: Test Protocol SPIs and Implementation Reporter: Aslak Knutsen Fix For: 1.0.0.Beta1 -- 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

13 years

1
2
0 / 0

[JBoss JIRA] Created: (ARQ-425) config parser code not in sync with schema

by Thomas Diesler (JIRA)

config parser code not in sync with schema ------------------------------------------ Key: ARQ-425 URL: https://issues.jboss.org/browse/ARQ-425 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.0.Alpha5 Reporter: Thomas Diesler The schema suggest <container qualifier="osgi" default="true"> <protocol type="jmx-osgi"> <property name="host">localhost</property> <property name="port">1090</property> <property name="urlPath">jmxrmi</property> </protocol> </container> the parser however wants <container qualifier="osgi" default="true"> <protocol type="jmx-osgi"> <configuration> <property name="host">localhost</property> <property name="port">1090</property> <property name="urlPath">jmxrmi</property> </configuration> </protocol> </container> Note, the extra configuration element. Please add a test that validates various config files against the schema and parsed values -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
3
0 / 0

[JBoss JIRA] Created: (ARQ-411) Doc: XSD at wrong URL:

by Ondrej Zizka (JIRA)

Doc: XSD at wrong URL: ----------------------- Key: ARQ-411 URL: https://issues.jboss.org/browse/ARQ-411 Project: Arquillian Issue Type: Quality Risk Security Level: Public (Everyone can see) Reporter: Ondrej Zizka This doc's example http://docs.jboss.org/arquillian/reference/latest/en-US/html_single/#cont... refers to http://jboss.org/schema/arquillian/arquillian_1_0.xsd However there's only http://jboss.org/schema/arquillian/arquillian_1.0.xsd I suggest to rename to http://jboss.org/schema/arquillian/arquillian_1_0.xsd since it's the usual form, see e.g. http://www.jboss.org/schema/jbossas/ (20:01:57) OndejZizka: Usual is _ (20:01:59) OndejZizka: http://www.jboss.org/schema/jbossas/ (20:02:26) aslak: yea, _ is used in spec xsds as well (20:02:37) aslak: need a new namespace as well -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
4
0 / 0

[JBoss JIRA] Created: (ARQ-314) CDIInjectionEnricher does not release the creationalContext

by Pete Muir (JIRA)

CDIInjectionEnricher does not release the creationalContext ----------------------------------------------------------- Key: ARQ-314 URL: https://jira.jboss.org/browse/ARQ-314 Project: Arquillian Issue Type: Bug Components: Weld Containers Affects Versions: 1.0.0.Alpha4 Reporter: Pete Muir In order for Weld to properly clean up injected dependent objects (such as calling the @PreDestroy or @Disposes method), it is important that creationalContext.release() is called when the scope of the test ends. -- 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

13 years

2
4
0 / 0

[JBoss JIRA] Created: (ARQ-123) Create a Arquillian Gradle example

by Aslak Knutsen (JIRA)

Create a Arquillian Gradle example ---------------------------------- Key: ARQ-123 URL: https://jira.jboss.org/jira/browse/ARQ-123 Project: Arquillian Issue Type: Task Components: Documentation Reporter: Aslak Knutsen Supply a example of how to run Arquillian using Gradle -- 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

13 years

3
10
0 / 0

[JBoss JIRA] Created: (ARQ-404) Better reporting when Arquillian fails to initialise

by Stuart Douglas (JIRA)

Better reporting when Arquillian fails to initialise ----------------------------------------------------- Key: ARQ-404 URL: https://issues.jboss.org/browse/ARQ-404 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Stuart Douglas At the moment when Arquillian fails to startup you get the following message: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See previous exceptions for cause. It would be good if this could also tell you the test that it failed on, so you know where to look for the exception. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
6
0 / 0

[JBoss JIRA] Created: (ARQ-422) Rename static field Arquillian.caughtTestException so it doesn't show in auto-complete

by Dan Allen (JIRA)

Rename static field Arquillian.caughtTestException so it doesn't show in auto-complete -------------------------------------------------------------------------------------- Key: ARQ-422 URL: https://issues.jboss.org/browse/ARQ-422 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.0.0.Alpha5 Reporter: Dan Allen Priority: Minor When adding Arquillian support to a test class, the caughtTestException gets in the way of auto-complete. For instance, when you type: @RunWith(Arquillian.c Then press <Ctrl>+Space you get .caughtTestException .class On more than one occasion, I've accidentally selected .caughtTestException. This field should either be renamed to CAUGHT_TEST_EXCEPTION, queuedTestException or moved to another class (the best solution). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
3
0 / 0

[JBoss JIRA] Created: (ARQ-57) JBossAS Remote Containers Depend upon Sun JDK

by Andrew Lee Rubinger (JIRA)

JBossAS Remote Containers Depend upon Sun JDK --------------------------------------------- Key: ARQ-57 URL: https://jira.jboss.org/jira/browse/ARQ-57 Project: Arquillian Issue Type: Bug Components: Jboss Containers Reporter: Andrew Lee Rubinger Assignee: Pete Muir Both the AS 5.1 and 6.0 implementations of JbossRemoteContainer have: import com.sun.net.httpserver.HttpExchange; import com.sun.net.httpserver.HttpHandler; import com.sun.net.httpserver.HttpServer Recommend an external dependency on a safe alternative like apache-httpcomponent's HttpClient or Jetty, ie: http://anonsvn.jboss.org/repos/jbossas/projects/ejb-book/trunk/ch07-rssca... -- 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

13 years, 1 month

3
8
0 / 0

[JBoss JIRA] Created: (ARQ-407) Documentation error? Should arquillian-glassfish-embedded-3 be arquillian-glassfish-embedded-3.1 Alpha 5 ?

by Steven Boscarine (JIRA)

Documentation error? Should arquillian-glassfish-embedded-3 be arquillian-glassfish-embedded-3.1 Alpha 5 ? ----------------------------------------------------------------------------------------------------------- Key: ARQ-407 URL: https://issues.jboss.org/browse/ARQ-407 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Steven Boscarine http://community.jboss.org/message/596806#596806 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues April 2011