-
Notifications
You must be signed in to change notification settings - Fork 3
Protractor spike 2016 09 19 #1
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
Conversation
catching up with fork origin
sturmf
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you hook this tests up to the travis.ci?
|
Pew... so this is green now. But the travis configuration exploded. We should talk about refactoring this. @sturmf Added you as contributor to my fork. |
|
How about merging this to master? Admittedly, there are a few ways to refactor this
but I'd rather see how we use the protractor tests locally for development and let this usage inform future refactorings. That way we can start test-driving new features now... :-) |
This is just a initial test. Could you verify if the install description is complete?
"It works on my machine..." :-)