History

Michael Gratton 0c563cf101 Fix ContactStoreImpl not saving flags removed from a contact Don't try to merge contacts, just assume the updated contact passed in is canonical.		2019-10-25 14:53:59 +11:00
..
client	build: Set up dual install for flatpak	2019-08-26 09:38:31 -07:00
data	TNEF (winmail.dat) parsing support via libytnef	2019-04-11 12:24:52 +03:00
engine	Fix ContactStoreImpl not saving flags removed from a contact	2019-10-25 14:53:59 +11:00
integration	Rename UNCONNECTED FSM and protocol state to NOT_CONNECTED	2019-08-26 13:55:43 +10:00
js	Fix ComposerPageState::containsAttachmentKeyword	2019-10-07 23:49:12 +11:00
meson.build	Consistently use '..._c_args' and '..._vala_args' for meson vars	2019-09-27 23:56:52 +10:00
mock-object.vala	Add support for uint args in expected calls in MockObject	2019-06-13 16:31:26 +10:00
README.md	Add initial integration test famework and IMAP client session tests	2019-03-31 02:05:14 +11:00
test-case.vala	Add TestCase.async_complete_full method to avoid requiring a lambda	2019-03-31 01:29:52 +11:00
test-client.vala	Remove Flatpak test locale hack, just use en_US.UTF-8 for now	2019-10-16 13:36:29 +11:00
test-engine.vala	Remove Flatpak test locale hack, just use en_US.UTF-8 for now	2019-10-16 13:36:29 +11:00
test-integration.vala	Switch to using GLib structured logging	2019-06-30 16:15:03 +10:00

README.md

Automated Test Infrastructure

Geary currently supports three types of automated tests:

Engine unit tests
Client (GTK and JavaScript) unit tests
Server integration tests

Unit tests

Unit tests test individual functions, in general avoid doing any I/O so they are fast, and can be run automatically.

The engine and client unit tests are hooked up to the Meson build, so you can use Meson's test infrastructure to build and run them. These are run automatically as part of the Gitlab CI process and if you use the development Makefile, you can execute them locally by simply calling:

make test

The engine tests can be run headless (i.e. without an X11 or Wayland session), but the client tests require a functioning display since they execute GTK code.

Integration tests

Integration tests run Geary's network code against actual servers, to ensure that the code also works in the real world.

The integration tests are built by default, but not currently hooked up to Meson and are not automatically run by Gitlab CI, since they require multiple working servers, network connection to the servers, and login credentials.

You can run them manually however against any server you have a test account on, using the following form:

build/test/test-integration PROTOCOL PROVIDER [HOSTNAME] LOGIN PASSWORD

For example, to test against GMail's IMAP service:

build/test/test-integration imap gmail test@gmail.com p455w04d

If PROVIDER is other, then HOSTNAME is required.

The easiest way to test against a number of different servers at the moment is to create a test account for each, then write a shell script or similar to execute the tests against each in turn.