@tfc - Yep, can do for both. As a general question: for these sorts of "porting tests" PRs, would it be better to do a mechanical line-by-line translation (like I did here), or a more general rewrite?

@tfc - Yep, can do for both. As a general question: for these sorts of "porting tests" PRs, would it be better to do a mechanical line-by-line translation (like I did here),

this is what i did when the whole project began, as i don't understand how all of the tested services really work. Then a 1:1 port was the minimal feasible thing to do.

or a more general rewrite?

If you are the maintainer of the service, the test, or simply happen to know how the tested service really works and ought to be tested, a rewrite that makes it better/more readable/more structured is always welcome!

@flokli @tfc - Okay, since improvements are okay, I rewrote the tests to use more modern Python, remove duplication, and use proper assertions.

@flokli @tfc - ping! Anything I can do to keep this moving forward?

@andrew-d sorry didn't see the latest changes. I think @flokli is pretty busy at the time.

cc @worldofpeace

@GrahamcOfBorg test networkingProxy

Fixed commit message.