- Dec 03, 2017
-
-
Mike Pennisi authored
Ensure that the linter's Python dependencies are satisfied in the continuous integration environment. Note that this is not currently necessary but only because the linter's dependencies happen to align with those of the test generation tool. The dependencies of the two tool should be satisfied explicitly in order to promote isolation.
-
- Dec 01, 2017
-
-
André Bargull authored
-
- Nov 28, 2017
-
-
Rick Waldron authored
Split class fields tags
-
Leo Balter authored
-
Leo Balter authored
-
Leo Balter authored
-
Leo Balter authored
-
Leo Balter authored
-
Leo Balter authored
-
Leo Balter authored
Class fields with the same name
-
Isiah Meadows authored
Fixes #1355
-
- Nov 27, 2017
-
-
Justin Ridgewell authored
The tests are explicitly for bad hex chars at certain indexes, and that rogue `%` was giving false positives.
-
- Nov 21, 2017
-
-
Daniel Ehrenberg authored
The change is done in the following patch, where default options have a null prototype. This matches what other Intl objects have. https://github.com/tc39/proposal-intl-plural-rules/commit/1abe8af440fb47d888ace701e8a46559bdbe7b06
-
Leo Balter authored
Added missing cases into BigIntConstructor with String parameters
-
Leo Balter authored
Fix #1345
-
- Nov 20, 2017
-
-
Rick Waldron authored
Originally discovered by Cait Potter (@caitp), reported in irc.mozilla.org#jslang
-
- Nov 17, 2017
- Nov 15, 2017
-
-
Leo Balter authored
-
Leo Balter authored
- Add tests for multiple public fields of the same name - Reorganize fields default templates - Add more tests for redeclaration of fields - Remove non used template - Add tests for computed property names in class fields definitions - Minor test fixes Thanks @andresaraujo for helping with the early review
-
- Nov 10, 2017
-
-
Leo Balter authored
* Accessing `ta[0]` throws a TypeError. * Fix array indices starting at 0 and property references * Fix classfields templates for properly checking static propnames. * Generate tests * `assert.equal` is not defined * Add missing includes * Generate tests * typo s/Avalue/42/ * fix whitespace * Add missing var for strict mode * Expand generated class fields tests for forbidden computed property name values Ref https://github.com/tc39/test262/pull/1339#issuecomment-342830243 * derived classes have access to private names in base classes, if private names are in scope
-
- Nov 06, 2017
-
-
Leo Balter authored
classfields: Tests for modified algorithms and Private Names
-
- Nov 03, 2017
-
-
Jeff Walden authored
Add tests for setting/defining an element of a typed array to a value, where converting that value to the typed array element type detaches the buffer underlying the typed array. (#1336)
-
Valerie R Young authored
-
Valerie R Young authored
-
Valerie R Young authored
-
Rick Waldron authored
fixup: swap actual and expected in test/built-ins/Promise/prototype/finally/species-symbol.js (#1333)
-
Leo Balter authored
classfields: add tests duplicate private fields and deleting private fields
-
Leo Balter authored
classfields: add tests for privatename production and ASI
-
Valerie R Young authored
-
Valerie R Young authored
-
Valerie R Young authored
-
Leo Balter authored
classfields: add early error tests for privatename references
-
Leo Balter authored
classfields: add tests for forbidden public/private propertynames
-
- Nov 01, 2017
-
-
Leo Balter authored
Fix multiple test issues
-
André Bargull authored
-
André Bargull authored
Changes: - Changed eval-err-contains-supercall-1.case to add a property access similar to eval-err-contains-supercall-2.case, without this property access eval-err-contains-supercall-1.case would be identical to eval-err-contains-supercall.case. - Remove unnecessary "earlyerror" and "executionerror" template arguments when the value is already clear from the context. - Fixed the description in eval-err-contains-supercall-2.case to refer to the correct early error rule. - Fixed a copy-paste error in eval-err-contains-superproperty-1.case and eval-err-contains-superproperty-2.case. - Split initializer-eval-super into initializer-eval-super-call and initializer-eval-super-property, because we actually need to test different behaviour for the super-call compared to the super-property case. - Split initializer-eval into initializer-eval-arguments and initializer-eval-newtarget, because `arguments` and `new.target` are differently handled in class-fields. - And fixed other copy-paste errors in the template files. Fixes #1325
-
André Bargull authored
Fixes #1313
-
André Bargull authored
Fixes #1312
-
André Bargull authored
Fixes #1306
-