Automated end2end/smoke testing connectivity evaluation
Let's use this as a meta-issue for a project to build some automated testing of our circumvention technology. This is in part an onboarding project, so we can allow it some room and flexibility to grow/shift as we find necessary.
Among the goals here:
- Develop robust automated end to end/smoke tests which we can integrate into development and CI flows.
- Improve logging, metrics, and observability of circumvention architecture/deployment.
- Introduce @Arti to our circumvention architecture, code bases, collaborative practices.
- Improve documentation and create some public facing writing re: architecture and usage.
I'd like to break out individual tasks and link to them here:
- Get obfsvpn docker sandbox running and manual evaluation/exploration #10 (closed)
Relevant links/notes/etc:
- Connection hopping issue: #6
- Connection hopping prototype/deployment tracking: #8 (closed) (this is a bit of a dead issue so we might want to garbage collect it and/or actually make use of it)
- Connection hopping/docker sandbox merge request: obfsvpn!20 (merged)
- Current connection hopping/docker sandbox branch: https://0xacab.org/maxb/obfsvpn/-/tree/maxb/pt3-poc (I'd like to merge this sooner than later as to avoid it getting stale/allowing divergence)
Edited by Kali Kaneko