Fix some of the finer details with regards to Completions

JS completion records have some finer details that can only be
seen when using eval(), where the value of the completion record
becomes important.

Fix most of those cases to be compliant with the spec.

Change-Id: I0c8105a8e778de7be3aea151d1bd64243aea067c
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>

1 files changed, 2 insertions, 2 deletions

diff --git a/tests/auto/qml/qqmlecmascript/tst_qqmlecmascript.cpp b/tests/auto/qml/qqmlecmascript/tst_qqmlecmascript.cpp
index 5959ecc19f..acdee3a808 100644
--- a/tests/auto/qml/qqmlecmascript/tst_qqmlecmascript.cpp
+++ b/tests/auto/qml/qqmlecmascript/tst_qqmlecmascript.cpp
@@ -7371,7 +7371,7 @@ void tst_qqmlecmascript::tryStatement()
         MyQmlObject *object = qobject_cast<MyQmlObject *>(component.create());
         QVERIFY(object != nullptr);
 
-        QCOMPARE(object->value(), 1);
+        QVERIFY(object->qjsvalue().isUndefined());
     }
 
     {
@@ -7379,7 +7379,7 @@ void tst_qqmlecmascript::tryStatement()
         MyQmlObject *object = qobject_cast<MyQmlObject *>(component.create());
         QVERIFY(object != nullptr);
 
-        QCOMPARE(object->value(), 1);
+        QVERIFY(object->qjsvalue().isUndefined());
     }
 }