find out how to test the checker...

[co0p]

oh my god we have go (routines).

[jevbelikov]

could use postman mock server? but it may cost something and is another dependency

would the hexagon way spin up a local http server that responds in a particular way?

i think checker should use hhtpclient to send real request somewhere (could be localhost) and collect + parse result (but if we have a local server for test duration we would need to test that too? e.g. localhost:8888/200 give 200 OK status /404 gives 404 etc tests for <200 >300 host unreachable and timeout?)

[co0p]

I already do http testing. See notifiy implementation / tests. It is basically a local http server with the relevant parts active and injected. There is no need to do a postman mock server - go has it's own http server mock framework / testing lib.

…

On Tue, Apr 17, 2018 at 6:47 PM, Evgenij Belikov ***@***.***> wrote: could use postman mock server? but it may cost something and is another dependency would the hexagon way spin up a local http server that responds in a particular way? i think checker should use hhtpclient to send real request somewhere (could be localhost) and collect + parse result (but if we have a local server for test duration we would need to test that too? e.g. localhost:8888/200 give 200 OK status /404 gives 404 etc tests for <200 >300 host unreachable and timeout?) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADLFtYr8-2UmhRQZr_hPWIIxGP3UP2v0ks5tphyigaJpZM4TVk6G> .