qmllint: Consider failure to find imports an error

There is no real reason to tolerate it. We can generate all qmltypes at
build time, and if we can't find them, the results are likely to be off.

Change-Id: Id935d76ac3ca6b601381b40a73d7fbacca342c4d
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>

1 files changed, 3 insertions, 3 deletions

diff --git a/tests/auto/qml/qmllint/tst_qmllint.cpp b/tests/auto/qml/qmllint/tst_qmllint.cpp
index 03412f0144..1cd9f8b0d1 100644
--- a/tests/auto/qml/qmllint/tst_qmllint.cpp
+++ b/tests/auto/qml/qmllint/tst_qmllint.cpp
@@ -48,7 +48,7 @@ private Q_SLOTS:
     void dirtyQmlCode_data();
     void dirtyQmlCode();
 
-    void testUnqualifiedNoSpuriousParentWarning();
+    void testUnknownCausesFail();
 
 private:
     QString runQmllint(const QString &fileToLint, bool shouldSucceed);
@@ -107,9 +107,9 @@ void TestQmllint::testUnqualified_data()
     QTest::newRow("NonSpuriousParent") << QStringLiteral("nonSpuriousParentWarning.qml") << QStringLiteral("property int x: <id>.parent.x") << 6 << 25;
 }
 
-void TestQmllint::testUnqualifiedNoSpuriousParentWarning()
+void TestQmllint::testUnknownCausesFail()
 {
-    const QString unknownNotFound = runQmllint("spuriousParentWarning.qml", false);
+    const QString unknownNotFound = runQmllint("unknownElement.qml", false);
     QVERIFY(unknownNotFound.contains(
                 QStringLiteral("warning: Unknown was not found. Did you add all import paths?")));
 }