https://vpnw.com/tags/testing/ Recent content in Testing on VPNW.com Hugo en-us Fri, 09 Oct 2026 00:00:00 +0000 https://vpnw.com/how-vpn-works-0.4.0-was-tested-121-tests-a-real-wireguard-peer-and-14-ways-out-blocked/ Fri, 09 Oct 2026 00:00:00 +0000 https://vpnw.com/how-vpn-works-0.4.0-was-tested-121-tests-a-real-wireguard-peer-and-14-ways-out-blocked/ <p><strong>Every number on vpnw.com comes from one script in the code repository, run on one Linux machine with 2 CPUs. Its output is committed next to the code, so anyone can check a figure against the run that produced it.</strong></p> <p>The script is <code>tools/record-results.sh</code>, and it writes to <a href="https://github.com/VPNWorks/vpnw/tree/main/test/results">test/results</a>. It builds the plugins and the binaries, runs every test, runs them again under Go&rsquo;s race detector, measures coverage, runs nine fuzz targets, times the plugins and the WireGuard path, and tries every known way out of the sealed sandbox.</p> https://vpnw.com/vpn-works-0.4.1-all-17-ways-out-of-the-sealed-sandbox-blocked-ipv6-included/ Fri, 09 Oct 2026 00:00:00 +0000 https://vpnw.com/vpn-works-0.4.1-all-17-ways-out-of-the-sealed-sandbox-blocked-ipv6-included/ <p><strong>VPN Works 0.4.1 adds no features. It closes the one gap the 0.4.0 tests left open, and it fixes a bug those same tests turned up along the way.</strong></p> <p>The gap was IPv6. A sealed program tries every known way around vpnw, and two of those ways go over IPv6. The machine that records the project&rsquo;s figures has no IPv6 in its kernel at all, so those two tests never ran. 0.4.0 said so: 14 of 14 blocked, 2 not run.</p>