tools: Rename tool to check-schemas.

docs/subsystems/events-system.md

@@ -369,7 +369,7 @@ in `frontend_tests/node_tests/lib/events.js`, a test of the
 `server_events_dispatch.js` code for that event in
 `frontend_tests/node_tests/dispatch.js`, and verify your example
 against the two versions of the schema that you declared above using
-`tools/check-node-fixtures`.
+`tools/check-schemas`.
 
 #### Code coverage
 

frontend_tests/node_tests/lib/events.js

@@ -2,7 +2,7 @@
 
 //  These events are not guaranteed to be perfectly
 //  representative of what the server sends.  We
-//  have a tool called check-node-fixtures that tries
+//  have a tool called check-schemas that tries
 //  to validate this data against server side schemas,
 //  but there are certain edge cases that the tool now
 //  skips.  And even when the data matches the schema,

tools/ci/frontend

@@ -10,8 +10,8 @@ set -x
 # Run the node tests first, since they're fast and deterministic
 ./tools/test-js-with-node --coverage
 
-# Check the node fixtures (also fast)
-./tools/check-node-fixtures
+# Check that various schemas are consistent. (is fast)
+./tools/check-schemas
 
 # Check capitalization of strings
 ./manage.py makemessages --locale en

tools/test-all

@@ -71,7 +71,7 @@ run ./tools/test-api
 # ci/frontend
 run ./tools/lint --groups=frontend $FORCEARG
 run ./tools/test-js-with-node
-run ./tools/check-node-fixtures
+run ./tools/check-schemas
 run ./manage.py makemessages --locale en
 run env PYTHONWARNINGS=ignore ./tools/check-capitalization --no-generate
 run env PYTHONWARNINGS=ignore ./tools/check-frontend-i18n --no-generate