Skip to content
This repository has been archived by the owner on Jan 17, 2023. It is now read-only.

Setup server unit tests #427

Closed
ianb opened this issue May 20, 2015 · 2 comments
Closed

Setup server unit tests #427

ianb opened this issue May 20, 2015 · 2 comments
Milestone

Comments

@ianb
Copy link
Contributor

ianb commented May 20, 2015

We can start simple: GET /, PUT/GET /data/someId, GET /someId – just a smoke test, though ideally end-to-end (not just calling functions).

@ianb ianb added this to the The Shallow MVP milestone May 20, 2015
@ianb
Copy link
Contributor Author

ianb commented Jul 15, 2015

For now, let's do a simple end-to-end integration test (over HTTP) that tests creating a shot and getting it back. This wouldn't include any testing of the addon. So it would be like:

PUT {dev_backend}/data/{random}/domain
{... test data ...}

And then expect back a specific response, and test that the response looks sane. Later we can look at including the addon in tests.

@ianb ianb modified the milestones: First Launch, The Shallow MVP Jul 15, 2015
@ianb ianb modified the milestones: Next Tasks, First Launch Aug 19, 2015
@ghost ghost modified the milestones: Next Tasks, Blue Sky Jun 28, 2017
@ianb
Copy link
Contributor Author

ianb commented Jan 10, 2018

We've done this in test/server

@ianb ianb closed this as completed Jan 10, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant