History

Michael Gratton cddbb28a43 Add initial integration test famework and IMAP client session tests		2019-03-31 02:05:14 +11:00
..
client	Constructors of abstract classes should not be public	2019-03-15 09:49:05 +11:00
data	Add a unit test for upgrading an actual Geary v0.6 database.	2018-05-19 14:55:19 +10:00
engine	Clean up protocol date handling substantially	2019-03-23 15:21:18 +11:00
integration/imap	Add initial integration test famework and IMAP client session tests	2019-03-31 02:05:14 +11:00
js	Fix signature not being updated when composer first opened without one	2019-03-11 12:19:57 +11:00
meson.build	Add initial integration test famework and IMAP client session tests	2019-03-31 02:05:14 +11:00
mock-object.vala	Add a mock object mixin that can check call expectations on mocks.	2018-04-07 10:02:18 +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	Attempt to de-mangle From names from Mailman, GitLab, etc	2019-03-09 20:17:01 +11:00
test-engine.vala	Work around DB tests always failing on gcc150.osuosl.org CI runner	2019-02-19 17:12:26 +11:00
test-integration.vala	Add initial integration test famework and IMAP client session tests	2019-03-31 02:05:14 +11: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.