-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
Add tests #154
Comments
Let's use https://github.com/sindresorhus/ava |
* Extracts the resolving of a page's path to it's own file for testability. * Adds `ava` as a development dependency to write and run tests. * Adds ava related settings to inherit the babel config and run the tests with npm test to package.json * Refactor the quad-nested if statements in path resolving. Working toward resolving Issue gatsbyjs#154
Any preference on other testing utilities? I wrote a single integration test with no real assertions, and came to the realization that we're probably going to need more stuff to get some really good coverage.
I'm pretty new to JS testing land, so I'm not really sure what's the best/hottest to use. |
No strong preferences. Those are very common utilities so are great choices. |
Closing as old and not very useful anymore. |
Tests are good.
Modules to unit test
glob-pages.js
(which should be split into two modules, one for globbing and one for processing the files).create-routes.js
gatsby-helpers.js
Integration tests
The text was updated successfully, but these errors were encountered: