clash/test
Dreamacro 121bc910f6 Chore: adjust vmess 0rtt code and split xray test 2021-08-22 16:16:45 +08:00
..
config Test: add vmess ws 0-rtt test 2021-08-22 01:17:29 +08:00
README.md Chore: benchmark explanation 2021-07-22 00:01:11 +08:00
clash_test.go Chore: benchmark explanation 2021-07-22 00:01:11 +08:00
dns_test.go Feature: add protocol test 2021-05-17 20:33:00 +08:00
docker_test.go Test: add direct benchmark 2021-07-18 19:26:51 +08:00
go.mod Test: add vmess ws 0-rtt test 2021-08-22 01:17:29 +08:00
go.sum Test: add vmess ws 0-rtt test 2021-08-22 01:17:29 +08:00
snell_test.go Test: add basic protocol benchmark 2021-07-18 17:23:30 +08:00
ss_test.go Test: ss use aes-256-gcm and vmess-aead for benchmark 2021-07-18 17:37:23 +08:00
trojan_test.go Test: add basic protocol benchmark 2021-07-18 17:23:30 +08:00
util_darwin_test.go Test: add basic protocol benchmark 2021-07-18 17:23:30 +08:00
util_other_test.go Test: add basic protocol benchmark 2021-07-18 17:23:30 +08:00
vmess_test.go Chore: adjust vmess 0rtt code and split xray test 2021-08-22 16:16:45 +08:00

README.md

Clash testing suit

Protocol testing suit

  • TCP pingpong test
  • UDP pingpong test
  • TCP large data test
  • UDP large data test

Protocols

  • Shadowsocks
    • Normal
    • ObfsHTTP
    • ObfsTLS
    • ObfsV2rayPlugin
  • Vmess
    • Normal
    • AEAD
    • HTTP
    • HTTP2
    • TLS
    • Websocket
    • Websocket TLS
    • gRPC
  • Trojan
    • Normal
    • gRPC
  • Snell
    • Normal
    • ObfsHTTP
    • ObfsTLS

Features

  • DNS
    • DNS Server
    • FakeIP
    • Host

Command

Prerequisite

  • docker (support Linux and macOS)
$ go test -p 1 -v

benchmark (Linux)

Cannot represent the throughput of the protocol on your machine but you can compare the corresponding throughput of the protocol on clash (change chunkSize to measure the maximum throughput of clash on your machine)

$ go test -benchmem -run=^$ -bench .