summaryrefslogtreecommitdiffstats
path: root/tests/dummyresourcetest.cpp
Commit message (Collapse)AuthorAge
* Made the pipeline an implementation detail of the resource.Christian Mollekopf2015-07-30
| | | | | This removes one dependency from the Listener and will allow us to test the Listener better.
* Test generic stuff separately from the dummyresourceChristian Mollekopf2015-07-27
|
* Separate test debug output a littleChristian Mollekopf2015-07-23
|
* Pass command around as QByteArrayChristian Mollekopf2015-07-23
| | | | | | | Simpler api, GenericResource didn't honor size anyways, and we copy the command for now to avoid sideeffects of data coming in in the meantime (although that should generally work since data is always appended).
* Modify/Delete actionsChristian Mollekopf2015-07-19
|
* Create resource in dummyresourcetest as wellChristian Mollekopf2015-07-09
|
* Use the resource instance nameChristian Mollekopf2015-07-07
|
* An almost generic query implementation.Christian Mollekopf2015-06-17
| | | | With equality filter on arbitrary properties as a bonus.
* Differentiate between resource name and instance identifierChristian Mollekopf2015-06-08
|
* Use a queryrunner to execute queries.Christian Mollekopf2015-04-15
| | | | | | | | | | | | | | The queryrunner is responsible for running queries and keeping them up to date. This is required for self-updating queries. To get this to work properly the ResultProvider/emitter had to be fixed. The emitter now only lives as long as the client holds a reference to it, allowing the provider to detect when it is no longer necessary to keep the query alive (because noone is listening). In the process various lifetime issues have been fixed, that we're caused by lambdas capturing smartpointers, that then extended the lifetime of the associated objects unpredictably.
* Renamed Akonadi::Domain to Akonadi::ApplicationDomainChristian Mollekopf2015-04-09
| | | | Because it's really the application domain and not the akonadi domain.
* Shutdown command for synchronizers, used by the dummyresourcetest.Christian Mollekopf2015-01-30
| | | | | Otherwise the synchronizer keeps a Storage object alive, while the tests deletes the db. This causes subsequent writes to fail in the next test.
* debug output, fixed dummyresourcetestChristian Mollekopf2015-01-25
|
* A way to ensure all messages have been processed.Christian Mollekopf2015-01-25
| | | | | As queries become reactive this should become less important. We can then just wait until all results become available. For tests it is in either case useful though.
* Uid index + query using that index.Christian Mollekopf2015-01-24
| | | | ...and a couple of other fixes.
* Fixed sync, detect errors during sync, wait until sync items are processed ↵Christian Mollekopf2015-01-19
| | | | until signalling completion.
* Use jobs in queries, sync works again.Christian Mollekopf2015-01-18
|
* Async message queue processing.Christian Mollekopf2015-01-15
| | | | The Job/Future in Pipeline::newEntity for some reason crashes with async pipeline processing.
* Writing from facade.Christian Mollekopf2015-01-15
|
* Made the domain adaptor actually work. We can read stuff now.Christian Mollekopf2015-01-07
|
* More descriptive testname.Christian Mollekopf2014-12-29
|
* Buffers wrapped into entity buffer, async command progress tracking.Christian Mollekopf2014-12-28
|
* Write-Read loop from clientside.Christian Mollekopf2014-12-21
It's a huge hack but starts to show results. Most urgently we need: * reliable command results * the 3 buffers instead of the 1 * A way to implement storage as preprocessor (or a place to impelement it after the preprocessors).