v8/test/test262
Frank Tang b819afeb4f [Intl] Implement Intl.RelativeTimeFormat.prototype.{format, formatToParts}
Spec: http://tc39.github.io/proposal-intl-relative-time/

Design Doc: go/add-intl.relativetimeformat-to-v8

Test: test262/intl402/RelativeTimeFormat/*, intl/relative-time-format/*

R=cira@chromium.org, gsathya@chromium.org

Bug: v8:7869
Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng
Change-Id: Ied95d601cf707db5d555f9d963b9b1f206e37331
Reviewed-on: https://chromium-review.googlesource.com/1124728
Reviewed-by: Sathya Gunasekaran <gsathya@chromium.org>
Commit-Queue: Frank Tang <ftang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#54520}
2018-07-18 12:49:22 +00:00
..
local-tests/test [test262] Test262 Roll 2018-02-22 22:31:50 +00:00
BUILD.gn Reland "[build] Remove legacy isolate configurations" 2018-03-28 12:36:55 +00:00
detachArrayBuffer.js test262 roll 2017-03-13 14:33:07 +00:00
harness-adapt.js test262 roll 2017-03-13 14:33:07 +00:00
harness-agent.js Expose "$262.agent.monotonicNow()" for use in testing Atomic operation timeouts. Bug: v8:7705 2018-05-01 15:27:59 +00:00
prune-local-tests.sh test262 roll 2017-02-10 19:05:55 +00:00
README
test262.status [Intl] Implement Intl.RelativeTimeFormat.prototype.{format, formatToParts} 2018-07-18 12:49:22 +00:00
testcfg.py [Intl] Implement Intl.RelativeTimeFormat constructor 2018-07-10 14:20:06 +00:00
upstream-local-tests.sh test262 roll 2017-03-13 14:33:07 +00:00

This directory contains code for binding the test262 test suite
into the v8 test harness. The tests are checked out as a dependency from

  https://chromium.googlesource.com/external/github.com/tc39/test262

at a revision specified in the DEPS file as 'data' in this directory. They are
fetched with 'gclient sync'. To update to a newer version, please change the
DEPS file.

Using a newer version, e.g. 'deadbeef' may be possible but the tests are only
known to pass (and indeed run) with the DEPS revision. Example:

  cd data
  git fetch
  git checkout deadbeef

If you do update to a newer revision you may have to change the test
harness adapter code since it uses internal functionality from the
harness that comes bundled with the tests.  You will most likely also
have to update the test expectation file.