We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Right now, we cannot do a clone of the repo, install dependencies and run tests.
Instead, we have to bower install google-map and then run tests from within the bower_components folder structure (see #81). This is really backward.
bower_components
I suggest that test cases use ../bower_components/[path] instead of ../../[path] in their script tags.
../bower_components/[path]
../../[path]
This would make contributing to this repo much more convenient.
The text was updated successfully, but these errors were encountered:
This is the recommended approach for https://github.com/Polymer/web-component-tester. However, when running the tests in a repo checkout, this works for me:
git clone git@github.com:GoogleWebComponents/google-map.git cd google-map; bower install wct -l chrome
Sorry, something went wrong.
They do run from the command line.
However, they don't load when served using a web server(used polymer serve) and opened in the browser.
polymer serve
I see. You may want to suggest this over on that repo.
No branches or pull requests
Right now, we cannot do a clone of the repo, install dependencies and run tests.
Instead, we have to bower install google-map and then run tests from within the
bower_components
folder structure (see #81). This is really backward.I suggest that test cases use
../bower_components/[path]
instead of../../[path]
in their script tags.This would make contributing to this repo much more convenient.
The text was updated successfully, but these errors were encountered: