-
Notifications
You must be signed in to change notification settings - Fork 48
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 functional tests to our JSON API #474
Labels
Comments
pascalchevrel
added a commit
to pascalchevrel/transvision
that referenced
this issue
Jun 10, 2015
- adds a dependency to a simple testing library I wrote - integrates with Travis - add tests to all our current API calls, currently test: http response code, expected content, validity of Json
pascalchevrel
added a commit
to pascalchevrel/transvision
that referenced
this issue
Jun 10, 2015
- adds a dependency to a simple testing library I wrote - integrates with Travis - add tests to all our current API calls, currently test: http response code, expected content, validity of Json
pascalchevrel
added a commit
to pascalchevrel/transvision
that referenced
this issue
Jun 10, 2015
- adds a dependency to a simple testing library I wrote - integrates with Travis - add tests to all our current API calls, currently test: http response code, expected content, validity of Json
pascalchevrel
added a commit
to pascalchevrel/transvision
that referenced
this issue
Jun 10, 2015
- adds a dependency to a simple testing library I wrote - integrates with Travis - add tests to all our current API calls, currently test: http response code, expected content, validity of Json
pascalchevrel
added a commit
to pascalchevrel/transvision
that referenced
this issue
Jun 10, 2015
- adds a dependency to a simple testing library I wrote - integrates with Travis - add tests to all our current API calls, currently test: http response code, expected content, validity of Json
pascalchevrel
added a commit
that referenced
this issue
Jun 11, 2015
Issue #474: Automate functional testing of our JSON API
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have unit tests but those can't expose errors caused by thiungs such as files permissions, url rewrites and other factors in the environment. Unit tests also give us results on how our classes work but not on if the app believes correctly, it doesn't test the actual end result.
For the JSON API, this can be a problem because we don't want to regress how it works while adding new features. I have code that allows testing that the Json API is behaving as expected.
The text was updated successfully, but these errors were encountered: