IndexScheduler::IndexingSpeed speed = IndexScheduler::SnailPace );

I would prefer a method which is also exposed via DBus. This makes sense in any case. I would often like to change the indexing speed for manual testing for example.

But for that I would not use the IndexScheduler enum but an int which directly expresses the delay between files.

Then we could even change the enum to have msec values or even replace it by static const ints.

using namespace Nepomuk;

void IndexerTests::testSimpleIndexing() {

Please follow the code indentation policy in KDE. Methods do not use trailing brackets.

using namespace Nepomuk;

	KConfig* config = new KConfig("nepomukstrigirc" );

KConfig objects are typically created on the stack. The only "advantage" of this approach is a nice memory leak. ;)

using namespace Nepomuk;

	config->group("General").writePathEntry("folders", QDir::currentPath().append("/testdata"));

Is QDir::currentPath() really appropriate? The test could be started from anywhere? How about a cmale config files which puts the actual path to the test data into the source file?

using namespace Nepomuk;

	Nepomuk::StrigiService s(NULL, QList<QVariant>(), IndexScheduler::FullSpeed); // This should start the strigi service and index scheduler.

"NULL" is a C definition. Please use "0" instead.

using namespace Nepomuk;

	bool gotSignal = QTest::kWaitForSignal(&s, SIGNAL(indexingStopped()), 15000);

Superfluous variable.

using namespace Nepomuk;

QTEST_KDEMAIN(IndexerTests, NoGUI)

#include "indexertests.moc"

This is just policy and slightly improves compilation performance since the moc file does not have to be compiled independently.

[Basic Settings]

Hm, how about we add a command line parameter to nepomukserver which specifies which services to start. Otherwise new services not mentioned in this list will be started.

Nepomuk::TestBase::TestBase(QObject* parent)

    d->m_serviceManager = new org::kde::nepomuk::ServiceManager( "org.kde.NepomukServer", "/servicemanager", QDBusConnection::sessionBus() );

This is never deleted.

Nepomuk::TestBase::TestBase(QObject* parent)

    Q_FOREACH( const QString & service, services )

See comment about the nepomukserver parameter. Once we have that there is no need to stop services here.

Nepomuk::TestBase::TestBase(QObject* parent)

{

This is IMHO unclean. It would be best to simply stop Virtuoso, recreate the DB from the tar and restart Virtuoso.

The removeAllStatements is not really public API anyway anymore and the storage service does create some information we might miss here.

This, however, has a low priority for me. :)

namespace {

    // It's hard to believe that Qt doesn't provide its own copy folder function

KIO can do that for you.

namespace {

Tabs are evil. :P

namespace {

    bool removeDir(const QString &dirName)

Again KIO can do this.

namespace {

    QTest::qSleep( 4000 );

This is very ugly. How about we add a signal to the filewatcher DBus interface which is emitted once the filewatcher has handled its queue.

namespace {

QString FileWatchTest::createTempDir()

Use KTempDir instead.