Fix some test-related documentation in the README.

(imported from commit 130f316ffc87c8032219660a26c0c9681c6ab52b)
This commit is contained in:
Tim Abbott 2015-09-19 15:50:55 -07:00
parent 36445d1576
commit 24dfa10556
1 changed files with 12 additions and 4 deletions

View File

@ -59,18 +59,26 @@ To start the development server:
Running the test suite
======================
One-time setup:
One-time setup of test databases:
./tools/postgres-init-test-db
./tools/do-destroy-rebuild-test-database
Backend tests:
./tools/test-backend
Run all tests:
./tools/test-all
Frontend tests: not yet supported
This runs the linter plus all of our test suites; they can all be run
separately (just read `tools/test-all` to see them). You can also run
individual tests, e.g.:
./tools/test-backend zerver.test_bugdown.BugdownTest.test_inline_youtube
./tools/test-js-with-casper 10-navigation.js
Possible issues
===============
The Casper tests are flaky on the Virtualbox environment (probably due
to some performance-sensitive races). Until this issue is debugged,
you may need to rerun them to get them to pass.
When running the test suite, if you get an error like this:
sqlalchemy.exc.ProgrammingError: (ProgrammingError) function ts_match_locs_array(unknown, text, tsquery) does not exist
LINE 2: ...ECT message_id, flags, subject, rendered_content, ts_match_l...