server tests: avoid actually binding to sockets
Mocking never looks as convincing, but in that case, it avoids assumptions on the surrounding networkin stack. For instance, our CI runs currently happens on Docker containers with no IPv6 capability, hence binding on `::1` just fails. Also, some build systems deliberately prohibit any networking in tests. This is (or has been) the case of Debian buildds.
Loading
Please register or sign in to comment