incorporating project filters into abstractfilemanagerimportbenchmark

[René J.V. Bertin]

Hi,

Is it possible to tap into the project filter mechanism from within a kdevplatform/project unittest? I'd be surprised (read: peeved) if it weren't but get only halfway. In the test (my recent abstractfilemanagerimportbenchmark.cpp addition) I do

    auto core = TestCore::initialize(Core::NoUi);
    const auto plugins = core->pluginController()->queryExtensionPlugins(QStringLiteral("org.kdevelop.IProjectFilter"));
    qInfo() << "Plugins for IProjectFilter:" << plugins.size();
    foreach (const auto p, plugins) {
        qInfo() << "plugin" << p.name() << "file" << p.fileName();
        core->pluginController()->loadPlugin(p.name());
    }

which gives me

Plugins for IProjectFilter: 1
plugin "Project Filter" file "/opt/local/share/qt5/plugins/kdevplatform/30/kdevprojectfilter.so"
kdevplatform.shell: Unable to find a plugin named ' "Project Filter" '!

That seems contradictory. Is this an inappropriately worded failure message hiding an actual reason like "this plugin has KDevelop-Mode:GUI and there is no GUI"?

R.