Timeline for How do you test a backend API?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 14, 2017 at 18:51 | history | edited | Sam Woods | CC BY-SA 3.0 |
Clarifying that you need a consumer, and not necessarily an application to test an API.
|
| Jun 14, 2017 at 18:49 | comment | added | Sam Woods | @FDM I only meant that you need to write some code to call into the API, that very likely would just be some tests and a test library or tool like postman. I edited the answer to be more clear. | |
| Jun 1, 2017 at 13:51 | comment | added | FDM | -1, since when do you HAVE to create an application to test an API? On the contrary, using a tool like Postman allows for API testing pur sang. | |
| Aug 18, 2014 at 23:06 | comment | added | Bruce | Also, if the back-end expects heavy traffic, it brings in a whole other category of load and performance testing. | |
| Aug 18, 2014 at 23:03 | comment | added | Bruce | Nice answer. I'd also specifically call out the network as another one of those dependencies you'll want to consider in your testing - the back-end must behave reasonably when the network gets wonky, which it will. (Wonky means things like missing responses and broken sessions.) | |
| Sep 5, 2013 at 18:25 | history | edited | Sam Woods | CC BY-SA 3.0 |
Added another example for mocking dependencies.
|
| Sep 5, 2013 at 16:30 | history | answered | Sam Woods | CC BY-SA 3.0 |