[Kde-pim] akonadi testing framework

[Kevin Krammer]

On Thursday 01 May 2008, Igor Trindade Oliveira wrote:

> And i am right now doing a requirement analysis to see
> what the testing framework need to do.
> So i am asking for you, when you are testing your
> agents/resources what are the steps done by you?

I'll start then.

Requirement:
a test should by default be self contained, i.e. must not affect another 
Akonadi setup

Use case:
have an archived test case, e.g. a .zip file, and just have to unzip, change 
into that directory and run a script

Subrequirements:
- setup of environment variables for Akonadi directories
- setup of agent/resource related directories, e.g. KDEHOME for KDE based ones
- setup of separate D-Bus session bus
- restoring of a specific Akonadi state, e.g. import of a database dump
====

Requirement:
perform checks on Akonadi state, e.g. number of collections, number of items 
in collections

Use cases:
- checking that the inital setup is actually valid to start the test
- checking that a test end state is as expected
====

Requirement:
perform manipulations of the Akonadi state, e.g. modify an item

Use cases:
- simulating resource backend changes when testing clients
- simulating client changes when testing resources

Subrequirements:
- create, modify, delete collections
- create, modify, delete items
====

Anyone else having additional requirements, or details to the one above?

Cheers,
Kevin

-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20080506/7809deea/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/