Skip to content

Latest commit

 

History

History

tests

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
_features
_features
 
 
e2e/ui_tests/windows_os
e2e/ui_tests/windows_os
 
 
features
features
 
 
testdata
testdata
 
 
utils/gmail
utils/gmail
 
 
README.md
README.md
 
 
api_test.go
api_test.go
 
 
bdd_test.go
bdd_test.go
 
 
bridge_test.go
bridge_test.go
 
 
collector_test.go
collector_test.go
 
 
contact_test.go
contact_test.go
 
 
ctx_bridge_test.go
ctx_bridge_test.go
 
 
ctx_heartbeat_test.go
ctx_heartbeat_test.go
 
 
ctx_helper_test.go
ctx_helper_test.go
 
 
ctx_imap_test.go
ctx_imap_test.go
 
 
ctx_reporter_test.go
ctx_reporter_test.go
 
 
ctx_smtp_test.go
ctx_smtp_test.go
 
 
ctx_test.go
ctx_test.go
 
 
diff.go
diff.go
 
 
diff_test.go
diff_test.go
 
 
environment_test.go
environment_test.go
 
 
external_test.go
external_test.go
 
 
fast.go
fast.go
 
 
frontend_test.go
frontend_test.go
 
 
heartbeat_test.go
heartbeat_test.go
 
 
imap_test.go
imap_test.go
 
 
main_test.go
main_test.go
 
 
observability_test.go
observability_test.go
 
 
smtp_test.go
smtp_test.go
 
 
steps_test.go
steps_test.go
 
 
types_test.go
types_test.go
 
 
user_test.go
user_test.go
 
 

README.md

Bridge Integration tests

Tests defined in this folder are using github.com/cucumber/godog library to define scenarios.

The scenarios are defined in ./features/ folder. The step definition can be found in ./steps_test.go.

How to run

All features are run as sub-test of TestFeatures in ./bdd_test.go. The most simple way to execute is make test-integration from project source directory.

There are several environment variables which can be used to control the tests:

  • FEATURES sets the path to folder / file / line in file to select which scenarios to run.

      FEATURES=${PWD}/tests/features/user/addressmode.feature:162

  • FEATURE_TEST_LOG_LEVEL the logrus level for tests (affects also testing bridge instance)

      FEATURE_TEST_LOG_LEVEL=trace

  • BRIDGE_API_DEBUG when enabled GPA client used in testing bridge instance will log http communication and logrus is automatically set to trace

      BRIDGE_API_DEBUG=1

  • GO_PROTON_API_SERVER_LOGGER_ENABLED GPA mock server will print log line per each request to stdout (not logrus)

      GO_PROTON_API_SERVER_LOGGER_ENABLED=1

  • FEATURE_API_DEBUG when enabled GPA client for preparation of test condiditions (see ./ctx_helper_test.go) will dump http communication to stdoout.

      FEATURE_API_DEBUG=1

  • FEATURE_TEST_LOG_IMAP when enabled bridge will dump all (client and server) IMAP communication to logs and logrus is automatically set to trace

      FEATURE_TEST_LOG_IMAP=1

  • GLUON_LOG_IMAP_LINE_LIMIT controls maximal number of lines (by default 1) which are printed into imap trace log (logrus). Needs FEATURE_TEST_LOG_IMAP enabled to take effect.

      GLUON_LOG_IMAP_LINE_LIMIT=1048576

  • FEATURE_TEST_LOG_SMTP when enabled bridge will dump all SMTP communication to logs and logrus is automatically set to trace

      FEATURE_TEST_LOG_SMTP=1