- Jun 18, 2015
-
-
Mike Pennisi authored
Unlike the console runner, the browser runner does not modify the strictness of tests prior to running them. Regardless of a given test's metadata, it runs every test exactly once, and it never enables strict mode. This means that tests intended to function in strict mode must declare the "use strict"; directive prologue in addition to the `onlyStrict` flag. For any test that specifies the `onlyStrict` metadata flag, transform the source code by injecting a "use strict" directive prologue prior to running the test.
-
Brian Terlson authored
Add tests for Object-Assign
-
Brian Terlson authored
Update browser runner to inject `assert.js`
-
Mike Pennisi authored
Since the Python runner was updated to include `assert.js` in all tests unconditionally, a number of tests have been written that implicitly rely on its presence. The browser runner does not currently provide this file's contents to these tests, so they fail unconditionally. Update the browser runner to inject that file's contents into every test context. Note: the existing approach to file retrieval (namely loading via synchronous XHR requests) is inefficient and deprecated in some browsers. It is honored here for the sake of consistency and to minimize the changeset necessary to fix the browser runner.
-
Yanli Xu authored
-
- Jun 17, 2015
-
-
Brian Terlson authored
Add tests for MethodDefinition forms new to ES6
-
Brian Terlson authored
Remove $PRINT helper function
-
Brian Terlson authored
Fix typo in test meta-data
-
Mike Pennisi authored
The `Negative` tag accepts a string value (not a list)
-
- Jun 16, 2015
-
-
Mike Pennisi authored
The `$PRINT` helper function has no effect on test behavior. The following tests use it to report assertion outcomes (and as a result will fail silently): - test/language/function-code/S10.2.1_A4_T2.js - test/language/function-code/S10.2.1_A5.1_T1.js - test/language/function-code/S10.2.1_A5.1_T2.js - test/language/function-code/S10.2.1_A5.2_T1.js Remove the function definition and all references within tests. Update tests that use it as an error reporting mechanism to instead use an appropriate `assert` helper function.
-
Brian Terlson authored
The Array.prototype.fill function is an ES6 function.
-
Brian Terlson authored
The Array.prototype.find function is an ES6 function.
-
Brian Terlson authored
ES6 numeric literals
-
Brian Terlson authored
Fix tautological pattern in tests
-
Mike Pennisi authored
In neglecting to assert the type of error thrown (or that any error was thrown at all), these tests cannot fail. Refactor the tests to use the `assert.throws` helper method, which takes these details into consideration.
-
Brian Terlson authored
Add tests for Proxy
-
Leonardo Balter authored
-
Leonardo Balter authored
-
Leonardo Balter authored
-
Leonardo Balter authored
-
Leonardo Balter authored
-
Leonardo Balter authored
-
Leonardo Balter authored
-
Leonardo Balter authored
-
Leonardo Balter authored
-
Leonardo Balter authored
-
Leonardo Balter authored
-
Leonardo Balter authored
-
Leonardo Balter authored
-
Leonardo Balter authored
-
Leonardo Balter authored
-
Leonardo Balter authored
-
- Jun 14, 2015
-
-
Pieter van Ginkel authored
A number of Array.prototype.find tests were missing a feature specification.
-
- Jun 13, 2015
-
-
Pieter van Ginkel authored
One of the Array.prototype.fill tests specifies an es5id. Changed to an es6id.
-
- Jun 12, 2015
-
-
Mike Pennisi authored
-
Mike Pennisi authored
-
- Jun 11, 2015
-
-
Brian Terlson authored
Use the more common array syntax for includes
-
Brian Terlson authored
Fix monkey yaml's handling of carriage return
-
- Jun 10, 2015
-
-
Erik Arvidsson authored
monkeyYaml didn't split lines correctly leading to \r in resulting values. Fixes #295
-
Tom Schuster authored
-