[JBoss JIRA] Created: (JBPM-2047) PersistenceDbServiceTest and PersistenceServiceDbTest are dependent
12:48 a.m.
PersistenceDbServiceTest and PersistenceServiceDbTest are dependent
-------------------------------------------------------------------
Key: JBPM-2047
URL: https://jira.jboss.org/jira/browse/JBPM-2047
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Core Engine
Affects Versions: jBPM-3.2.5.SP1
Reporter: Jiri Pechanec
Assignee: Thomas Diesler
The tests can fail based on the execution order of these tests.
If PersistenceDbServiceTest is executed first then it sets session factory to
MockSessionFactory.
Unfortunately it seems that the setting is SAME for ALL future newly created
JbpmContexts.
PersistenceServiceDbTest then tests that the factory is null but it is not
assertNull(persistenceServiceFactory.sessionFactory). The same test also tests few more
features that ends in calls of unsupported operations on the MockSessionFactory.
I am not sure if this is a problem of test - then the sessionFactory should be cleard
after test or if it is wrong that the setting is shared for all JBpmContexts.
--
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
6 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-2047) PersistenceDbServiceTest and PersistenceServiceDbTest are dependent
[
https://jira.jboss.org/jira/browse/JBPM-2047?page=com.atlassian.jira.plug...
]
Thomas Diesler updated JBPM-2047:
---------------------------------
Fix Version/s: jBPM 3.2.7 GA
PersistenceDbServiceTest and PersistenceServiceDbTest are dependent
-------------------------------------------------------------------
Key: JBPM-2047
URL: https://jira.jboss.org/jira/browse/JBPM-2047
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Engine
Affects Versions: jBPM-3.2.5.SP1
Reporter: Jiri Pechanec
Assignee: Thomas Diesler
Fix For: jBPM 3.2.7 GA
The tests can fail based on the execution order of these tests.
If PersistenceDbServiceTest is executed first then it sets session factory to
MockSessionFactory.
Unfortunately it seems that the setting is SAME for ALL future newly created
JbpmContexts.
PersistenceServiceDbTest then tests that the factory is null but it is not
assertNull(persistenceServiceFactory.sessionFactory). The same test also tests few more
features that ends in calls of unsupported operations on the MockSessionFactory.
I am not sure if this is a problem of test - then the sessionFactory should be cleard
after test or if it is wrong that the setting is shared for all JBpmContexts.
--
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
10:23 a.m.
New subject: [JBoss JIRA] Assigned: (JBPM-2047) PersistenceDbServiceTest and PersistenceServiceDbTest are dependent
[
https://jira.jboss.org/jira/browse/JBPM-2047?page=com.atlassian.jira.plug...
]
Tom Baeyens reassigned JBPM-2047:
---------------------------------
Assignee: Alejandro Guizar (was: Tom Baeyens)
assigning to Alejandro
PersistenceDbServiceTest and PersistenceServiceDbTest are dependent
-------------------------------------------------------------------
Key: JBPM-2047
URL: https://jira.jboss.org/jira/browse/JBPM-2047
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Engine
Affects Versions: jBPM-3.2.5.SP1
Reporter: Jiri Pechanec
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.7 GA
The tests can fail based on the execution order of these tests.
If PersistenceDbServiceTest is executed first then it sets session factory to
MockSessionFactory.
Unfortunately it seems that the setting is SAME for ALL future newly created
JbpmContexts.
PersistenceServiceDbTest then tests that the factory is null but it is not
assertNull(persistenceServiceFactory.sessionFactory). The same test also tests few more
features that ends in calls of unsupported operations on the MockSessionFactory.
I am not sure if this is a problem of test - then the sessionFactory should be cleard
after test or if it is wrong that the setting is shared for all JBpmContexts.
--
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
4:41 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-2047) PersistenceDbServiceTest and PersistenceServiceDbTest are dependent
[
https://jira.jboss.org/jira/browse/JBPM-2047?page=com.atlassian.jira.plug...
]
Alejandro Guizar updated JBPM-2047:
-----------------------------------
Fix Version/s: jBPM 3.2.5 SP6
PersistenceDbServiceTest and PersistenceServiceDbTest are dependent
-------------------------------------------------------------------
Key: JBPM-2047
URL: https://jira.jboss.org/jira/browse/JBPM-2047
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM-3.2.5.SP1
Reporter: Jiri Pechanec
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.7, jBPM 3.2.5 SP6
The tests can fail based on the execution order of these tests.
If PersistenceDbServiceTest is executed first then it sets session factory to
MockSessionFactory.
Unfortunately it seems that the setting is SAME for ALL future newly created
JbpmContexts.
PersistenceServiceDbTest then tests that the factory is null but it is not
assertNull(persistenceServiceFactory.sessionFactory). The same test also tests few more
features that ends in calls of unsupported operations on the MockSessionFactory.
I am not sure if this is a problem of test - then the sessionFactory should be cleard
after test or if it is wrong that the setting is shared for all JBpmContexts.
--
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
9:11 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-2047) PersistenceDbServiceTest and PersistenceServiceDbTest are dependent
[
https://jira.jboss.org/jira/browse/JBPM-2047?page=com.atlassian.jira.plug...
]
Alejandro Guizar updated JBPM-2047:
-----------------------------------
Fix Version/s: jBPM 3.2.9
(was: jBPM 3.3.2)
PersistenceDbServiceTest and PersistenceServiceDbTest are dependent
-------------------------------------------------------------------
Key: JBPM-2047
URL: https://jira.jboss.org/jira/browse/JBPM-2047
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM-3.2.5.SP1
Reporter: Jiri Pechanec
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.9
The tests can fail based on the execution order of these tests.
If PersistenceDbServiceTest is executed first then it sets session factory to
MockSessionFactory.
Unfortunately it seems that the setting is SAME for ALL future newly created
JbpmContexts.
PersistenceServiceDbTest then tests that the factory is null but it is not
assertNull(persistenceServiceFactory.sessionFactory). The same test also tests few more
features that ends in calls of unsupported operations on the MockSessionFactory.
I am not sure if this is a problem of test - then the sessionFactory should be cleard
after test or if it is wrong that the setting is shared for all JBpmContexts.
--
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
3:10 a.m.
New subject: [JBoss JIRA] Resolved: (JBPM-2047) PersistenceDbServiceTest and PersistenceServiceDbTest are dependent
[
https://jira.jboss.org/jira/browse/JBPM-2047?page=com.atlassian.jira.plug...
]
Alejandro Guizar resolved JBPM-2047.
------------------------------------
Resolution: Done
The problem no longer occurs as shown in the following maven build. In
PersistenceDbServiceTest and all other test cases that use a custom configuration, the
JbpmConfiguration instance is explicitly closed on tearDown to avoid affecting other
tests.
[aguizar@siankaan core]$ mvn -Dtest=PersistenceDbServiceTest,PersistenceServiceDbTest
test
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.jbpm.persistence.db.PersistenceDbServiceTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.758 sec
Running org.jbpm.persistence.db.PersistenceServiceDbTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.262 sec
Results :
Tests run: 16, Failures: 0, Errors: 0, Skipped: 0
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
PersistenceDbServiceTest and PersistenceServiceDbTest are dependent
-------------------------------------------------------------------
Key: JBPM-2047
URL: https://jira.jboss.org/jira/browse/JBPM-2047
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM-3.2.5.SP1
Reporter: Jiri Pechanec
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.9
The tests can fail based on the execution order of these tests.
If PersistenceDbServiceTest is executed first then it sets session factory to
MockSessionFactory.
Unfortunately it seems that the setting is SAME for ALL future newly created
JbpmContexts.
PersistenceServiceDbTest then tests that the factory is null but it is not
assertNull(persistenceServiceFactory.sessionFactory). The same test also tests few more
features that ends in calls of unsupported operations on the MockSessionFactory.
I am not sure if this is a problem of test - then the sessionFactory should be cleard
after test or if it is wrong that the setting is shared for all JBpmContexts.
--
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
1:20 a.m.
New subject: [JBoss JIRA] Reopened: (JBPM-2047) PersistenceDbServiceTest and PersistenceServiceDbTest are dependent
[
https://jira.jboss.org/jira/browse/JBPM-2047?page=com.atlassian.jira.plug...
]
Alejandro Guizar reopened JBPM-2047:
------------------------------------
Even though PersistenceDbServiceTest cleans up after itself, SOA-1863 provided further
evidence that PersistenceServiceDbTest is affected by the order of execution.
PersistenceDbServiceTest and PersistenceServiceDbTest are dependent
-------------------------------------------------------------------
Key: JBPM-2047
URL: https://jira.jboss.org/jira/browse/JBPM-2047
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM-3.2.5.SP1
Reporter: Jiri Pechanec
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.9
The tests can fail based on the execution order of these tests.
If PersistenceDbServiceTest is executed first then it sets session factory to
MockSessionFactory.
Unfortunately it seems that the setting is SAME for ALL future newly created
JbpmContexts.
PersistenceServiceDbTest then tests that the factory is null but it is not
assertNull(persistenceServiceFactory.sessionFactory). The same test also tests few more
features that ends in calls of unsupported operations on the MockSessionFactory.
I am not sure if this is a problem of test - then the sessionFactory should be cleard
after test or if it is wrong that the setting is shared for all JBpmContexts.
--
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
1:43 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-2047) PersistenceDbServiceTest and PersistenceServiceDbTest are dependent
[
https://jira.jboss.org/jira/browse/JBPM-2047?page=com.atlassian.jira.plug...
]
Alejandro Guizar updated JBPM-2047:
-----------------------------------
Comment: was deleted
PersistenceDbServiceTest and PersistenceServiceDbTest are dependent
-------------------------------------------------------------------
Key: JBPM-2047
URL: https://jira.jboss.org/jira/browse/JBPM-2047
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM-3.2.5.SP1
Reporter: Jiri Pechanec
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.9
The tests can fail based on the execution order of these tests.
If PersistenceDbServiceTest is executed first then it sets session factory to
MockSessionFactory.
Unfortunately it seems that the setting is SAME for ALL future newly created
JbpmContexts.
PersistenceServiceDbTest then tests that the factory is null but it is not
assertNull(persistenceServiceFactory.sessionFactory). The same test also tests few more
features that ends in calls of unsupported operations on the MockSessionFactory.
I am not sure if this is a problem of test - then the sessionFactory should be cleard
after test or if it is wrong that the setting is shared for all JBpmContexts.
--
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
1:49 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-2047) PersistenceDbServiceTest and PersistenceServiceDbTest are dependent
[
https://jira.jboss.org/jira/browse/JBPM-2047?page=com.atlassian.jira.plug...
]
Alejandro Guizar commented on JBPM-2047:
----------------------------------------
SOA-1863 provided evidence that PersistenceServiceDbTest is still affected by the order of
execution. PersistenceServiceDbTest relies on the shared object returned by
JbpmConfiguration.getInstance(). Other tests are somehow affecting that instance.
PersistenceDbServiceTest and PersistenceServiceDbTest are dependent
-------------------------------------------------------------------
Key: JBPM-2047
URL: https://jira.jboss.org/jira/browse/JBPM-2047
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM-3.2.5.SP1
Reporter: Jiri Pechanec
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.9
The tests can fail based on the execution order of these tests.
If PersistenceDbServiceTest is executed first then it sets session factory to
MockSessionFactory.
Unfortunately it seems that the setting is SAME for ALL future newly created
JbpmContexts.
PersistenceServiceDbTest then tests that the factory is null but it is not
assertNull(persistenceServiceFactory.sessionFactory). The same test also tests few more
features that ends in calls of unsupported operations on the MockSessionFactory.
I am not sure if this is a problem of test - then the sessionFactory should be cleard
after test or if it is wrong that the setting is shared for all JBpmContexts.
--
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
1:59 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-2047) PersistenceDbServiceTest and PersistenceServiceDbTest are dependent
[
https://jira.jboss.org/jira/browse/JBPM-2047?page=com.atlassian.jira.plug...
]
Alejandro Guizar updated JBPM-2047:
-----------------------------------
Attachment: PersistenceServiceDbTest.diff
Attaching patch to prevent PersistenceServiceDbTest from being affected by other tests.
PersistenceDbServiceTest and PersistenceServiceDbTest are dependent
-------------------------------------------------------------------
Key: JBPM-2047
URL: https://jira.jboss.org/jira/browse/JBPM-2047
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM-3.2.5.SP1
Reporter: Jiri Pechanec
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.9
Attachments: PersistenceServiceDbTest.diff
The tests can fail based on the execution order of these tests.
If PersistenceDbServiceTest is executed first then it sets session factory to
MockSessionFactory.
Unfortunately it seems that the setting is SAME for ALL future newly created
JbpmContexts.
PersistenceServiceDbTest then tests that the factory is null but it is not
assertNull(persistenceServiceFactory.sessionFactory). The same test also tests few more
features that ends in calls of unsupported operations on the MockSessionFactory.
I am not sure if this is a problem of test - then the sessionFactory should be cleard
after test or if it is wrong that the setting is shared for all JBpmContexts.
--
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
2:59 a.m.
New subject: [JBoss JIRA] Resolved: (JBPM-2047) PersistenceDbServiceTest and PersistenceServiceDbTest are dependent
[
https://jira.jboss.org/jira/browse/JBPM-2047?page=com.atlassian.jira.plug...
]
Alejandro Guizar resolved JBPM-2047.
------------------------------------
Resolution: Done
PersistenceDbServiceTest and PersistenceServiceDbTest are dependent
-------------------------------------------------------------------
Key: JBPM-2047
URL: https://jira.jboss.org/jira/browse/JBPM-2047
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM-3.2.5.SP1
Reporter: Jiri Pechanec
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.9
Attachments: PersistenceServiceDbTest.diff
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
The tests can fail based on the execution order of these tests.
If PersistenceDbServiceTest is executed first then it sets session factory to
MockSessionFactory.
Unfortunately it seems that the setting is SAME for ALL future newly created
JbpmContexts.
PersistenceServiceDbTest then tests that the factory is null but it is not
assertNull(persistenceServiceFactory.sessionFactory). The same test also tests few more
features that ends in calls of unsupported operations on the MockSessionFactory.
I am not sure if this is a problem of test - then the sessionFactory should be cleard
after test or if it is wrong that the setting is shared for all JBpmContexts.
--
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
2:59 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-2047) PersistenceDbServiceTest and PersistenceServiceDbTest are dependent
[
https://jira.jboss.org/jira/browse/JBPM-2047?page=com.atlassian.jira.plug...
]
Alejandro Guizar updated JBPM-2047:
-----------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
PersistenceDbServiceTest and PersistenceServiceDbTest are dependent
-------------------------------------------------------------------
Key: JBPM-2047
URL: https://jira.jboss.org/jira/browse/JBPM-2047
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM-3.2.5.SP1
Reporter: Jiri Pechanec
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.9
Attachments: PersistenceServiceDbTest.diff
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
The tests can fail based on the execution order of these tests.
If PersistenceDbServiceTest is executed first then it sets session factory to
MockSessionFactory.
Unfortunately it seems that the setting is SAME for ALL future newly created
JbpmContexts.
PersistenceServiceDbTest then tests that the factory is null but it is not
assertNull(persistenceServiceFactory.sessionFactory). The same test also tests few more
features that ends in calls of unsupported operations on the MockSessionFactory.
I am not sure if this is a problem of test - then the sessionFactory should be cleard
after test or if it is wrong that the setting is shared for all JBpmContexts.
--
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
5235
days inactive
5579
days old
11 comments
4 participants
participants (4)
-
Alejandro Guizar (JIRA) -
Jiri Pechanec (JIRA)
-
Thomas Diesler (JIRA)
-
Tom Baeyens (JIRA)