From 4f8ffbf2ce0557d46688b2dce5f176542751b04a Mon Sep 17 00:00:00 2001 From: Tobias Bieniek Date: Sat, 9 Mar 2013 20:05:31 +0100 Subject: [PATCH] Added notes that "./build.py test" requires plovr to be running --- CONTRIBUTING.md | 3 ++- test/README.md | 3 +++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 0991e72756..956bd83fb2 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -50,7 +50,8 @@ Use the following to run the tests: $ ./build.py test -This command assumes that the `phantomjs` command is on your PATH. +This command assumes that the `phantomjs` command is on your PATH and that the +polvr web server is running (`./build.py serve`). ### The `precommit` target diff --git a/test/README.md b/test/README.md index 95b51ebf69..3d025a53a4 100644 --- a/test/README.md +++ b/test/README.md @@ -24,6 +24,9 @@ With PhantomJS installed, and assuming phantomjs is in the PATH: This command can also be run by doing `./build.py test` at the root of ol3. +Make sure that the polvr web server is running (`./build.py serve`), otherwise +you will most likely see something like `0 specs, 0 failures in 0.001s.`. + Tip for TDD'ers: to make PhantomJS run the test suite continuously each time a spec file is changed you can use nosier (http://pypi.python.org/pypi/nosier) and do `nosier -p test -p src "./build.py test"`.