Skip to content
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

More unit tests #44

Closed
sneakypete81 opened this issue Jun 15, 2013 · 0 comments · Fixed by #45
Closed

More unit tests #44

sneakypete81 opened this issue Jun 15, 2013 · 0 comments · Fixed by #45
Assignees
Milestone

Comments

@sneakypete81
Copy link
Contributor

As mentioned in #37, the majority of the current tests are integration tests, communicating via the API with a photo/frontend server. Multiple test servers can be used to validate against different server/API versions.

While this is a useful strategy for flushing out issues and generally making sure the API doesn't accidentally get broken, it would also be useful to have a wider variety of unit tests that don't require a server connection.

In particular:

  • Get/Post testing of openphoto_http.py
  • Each API endpoint
  • The commandline interface

The goal should be to mock at the socket level (eg. Httpretty).

Once we have good unit test coverage, we can use Travis to run unit tests, and run the integration tests manually as required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant