February 2012 - arquillian-issues

[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

12 years, 2 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

12 years, 2 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

12 years, 2 months

2
7
0 / 0

[JBoss JIRA] (ARQ-751) Empty YML file is causing error whereas it should be simply skipped

by Bartosz Majsak (JIRA)

Bartosz Majsak created ARQ-751: ---------------------------------- Summary: Empty YML file is causing error whereas it should be simply skipped Key: ARQ-751 URL: https://issues.jboss.org/browse/ARQ-751 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha3 Reporter: Bartosz Majsak Assignee: Bartosz Majsak Priority: Minor 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

12 years, 2 months

2
5
0 / 0

[JBoss JIRA] (ARQ-718) Customization for DBUnit

by Bartosz Majsak (Created) (JIRA)

Customization for DBUnit ------------------------ Key: ARQ-718 URL: https://issues.jboss.org/browse/ARQ-718 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Persistence Reporter: Bartosz Majsak Assignee: Bartosz Majsak There is a need for exposing customization features of DBUnit used for seeding underlying database (such as those available in org.dbunit.database.DatabaseConfig). -- 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

12 years, 2 months

5
12
0 / 0

[JBoss JIRA] (ARQ-764) Using DBUnit with IDENTITY or auto-increment columns

by Bartosz Majsak (JIRA)

Bartosz Majsak created ARQ-764: ---------------------------------- Summary: Using DBUnit with IDENTITY or auto-increment columns Key: ARQ-764 URL: https://issues.jboss.org/browse/ARQ-764 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha3 Environment: MS SQL Reporter: Bartosz Majsak Assignee: Bartosz Majsak Fix For: persistence_1.0.0.next MSSQL doesn't allow INSERTs with values specified for autoincrement columns. Provide a way to set the DatabaseOperation to one of the InsertIdentityOperation choices. -- 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

12 years, 2 months

2
4
0 / 0

[JBoss JIRA] (ARQ-752) Persistence extension is failing to enrich archive when there is no dataset defined

by Bartosz Majsak (JIRA)

Bartosz Majsak created ARQ-752: ---------------------------------- Summary: Persistence extension is failing to enrich archive when there is no dataset defined Key: ARQ-752 URL: https://issues.jboss.org/browse/ARQ-752 Project: Arquillian Issue Type: Bug 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

12 years, 2 months

2
8
0 / 0

[JBoss JIRA] (ARQ-771) Global DBUnit configuration should be exposed in arquillian.xml

by Bartosz Majsak (JIRA)

Bartosz Majsak created ARQ-771: ---------------------------------- Summary: Global DBUnit configuration should be exposed in arquillian.xml Key: ARQ-771 URL: https://issues.jboss.org/browse/ARQ-771 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 Use arquillian.xml with dedicated qualifier such as "persistence-dbunit" and handle it in the same fashion as currently available properties for the extension (preferably in dbunit package): * Create configuration class similar to [PersistenceConfiguration|https://github.com/arquillian/arquillian-extensi...] * Make [ConfigurationImporter|https://github.com/arquillian/arquillian-extension-...] and [ConfigurationExporter|https://github.com/arquillian/arquillian-extension-...] generic to work for currently existing configuration and newly created DBUnit specific. * Introduce DBUnitConfiguration producer similar to [PersistenceConfigurationProducer|https://github.com/arquillian/arquillian...]. * Serialize new properties in [PersistenceExtensionArchiveAppender|https://github.com/arquillian/arquill...] (same as for general properties) * Introduce remote producer (which deserialize deployed property file and make it available on the server side) similar to [RemotePersistenceConfigurationProducer|https://github.com/arquillian/arqu...] * Configuration object then might be injected and used for customizing DBUnit connection in [DBUnitPersistenceTestLifecycleHandler|https://github.com/arquillian/arqui...] -- 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

12 years, 2 months

2
5
0 / 0

[JBoss JIRA] (ARQ-755) Introduce annotation based db cleanup configuration

by Bartosz Majsak (JIRA)

Bartosz Majsak created ARQ-755: ---------------------------------- Summary: Introduce annotation based db cleanup configuration Key: ARQ-755 URL: https://issues.jboss.org/browse/ARQ-755 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 User should have control on data cleanup event. Currently it's always executed after the test. Provide @Cleanup annotation with following options: - DISABLED - BEFORE (default) - AFTER This annotation can be placed on class level - defining the default behaviour for all test cases, but when define on method level it will override global settings. -- 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

12 years, 2 months

2
6
0 / 0

[JBoss JIRA] (ARQ-723) TransactionalWrapper.afterTest() ignores SessionContext.setRollbackOnly()

by Juergen Zimmermann (Created) (JIRA)

TransactionalWrapper.afterTest() ignores SessionContext.setRollbackOnly() ------------------------------------------------------------------------- Key: ARQ-723 URL: https://issues.jboss.org/browse/ARQ-723 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha3 Reporter: Juergen Zimmermann Assignee: Bartosz Majsak If a method is being tested that invokes SessionContext.setRollbackOnly(), then the commit mode doesn't work correctly, because doing a commit() after setRollbackOnly() will fail. Therefore, the method TransactionalWrapper.afterTest() should be implemented as follows: final TransactionMode mode = metadataProvider.get().getTransactionalMode(); final UserTransaction trans; if (TransactionMode.COMMIT.equals(mode)) { if (Status.STATUS_MARKED_ROLLBACK.equals(trans.getStatus())) { trans.rollback(); } else { trans.commit(); } } else { trans.rollback(); } -- 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

12 years, 2 months

7
13
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues February 2012