lib/aiodatalite
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix mass action test when run multiple times

Browse Source 
Take initial db state into account for output expectations
This commit is contained in:
mathyba
2021-05-08 04:16:48 +02:00
parent 65ff76beba
commit db7eda11b3
1 changed files with 10 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
test/main_tests.py
View File

@@ -199,16 +199,23 @@ class DatabaseMassInsert(unittest.TestCase):
def setUp(self) -> None:
self.objs = [MassCommit(f'cat + {i}') for i in range(30)]
def testMassCreate(self):
with connect('other.db') as con:
cur = con.cursor()
cur.execute(f'CREATE TABLE IF NOT EXISTS MASSCOMMIT (obj_id, str_)')
start_tup = fetch_all(MassCommit)
create_many(self.objs, protect_memory=False)
_objs = fetch_all(MassCommit)
self.assertEqual(_objs, tuple(self.objs))
self.assertEqual(_objs, start_tup + tuple(self.objs))
def testMassCopy(self):
copy_many(self.objs, 'other.db', False)
setattr(MassCommit, 'db_path', 'other.db')
start_tup = fetch_all(MassCommit)
copy_many(self.objs, 'other.db', False)
tup = fetch_all(MassCommit)
self.assertEqual(tup, tuple(self.objs))
self.assertEqual(tup, start_tup + tuple(self.objs))
def tearDown(self) -> None:
[obj.remove_entry() for obj in self.objs]