March 2012 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-738) Update integration Jacoco integration to 5.6 level

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-738: --------------------------------- Summary: Update integration Jacoco integration to 5.6 level Key: ARQ-738 URL: https://issues.jboss.org/browse/ARQ-738 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Jacoco Affects Versions: jacoco_1.0.0.Alpha2 Reporter: Aslak Knutsen Fix For: jacoco_1.0.0.next Jacoco API/SPI changed from 5.3 to 5.6. Need to update the Arquillian integration code to reflect the changes -- 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, 11 months

3
9
0 / 0

[JBoss JIRA] Created: (ARQ-141) Add option to export the generated Archive to inspect the final deployment

by Aslak Knutsen (JIRA)

Add option to export the generated Archive to inspect the final deployment -------------------------------------------------------------------------- Key: ARQ-141 URL: https://jira.jboss.org/browse/ARQ-141 Project: Arquillian Issue Type: Task Components: Configuration, Documentation Reporter: Aslak Knutsen It is useful for debugging to have Arquillian export the Archive it is about to deploy, specially in IN_CONTAINER mode. Create a ArchiveExporter EventHandler on class level and make the export folder configurable. If option is not set: don't export -- 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, 11 months

4
10
0 / 0

[JBoss JIRA] Created: (ARQ-350) Map client events 1 to 1 with container events

by Aslak Knutsen (JIRA)

Map client events 1 to 1 with container events ---------------------------------------------- Key: ARQ-350 URL: https://issues.jboss.org/browse/ARQ-350 Project: Arquillian Issue Type: Feature Request Components: Base Implementation, Test Protocol SPIs and Implementation Reporter: Aslak Knutsen We should redo how the test execution lifecycles happen. In the current impl the flow is: Client(BeforSuite, BeforeClass, Before) -> Container(BeforSuite, BeforeClass, Before, Test, After, AfterClass, AfterSuite) -> Client(After, AfterClass, AfterSuite) We should map these 1 to 1 with the incontainer execution and keep the test instance alive between the calls. Client(BeforeClass) -> Container(BeforeClass) Client(Before) -> Container(Before) .. This way the execution is closer to how it normally would be, and extensions can interact with the Container/Environment or Client in the appropriate lifecycles more naturally. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] (ARQ-762) Add JBoss AS 4.2 and 5.1 containers to the test suite

by Bartosz Majsak (JIRA)

Bartosz Majsak created ARQ-762: ---------------------------------- Summary: Add JBoss AS 4.2 and 5.1 containers to the test suite Key: ARQ-762 URL: https://issues.jboss.org/browse/ARQ-762 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha3 Reporter: Bartosz Majsak Assignee: Bartosz Majsak Fix For: persistence_1.0.0.next -- 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, 11 months

1
3
0 / 0

[JBoss JIRA] (ARQ-812) Split DBUnit and Core implemenation

by Bartosz Majsak (JIRA)

Bartosz Majsak created ARQ-812: ---------------------------------- Summary: Split DBUnit and Core implemenation Key: ARQ-812 URL: https://issues.jboss.org/browse/ARQ-812 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha3 Reporter: Bartosz Majsak Assignee: Bartosz Majsak Fix For: persistence_1.0.0.next Introduce SPIs for core functionalities. -- 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, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (ARQ-506) Support more complex property types in container configuration

by Gerhard Poul (JIRA)

Support more complex property types in container configuration -------------------------------------------------------------- Key: ARQ-506 URL: https://issues.jboss.org/browse/ARQ-506 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Configuration Reporter: Gerhard Poul Priority: Optional It might sometimes be helpful to support arbitrary property lists within an arquillian configuration, such as when we want to make it possible to pass properties to the underlying container implementations, but that have no effect on the behavior of the arquillian-container-implementation itself. This is not to replace, but to augment the current configuration capability, such that we can provide something like the following in an arquillian.xml: <container qualifier="someQualifier" default="true"> <configuration> <propertyList name="somePropertyName"> <propertyEntry name="somePropertyEntryName" type="java.lang.String" value="someValue" /> <propertyEntry name="somePropertyEntryName2" type="java.lang.Integer" value="1234" /> ... </propertyList> <property name="someOtherProperty">someValue</property> </configuration> </container> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
4
0 / 0

