From: Elrond <elrond+mediagoblin.org@samba-tng.org>
Date: Fri, 21 Oct 2011 22:21:25 +0000 (+0200)
Subject: Change unit tests to use add_table_field
X-Git-Url: https://vcs.fsf.org/?a=commitdiff_plain;h=733dc2c27595961e17fd9ab205c1f47e8e3918a6;p=mediagoblin.git

Change unit tests to use add_table_field

One of the test migrations adds a field. So rewrite it to
use the new add_table_field helper function.  This is a
good test for it.
---

diff --git a/mediagoblin/tests/test_migrations.py b/mediagoblin/tests/test_migrations.py
index fc2449f7..e7cef0a1 100644
--- a/mediagoblin/tests/test_migrations.py
+++ b/mediagoblin/tests/test_migrations.py
@@ -23,6 +23,7 @@ from mediagoblin.tests.tools import (
 from mediagoblin.db.util import (
     RegisterMigration, MigrationManager, ObjectId,
     MissingCurrentMigration)
+from mediagoblin.db.migrations import add_table_field
 
 # This one will get filled with local migrations
 TEST_MIGRATION_REGISTRY = {}
@@ -45,10 +46,7 @@ def creature_add_magical_powers(database):
     magical powers, all existing monsters, setting to an empty list is
     fine.
     """
-    database['creatures'].update(
-        {'magical_powers': {'$exists': False}},
-        {'$set': {'magical_powers': []}},
-        multi=True)
+    add_table_field(database, 'creatures', 'magical_powers', [])
 
 
 @RegisterMigration(2, TEST_MIGRATION_REGISTRY)