From 7bd037fae43c963d5f67e9447b3ee6875591a2c7 Mon Sep 17 00:00:00 2001 From: Christian Mollekopf Date: Thu, 15 Dec 2016 17:26:59 +0100 Subject: Don't set capabilities as property on creation. Instead we make it part of the plugin. This ensure we also have access to the proper capabilities when creating a resource via sinksh. --- tests/mailsynctest.cpp | 4 +++- tests/mailtest.cpp | 3 +++ 2 files changed, 6 insertions(+), 1 deletion(-) (limited to 'tests') diff --git a/tests/mailsynctest.cpp b/tests/mailsynctest.cpp index 6658d8b..31e40c4 100644 --- a/tests/mailsynctest.cpp +++ b/tests/mailsynctest.cpp @@ -46,7 +46,9 @@ void MailSyncTest::initTestCase() VERIFYEXEC(Store::create(resource)); mResourceInstanceIdentifier = resource.identifier(); - mCapabilities = resource.getProperty("capabilities").value(); + //Load the capabilities + resource = Store::readOne(Sink::Query{resource}); + mCapabilities = resource.getCapabilities(); } void MailSyncTest::cleanup() diff --git a/tests/mailtest.cpp b/tests/mailtest.cpp index ae5295e..fe28cde 100644 --- a/tests/mailtest.cpp +++ b/tests/mailtest.cpp @@ -45,6 +45,9 @@ void MailTest::initTestCase() VERIFYEXEC(Store::create(resource)); mResourceInstanceIdentifier = resource.identifier(); + + //Load the capabilities + resource = Store::readOne(Sink::Query{resource}); mCapabilities = resource.getCapabilities(); } -- cgit v1.2.3