-
Notifications
You must be signed in to change notification settings - Fork 128
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
Expand all docs to have examples (including HTML) #25
Comments
In fact, for running doctests, we should probably use one of the techniques suggested by Travis here: https://docs.travis-ci.com/user/gui-and-headless-browsers/ |
Agreed that this is a good thing to do! |
Oh, yeah, that's a good idea. What we might actually want to do is use a free @saucelabs' open-source plan to run all the tests: https://saucelabs.com/open-source. |
I've sent them an e-mail. |
FWIW, this will likely depend on #18, since that's how you indicate to @saucelabs what backend to use. |
d2843b0 🎉 |
I'd like all the methods we provide to have doctests, and ideally to also give the HTML that they are operating over. I'd be happy to alos host those HTML snippets somewhere so that we don't have all the tests use
wikipedia.org
(which could also change).It's a little sad that we need to disable these tests by default. We should probably get phantomjs or slimerjs running on travis so that it can run all the test cases too!
/cc @phrohdoh
The text was updated successfully, but these errors were encountered: