| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/276
|
| |
|
|
|
|
|
|
| |
This can be used by code which doesn't need to use an ECalComponent
wrapper just to get to the categories.
The change also sanitizes the categories by removing trailing white-spaces
and ignores empty strings.
|
| |
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/-/merge_requests/106
|
| |
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/421
|
| |
|
|
|
|
| |
This helps to read properties related only to certain language/locale.
Related to https://gitlab.gnome.org/GNOME/evolution/-/issues/876
|
| |
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/393
|
| |
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/391
|
| |
|
|
|
|
| |
These are available only on certain component types, thus test for it.
Let the getters return NULL silently, but warn when the setter is used
with an invalid component type (though still allow to do it).
|
| |
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/371
|
| |
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/-/merge_requests/84
|
| |
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/366
|
| |
|
|
|
|
| |
The `g_assert()` can be disabled by `G_DISABLE_ASSERT` when compiling,
which is not desired for the unit tests, thus use the `g_assert_true()`
in the tests instead.
|
| |
|
|
| |
Related to https://gitlab.gnome.org/GNOME/evolution/-/issues/1639
|
| |
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/-/merge_requests/72
|
| |
|
|
|
|
|
| |
Let it use the global main loop, to avoid stale GSource-s being
lost in the private context scheduled by GDBus, which could cause
a crash due to the GDBusConnection not being finalized at the end
of the test.
|
| |
|
|
|
|
| |
Turn off the sub-test, because different libphonenumber behaves
differently. Having a (runtime) way to check the libphonenumber version
it could be adapted in a better way.
|
| |
|
|
|
|
|
|
| |
The ECalComponent needs to read/write the range kind, thus it's preserved.
The backends need to read the kind and update the local components properly,
when an update of the component is received.
Related to https://gitlab.gnome.org/GNOME/evolution/-/issues/1527
|
| |
|
|
|
| |
There had been some issues with the compare code, which could match
two href-s, which were not equal.
|
| |
|
|
|
|
| |
Run old book migration tests from the Berkeley DB databases only if
being compiled with libdb, otherwise there is not done any migration
and the tests fail.
|
| |
|
|
|
|
|
| |
A new stable version of libical (3.10) can change order or values
in the RRULE string representation, which breaks the test. Rather
than special-case the test according to libical version change
the way the timezone component is compared.
|
| |
|
|
|
|
|
|
| |
This broke with commit 0394a3bd9cd0b0cbf3a9bc1eac70f5a4849f6df6 for the file
backend, because the EContact's e_contact_inline_local_photos() could not
decipher the original MIME type from the file extension.
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/309
|
| |
|
|
| |
Related to https://gitlab.gnome.org/GNOME/evolution-ews/-/issues/144
|
| | |
|
| |
|
|
|
| |
Can be used to limit the data transfer for simple events where
the whole history of the timezone shifts doesn't matter.
|
| |
|
|
|
|
| |
The g_main_loop_quit() can continue its execution, in contrast
to what the code needed. It stroke when running the test under
valgrind, thus when things were slowed down significantly.
|
| |
|
|
|
|
|
|
| |
Touches the 'file' and the 'CalDAV' backends, storing the current time
when the reminder had been dismissed. The reminder watcher ignores
any reminders, which are scheduled before the acknowledged time.
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/295
|
| |
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/-/merge_requests/65
|
| |
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/282
|
| |
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/-/merge_requests/53
|
| |
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/272
|
| |
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/260
|
| |
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/254
|
| |
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/-/merge_requests/43
|
| |
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-ews/issues/87
|
| |
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/194
|
| |
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/162
|
| |
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/148
|
| |
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/136
|
| |
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/142
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Calling “x = g_string_append (x, y)” is equivalent to
“g_string (x, y)”. Or take it into account, when this leads
to shorter code.
Likewise for g_string_append_unichar().
Use the return value fo g_string_append(), when this makes
the code sherter.
In camel_content_disposition_format: skip a realloc() call.
In camel-sasl-ntlm.c: skip a g_string_append_len() call.
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/22
|
| |
|
|
|
|
|
| |
Even with the previous commit there still could happen some issue
with D-Bus property change notifications, thus add a workaround to
the related book and calendar tests, because it's not a problem
on the evolution-data-server side, but somewhere deeper.
|
| |
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/117
|
| | |
|
| |
|
|
|
| |
Related to https://gitlab.gnome.org/GNOME/evolution-data-server/issues/83
and https://gitlab.gnome.org/GNOME/evolution-data-server/issues/85
|
| |
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/33
|
| |
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/91
|
| |
|
|
|
|
|
| |
This will make sure the required databases are available before
the migration test itself is built, which is not strictly necessary
for the test build, but it also doesn't hurt and makes the dependency
explicit.
|
| |
|
|
| |
Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/61
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Couple changes in the test:
1) add also a component into the calendar, thus the returned
Free/Busy component is not empty
2) let the sync variant wait for the D-Bus signal with Free/Busy
data again
3) wait for the D-Bus signal in case it's not received in time
of the method execution finish.
Especially the 3) is important, because the D-Bus signal can be delivered
after the method invocation is received, which could break the test.
|
| |
|
|
|
|
| |
The test could fail when creating the instance, not when opening it,
thus retry also when the instance creation fails. Left the code
for the open() too, just in case.
|