summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMarcel Klehr <mklehr@gmx.net>2013-09-01 02:28:21 -0700
committerMarcel Klehr <mklehr@gmx.net>2013-09-01 02:28:21 -0700
commited77bffbabc16e4fcb1db8cea27ea11f4eaa2db3 (patch)
treeca7c2a6a7e08aa524b5d9cf692acac9b2aaeb647
parent20ae3b333bf9903135eae16192e9eb4bd8d38b88 (diff)
parent384f500d4c908bc4416a7e06a21480d3c49a19cd (diff)
downloadetherpad-lite-ed77bffbabc16e4fcb1db8cea27ea11f4eaa2db3.zip
Merge pull request #1869 from codingisacopingstrategy/clarify-how-to-access-tests
Clarify how to acces tests
-rw-r--r--CONTRIBUTING.md3
-rw-r--r--tests/README.md5
2 files changed, 8 insertions, 0 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index e185d9c5..74aa8b3f 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -63,3 +63,6 @@ The docs are in the `doc/` folder in the git repository, so people can easily fi
Documentation should be kept up-to-date. This means, whenever you add a new API method, add a new hook or change the database model, pack the relevant changes to the docs in the same pull request.
You can build the docs e.g. produce html, using `make docs`. At some point in the future we will provide an online documentation. The current documentation in the github wiki should always reflect the state of `master` (!), since there are no docs in master, yet.
+
+## Testing
+Front-end tests are found in the `tests/frontend/` folder in the repository. Run them by pointing your browser to `<yourdomainhere>/tests/frontend`. \ No newline at end of file
diff --git a/tests/README.md b/tests/README.md
new file mode 100644
index 00000000..1851305f
--- /dev/null
+++ b/tests/README.md
@@ -0,0 +1,5 @@
+# About this folder: Tests
+
+## Frontend
+
+To run the tests, point your browser to `<yourdomainhere>/tests/frontend`