morethanreal
commented
11 years ago I apologize that this is a bit of a pain right now, but the polymer tests depend on other supporting repos (CustomElements, HTMLImports, mdv, ShadowDOM, platform) being cloned next to it. The easiest way might be to check out polymer-all and switch the polymer repo to your fork. The webserver root should be the parent directory of the cloned projects.
You also need to "git submodule update --init --recursive" after cloning, because our test tools are checked in as a submodule. Hope that helps!
On Mon, Jul 29, 2013 at 8:49 PM, Michael notifications@github.com wrote:
Hey Guys - Sorry if this is a lame question. I don't have much node experience. I forked the repo and tried to run the tests so i could give you a pull request, but I could not get the tests running. Here are my steps to reproduce.
1) Fork the repo 2) git clone --recursive 3) cd 4) npm install 5) start a webserver with document root at 6) open a browser with to localhost:4000/test/runner.html
I basically get some 404's for missing a mocha test file and then get some javascript errors about missing methods.
[image: screen shot 2013-07-29 at 9 46 04 pm]https://f.cloud.github.com/assets/80008/876438/fcf6ba2c-f8ca-11e2-9056-5de695fd34cc.png
— Reply to this email directly or view it on GitHubhttps://github.com/Polymer/polymer-elements/issues/13 .
mmmries
Hey Guys - Sorry if this is a lame question. I don't have much node experience. I forked the repo and tried to run the tests so i could give you a pull request, but I could not get the tests running. Here are my steps to reproduce.
1) Fork the repo 2) git clone --recursive
3) cd
4) npm install
5) start a webserver with document root at
6) open a browser with to localhost:4000/test/runner.html
I basically get some 404's for missing a mocha test file and then get some javascript errors about missing methods.