Use the same root test class.

Instead of being strongly tied to unittest2 make
it easier for taskflow to switch to another root
class (testr?) by abstracting out the unittest2
usage. This also enables some useful functionality
to exist in that root test class that other tasks
can take advantage of.

Change-Id: I381b6fb07e47f984b44cde439a17f39a1c1d32ac

2 files changed, 4 insertions, 6 deletions

diff --git a/taskflow/tests/unit/persistence/test_memory_persistence.py b/taskflow/tests/unit/persistence/test_memory_persistence.py
index 37aaa36..0d940b3 100644
--- a/taskflow/tests/unit/persistence/test_memory_persistence.py
+++ b/taskflow/tests/unit/persistence/test_memory_persistence.py
@@ -17,12 +17,11 @@
 #    under the License.
 
 from taskflow.persistence.backends import api as b_api
+from taskflow import test
 from taskflow.tests.unit.persistence import base
 
-import unittest2
 
-
-class MemoryPersistenceTest(unittest2.TestCase, base.PersistenceTestMixin):
+class MemoryPersistenceTest(test.TestCase, base.PersistenceTestMixin):
     def _get_backend(self):
         return 'memory'
 
diff --git a/taskflow/tests/unit/persistence/test_sql_persistence.py b/taskflow/tests/unit/persistence/test_sql_persistence.py
index 1a67f6a..44a7b0c 100644
--- a/taskflow/tests/unit/persistence/test_sql_persistence.py
+++ b/taskflow/tests/unit/persistence/test_sql_persistence.py
@@ -22,12 +22,11 @@ import tempfile
 from taskflow.openstack.common.db.sqlalchemy import session
 from taskflow.persistence.backends import api as b_api
 from taskflow.persistence.backends.sqlalchemy import migration
+from taskflow import test
 from taskflow.tests.unit.persistence import base
 
-import unittest2
 
-
-class SqlPersistenceTest(unittest2.TestCase, base.PersistenceTestMixin):
+class SqlPersistenceTest(test.TestCase, base.PersistenceTestMixin):
     """Inherits from the base test and sets up a sqlite temporary db."""
     def _get_backend(self):
         return 'sqlalchemy'