nettika/geary
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
geary/test/test-engine.vala

113 lines
4.6 KiB
Vala
Raw Normal View History

Basic unit test build configuration.
2016-12-12 22:47:53 +11:00
/*
Add unit test for IMAP FETCH command constructor.
2018-07-26 11:25:35 +10:00
* Copyright 2016-2018 Michael Gratton <mike@vee.net>
Basic unit test build configuration.
2016-12-12 22:47:53 +11:00
*
* This software is licensed under the GNU Lesser General Public License
* (version 2.1 or later). See the COPYING file in this distribution.
*/
Add an initial/example unit test.
2016-12-12 23:39:46 +11:00
int main(string[] args) {
Add client lib to the test build. * test/CMakeLists.txt: Add client lib and dependent packages to the build. * test/main.vala (main): Add test suites for both client and engine tests to allow some more fine-grained control when running them. Also add some sectioning doc comments.
2016-12-26 13:18:51 +10:30
/*
* Initialise all the things.
*/
migrate locale from en_US.UTF-8 to C.UTF-8
2025-07-02 14:32:07 +02:00
GLib.Intl.setlocale(LocaleCategory.ALL, "C.UTF-8");
Fix engine test failure under flatpak Geary.ImapDb.Database/utf8_case_insensitive_collation depends on a well known UTF-8 collation order, but distros only ship C.UTF-8 by default and Flatpak doesn't ship that, so support en_US.UTF-8 as a fallback. See https://gitlab.com/freedesktop-sdk/freedesktop-sdk/issues/812
2019-06-24 21:00:51 +10:00
Test.init(ref args);
Ensure test drivers all have sane locales set
2019-06-22 14:08:03 +10:00
Fix HTML, CSS and JS leaking into conversation list preview. Bug 714317 When generating the preview, only the first 128 bytes of the first MIME part is fetched and used. If this part is text/html with a significant amount of embedded CSS, then there is a good chance the string passed to Geary.HTML::remove_html_tags() will be invalid, or be missing closing elements. Since that function uses regexes that require balanced tags to remove script and style blocks, then it was very possible that in these cases this method will miss removing these blocks. To solve this, remove_html_tags() is removed and its call sites are replaced by calls to Geary.HTML::html_to_text(), which has been tidyied up to produce more human-readable result. Add unit tests to cover new html_to_text functionality and its call sites. * src/engine/util/util-html.vala: Remove remove_html_tags(). Update html_to_text() to not just insert line breaks, but also insert spaces and alt text, and ignore tags like HEAD, SCRIPT and STYLE, as appropriate. Add an optional param to also allow skipping BLOCKQUOTE elements, which we don't want in the preview.
2016-12-18 23:28:53 +11:00
Geary.RFC822.init();
Geary.HTML.init();
Fix JS error getting F=F text from ComposerWebView. Add JS unit tests. * ui/composer-web-view.js (ComposerPageState::resolveNesting): Apply JS RegExp globally, to match default GLib RegEx behaviour. * test/js/composer-page-state-test.vala: New tests covering generation of HTML and F=F text from JS ComposerPageState object. * test/CMakeLists.txt: Add the new test. * test/main.vala (main): Add a test suite for JS tests, add the new test to it. * src/client/components/client-web-view.vala (ClientWebView): Add a reason to the JSError domain for when a JS exception is thrown. * bindings/vapi/javascriptcore-4.0.vapi (JS::Context): Add JS.Type and some additional methods needed for the unit tests. Move most GlobalContext methods to Context so we can pass the lowest common demominator around.
2017-01-01 12:37:08 +11:00
Geary.Logging.init();
test: Enable engine logging if test harness verbose flag is set
2020-04-10 14:31:41 +10:00
if (GLib.Test.verbose()) {
GLib.Log.set_writer_func(Geary.Logging.default_log_writer);
Geary.Logging.log_to(GLib.stdout);
}
Fix HTML, CSS and JS leaking into conversation list preview. Bug 714317 When generating the preview, only the first 128 bytes of the first MIME part is fetched and used. If this part is text/html with a significant amount of embedded CSS, then there is a good chance the string passed to Geary.HTML::remove_html_tags() will be invalid, or be missing closing elements. Since that function uses regexes that require balanced tags to remove script and style blocks, then it was very possible that in these cases this method will miss removing these blocks. To solve this, remove_html_tags() is removed and its call sites are replaced by calls to Geary.HTML::html_to_text(), which has been tidyied up to produce more human-readable result. Add unit tests to cover new html_to_text functionality and its call sites. * src/engine/util/util-html.vala: Remove remove_html_tags(). Update html_to_text() to not just insert line breaks, but also insert spaces and alt text, and ignore tags like HEAD, SCRIPT and STYLE, as appropriate. Add an optional param to also allow skipping BLOCKQUOTE elements, which we don't want in the preview.
2016-12-18 23:28:53 +11:00
Add client lib to the test build. * test/CMakeLists.txt: Add client lib and dependent packages to the build. * test/main.vala (main): Add test suites for both client and engine tests to allow some more fine-grained control when running them. Also add some sectioning doc comments.
2016-12-26 13:18:51 +10:30
/*
* Hook up all tests into appropriate suites
*/
TestSuite engine = new TestSuite("engine");
Add an initial/example unit test.
2016-12-12 23:39:46 +11:00
Adapt vala-unit and tests to GLib 2.70 and later `GLib.TestSuite` is a special type of object, as it doesn't actually have an associated copy function or a reference/unreference function. In practice, that actually means there's no way to actually have 2 strong references to such an object, or to copy it somehow. Due to the way GObject properties in Vala work, that means you can't really use them either. Ever since vala commit 5f0a146f65, this got reflected properly in the internally maintained GLib VAPI (as people were experiencing double frees otherwise), but it was added only conditionally for GLib 2.70 or later. In practice, that means you only get vala compiler issues if you (impliclty) set `--target-glib=2.70` (or a later version). To fix this for vala-unit and our own Geary tests, this commit changes the `ValaUnit.TestCase` class to only allow "stealing" the strong reference to the `GLib.TestSuite`, rather than somehowing allowing people to hold a weak reference, and by also making it a protected field rather than a property. Since this changes the API of ValaUnit, we also bump the version. In general though, I hope people aren't using ValaUnit externally, since these types of API/ABI breaks can happen with Vala libraries. Link: https://gitlab.gnome.org/GNOME/vala/-/commit/5f0a146f65673379fc84c3cd8e6bca826ffad96f
2025-12-07 10:09:15 +01:00
engine.add_suite(new Geary.AccountInformationTest().steal_suite());
engine.add_suite(new Geary.AttachmentTest().steal_suite());
engine.add_suite(new Geary.ContactHarvesterImplTest().steal_suite());
engine.add_suite(new Geary.EngineTest().steal_suite());
engine.add_suite(new Geary.FolderPathTest().steal_suite());
engine.add_suite(new Geary.IdleManagerTest().steal_suite());
engine.add_suite(new Geary.TimeoutManagerTest().steal_suite());
engine.add_suite(new Geary.TlsNegotiationMethodTest().steal_suite());
engine.add_suite(new Geary.App.ConversationTest().steal_suite());
engine.add_suite(new Geary.App.ConversationSetTest().steal_suite());
Add unit tests for ConversationMonitor, fix a few issues. * src/engine/app/app-conversation-monitor.vala (ConversationMonitor): Don't check the folder blacklist for external folder signals when the signal is received, do it when the operation is executed so it's fresh. * src/engine/app/conversation-monitor/app-fill-window-operation.vala (FillWindowOperation): Only re-fill the conversation if we get a full load, anything else means we hit the end of the folder. * test/engine/app/app-conversation-monitor-test.vala: New unit tests for ConversationMonitor. * test/engine/api/geary-account-mock.vala, test/engine/api/geary-folder-mock.vala: Mix in MockObject mock up all method calls. * test/engine/api/geary-email-identifier-mock.vala: Fix the comparator method when the other instance is null.
2018-04-04 15:58:44 +10:00
// Depends on ConversationTest and ConversationSetTest passing
Adapt vala-unit and tests to GLib 2.70 and later `GLib.TestSuite` is a special type of object, as it doesn't actually have an associated copy function or a reference/unreference function. In practice, that actually means there's no way to actually have 2 strong references to such an object, or to copy it somehow. Due to the way GObject properties in Vala work, that means you can't really use them either. Ever since vala commit 5f0a146f65, this got reflected properly in the internally maintained GLib VAPI (as people were experiencing double frees otherwise), but it was added only conditionally for GLib 2.70 or later. In practice, that means you only get vala compiler issues if you (impliclty) set `--target-glib=2.70` (or a later version). To fix this for vala-unit and our own Geary tests, this commit changes the `ValaUnit.TestCase` class to only allow "stealing" the strong reference to the `GLib.TestSuite`, rather than somehowing allowing people to hold a weak reference, and by also making it a protected field rather than a property. Since this changes the API of ValaUnit, we also bump the version. In general though, I hope people aren't using ValaUnit externally, since these types of API/ABI breaks can happen with Vala libraries. Link: https://gitlab.gnome.org/GNOME/vala/-/commit/5f0a146f65673379fc84c3cd8e6bca826ffad96f
2025-12-07 10:09:15 +01:00
engine.add_suite(new Geary.App.ConversationMonitorTest().steal_suite());
engine.add_suite(new Geary.Ascii.Test().steal_suite());
engine.add_suite(new Geary.ConfigFileTest().steal_suite());
engine.add_suite(new Geary.Db.DatabaseTest().steal_suite());
engine.add_suite(new Geary.Db.VersionedDatabaseTest().steal_suite());
engine.add_suite(new Geary.HTML.UtilTest().steal_suite());
Add unit test for Geary.Imap.ClientConnection
2019-12-29 01:56:48 +10:30
// Other IMAP tests rely on these working, so test them first
Adapt vala-unit and tests to GLib 2.70 and later `GLib.TestSuite` is a special type of object, as it doesn't actually have an associated copy function or a reference/unreference function. In practice, that actually means there's no way to actually have 2 strong references to such an object, or to copy it somehow. Due to the way GObject properties in Vala work, that means you can't really use them either. Ever since vala commit 5f0a146f65, this got reflected properly in the internally maintained GLib VAPI (as people were experiencing double frees otherwise), but it was added only conditionally for GLib 2.70 or later. In practice, that means you only get vala compiler issues if you (impliclty) set `--target-glib=2.70` (or a later version). To fix this for vala-unit and our own Geary tests, this commit changes the `ValaUnit.TestCase` class to only allow "stealing" the strong reference to the `GLib.TestSuite`, rather than somehowing allowing people to hold a weak reference, and by also making it a protected field rather than a property. Since this changes the API of ValaUnit, we also bump the version. In general though, I hope people aren't using ValaUnit externally, since these types of API/ABI breaks can happen with Vala libraries. Link: https://gitlab.gnome.org/GNOME/vala/-/commit/5f0a146f65673379fc84c3cd8e6bca826ffad96f
2025-12-07 10:09:15 +01:00
engine.add_suite(new Geary.Imap.DataFormatTest().steal_suite());
Add unit test for Geary.Imap.ClientConnection
2019-12-29 01:56:48 +10:30
Adapt vala-unit and tests to GLib 2.70 and later `GLib.TestSuite` is a special type of object, as it doesn't actually have an associated copy function or a reference/unreference function. In practice, that actually means there's no way to actually have 2 strong references to such an object, or to copy it somehow. Due to the way GObject properties in Vala work, that means you can't really use them either. Ever since vala commit 5f0a146f65, this got reflected properly in the internally maintained GLib VAPI (as people were experiencing double frees otherwise), but it was added only conditionally for GLib 2.70 or later. In practice, that means you only get vala compiler issues if you (impliclty) set `--target-glib=2.70` (or a later version). To fix this for vala-unit and our own Geary tests, this commit changes the `ValaUnit.TestCase` class to only allow "stealing" the strong reference to the `GLib.TestSuite`, rather than somehowing allowing people to hold a weak reference, and by also making it a protected field rather than a property. Since this changes the API of ValaUnit, we also bump the version. In general though, I hope people aren't using ValaUnit externally, since these types of API/ABI breaks can happen with Vala libraries. Link: https://gitlab.gnome.org/GNOME/vala/-/commit/5f0a146f65673379fc84c3cd8e6bca826ffad96f
2025-12-07 10:09:15 +01:00
engine.add_suite(new Geary.Imap.CreateCommandTest().steal_suite());
engine.add_suite(new Geary.Imap.FetchCommandTest().steal_suite());
engine.add_suite(new Geary.Imap.FetchDataDecoderTest().steal_suite());
engine.add_suite(new Geary.Imap.ListParameterTest().steal_suite());
engine.add_suite(new Geary.Imap.MailboxSpecifierTest().steal_suite());
engine.add_suite(new Geary.Imap.NamespaceResponseTest().steal_suite());
Add unit test for Geary.Imap.ClientConnection
2019-12-29 01:56:48 +10:30
// Depends on IMAP commands working
Adapt vala-unit and tests to GLib 2.70 and later `GLib.TestSuite` is a special type of object, as it doesn't actually have an associated copy function or a reference/unreference function. In practice, that actually means there's no way to actually have 2 strong references to such an object, or to copy it somehow. Due to the way GObject properties in Vala work, that means you can't really use them either. Ever since vala commit 5f0a146f65, this got reflected properly in the internally maintained GLib VAPI (as people were experiencing double frees otherwise), but it was added only conditionally for GLib 2.70 or later. In practice, that means you only get vala compiler issues if you (impliclty) set `--target-glib=2.70` (or a later version). To fix this for vala-unit and our own Geary tests, this commit changes the `ValaUnit.TestCase` class to only allow "stealing" the strong reference to the `GLib.TestSuite`, rather than somehowing allowing people to hold a weak reference, and by also making it a protected field rather than a property. Since this changes the API of ValaUnit, we also bump the version. In general though, I hope people aren't using ValaUnit externally, since these types of API/ABI breaks can happen with Vala libraries. Link: https://gitlab.gnome.org/GNOME/vala/-/commit/5f0a146f65673379fc84c3cd8e6bca826ffad96f
2025-12-07 10:09:15 +01:00
engine.add_suite(new Geary.Imap.DeserializerTest().steal_suite());
engine.add_suite(new Geary.Imap.ClientConnectionTest().steal_suite());
engine.add_suite(new Geary.Imap.ClientSessionTest().steal_suite());
Add unit test for Geary.Imap.ClientConnection
2019-12-29 01:56:48 +10:30
Adapt vala-unit and tests to GLib 2.70 and later `GLib.TestSuite` is a special type of object, as it doesn't actually have an associated copy function or a reference/unreference function. In practice, that actually means there's no way to actually have 2 strong references to such an object, or to copy it somehow. Due to the way GObject properties in Vala work, that means you can't really use them either. Ever since vala commit 5f0a146f65, this got reflected properly in the internally maintained GLib VAPI (as people were experiencing double frees otherwise), but it was added only conditionally for GLib 2.70 or later. In practice, that means you only get vala compiler issues if you (impliclty) set `--target-glib=2.70` (or a later version). To fix this for vala-unit and our own Geary tests, this commit changes the `ValaUnit.TestCase` class to only allow "stealing" the strong reference to the `GLib.TestSuite`, rather than somehowing allowing people to hold a weak reference, and by also making it a protected field rather than a property. Since this changes the API of ValaUnit, we also bump the version. In general though, I hope people aren't using ValaUnit externally, since these types of API/ABI breaks can happen with Vala libraries. Link: https://gitlab.gnome.org/GNOME/vala/-/commit/5f0a146f65673379fc84c3cd8e6bca826ffad96f
2025-12-07 10:09:15 +01:00
engine.add_suite(new Geary.ImapDB.AccountTest().steal_suite());
engine.add_suite(new Geary.ImapDB.AttachmentTest().steal_suite());
engine.add_suite(new Geary.ImapDB.AttachmentIoTest().steal_suite());
engine.add_suite(new Geary.ImapDB.DatabaseTest().steal_suite());
engine.add_suite(new Geary.ImapDB.EmailIdentifierTest().steal_suite());
engine.add_suite(new Geary.ImapDB.FolderTest().steal_suite());
Geary.ImapDb.SearchQuery: Rename to Geary.FtsSearchQuery There's nothing IMAP-specific about the class, so move it to common and rename to reflect what it is actually used for.
2020-11-05 00:21:39 +11:00
// Depends on ImapDB working
Adapt vala-unit and tests to GLib 2.70 and later `GLib.TestSuite` is a special type of object, as it doesn't actually have an associated copy function or a reference/unreference function. In practice, that actually means there's no way to actually have 2 strong references to such an object, or to copy it somehow. Due to the way GObject properties in Vala work, that means you can't really use them either. Ever since vala commit 5f0a146f65, this got reflected properly in the internally maintained GLib VAPI (as people were experiencing double frees otherwise), but it was added only conditionally for GLib 2.70 or later. In practice, that means you only get vala compiler issues if you (impliclty) set `--target-glib=2.70` (or a later version). To fix this for vala-unit and our own Geary tests, this commit changes the `ValaUnit.TestCase` class to only allow "stealing" the strong reference to the `GLib.TestSuite`, rather than somehowing allowing people to hold a weak reference, and by also making it a protected field rather than a property. Since this changes the API of ValaUnit, we also bump the version. In general though, I hope people aren't using ValaUnit externally, since these types of API/ABI breaks can happen with Vala libraries. Link: https://gitlab.gnome.org/GNOME/vala/-/commit/5f0a146f65673379fc84c3cd8e6bca826ffad96f
2025-12-07 10:09:15 +01:00
engine.add_suite(new Geary.FtsSearchQueryTest().steal_suite());
Add unit test for Geary.Imap.ClientConnection
2019-12-29 01:56:48 +10:30
Adapt vala-unit and tests to GLib 2.70 and later `GLib.TestSuite` is a special type of object, as it doesn't actually have an associated copy function or a reference/unreference function. In practice, that actually means there's no way to actually have 2 strong references to such an object, or to copy it somehow. Due to the way GObject properties in Vala work, that means you can't really use them either. Ever since vala commit 5f0a146f65, this got reflected properly in the internally maintained GLib VAPI (as people were experiencing double frees otherwise), but it was added only conditionally for GLib 2.70 or later. In practice, that means you only get vala compiler issues if you (impliclty) set `--target-glib=2.70` (or a later version). To fix this for vala-unit and our own Geary tests, this commit changes the `ValaUnit.TestCase` class to only allow "stealing" the strong reference to the `GLib.TestSuite`, rather than somehowing allowing people to hold a weak reference, and by also making it a protected field rather than a property. Since this changes the API of ValaUnit, we also bump the version. In general though, I hope people aren't using ValaUnit externally, since these types of API/ABI breaks can happen with Vala libraries. Link: https://gitlab.gnome.org/GNOME/vala/-/commit/5f0a146f65673379fc84c3cd8e6bca826ffad96f
2025-12-07 10:09:15 +01:00
engine.add_suite(new Geary.ImapEngine.AccountProcessorTest().steal_suite());
engine.add_suite(new Geary.ImapEngine.GenericAccountTest().steal_suite());
ContactStoreImpl unit tests
2019-06-09 21:56:25 +10:00
// Depends on ImapDb.Database working correctly
Adapt vala-unit and tests to GLib 2.70 and later `GLib.TestSuite` is a special type of object, as it doesn't actually have an associated copy function or a reference/unreference function. In practice, that actually means there's no way to actually have 2 strong references to such an object, or to copy it somehow. Due to the way GObject properties in Vala work, that means you can't really use them either. Ever since vala commit 5f0a146f65, this got reflected properly in the internally maintained GLib VAPI (as people were experiencing double frees otherwise), but it was added only conditionally for GLib 2.70 or later. In practice, that means you only get vala compiler issues if you (impliclty) set `--target-glib=2.70` (or a later version). To fix this for vala-unit and our own Geary tests, this commit changes the `ValaUnit.TestCase` class to only allow "stealing" the strong reference to the `GLib.TestSuite`, rather than somehowing allowing people to hold a weak reference, and by also making it a protected field rather than a property. Since this changes the API of ValaUnit, we also bump the version. In general though, I hope people aren't using ValaUnit externally, since these types of API/ABI breaks can happen with Vala libraries. Link: https://gitlab.gnome.org/GNOME/vala/-/commit/5f0a146f65673379fc84c3cd8e6bca826ffad96f
2025-12-07 10:09:15 +01:00
engine.add_suite(new Geary.ContactStoreImplTest().steal_suite());
engine.add_suite(new Geary.Inet.Test().steal_suite());
engine.add_suite(new Geary.Mime.ContentTypeTest().steal_suite());
engine.add_suite(new Geary.Outbox.EmailIdentifierTest().steal_suite());
engine.add_suite(new Geary.RFC822.MailboxAddressTest().steal_suite());
engine.add_suite(new Geary.RFC822.MailboxAddressesTest().steal_suite());
engine.add_suite(new Geary.RFC822.MessageDataTest().steal_suite());
engine.add_suite(new Geary.RFC822.PartTest().steal_suite());
engine.add_suite(new Geary.RFC822.Utils.Test().steal_suite());
test/test-engine.vala: Minor test ordering improvement
2020-05-06 12:23:18 +10:00
// Message requires all of the rest of the package working, so put
// last
Adapt vala-unit and tests to GLib 2.70 and later `GLib.TestSuite` is a special type of object, as it doesn't actually have an associated copy function or a reference/unreference function. In practice, that actually means there's no way to actually have 2 strong references to such an object, or to copy it somehow. Due to the way GObject properties in Vala work, that means you can't really use them either. Ever since vala commit 5f0a146f65, this got reflected properly in the internally maintained GLib VAPI (as people were experiencing double frees otherwise), but it was added only conditionally for GLib 2.70 or later. In practice, that means you only get vala compiler issues if you (impliclty) set `--target-glib=2.70` (or a later version). To fix this for vala-unit and our own Geary tests, this commit changes the `ValaUnit.TestCase` class to only allow "stealing" the strong reference to the `GLib.TestSuite`, rather than somehowing allowing people to hold a weak reference, and by also making it a protected field rather than a property. Since this changes the API of ValaUnit, we also bump the version. In general though, I hope people aren't using ValaUnit externally, since these types of API/ABI breaks can happen with Vala libraries. Link: https://gitlab.gnome.org/GNOME/vala/-/commit/5f0a146f65673379fc84c3cd8e6bca826ffad96f
2025-12-07 10:09:15 +01:00
engine.add_suite(new Geary.RFC822.MessageTest().steal_suite());
engine.add_suite(new Geary.String.Test().steal_suite());
engine.add_suite(new Geary.EmailTest().steal_suite());
engine.add_suite(new Geary.ComposedEmailTest().steal_suite());
Add client lib to the test build. * test/CMakeLists.txt: Add client lib and dependent packages to the build. * test/main.vala (main): Add test suites for both client and engine tests to allow some more fine-grained control when running them. Also add some sectioning doc comments.
2016-12-26 13:18:51 +10:30
/*
* Run the tests
*/
Adapt vala-unit and tests to GLib 2.70 and later `GLib.TestSuite` is a special type of object, as it doesn't actually have an associated copy function or a reference/unreference function. In practice, that actually means there's no way to actually have 2 strong references to such an object, or to copy it somehow. Due to the way GObject properties in Vala work, that means you can't really use them either. Ever since vala commit 5f0a146f65, this got reflected properly in the internally maintained GLib VAPI (as people were experiencing double frees otherwise), but it was added only conditionally for GLib 2.70 or later. In practice, that means you only get vala compiler issues if you (impliclty) set `--target-glib=2.70` (or a later version). To fix this for vala-unit and our own Geary tests, this commit changes the `ValaUnit.TestCase` class to only allow "stealing" the strong reference to the `GLib.TestSuite`, rather than somehowing allowing people to hold a weak reference, and by also making it a protected field rather than a property. Since this changes the API of ValaUnit, we also bump the version. In general though, I hope people aren't using ValaUnit externally, since these types of API/ABI breaks can happen with Vala libraries. Link: https://gitlab.gnome.org/GNOME/vala/-/commit/5f0a146f65673379fc84c3cd8e6bca826ffad96f
2025-12-07 10:09:15 +01:00
unowned TestSuite root = TestSuite.get_root();
root.add_suite((owned) engine);
Split test running up into test-engine and test-client. This allows us to compile the engine tests against the internal VAPI, so we can unit test internal classes. * CMakeLists.txt: Add top-level targets test-engine-run and test-client-run that execute the respective test binaries. Make the tests target depend on them and make them depend on their binaries. * Makefile.in: Add test-client and test-engin targets for convenience. * src/CMakeLists.txt: Make the right invocation of valac to generate a correct geary-engine-internal.vapi. Make gsettings schema generation depend on geary-client so it exists for test-client if the main binary hasn't been built. * test/CMakeLists.txt: Split everything up into to builds, one for test-engine and the other for test-client. Use geary-engine-internal when building test-engine for access to internal classes and members. * test/engine/util-idle-manager-test.vala, test/engine/util-timeout-manager-test.vala: Use Glib MainContext rather than the GTK main loop for pumping events so the test cases compile without GTK. * test/test-engine.vala, test/test-client.vala: New main source file for test binaries based on old main.vala.
2017-11-23 09:35:51 +11:00
MainLoop loop = new MainLoop ();
Add an initial/example unit test.
2016-12-12 23:39:46 +11:00
Make GTK & async unit tests work by running them in a GTK+ main loop. Include GResources in the build so they can be loaded. Bug 776421. * test/main.vala (main): Init GTK, start a main loop and run the tests in that. * test/CMakeLists.txt: Include GResources in unit test binary so they can be loaded by tests, and since we can't compile them into the client static lib.
2016-12-31 14:49:38 +11:00
int ret = -1;
Idle.add(() => {
ret = Test.run();
Split test running up into test-engine and test-client. This allows us to compile the engine tests against the internal VAPI, so we can unit test internal classes. * CMakeLists.txt: Add top-level targets test-engine-run and test-client-run that execute the respective test binaries. Make the tests target depend on them and make them depend on their binaries. * Makefile.in: Add test-client and test-engin targets for convenience. * src/CMakeLists.txt: Make the right invocation of valac to generate a correct geary-engine-internal.vapi. Make gsettings schema generation depend on geary-client so it exists for test-client if the main binary hasn't been built. * test/CMakeLists.txt: Split everything up into to builds, one for test-engine and the other for test-client. Use geary-engine-internal when building test-engine for access to internal classes and members. * test/engine/util-idle-manager-test.vala, test/engine/util-timeout-manager-test.vala: Use Glib MainContext rather than the GTK main loop for pumping events so the test cases compile without GTK. * test/test-engine.vala, test/test-client.vala: New main source file for test binaries based on old main.vala.
2017-11-23 09:35:51 +11:00
loop.quit();
Make GTK & async unit tests work by running them in a GTK+ main loop. Include GResources in the build so they can be loaded. Bug 776421. * test/main.vala (main): Init GTK, start a main loop and run the tests in that. * test/CMakeLists.txt: Include GResources in unit test binary so they can be loaded by tests, and since we can't compile them into the client static lib.
2016-12-31 14:49:38 +11:00
return false;
});
Split test running up into test-engine and test-client. This allows us to compile the engine tests against the internal VAPI, so we can unit test internal classes. * CMakeLists.txt: Add top-level targets test-engine-run and test-client-run that execute the respective test binaries. Make the tests target depend on them and make them depend on their binaries. * Makefile.in: Add test-client and test-engin targets for convenience. * src/CMakeLists.txt: Make the right invocation of valac to generate a correct geary-engine-internal.vapi. Make gsettings schema generation depend on geary-client so it exists for test-client if the main binary hasn't been built. * test/CMakeLists.txt: Split everything up into to builds, one for test-engine and the other for test-client. Use geary-engine-internal when building test-engine for access to internal classes and members. * test/engine/util-idle-manager-test.vala, test/engine/util-timeout-manager-test.vala: Use Glib MainContext rather than the GTK main loop for pumping events so the test cases compile without GTK. * test/test-engine.vala, test/test-client.vala: New main source file for test binaries based on old main.vala.
2017-11-23 09:35:51 +11:00
loop.run();
Make GTK & async unit tests work by running them in a GTK+ main loop. Include GResources in the build so they can be loaded. Bug 776421. * test/main.vala (main): Init GTK, start a main loop and run the tests in that. * test/CMakeLists.txt: Include GResources in unit test binary so they can be loaded by tests, and since we can't compile them into the client static lib.
2016-12-31 14:49:38 +11:00
return ret;
Basic unit test build configuration.
2016-12-12 22:47:53 +11:00
}
Reference in a new issue Copy permalink