AutoTest: Simplify determination of RunConfiguration

Since bc698d4ce61b the build system targets / build keys are
unique on their own.
Simplify the completion of test configurations and improve
readability.

Change-Id: I258e8a35a4740dd58b1365498ca399258092e0e3
Reviewed-by: hjk <[email protected]>

1 files changed, 1 insertions, 7 deletions

diff --git a/src/plugins/autotest/testconfiguration.cpp b/src/plugins/autotest/testconfiguration.cpp
index 6e26b910a33..09617d17a4a 100644
--- a/src/plugins/autotest/testconfiguration.cpp
+++ b/src/plugins/autotest/testconfiguration.cpp
@@ -148,13 +148,7 @@ void TestConfiguration::completeTestInformation(TestRunMode runMode)
     BuildTargetInfo targetInfo
             = Utils::findOrDefault(target->applicationTargets().list,
                                    [&buildSystemTargets] (const BuildTargetInfo &bti) {
-        return Utils::anyOf(buildSystemTargets, [&bti](const QString &b) {
-            const QStringList targWithProjectFile = b.split('|');
-            if (targWithProjectFile.size() != 2) // some build targets might miss the project file
-                return false;
-            return !bti.targetFilePath.isEmpty() && targWithProjectFile.at(0) == bti.buildKey
-                    && targWithProjectFile.at(1).startsWith(bti.projectFilePath.toString());
-        });
+        return buildSystemTargets.contains(bti.buildKey);
     });
     // we might end up with an empty targetFilePath - e.g. when having a library we just link to
     // there would be no BuildTargetInfo that could match