[
https://issues.jboss.org/browse/ARQ-1131?page=com.atlassian.jira.plugin.s...
]
Bartosz Majsak edited comment on ARQ-1131 at 3/6/13 11:40 AM:
--------------------------------------------------------------
It turned out that this approach [is not recommended by DBUnit
guys|http://www.dbunit.org/faq.html#performance] as it can have performance penalty.
Ideally the connection should span the whole test class lifecycle, but this won't be
possible until we have [
ARQ-350|https://issues.jboss.org/browse/ARQ-350] in place.
Therefore current approach, where we open connection before and after test is not any
different than the original one implemented in APE. Leaving it like this for the moment.
was (Author: bmajsak):
It turned out that this approach is not recommended by DBUnit guys as it can have
performance penalty. Ideally the connection should span the whole test class, but this
won't be possible until we have
https://issues.jboss.org/browse/ARQ-350 in place.
Improve DBUnit database connection handling
-------------------------------------------
Key: ARQ-1131
URL:
https://issues.jboss.org/browse/ARQ-1131
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Extension - Persistence
Reporter: Bartosz Majsak
Assignee: Bartosz Majsak
Fix For: persistence_1.0.0.next
-As Vineet Reynolds pointed out, current implementation initializes the connection and
holds on to it, until the verification is performed. It would be better to relinquish the
connection after the seeding phase (so utilize it only around "before persistence
test" event), and obtain another connection for the dataset verification phase
(around "after persistence test" event).-
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira