[tracker] functional-tests: Handle DISABLE_JOURNAL in backup-restore tests



commit 5d4a3ad8edcfe30fbb27bcab78a3316ded5f0d09
Author: JÃrg Billeter <j bitron ch>
Date:   Fri Jun 24 15:48:15 2011 +0200

    functional-tests: Handle DISABLE_JOURNAL in backup-restore tests

 tests/functional-tests/200-backup-restore.py |    4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)
---
diff --git a/tests/functional-tests/200-backup-restore.py b/tests/functional-tests/200-backup-restore.py
index 47060f7..61cc368 100755
--- a/tests/functional-tests/200-backup-restore.py
+++ b/tests/functional-tests/200-backup-restore.py
@@ -24,7 +24,7 @@ from common.utils.system import TrackerSystemAbstraction
 from common.utils.helpers import StoreHelper
 from common.utils import configuration as cfg
 from common.utils.storetest import CommonTrackerStoreTest as CommonTrackerStoreTest
-from common.utils.expectedFailure import expectedFailureBug as expectedFailureBug
+from common.utils.expectedFailure import expectedFailureBug, expectedFailureJournal
 import unittest2 as ut
 
 
@@ -253,6 +253,7 @@ class JournalReplayTest (CommonTrackerStoreTest):
         """
         Force journal replaying and check that the DB is correct aftewards
         """
+	@expectedFailureJournal()
  	def test_journal_01 (self) :
             """
             Journal replaying when the DB is corrupted
@@ -288,6 +289,7 @@ class JournalReplayTest (CommonTrackerStoreTest):
 
             self.tracker.update ("DELETE { <test://journal-replay/01> a rdfs:Resource. }")
 
+	@expectedFailureJournal()
 	def test_journal_02 (self) :
             """
             Journal replaying when the DB disappears



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]