- Apr 25, 2016
-
-
Mike Pennisi authored
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).
-
- Jul 17, 2015
-
-
André Bargull authored
-
- Jun 18, 2015
-
-
Mike Pennisi authored
Some tests specifically concern the application of the `use strict` directive as it appears in JavaScript source code. These tests should *not* be run with the `onlyStrict` flag because relying on the test runner to enable strict mode makes the semantics of the source code irrelevant. Update these tests to use the `noStrict` flag. Other tests concern language semantics that are only valid in strict mode, but the mechanism for enabling strictness is inconseqential. Update these tests to use the `onlyStrict` flag and remove any redundant `use strict` directive prologues contained within. Still other tests are valid both within and outside of strict mode. In keeping with the majority of other tests, do not specify any restrictions on the environments in which these tests may be run.
-
- Dec 07, 2014
-
-
Brian Terlson authored
-
- Jul 30, 2014
-
-
Brian Terlson authored
-
Brian Terlson authored
This commit normalizes the test case format used across test262. It applies the following transformations: * Convert to YAML for frontmatter * Remove of trailing whitespace * Replace /r/n with /n except in chapters 6 and 7. * Copyright header always uses // comments * new includes attribute replaces $INCLUDE * No implicit assumptions about test environment other than $ERROR. Everything else appears in the include array. This includes "runTestCase" which is now included in a substantial number of tests.
-
- Feb 29, 2012
-
-
David Fugate authored
All Microsoft-contributed *.js and *.py sources now have Ecma's copyright header.
-
- Feb 27, 2012
-
-
David Fugate authored
-
David Fugate authored
-
- Nov 04, 2011
-
-
David Fugate authored
77 new (mostly) strict mode tests plus the removal of one invalid test case. Sputnik and IE Test Center tests now live side-by-side in ch* directories under test/suite.
-
- Sep 25, 2011
-
-
Mark Miller authored
source starting NOW, to test/suite.
-
- Sep 24, 2011
-
-
Mark Miller authored
-
Mark Miller authored
-
- Sep 23, 2011
-
-
Mark Miller authored
(between David Fugate and I) canonical test262 test format
-
- Sep 14, 2011
-
-
Mark Miller authored
-
Mark Miller authored
-
- Aug 25, 2011
-
-
David Fugate authored
- a lot of JS harness code written in strings have been moved out to actual physical files such as ed.js (syntax error detection for globally scoped tests) and gs.js (global scope test case validator). This change makes it far easier to maintain the test harness code - reorganized helper.js providing a clear indication which methods are used by external objects, which are implementation details, and which are unequivocally test262-specific. I've also added, openErrorWindow, which will be used to open a descriptive error message window for each test case failure reported on the 'Run' tab - improved the error message for syntax errors occurring when a test case fails to load - sta.js no longer tries to pickle all helper functions it contains! Instead, we load the file directly from sth.js. The performance of fnGlobalObject has been improved. Finally, the ES5Harness object has been moved from sth.js (in a string) to here - sth.js now has a browser implementer hook, controller.implementerHook, which allows browser implementers to handle test case failures in their own way (e.g., log to the filesystem). The 'run' function was basically re-written Added 37 new test cases from the "IE Test Center" Build release. There were 14 modifications to existing test cases as well. Refactored SputnikGlobalScope.js such that test case paths are now used as indices into the GlobalScopeTests array. TestCasePackager.py had the concept of templated test harnesses introduced - see templates\runner.test262.html. Also added support for one HTML test harness per ES5 chapter. Last but not least, TestCasePackagerConfig.py now has a 'source control' abstraction class which abstracts away source control adds|edits when dynamically generating *.json and *.html test chapters.
-
- Aug 24, 2011
-
-
David Fugate authored
for the Build 2011 conference.
-
- Mar 09, 2011
-
-
David Fugate authored
-
- Feb 02, 2011
-
-
David Fugate authored
- 12.14-7.js: cleaned up - 15.2.3.3: 89 test case additions - 15.2.3.4: 29 test case additions - 15.2.3.6: 1,076 test case additions and 15 minor test case fixes - 15.2.3.9-1.js: cleaned up - 15.3.4.5-2-8.js: cleaned up - 15.4.4.14: 14 test case additions and 3 minor test case fixes - 15.4.4.15: 9 test case additions and 3 minor test case fixes - 15.4.4.17: 1 test case additions and 1 minor test case fix - 15.4.4.18: 1 minor test case fix - 15.4.4.19: 1 test case addition and 2 minor test case fixes - 15.4.4.20: 3 minor test case fixes - 15.4.4.21: 1 test case addition and 1 minor test case fix - 15.4.4.22: 2 minor test case fixes - 15.9.4.4: 2 minor test case fixes - 15.9.5.43-0-2.js: minor test case fix
-
- Oct 19, 2010
-
-
David Fugate authored
- external\contributions\: test contributions to Test262 from external entities such as Microsoft and Google. This directory consists of the external tests without any modifications - test\harness\: test harness used to run Test262 tests. Presently web-based - test\suite\: suite of vendor-neutral ECMAScript test cases conforming to the ES5 spec - tools\: among other things this includes a set of tools used to convert various external test contributions to a format the Test262 test harness can consume - website\: an archived copy of the http://test262.ecmascript.org website
-