Exports: specific configuration to manage ambiguous column (refs #3446)

1 files changed, 14 insertions, 1 deletions

diff --git a/archaeological_operations/tests.py b/archaeological_operations/tests.py
index 63f572643..c2d5aad83 100644
--- a/archaeological_operations/tests.py
+++ b/archaeological_operations/tests.py
@@ -332,7 +332,20 @@ class ImportOperationTest(ImportTest, TestCase):
         impt.delete()
         self.assertEqual(parcel_count - 3, models.Parcel.objects.count())
 
-    def testParseParcels(self):
+
+class ParcelTest(ImportTest, TestCase):
+    fixtures = [settings.ROOT_PATH +
+                '../fixtures/initial_data-auth-fr.json',
+                settings.ROOT_PATH +
+                '../ishtar_common/fixtures/initial_data-fr.json',
+                settings.ROOT_PATH +
+                '../ishtar_common/fixtures/test_towns.json',
+                settings.ROOT_PATH +
+                '../ishtar_common/fixtures/initial_importtypes-fr.json',
+                settings.ROOT_PATH +
+                '../archaeological_operations/fixtures/initial_data-fr.json']
+
+    def test_parse_parcels(self):
         # the database needs to be initialised before importing
         from archaeological_operations.import_from_csv import parse_parcels
         # default_town = Town.objects.create(numero_insee="12345",