[JBoss JIRA] (ARQ-747) Arquillian Extension Persistence - DB cleanup does not work with Maven Archetype
11:35 p.m.
david meier created ARQ-747:
-------------------------------
Summary: Arquillian Extension Persistence - DB cleanup does not work with
Maven Archetype
Key: ARQ-747
URL: https://issues.jboss.org/browse/ARQ-747
Project: Arquillian
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Integration Test Suite
Affects Versions: persistence_1.0.0.Alpha3
Environment: Eclipse JavaEE IDE for Web Developers, Indigo SR1
Win7 x64
Java 1.7.0-b147
jboss-as-web-7.0.2.Final
Reporter: david meier
You can easily reproduce it yourself, based on maven archetypes.
After executing steps to reproduce:
Actual result:
if method testRegister() is executed before testProducer(), then the latter fails. Because
getMembers() does return a list of size == 1.
Expected result:
as the DB is to be cleaned after each test, the getMembers() method should be empty and
both tests should verify.
--
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
11:37 p.m.
[
https://issues.jboss.org/browse/ARQ-747?page=com.atlassian.jira.plugin.sy...
]
david meier updated ARQ-747:
----------------------------
Attachment: arquillian_cleanup_fails.zip
Arquillian Extension Persistence - DB cleanup does not work with
Maven Archetype
--------------------------------------------------------------------------------
Key: ARQ-747
URL: https://issues.jboss.org/browse/ARQ-747
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Integration Test Suite
Affects Versions: persistence_1.0.0.Alpha3
Environment: Eclipse JavaEE IDE for Web Developers, Indigo SR1
Win7 x64
Java 1.7.0-b147
jboss-as-web-7.0.2.Final
Reporter: david meier
Attachments: arquillian_cleanup_fails.zip
You can easily reproduce it yourself, based on maven archetypes.
After executing steps to reproduce:
Actual result:
if method testRegister() is executed before testProducer(), then the latter fails.
Because getMembers() does return a list of size == 1.
Expected result:
as the DB is to be cleaned after each test, the getMembers() method should be empty and
both tests should verify.
--
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
11:39 p.m.
[
https://issues.jboss.org/browse/ARQ-747?page=com.atlassian.jira.plugin.sy...
]
david meier updated ARQ-747:
----------------------------
Description:
Problem: based on discussion in the forums, the DB should be cleaned up after each @Test
execution. This was not the case for a very simple project, and can be easily reproduced
based on maven archetypes.
After executing steps to reproduce:
Actual result:
if method testRegister() is executed before testProducer(), then the latter fails. Because
getMembers() does return a list of size == 1.
Expected result:
as the DB is to be cleaned after each test, the getMembers() method should be empty and
both tests should verify.
was:
You can easily reproduce it yourself, based on maven archetypes.
After executing steps to reproduce:
Actual result:
if method testRegister() is executed before testProducer(), then the latter fails. Because
getMembers() does return a list of size == 1.
Expected result:
as the DB is to be cleaned after each test, the getMembers() method should be empty and
both tests should verify.
Forum Reference: https://community.jboss.org/message/716346#716346 (was:
https://community.jboss.org/message/716346#716346)
Arquillian Extension Persistence - DB cleanup does not work with
Maven Archetype
--------------------------------------------------------------------------------
Key: ARQ-747
URL: https://issues.jboss.org/browse/ARQ-747
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Integration Test Suite
Affects Versions: persistence_1.0.0.Alpha3
Environment: Eclipse JavaEE IDE for Web Developers, Indigo SR1
Win7 x64
Java 1.7.0-b147
jboss-as-web-7.0.2.Final
Reporter: david meier
Attachments: arquillian_cleanup_fails.zip
Problem: based on discussion in the forums, the DB should be cleaned up after each @Test
execution. This was not the case for a very simple project, and can be easily reproduced
based on maven archetypes.
After executing steps to reproduce:
Actual result:
if method testRegister() is executed before testProducer(), then the latter fails.
Because getMembers() does return a list of size == 1.
Expected result:
as the DB is to be cleaned after each test, the getMembers() method should be empty and
both tests should verify.
--
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
6:57 a.m.
[
https://issues.jboss.org/browse/ARQ-747?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen updated ARQ-747:
------------------------------
Component/s: Extension - Persistence
(was: Integration Test Suite)
Forum Reference: https://community.jboss.org/message/716346#716346 (was:
https://community.jboss.org/message/716346#716346)
Arquillian Extension Persistence - DB cleanup does not work with
Maven Archetype
--------------------------------------------------------------------------------
Key: ARQ-747
URL: https://issues.jboss.org/browse/ARQ-747
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Extension - Persistence
Affects Versions: persistence_1.0.0.Alpha3
Environment: Eclipse JavaEE IDE for Web Developers, Indigo SR1
Win7 x64
Java 1.7.0-b147
jboss-as-web-7.0.2.Final
Reporter: david meier
Attachments: arquillian_cleanup_fails.zip
Problem: based on discussion in the forums, the DB should be cleaned up after each @Test
execution. This was not the case for a very simple project, and can be easily reproduced
based on maven archetypes.
After executing steps to reproduce:
Actual result:
if method testRegister() is executed before testProducer(), then the latter fails.
Because getMembers() does return a list of size == 1.
Expected result:
as the DB is to be cleaned after each test, the getMembers() method should be empty and
both tests should verify.
--
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
9:37 a.m.
[
https://issues.jboss.org/browse/ARQ-747?page=com.atlassian.jira.plugin.sy...
]
Bartosz Majsak updated ARQ-747:
-------------------------------
Assignee: Bartosz Majsak
Forum Reference: https://community.jboss.org/message/716346#716346 (was:
https://community.jboss.org/message/716346#716346)
Arquillian Extension Persistence - DB cleanup does not work with
Maven Archetype
--------------------------------------------------------------------------------
Key: ARQ-747
URL: https://issues.jboss.org/browse/ARQ-747
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Extension - Persistence
Affects Versions: persistence_1.0.0.Alpha3
Environment: Eclipse JavaEE IDE for Web Developers, Indigo SR1
Win7 x64
Java 1.7.0-b147
jboss-as-web-7.0.2.Final
Reporter: david meier
Assignee: Bartosz Majsak
Attachments: arquillian_cleanup_fails.zip
Problem: based on discussion in the forums, the DB should be cleaned up after each @Test
execution. This was not the case for a very simple project, and can be easily reproduced
based on maven archetypes.
After executing steps to reproduce:
Actual result:
if method testRegister() is executed before testProducer(), then the latter fails.
Because getMembers() does return a list of size == 1.
Expected result:
as the DB is to be cleaned after each test, the getMembers() method should be empty and
both tests should verify.
--
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
7:58 p.m.
[
https://issues.jboss.org/browse/ARQ-747?page=com.atlassian.jira.plugin.sy...
]
Bartosz Majsak closed ARQ-747.
------------------------------
Resolution: Rejected
As described in the [realated forum
thread|https://community.jboss.org/message/716614#716614] it was not an issue with
cleaning database, but missing artifact. Due to lack of "implementation"
Arquillian Persistence Extension wasn't enabled and hence reported symptoms occured.
Arquillian Extension Persistence - DB cleanup does not work with
Maven Archetype
--------------------------------------------------------------------------------
Key: ARQ-747
URL: https://issues.jboss.org/browse/ARQ-747
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Extension - Persistence
Affects Versions: persistence_1.0.0.Alpha3
Environment: Eclipse JavaEE IDE for Web Developers, Indigo SR1
Win7 x64
Java 1.7.0-b147
jboss-as-web-7.0.2.Final
Reporter: david meier
Assignee: Bartosz Majsak
Attachments: arquillian_cleanup_fails.zip
Problem: based on discussion in the forums, the DB should be cleaned up after each @Test
execution. This was not the case for a very simple project, and can be easily reproduced
based on maven archetypes.
After executing steps to reproduce:
Actual result:
if method testRegister() is executed before testProducer(), then the latter fails.
Because getMembers() does return a list of size == 1.
Expected result:
as the DB is to be cleaned after each test, the getMembers() method should be empty and
both tests should verify.
--
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
4505
days inactive
4506
days old
arquillian-issues@lists.jboss.org
5 comments
3 participants
participants (3)
-
Aslak Knutsen (JIRA) -
Bartosz Majsak (JIRA)
-
david meier (JIRA)