Use counter caches to improve spam scoring

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

diff --git a/test/fixtures/current_nodes.yml b/test/fixtures/current_nodes.yml
index 10c48196d54163e16d074cb1a8047315bd1c091f..3f34ddabefac20d98112e619f1e5c58d86da7680 100644 (file)
--- a/test/fixtures/current_nodes.yml
+++ b/test/fixtures/current_nodes.yml
@@ -25,7 +25,7 @@ used_node_1:
   id: 3
   latitude: <%= 3*SCALE %>
   longitude: <%= 3*SCALE %>
-  changeset_id: 1
+  changeset_id: 2
   visible: true
   version: 1
   tile: <%= QuadTile.tile_for_point(3,3) %>
@@ -45,7 +45,7 @@ node_used_by_relationship:
   id: 5
   latitude: <%= 5*SCALE %>
   longitude: <%= 5*SCALE %>
-  changeset_id: 1
+  changeset_id: 2
   visible: true
   version: 1
   tile: <%= QuadTile.tile_for_point(5,5) %>
@@ -161,3 +161,13 @@ public_visible_node:
   tile: <%= QuadTile.tile_for_point(1,1) %>
   timestamp: 2007-01-01 00:00:00
 
+redacted_node:
+  id: 17
+  latitude: <%= 1*SCALE %>
+  longitude: <%= 1*SCALE %>
+  changeset_id: 2
+  visible: false
+  version: 2
+  tile: <%= QuadTile.tile_for_point(1,1) %>
+  timestamp: 2007-01-01 00:00:00
+