write tests for current endpoints
It would be very useful to be able to have a test that documents and exercises the current api.
part of the problem is that some of the details (api verbs, which cert signs what) is under-specified, and desktop and android have diverged from the original bonafide specification. we shouldn't rely on code-as-documentation, since this is costly to maintain.
(it should be also noted that some of the original assumptions behind bonafide are no longer valid, and they should be re-thinked at some point).
for now, it is enough if we document the types for the various json fields, and their original intent. there's an ongoing discussion (see !1 (closed)) for the upgrade to v4 of the api - being able to easily diff versions would be also a very nice thing to have in the toolbox. we have tried in the past to use json spec documents, and swagger to document the api, but the whole tooling seemed a bit overkill. but in theory, having the ability to get automatic parsers from one single declaration sounds like a good idea. (we might want to write our own haha!)
a minimal test could probably be an e2e test against a given float endpoint that fetches the relevant files in order (provider.json, ca.crt, eip-service.json, certificate and menshen call) and checks that they are not malformed (non empty gateways, valid certificate, etc).