[hibernate-issues] [Hibernate-JIRA] Commented: (EJB-418) JBPAPP-1787 - Implement tearDown in EJB3TestCase

[Hardy Ferentschik (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/EJB-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32736#action_32736 ] 

Hardy Ferentschik commented on EJB-418:
---------------------------------------

Adding a proper tearDown to EJB3TestCase seems to be a good idea. There were several (and probably still are) issues with the test setup when using non in memory databases. I see no problem with this patch.

> JBPAPP-1787 - Implement tearDown in EJB3TestCase
> ------------------------------------------------
>
>                 Key: EJB-418
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-418
>             Project: Hibernate Entity Manager
>          Issue Type: Bug
>          Components: EntityManager
>         Environment: Any database using the tests PersistTest and XmlAttributeOverrideTest. 
>            Reporter: Juraci Paixao Krohling
>         Attachments: EJB3TestCase.java.2.diff, EJB3TestCase.java.diff
>
>
> https://jira.jboss.org/jira/browse/JBPAPP-1787
> There are some tests in EM test suite which subclasses EJB3TestCase (all of them in the package org.hibernate.ejb.test.ops), while most of the other tests subclasses org.hibernate.ejb.test.TestCase.
> Tests subclassing EJB3TestCase are not having its tables dropped after the execution, causing failures in other tests which uses the same table names with different table definitions.
> How to reproduce:
> - Drop all tables from the database to be used in the test
> - Run org.hibernate.ejb.test.ops.PersistTest#testBasic
> - There should be, among others, three tables: employer_employee,employer,employee
> - Run org.hibernate.ejb.test.xml.XmlAttributeOverrideTest#testAttributeOverriding
> - It should fail to drop the table "employee" (check the logs), failing with "java.sql.BatchUpdateException: Unknown column 'home_city' in 'field list'"
> - Drop all tables from the database
> - Run org.hibernate.ejb.test.xml.XmlAttributeOverrideTest#testAttributeOverriding again
> - There should be no failures. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira