June 2011 - arquillian-issues - Jboss List Archives

[JBoss JIRA] Created: (ARQ-466) Add support for injected PackageAdmin

by Thomas Diesler (JIRA)

Add support for injected PackageAdmin ------------------------------------- Key: ARQ-466 URL: https://issues.jboss.org/browse/ARQ-466 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: OSGi Containers Reporter: Thomas Diesler Assignee: Thomas Diesler -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
1
0 / 0

[JBoss JIRA] Created: (ARQ-288) Document how to integration Arquillian into non-Maven builds (build integration chapter)

by Dan Allen (JIRA)

Document how to integration Arquillian into non-Maven builds (build integration chapter) ---------------------------------------------------------------------------------------- Key: ARQ-288 URL: https://jira.jboss.org/browse/ARQ-288 Project: Arquillian Issue Type: Task Components: Documentation Affects Versions: 1.0.0.Alpha4 Reporter: Dan Allen Fix For: 1.0.0.Beta1 There is a misconception spreading that Arquillian can only be used from a Maven. We need a build integration chapter to clarify the message that Arquillian is build-independent. The chapter should describe in general how Arquillian is hooked into a build system, then provide tutorials for Ant and Gradle. -- 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
9
0 / 0

[JBoss JIRA] Created: (ARQ-463) Document jars needed between 'test-framework-bom' and 'container-profile-bom' for build system with no DependencyManagement

by Aslak Knutsen (JIRA)

Document jars needed between 'test-framework-bom' and 'container-profile-bom' for build system with no DependencyManagement --------------------------------------------------------------------------------------------------------------------------- Key: ARQ-463 URL: https://issues.jboss.org/browse/ARQ-463 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 1.0.0.CR1 Reporter: Aslak Knutsen The only thing missing is that we still don't have a well-documented way of listing which dependencies are required if you didn't want to use a dependency management system. My vision for this is a script which will pull down the dependencies you need for a given container and stick them in a folder somewhere. Obviously, you limit your ability to use different containers, which I don't think needs to be our concern. In fact, the best way to resolve it is to simply be able to produce a report of which JARs are used, with links to download them. Combine the 'container-profile-bom' with the 'test-framework-bom' and grind it through some dep resolver ('dependency:tree') and we should have a somewhat report of what is needed. http://www.jboss.org/tattletale ? >From that we need some manual evaluation of things like: * You probably don't want to add those 250 container libs, but rather depend on jboss-client.jar found in $JBOSS_HOME/client -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[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-50) research an alternative approach to inheriting from Arquillian base class in TestNG

by Dan Allen (JIRA)

research an alternative approach to inheriting from Arquillian base class in TestNG ----------------------------------------------------------------------------------- Key: ARQ-50 URL: https://jira.jboss.org/jira/browse/ARQ-50 Project: Arquillian Issue Type: Feature Request Affects Versions: 1.0.0-alpha-1 Reporter: Dan Allen Priority: Minor This issue is a research and development task to determine if there is an alternative approach that can be used, rather than inheriting from the Arquillian base class, to hook a TestNG test into the Arquillian functionality. JUnit offers a @RunWith annotation which is what the JUnit module uses. The closest hook TestNG seems to offer is the ITestListener interface. However, the question becomes, how does that map to the requirements: @BeforeSuite -> start container (~ ITestListener.onStart) @BeforeClass -> deploy (??) TestMethod/IHookable -> remote call (??) @AfterClass -> undeploy -> (??) @AfterSuite -> stop container -> (~ ITestListener.onFinish) There was discussion on this thread about supporting @RunWith in TestNG: http://markmail.org/message/fxm6bddk6wzqa4yp -- 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

4
14
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] Updated: (ARQ-13) Provide an example that shows Arquillian being used with Ant

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-13?page=com.atlassian.jira.plugin.sys... ] Aslak Knutsen updated ARQ-13: ----------------------------- Fix Version/s: 1.0.0.Final (was: 1.0.0.CR1) > Provide an example that shows Arquillian being used with Ant > ------------------------------------------------------------ > > Key: ARQ-13 > URL: https://issues.jboss.org/browse/ARQ-13 > Project: Arquillian > Issue Type: Feature Request > Components: Examples/Showcase > Reporter: Pete Muir > Assignee: Jason Porter > Fix For: 1.0.0.Final > > > This example needs to use vanilla Ant. > A second example could show the use of Ant + Maven Ant Tasks or Ivy. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
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-456) Client side SPIs are found InContainer when running Embedded

by Aslak Knutsen (JIRA)

Client side SPIs are found InContainer when running Embedded ------------------------------------------------------------ Key: ARQ-456 URL: https://issues.jboss.org/browse/ARQ-456 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.0.0.Beta1 Reporter: Aslak Knutsen Embedded containers which share AppCl has the same issue, they leak the AppCL SPIs into the InContainer. When Arquillian reexecutes InContainer all the Client configuration is found and Core is missconfigured.. Two possible options, ClassLoader isolation between Arq-Core and the Container, or Switching to Local when embedded. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues June 2011