Igor's GSoC project, found in kdepimlibs/akonadi/tests/testrunner.
Documentation based on Igor's mail to kde-pim ML:
First you need create a configuration file in KStandardDirs config resource type (try to use: kde4-config --path config, to find the path in my case the path is /usr/share/kde4/config) , the configuration file is a xml and look like:
<kdehome>/home/igor/kde/installs/trunk </kdehome> <confighome>/home/igor/codes/kde/tests/test_akonadi/</confighome> <datahome>/home/igor/codes/kde/tests/test_akonadi/data</datahome> <agent>akonadi_ical_resource</agent> <agent>akonadi_vcard_resource</agent> <item location="/path/to/file.vcf" collection="akonadi_vcard_resource_0"/>
After that you only needs to run the testrunner:
and it creates a shell script file in your current directory called testenvironment.sh and you just need to run it.
And right now you have a self contained Akonadi server.
In kdepim/akonadi/resources, fully featured resource that operates on a single XML file. File format is decribed in knut.xsd and follows closely the internal structure of Akonadi. New files can be created in eg. Akonadiconsole by creating a resource and specifying a non-existing file.
Second part of Igor's GSoC project, currently in playground/pim/akonaditest.
In kdepimlibs/akonadi/test, part of Robert's thesis.
Usable without installation, run with ctest/make test as usual.
Better coverage than the above, but require special setup that destroys the data of the database of the regular Akonadi server instance.
This needs porting to the Akonadi Testrunner, to avoid the aforementioned setup.
Are there any? TODO