mirror of
https://github.com/go-gost/gost.git
synced 2026-10-08 03:55:45 +00:00
ginuerzh
64b71bd8a6
Adds an e2e suite (tests/e2e/utls_test.go + testdata/utls/*)
that exercises the utls dialer in a forward-proxy chain:
curl -> client gost (http proxy :8080)
-> chain node (http connector + utls dialer)
-> server gost (http over TLS listener :8443)
-> tcp-echo
Two cases:
- TestUTLSInsecure: regression for go-gost/gost#887. A utls
dialer with `secure: false` must still complete the handshake
(InsecureSkipVerify must be honoured). The old unsafe cast read
garbage for InsecureSkipVerify and the handshake failed.
- TestUTLSSecureWithCA: exercises the converter's RootCAs /
ServerName path with a CA-signed server cert.
Uses the deterministic `Chrome` fingerprint (not `randomized`, which
randomises the ClientHello and is flaky against a standard Go TLS
server).
Bumps github.com/go-gost/x to v0.13.11, which fixes the
second half of #887: the curve-preference enum divergence between
crypto/tls and utls (Go 1.24+ appends PQC hybrid curves that
utls does not define).
Related: go-gost/gost#887, go-gost/x#111, go-gost/x#112
End-to-End Tests
Integration tests that spin up real gost instances inside Docker containers and verify protocol behavior over the network.
Prerequisites
- Docker (running daemon)
- Go toolchain (for compiling the gost binary under test)
Running
From the repository root:
# Run all e2e tests
go test ./tests/e2e/ -v -timeout 10m
# Run a specific test suite
go test ./tests/e2e/ -v -run TestShadowsocksSuite -timeout 5m
go test ./tests/e2e/ -v -run TestParallelSelectorSuite -timeout 5m
# Use a pre-built gost binary (skips compilation)
go test ./tests/e2e/ -v -gost-bin /path/to/gost
Architecture
tests/e2e/
├── Dockerfile # Shared base image (Alpine + curl, python3, etc.)
├── main_test.go # TestMain: compiles gost, creates Docker network
├── utils.go # Helpers: container lifecycle, config rendering
├── scripts/
│ ├── tcp_echo.py # HTTP echo server (responds with "hello-gost")
│ └── udp_echo.py # UDP echo server (reflects payloads)
├── testdata/ # config files or data files for running cases
├── shadowsocks_test.go # Shadowsocks protocol tests
└── parallel_selector_test.go # Parallel node selector tests
How it works
- TestMain (
main_test.go) compiles the gost binary from../../cmd/gost(unless-gost-binis provided) and creates a shared Docker network for all containers. - Each test suite starts echo server containers (TCP/UDP), then launches separate gost containers for server and client roles.
- Client configs use Go template syntax (
{{.ServerAddr}}) so the server address is injected at runtime. - Tests verify end-to-end connectivity by sending traffic through the gost proxy chain and checking that the echo server responds correctly.
Tips
- Increase
-timeoutfor CI or slow networks. Container image builds on first run take extra time. - Use
-gost-binto avoid recompiling when iterating on tests locally. - Add
-vto see container log output on failure. - RunGostContainer will wait for exposedPorts automatically, but it's not reliable for udp ports. So, you should check the readiness of udp ports inside cases.