Remove fragile assumption from var properties unit test

Previously, the test included some hardcoded property index values
which would break if the layout of an item changed.  This commit
ensures that the index of the properties are looked up dynamically.

Change-Id: I5a499f81a0cb859d89f0972eb7cd645107336bc9
Reviewed-by: Martin Jones <martin.jones@nokia.com>

1 files changed, 2 insertions, 2 deletions

diff --git a/tests/auto/declarative/qdeclarativeecmascript/tst_qdeclarativeecmascript.cpp b/tests/auto/declarative/qdeclarativeecmascript/tst_qdeclarativeecmascript.cpp
index 7cddfd22f1..a01c80b7e3 100644
--- a/tests/auto/declarative/qdeclarativeecmascript/tst_qdeclarativeecmascript.cpp
+++ b/tests/auto/declarative/qdeclarativeecmascript/tst_qdeclarativeecmascript.cpp
@@ -4002,8 +4002,8 @@ void tst_qdeclarativeecmascript::propertyVarInheritance()
         v8::HandleScope hs;
         // XXX NOTE: this is very implementation dependent.  QDVMEMO->vmeProperty() is the only
         // public function which can return us a handle to something in the varProperties array.
-        icoCanaryHandle = qPersistentNew(icovmemo->vmeProperty(41));
-        ccoCanaryHandle = qPersistentNew(ccovmemo->vmeProperty(41));
+        icoCanaryHandle = qPersistentNew(icovmemo->vmeProperty(ico5->metaObject()->indexOfProperty("circ")));
+        ccoCanaryHandle = qPersistentNew(ccovmemo->vmeProperty(cco5->metaObject()->indexOfProperty("circ")));
         // we make them weak and invoke the gc, but we should not hit the weak-callback yet
         // as the varproperties array of each vmemo still references the resource.
         icoCanaryHandle.MakeWeak(&propertyVarWeakRefCallbackCount, propertyVarWeakRefCallback);