Skip to content

Files

Latest commit

 

History

History

tests

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
testdata
testdata
 
 
README.md
README.md
 
 
basic_test.go
basic_test.go
 
 
build_cover.sh
build_cover.sh
 
 
conn.go
conn.go
 
 
cover_test.go
cover_test.go
 
 
dovecot_sasl_test.go
dovecot_sasl_test.go
 
 
dovecot_sasld_test.go
dovecot_sasld_test.go
 
 
gocovcat.go
gocovcat.go
 
 
golangci-noisy.yml
golangci-noisy.yml
 
 
imap_test.go
imap_test.go
 
 
imapsql_test.go
imapsql_test.go
 
 
issue327_test.go
issue327_test.go
 
 
limits_test.go
limits_test.go
 
 
lmtp_test.go
lmtp_test.go
 
 
mta_test.go
mta_test.go
 
 
multiple_domains_test.go
multiple_domains_test.go
 
 
replace_addr_test.go
replace_addr_test.go
 
 
run.sh
run.sh
 
 
smtp_autobuffer_test.go
smtp_autobuffer_test.go
 
 
smtp_test.go
smtp_test.go
 
 
stress_test.go
stress_test.go
 
 
t.go
t.go
 
 

README.md

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.