...
So every time you think that a route is ready for production deployment or is used by some client, you will have to write all kinds of interface tests for this route. Remember to check for:
- All HTTP response codes structure (2XX, 3XX, 4XX, 5XX)
- Structure of your data (e.g. the response needs to match an array, that consists of separate values)
- content Content of your data (e.g. the separate values are typed as String, it should be exactly at least five of them, these strings are not empty and match you're previously inserted data)
- Always test as open minded (e.g. use object.contains(name) instead of object === {name: "..."}) → this allows non-breaking extensions
...
What if a test fails to execute?
Well, you probably broke a API method and it's not backward compatible anymore. That's really bad! Instead of fixing or out commenting the test, please fix the API method, so the test succeeds again, or introduce a new version of this method, or discard your changes - because breaking a API method is not allowed!
| Info |
|---|
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...