[JBoss JIRA] (ARQ-835) Enable discarding commits from arquillian after tests are finished

by Jan Papousek (JIRA)

Jan Papousek created ARQ-835: -------------------------------- Summary: Enable discarding commits from arquillian after tests are finished Key: ARQ-835 URL: https://issues.jboss.org/browse/ARQ-835 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: OpenShift Containers Affects Versions: 1.0.0.Beta1 Reporter: Jan Papousek Assignee: Jan Papousek When Arquillian Container OpenShift Express is used very often, it slows down the deployment (the history of GIT repository is larger and larger). There should be possibility to discard commits from arquillian to keep the history of GIT repository clean. -- 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, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (ARQ-567) Supporting Test Suites (@ArquillianSuite)

by Mousavi Jahan Abadi S. M. (JIRA)

Supporting Test Suites (@ArquillianSuite) ----------------------------------------- Key: ARQ-567 URL: https://issues.jboss.org/browse/ARQ-567 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mousavi Jahan Abadi S. M. Currently, it is supported that JUnit test cases being run by Arquillian. This feature request is request for supporting test suites too to be run by Arquillian too. Idea is like: @RunWith(ArquillianSuite.class) @Suite.SuiteClasses( { TestCase1.class, TestCase2.class, .... } ) public class AllTests{ @Deployment public static JavaArchive createTestArchive(){ return ShrinkWrap.create(JavaArchive.class,"test.jar"); } } The advantages of above approach for users of Arquillian framework are: - Test cases don't needed to be modified to have: "@RunWith(Arquillian.class)" annotation. In other words, test cases will be pure JUnit code, and no Arquillian code (results in less coding for end users). - It is not necessary to include the static "@Deployment" methods in all test cases any more, and only Test Suite need to define the archieving/deployment related setting/definitions. The advantage of above approach for framework itself is: - From performance point-of-view, it becomes possible for Arquillian to deploy all test cases in the Test Suite into J2EE container in one action (one deploy/undeploy for one test suite, instead of mulitple deploy/undeploy for each test case). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

5
5
0 / 0

[JBoss JIRA] Created: (ARQ-271) TestEnricher should be called in @BeforeClass as well

by Thomas Diesler (JIRA)

TestEnricher should be called in @BeforeClass as well ----------------------------------------------------- Key: ARQ-271 URL: https://jira.jboss.org/browse/ARQ-271 Project: Arquillian Issue Type: Feature Request Reporter: Thomas Diesler The TestEnricher API could be extended such that static fields can be initialized. @Inject public static BundleContext context; @BeforeClass public static void beforeClass() { System.out.println("BeforeClass: " + context); } There would be two calls to TestEnricher. #1 After test class load, but before a call to @BeforeClass. #2 After instantiation of the test class, but before a call to @Before (#2 is the current behaviour) -- 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, 11 months

4
10
0 / 0

[JBoss JIRA] (ARQ-772) Introduce column filtering for data set matching

by Bartosz Majsak (JIRA)

Bartosz Majsak created ARQ-772: ---------------------------------- Summary: Introduce column filtering for data set matching Key: ARQ-772 URL: https://issues.jboss.org/browse/ARQ-772 Project: Arquillian Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha3 Reporter: Bartosz Majsak Assignee: Bartosz Majsak Fix For: persistence_1.0.0.next Strict mode is not always suitable, especially when using large data sets exported from the database for matching. Therefore there should be a mechanism (preferably annotation based) to define columns to filter. -- 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, 11 months

2
7
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues March 2012