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.

2 files changed, 6 insertions, 1 deletions

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<QByteArrayList>();
+    //Load the capabilities
+    resource = Store::readOne<Sink::ApplicationDomain::SinkResource>(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::ApplicationDomain::SinkResource>(Sink::Query{resource});
     mCapabilities = resource.getCapabilities();
 }