From 0c6af8c803e3c13b708b11df498cbd99c129d809 Mon Sep 17 00:00:00 2001 From: Michael Ries Date: Wed, 31 Jul 2013 15:59:11 -0600 Subject: [PATCH] adding section to talk about running tests --- CONTRIBUTING.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 3c71fdb..032e038 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -37,6 +37,17 @@ Here's an easy guide that should get you up and running: That's it for the one time setup. Now you're ready to make a change. +## Running the tests + +To run the tests make sure you have a webserver running with its docroot pointing to the polymer-all directory. Then navigate to /polymer-elements/test/runner.html + +For Example: + + cd polymer-all + ruby -rwebrick -e'WEBrick::HTTPServer.new(:Port => 4000, :DocumentRoot => Dir.pwd).start' + +Then in your browser open: http://localhost:4000/polymer-elements/test/runner.html + ## Submitting a pull request We iterate fast! To avoid potential merge conflicts, it's a good idea to pull from the main project before making a change and submitting a pull request. The easiest way to do this is setup a remote called `upstream` and do a pull before working on a change: