maddy/tests
2025-09-05 16:54:41 +02:00
..
testdata first commit 2025-09-05 16:54:41 +02:00
basic_test.go first commit 2025-09-05 16:54:41 +02:00
build_cover.sh first commit 2025-09-05 16:54:41 +02:00
conn.go first commit 2025-09-05 16:54:41 +02:00
cover_test.go first commit 2025-09-05 16:54:41 +02:00
dovecot_sasl_test.go first commit 2025-09-05 16:54:41 +02:00
dovecot_sasld_test.go first commit 2025-09-05 16:54:41 +02:00
gocovcat.go first commit 2025-09-05 16:54:41 +02:00
golangci-noisy.yml first commit 2025-09-05 16:54:41 +02:00
imap_test.go first commit 2025-09-05 16:54:41 +02:00
imapsql_test.go first commit 2025-09-05 16:54:41 +02:00
issue327_test.go first commit 2025-09-05 16:54:41 +02:00
limits_test.go first commit 2025-09-05 16:54:41 +02:00
lmtp_test.go first commit 2025-09-05 16:54:41 +02:00
mta_test.go first commit 2025-09-05 16:54:41 +02:00
multiple_domains_test.go first commit 2025-09-05 16:54:41 +02:00
README.md first commit 2025-09-05 16:54:41 +02:00
replace_addr_test.go first commit 2025-09-05 16:54:41 +02:00
run.sh first commit 2025-09-05 16:54:41 +02:00
smtp_autobuffer_test.go first commit 2025-09-05 16:54:41 +02:00
smtp_test.go first commit 2025-09-05 16:54:41 +02:00
stress_test.go first commit 2025-09-05 16:54:41 +02:00
t.go first commit 2025-09-05 16:54:41 +02:00

maddy integration testing

Tests structure

The test library creates a temporary state and runtime directory, starts the server with the specified configuration file and lets you interact with it using a couple of convenient wrappers.

Running

To run tests, use go test -tags integration in this directory. Make sure to have a maddy executable in the current working directory. Use -integration.executable if the executable is named different or is placed somewhere else. Use -integration.coverprofile to pass -test.coverprofile your_value.RANDOM to test executable. See ./build_cover.sh to build a server executable instrumented with coverage counters.