-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
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
Add testing suite for Web Components #9
Comments
This is a start to a web component test. cd into the seed element dir and then run wct. Right now we have issues we need to settle with selenium as you will see when the tests run
@Nevraeka @DannyBlueDesign - This branch is the start for the web component testing. Read the commit message and see that we will need to determine how to handle the selenium/safari issues that come up when running the test. More to be added with Mocha/Chai |
seed-element now back in the repo without being an external repository that it was originally.
Added wrong issue reference. |
So, once we complete the issue #21 the test cases will be in the project directory. |
I still cant figure out how to integrate it with Divshot/Travis. Need more time XD |
I havent been able to made progress on this. Can someone else work on Divshot and travis? |
I can look into Divshot & Travis |
Awesome!!. Thanks @Nevraeka |
Add web-components-tester npm module and setup scripts and files for easy unit and functional tests. Integrate with Divshot/Travis if possible.
The text was updated successfully, but these errors were encountered: