Skip to content
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

Question: still up-to-date? #6

Open
noopole opened this issue Apr 15, 2016 · 2 comments
Open

Question: still up-to-date? #6

noopole opened this issue Apr 15, 2016 · 2 comments

Comments

@noopole
Copy link

noopole commented Apr 15, 2016

I'm using this library in place of chai-webdriver in order to deal with Promises and to drop the done() callbacks.

I wonder if it is recommended to use it or is there a new recommended way?

Thank you for your advice.

@benmosher
Copy link

benmosher commented Apr 15, 2016

FWIW, I have been using the Mocha BDD wrappers and the assert helper provided with the WebDriver npm package.

If you use the provided describe/it/before, etc., a queue manages control flow and allows you to structure your test code as if they were being executed synchronously.

I found this to be much simpler, after making my own fork of this wrapper and using it for a while.

Ultimately, I found that for my scripts, I was spending a lot of time writing new Chai wrapper code and it was simpler--both more readable and more obvious what was happening--when I just used the provided tools in the selenium-webdriver package.

@noopole
Copy link
Author

noopole commented Apr 19, 2016

Thank you Ben for your answer and for your piece of advice. It didn't know this feature!

I'll give it a try. Also I will take a look at chai-as-promised which could do the trick.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants