-
-
Notifications
You must be signed in to change notification settings - Fork 124
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
Replace testling (this project is dead) #63
Comments
I've been doing research on options for testing. It seems that since pjax doesn't do any rendering, most of the goals of testing could be achieved by just using jsdom. This won't indicate any browser-specific quirks, but I think as of now, those should be ironed out, and testing is really to prevent regressions. I've gotten all the tests to pass using jsdom, with a few small fixes to account for the differences between it and a real browser. @MoOx what's your opinion? |
One thing that will have to changed regardless, is the REST API used for testing XHR requests. The Github API refuses requests with custom headers, due to CORS. I've tested using httpbin instead, and that seems to be working as expected. |
jsdom is ok for me! |
On the subject of testing, It looks like the Travis config needs to be updated. It's running Node 0.10 and NPM 2, which are way out of date. I don't know where that's coming from, since those aren't specified in .travis.yml |
it's default travis version :/ |
I have 2 HDD and cannot start testling due to a really stupid bug (I opened an issue several months/years ago)
tape-testing/testling#111
The text was updated successfully, but these errors were encountered: