HomeSort by relevance Sort by last modified time
    Searched full:checks (Results 801 - 825 of 7809) sorted by null

<<31323334353637383940>>

  /external/chromium_org/v8/test/webkit/
pretty-print-expected.txt 24 This test checks that regexps, strings with special characters, object literals with non-identifier names, and array literals are pretty-printed correctly
pretty-print.js 25 "This test checks that regexps, strings with special characters, object literals with non-identifier names, and array literals are pretty-printed correctly"
primitive-method-this-expected.txt 24 This test checks that methods called directly on primitive types get the wrapper, not the primitive, as the 'this' object.
primitive-method-this.js 26 "This test checks that methods called directly on primitive types get the wrapper, not the primitive, as the 'this' object."
reentrant-call-unwind-expected.txt 24 This test checks that unwinding of exceptions properly copies registers of activation frames created by reentrant calls to JavaScript.
reentrant-call-unwind.js 25 "This test checks that unwinding of exceptions properly copies registers of activation frames created by reentrant calls to JavaScript."
regexp-extended-characters-more-expected.txt 24 This test checks a few cases of extended (> 127) characters in repeat regular expressions.
regexp-extended-characters-more.js 25 "This test checks a few cases of extended (> 127) characters in repeat regular expressions."
slash-lineterminator-parse-expected.txt 24 This test checks for correct handling ofr backslash-newline in JS strings.
sort-no-jit-code-crash-expected.txt 24 This test checks that non-numeric sort functions always have JIT code. This test passes if it does not crash.
sort-no-jit-code-crash.js 25 "This test checks that non-numeric sort functions always have JIT code. This test passes if it does not crash."
sort-with-side-effecting-comparisons-expected.txt 24 Checks that sorting an array with a side-effecting comparison function doesn't trigger assertions.
sort-with-side-effecting-comparisons.js 25 "Checks that sorting an array with a side-effecting comparison function doesn't trigger assertions."
stack-unwinding-expected.txt 24 This test checks that JavaScriptCore does not crash when uwinding the stack that includes a host function.
stack-unwinding.js 26 "This test checks that JavaScriptCore does not crash when uwinding the stack that includes a host function."
string-index-overflow-expected.txt 24 This test checks that accessing a string by an out of bounds index doesn't crash, furthermore the string should not appear to have out-of-bounds numeric properties.
string-index-overflow.js 25 "This test checks that accessing a string by an out of bounds index doesn't crash, furthermore the string should not appear to have out-of-bounds numeric properties."
string-slice-abnormal-values-expected.txt 24 This test checks for handling of abnormal values passed to String.slice
this-non-object-proto-expected.txt 24 This test checks that setting a non-object, non-null value for this.__proto__ does not lead to a crash when setting a property on the this object.
this-non-object-proto.js 25 'This test checks that setting a non-object, non-null value for this.__proto__ does not lead to a crash when setting a property on the this object.'
toString-for-var-decl-expected.txt 24 This test checks for a couple of specific ways that bugs in toString() round trips have changed the meanings of functions with var declarations inside for loops.
toString-number-dot-expr-expected.txt 24 This test checks that toString() round-trip on a function that has a expression of form 4..x does not lose its meaning. The expression accesses the property 'x' from number '4'.
toString-recursion-expected.txt 24 This test checks that toString() does not have a problem when an object has itself as a property.
toString-recursion.js 25 "This test checks that toString() does not have a problem when an object has itself as a property."
unexpected-constant-crash-expected.txt 24 This test checks that the regexp and unexpected constant counters are not confused with each other. It will fail with an assertion failure in a debug build if this is the case.

Completed in 142 milliseconds

<<31323334353637383940>>