Real-life RESTful server example on Flask-RESTplus
#26 showed that there might be a situation when all tests pass, the response is expected, but it was not explicitly covered with `@api.response()` decorator. I think we will need to override `Api.output` from `flask_restplus/api.py` (note, there is already customization on Api class in `flask_restplus_patched`, so you can just add this patch there), so we can check what responses are defined on the `resource`, and the current response is expected (don't forget about special care around HTTP/500 internal error, this can happen anywhere and shouldn't be shadowed).
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be still under discussion. The issue was opened by frol and has received 2 comments.