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
Use nightwatch.js for functional tests #122
Conversation
module.exports = { | ||
before: done => { | ||
chromedriver.start(); | ||
done(); |
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.
done()
should always be called.
|
||
'changes slides states when moving backward': browser => { | ||
browser.url(`file:///${__dirname}/list.html#3`); | ||
browser.keys(browser.Keys.ARROW_LEFT); |
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.
Nightwatch's constants for key codes are cool.
@@ -0,0 +1,16 @@ | |||
<!DOCTYPE html> |
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.
Several tests had
- open
list
- go
full
- really test stuff
algorithms in keys/tests.js
. With addition of this file, they are greatly simplified.
(Shift) F5 key has dropped in 2f0af4d so test could be dropped as well, otherwise WFM locally and LGTM in general. |
c173e0e
to
f488710
Compare
I've also added tests for a1567ac |
There are still some wdio dependencies left:
Do we still need Could you please clean up? |
Oops, my bad. Please, see #123. |
Each test case happen in separate process (Chrome gets restarted every time). If
browser.end()
is dropped, random tests start to fail. It takes 50sec on my machine to run them all. Please, let me know if we should find a way around this and whether I should prioritize this.