-
Notifications
You must be signed in to change notification settings - Fork 0
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
Implement client side tests #126
Comments
It seems like Protractor is really the best tool for the job, please check it out first: |
nvernooy
added a commit
that referenced
this issue
Aug 11, 2015
nvernooy
added a commit
that referenced
this issue
Aug 13, 2015
nvernooy
added a commit
that referenced
this issue
Aug 17, 2015
nvernooy
added a commit
that referenced
this issue
Aug 17, 2015
nvernooy
added a commit
that referenced
this issue
Sep 1, 2015
nvernooy
added a commit
that referenced
this issue
Sep 29, 2015
nvernooy
added a commit
that referenced
this issue
Oct 23, 2015
nvernooy
added a commit
that referenced
this issue
Oct 26, 2015
nvernooy
added a commit
that referenced
this issue
Oct 27, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Refer to the article below to see how we can implement client side tests:
http://krasimirtsonev.com/blog/article/unit-test-your-client-side-javascript-jsdom-nodejs
Perhaps start with a simple test to add a project and then we build it up from there.
The text was updated successfully, but these errors were encountered: