Skip to content
This repository was archived by the owner on Aug 15, 2024. It is now read-only.

Tests status #5

Closed
sokra opened this issue Feb 27, 2013 · 3 comments
Closed

Tests status #5

sokra opened this issue Feb 27, 2013 · 3 comments

Comments

@sokra
Copy link
Member

sokra commented Feb 27, 2013

module tested status one browser status all browsers
events yes pass
punycode yes pass
querystring yes fail
timers some
buffer separate
vm separate
zlib separate
crypto some separate
assert no
child_process no
http/https no
path no
stream no
util/sys no
@defunctzombie
Copy link
Contributor

I would add tests for the separate modules as well. Seems strange but for
now it will be a good single place of testing until we decide how to best
handle separation.

Also, check out zuul to run tests in a browser locally to help in debugging.

On Wed, Feb 27, 2013 at 3:21 AM, Tobias Koppers [email protected]:

module tested status events yes pass punycode yes pass querystring yes
fail timers some buffer separate vm separate zlib separate crypto some
separate assert no child_process no http/https no path no stream no
util/sys no


Reply to this email directly or view it on GitHubhttps://github.com//issues/5
.

@sokra
Copy link
Member Author

sokra commented Feb 27, 2013

I tried it, but it don't support ./test/*.js on windows... I have to specify each test file.

I have a similar tool for webpack: webpack-dev-server

So you could run the tests also with

npm install mocha-loader
webpack-dev-server --colors --cache mocha-loader?interface=qunit!./test/events.js ./test/timers.js

@defunctzombie
Copy link
Contributor

I don't have windows so don't know why the *.js didn't work :P

Anyhow, glad to see many more tests added!

@sokra sokra closed this as completed Mar 18, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants