From: Simon Hausmann Date: Fri, 7 Jun 2013 18:09:55 +0000 (+0200) Subject: Fix qqmlecmascript::nonExistentAttachedObject X-Git-Tag: upstream/5.2.1~669^2~292 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=fe1528f90cee97b3b1e99fb7101467b32a6f95e4;p=platform%2Fupstream%2Fqtdeclarative.git Fix qqmlecmascript::nonExistentAttachedObject Add column to the expected error message output Change-Id: I585fdcedd7a78f1a208770765851f04ee5a5b207 Reviewed-by: Lars Knoll --- diff --git a/tests/auto/qml/qqmlecmascript/tst_qqmlecmascript.cpp b/tests/auto/qml/qqmlecmascript/tst_qqmlecmascript.cpp index bb38b85..e586fbc 100644 --- a/tests/auto/qml/qqmlecmascript/tst_qqmlecmascript.cpp +++ b/tests/auto/qml/qqmlecmascript/tst_qqmlecmascript.cpp @@ -1173,7 +1173,7 @@ void tst_qqmlecmascript::nonExistentAttachedObject() { QQmlComponent component(&engine, testFileUrl("nonExistentAttachedObject.qml")); - QString warning = component.url().toString() + ":4: Unable to assign [undefined] to QString"; + QString warning = component.url().toString() + ":4:21: Unable to assign [undefined] to QString"; QTest::ignoreMessage(QtWarningMsg, qPrintable(warning)); QObject *object = component.create();