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
Consider running tests in Node.js #875
Labels
Comments
Merged
codinsonn
pushed a commit
to codinsonn/date-fns
that referenced
this issue
Jun 9, 2019
…#875; closes date-fns#1066) * Setup Jest * Update Babel and Power Assert * Make test karma suite work * Fix multiple it used instead of describe * Fix accidentally disabled tests * Upgrade Sinon * Add Node.js suite to Travis CI * Remove node_modules from .flowconfig ignore * Remove console.log from a test * Use regexp for exception assertion to make it work in any Node.js * Disable Sauce Connect because it gives me headaches
codinsonn
pushed a commit
to codinsonn/date-fns
that referenced
this issue
Jun 10, 2019
…#875; closes date-fns#1066) * Setup Jest * Update Babel and Power Assert * Make test karma suite work * Fix multiple it used instead of describe * Fix accidentally disabled tests * Upgrade Sinon * Add Node.js suite to Travis CI * Remove node_modules from .flowconfig ignore * Remove console.log from a test * Use regexp for exception assertion to make it work in any Node.js * Disable Sauce Connect because it gives me headaches
elmomalmo
pushed a commit
to elmomalmo/date-fns
that referenced
this issue
Jul 12, 2019
…#875; closes date-fns#1066) * Setup Jest * Update Babel and Power Assert * Make test karma suite work * Fix multiple it used instead of describe * Fix accidentally disabled tests * Upgrade Sinon * Add Node.js suite to Travis CI * Remove node_modules from .flowconfig ignore * Remove console.log from a test * Use regexp for exception assertion to make it work in any Node.js * Disable Sauce Connect because it gives me headaches
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now we run tests only in headless Chrome. To make sure that date-fns don't break in different Node.js environments, we should consider running tests in Node as well.
For the background, see discussion: #874
The text was updated successfully, but these errors were encountered: