* Add tests for escape function when parameter is not a string.
Fixes#2687Fixes#2637
* Add test for indirect eval calls when script is a for statement.
When for statement doesn't have a body, it should throw a SyntaxError.
Fixes#2661
* Add tests for Function Constructor when body contains usestrict.
Fixes#2688Fixes#2638
Extend tests for the `escape` and `unescape` built-ins to assert their
behavior. Rely on the latest ECMAScript draft, which specifies that
`escape` returns hexadecimal codes in upper case.
This harness function is not necessary in the majority of cases in which
it is used. Remove its usage to simplify tests and decrease the amount
of domain-specific knowledge necessary to contribute to the test suite.
Persist the harness function itself for use by future tests for ES2015
modules (such a helper is necessary for tests that are interpreted as
module code).
The "mainline" tests in Test262 are converging on a more formal
structure. Files are organized as tests for either either "language"
(e.g. syntax-driven) or "built-in" (e.g. API-driven). "Language" test
locations are themselves structured according to whether the syntactic
form under test is an Expression or a Statement.
To limit ambiguity when locating/adding tests, re-organize the tests for
Annex B extensions to match this structure.
Rick Waldron
QuXing9
Leo Balter
André Bargull
Doug Ilijev
jugglinmike