Migration manager's current migration should be 3, not 7, after running all migrations!
authorChristopher Allan Webber <cwebber@dustycloud.org>
Sun, 29 Jan 2012 23:23:27 +0000 (17:23 -0600)
committerChristopher Allan Webber <cwebber@dustycloud.org>
Sun, 29 Jan 2012 23:23:27 +0000 (17:23 -0600)
mediagoblin/tests/test_sql_migrations.py

index 8bb82efdf4e4195c28f761445c1113ba882c6d27..92925e645671669330a3e1616d7aed4bf1645e5d 100644 (file)
@@ -640,7 +640,7 @@ def test_set1_to_set3():
         '__main__', SET3_MODELS, SET3_MIGRATIONS, Session(),
         printer)
 
-    assert migration_manager.latest_migration == 3
+    assert migration_manager.latest_migration == 7
     assert migration_manager.database_current_migration == 0
 
     # Migrate
@@ -660,8 +660,8 @@ def test_set1_to_set3():
     migration_manager = MigrationManager(
         '__main__', SET3_MODELS, SET3_MIGRATIONS, Session(),
         printer)
-    assert migration_manager.latest_migration == 3
-    assert migration_manager.database_current_migration == 3
+    assert migration_manager.latest_migration == 7
+    assert migration_manager.database_current_migration == 7
 
     # Check all things in database match expected