monit-configuration issueshttps://gitlab.torproject.org/tpo/anti-censorship/monit-configuration/-/issues2022-03-01T17:56:58Zhttps://gitlab.torproject.org/tpo/anti-censorship/monit-configuration/-/issues/6Add "end-to-end" test that talks to moat2022-03-01T17:56:58ZPhilipp Winterphw@torproject.orgAdd "end-to-end" test that talks to moatTo catch issues like the one in tpo/anti-censorship/pluggable-transports/meek#40001 early, we could add a new monit test that talks to moat over obfs4proxy. Basically, we would spawn a tor instance and let it bootstrap over meek. We then...To catch issues like the one in tpo/anti-censorship/pluggable-transports/meek#40001 early, we could add a new monit test that talks to moat over obfs4proxy. Basically, we would spawn a tor instance and let it bootstrap over meek. We then try to talk to moat and return with exit code 0 if this succeeded.
The challenge is that we should use the same tor and obfs4proxy version as Tor Browser does. And even then, there is no guarantee that we're catching all possible problems – for example, an issue may be limited to Windows. Still, having a test like this would probably go a long way.
(We discussed this topic in [today's anti-censorship meeting](http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-12-17-15.57.html)).