mirror of
https://github.com/tc39/test262.git
synced 2025-05-26 01:30:28 +02:00
d87a7da6e1
While we're at it, use assert() instead of assert.sameValue() for brevity,
if we are not specifically testing that the return value of hasOwnProperty
is the value true or false; and add more informative assertion messages to
help with debugging.
In some cases, the Object.hasOwnProperty.call could be replaced with
verifyProperty(), if the property descriptor was also being verified at
the same time.
This fixes some tests that were faulty to begin with: a common mistake was
Object.hasOwnProperty(obj, prop) which is probably going to return false
when that's not what you want.
The only instances left of `Object.hasOwnProperty` are one regression test
in implementation-contributed which I can't tell if it was intentionally
needed to trigger the regression, and a few instances of
`Object.hasOwnProperty('prototype')` which would defeat the purpose to
convert into `Object.prototype.hasOwnProperty.call(Object, 'prototype')`
form.
Closes: #3524
15 lines
471 B
JavaScript
15 lines
471 B
JavaScript
// Copyright 2009 the Sputnik authors. All rights reserved.
|
|
// This code is governed by the BSD license found in the LICENSE file.
|
|
|
|
/*---
|
|
info: Object constructor has length property whose value is 1
|
|
es5id: 15.2.3_A3
|
|
description: Checking Object.length
|
|
---*/
|
|
assert(
|
|
Object.prototype.hasOwnProperty.call(Object, "length"),
|
|
"The Object constructor has a 'length' own property"
|
|
);
|
|
|
|
assert.sameValue(Object.length, 1, 'The value of Object.length is expected to be 1');
|