Akonadi: disable testing of iCalendar 2.0 semantic

Akonadi and Akonadi resources do not enforce iCalendar 2.0 semantic
like "UID+RECURRENCE-ID must be unique in a collection". Therefore we
must disable all tests expecting that behavior.

Regular syncing should work okay as long as the peer behaves. A misbehaving
peer will be able to send us invalid sets of items and syncing will not be
able to detect that because the sync engine itself is also agnostic to the
special iCalendar 2.0 semantic.

See "[Kde-pim] iCalendar semantic".
This commit is contained in:
Patrick Ohly 2014-03-19 06:04:51 -07:00
parent 05c5d53627
commit b97dddc4b2
1 changed files with 9 additions and 0 deletions

View File

@ -365,6 +365,13 @@ public:
virtual void updateConfig(ClientTestConfig &config) const
{
config.m_type = "kde-calendar";
// Looks like iCalendar file resource in Akonadi 1.11.0 does
// not actually enforce iCalendar 2.0 semantic. It allows
// updating of events with no UID
// (testLinkedItemsInsertBothUpdateChildNoIDs)
// and fails to detect double-adds (testInsertTwice).
// TODO: this should better be fixed.
config.m_sourceKnowsItemSemantic = false;
}
} iCal20Test;
@ -375,6 +382,8 @@ public:
virtual void updateConfig(ClientTestConfig &config) const
{
config.m_type = "kde-tasks";
// See above.
config.m_sourceKnowsItemSemantic = false;
}
} iTodo20Test;