-
Notifications
You must be signed in to change notification settings - Fork 55
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 Jasmine tests to help document features #16
Comments
+1. I'll look into it. |
FWIW, we used Jasmine for our original Louisville project. Feel free to reference and steal from https://github.com/codeforamerica/hermes-be/tree/master/spec/lib. Shaunak |
Do I want to use this? https://github.com/mhevery/jasmine-node I may need some help with figuring out how you get it to test against the server. |
Correct. Specifically:
(You might want to check the latest major version of This says that only in development environments (such as your laptop), download and install
Hope that helps. Let me know if you more questions. |
Thanks @ycombinator. That definitely got me started. I've got a basic suite of tests up there at https://github.com/louh/naics-api/blob/master/spec/query.spec.js, that definitely doesn't cover all the possible results but I think it's a good enough start and to make sure I'm not doing anything wrong. There's also a test in there that was deliberately meant to fail because it's functionality that should be present but isn't. |
Jasmine is a nice little Javascript behavior-testing framework (similar to RSpec in Ruby) that lets you describe your code in very human-readable terms.
http://pivotal.github.io/jasmine/
Given a lot of the structure of issues I've seen so far, I think it'd be a great enhancement to add tests that cover these features using Jasmine.
The text was updated successfully, but these errors were encountered: