-
Notifications
You must be signed in to change notification settings - Fork 207
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
Planning issue: expand test coverage with more thorough testing #304
Comments
Pasting from @jywarren 's suggestions
|
Big start to testing here: #313 |
I think for the unit and functional tests, the process could be:
How does this sound? This can get us a long way there. Coverage trackingWe could also add a coverage badge using Coveralls or another service, like CodeClimate. CodeClimate actually gives MapKnitter a decent score! |
Just chiming in that this ended up being a really good self contained update which built out node, warpable fixtures and added decent warpable unit tests! It's a good reference for further work of this kind. https://github.com/publiclab/mapknitter/pull/331/files |
https://coveralls.io/github/publiclab/mapknitter working!!!! Thanks @kaunair !!! |
Lots of progress to be made here... many areas are very low coverage, esp. controllers! |
Do we intend to change our testing framework to RSpec? |
Mapknitter repository requires a lot of unit tests, integration tests, fixtures and functional tests for each MVC pattern present in the repo along with routes explorations.
So @jywarren we can discuss testing in this issue.
Refer #300
The text was updated successfully, but these errors were encountered: