service-template-node uses preq and Swagger specs to do automated testing (and monitoring in production), but preq won't work with http stream endpoints, as the response never finishes, and the promise never resolves. We need to figure out a way to test stream http endpoints in service-template.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | Xqt | T125197 Give hint to the current socketIO_client in ImportError of rcstream.py | |||
| Declined | None | T91393 RCStream is not accessible from python client due to using socket-io 1.0 while only socket-io 0.9 is offered | |||
| Declined | None | T68232 Upgrade RCStream backend to use socket.io 1.0 protocol | |||
| Resolved | Ottomata | T130651 EventStreams | |||
| Declined | None | T150439 Tests for swagger spec stream routes in EventStreams |
Event Timeline
Comment Actions
Some links regarding service template execution:
https://github.com/wikimedia/service-template-node/blob/master/test/features/app/spec.js
https://github.com/wikimedia/service-template-node/blob/master/test/features/app/spec.js#L269-L282
https://github.com/wikimedia/service-template-node/blob/master/spec.template.yaml#L113
https://github.com/wikimedia/mediawiki-services-eventstreams
https://www.mediawiki.org/wiki/ServiceTemplateNode/Updating
https://github.com/wikimedia/service-template-node/blob/master/test/utils/server.js
Comment Actions
Or, perhaps we should just wait until this happens:
https://github.com/go-swagger/go-swagger/issues/150
If it ever does, this will be easy! (maybe?)
Comment Actions
the automated testing doesn't work easily with this, it's too much work to make it work.