Split out subscript to see which one is erroring

[rails.git] / test / fixtures / changesets.yml

diff --git a/test/fixtures/changesets.yml b/test/fixtures/changesets.yml
index defd691d2c773d67a4579cb37273fa72660fcdf0..055381ae48140af59b22c901a8f2d8bea85ffb38 100644 (file)
--- a/test/fixtures/changesets.yml
+++ b/test/fixtures/changesets.yml
@@ -14,7 +14,7 @@ normal_user_first_change:
   max_lat: <%= 5 * SCALE %>
   num_changes: 11
   
-second_user_first_change:
+public_user_first_change:
   id: 2
   user_id: 2
   created_at: "2008-05-01 01:23:45"
@@ -28,6 +28,13 @@ normal_user_closed_change:
   closed_at: "2007-01-02 00:00:00"
   num_changes: 0
 
+public_user_closed_change:
+  id: 7
+  user_id: 2
+  created_at: "2007-01-01 00:00:00"
+  closed_at: "2007-01-02 00:00:00"
+  num_changes: 0
+
 normal_user_version_change:
   id: 4
   user_id: 1
@@ -48,3 +55,17 @@ invalid_changeset:
   created_at: "2008-01-01 00:00:00"
   closed_at: "2008-01-02 00:00:00"
   num_changes: 9
+
+# changeset which still has time remaining, but has been closed
+# by containing too many elements.
+too_many_elements_changeset:
+  id: 6
+  user_id: 1
+  created_at: "2008-01-01 00:00:00"
+  closed_at: <%= DateTime.now + Rational(1,24) %>
+  min_lon: <%= 1 * SCALE %>
+  min_lat: <%= 1 * SCALE %>
+  max_lon: <%= 4 * SCALE %>
+  max_lat: <%= 4 * SCALE %>
+  num_changes: <%= Changeset::MAX_ELEMENTS + 1 %>
+