Issue Details (XML | Word | Printable)

Key: JRA-11652
Type: Task Task
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Dylan Etkin [Atlassian]
Votes: 1
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA

Fix the test entityengine.xml to use JotmFactory as the transaction factory and remove UtilsForTestSetup.loadDatabaseDriver(); from the unit tests

Created: 01/Dec/06 12:01 AM   Updated: 06/Dec/07 08:00 PM
Component/s: Backend / Domain Model
Affects Version/s: 3.7 Beta 2
Fix Version/s: 3.13.x

Time Tracking:
Original Estimate: 6 hours
Original Estimate - 6 hours
Remaining Estimate: 6 hours
Remaining Estimate - 6 hours
Time Spent: Not Specified
Remaining Estimate - 6 hours

Participants: Dylan Etkin [Atlassian] and Jed Wesley-Smith [Atlassian]
Since last comment: 43 weeks, 5 days ago
To be done by: Pair of developers
Labels:


 Description  « Hide
Currently the unit test entityengine.xml is using the DumbFactory transaction factory, which causes us to need to invoke the UtilsForTestSetup.loadDatabaseDriver() method. There are lots of JIRA classes that initialize the db without us really realizing it and the ordering of the running of the unit tests can make it such that the "test" db connection gets initialized incorrectly.

We need to change the test entityengine.xml to use the Jotm transaction factory. This will cause the TestUpgradeUtils test to fail because the upgrade util is written in such a way that it assumes the Connection is in autocommit mode. This test and the method it tests either needs to be removed or we need to update the code to check if the connection is set to autocommit and if not then commit the connection.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Jed Wesley-Smith [Atlassian] added a comment - 06/Dec/07 08:00 PM
The fix for this issue has not been able to make it into JIRA v3.12. We are hoping to incorporate it into v3.12.1. As of writing however, there are 163 items scheduled as Fix For v3.12.1. We will not be able to include all of them.