Renumber the casper tests to make space for realm-creation test.

And also fix the mysterious gaps at 6 and 8.

README.dev.md

@@ -1296,7 +1296,7 @@ time debugging a test failure, e.g.:
 ```
 ./tools/lint-all # Runs all the linters in parallel
 ./tools/test-backend zerver.tests.test_bugdown.BugdownTest.test_inline_youtube
-./tools/test-js-with-casper 10-navigation.js
+./tools/test-js-with-casper 09-navigation.js
 ./tools/test-js-with-node # Runs all node tests but is very fast
 ```
 

docs/testing.md

@@ -58,7 +58,7 @@ Since this is interacting with a real dev server, it can catch backend
 bugs as well.
 
 You can run this with `./tools/test-js-with-casper` or as
-`./tools/test-js-with-casper 05-settings.js` to run a single test file
+`./tools/test-js-with-casper 06-settings.js` to run a single test file
 from `frontend_tests/casper_tests/`.
 
 #### Debugging Casper.JS

frontend_tests/casper_tests/03-narrow.js

@@ -2,7 +2,7 @@ var common = require('../casper_lib/common.js').common;
 
 common.start_and_log_in();
 
-// We could use the messages sent by 01-site.js, but we want to
+// We could use the messages sent by 02-site.js, but we want to
 // make sure each test file can be run individually (which the
 // 'run' script provides for).