tyler.durden
/
test262
mirror of https://github.com/tc39/test262.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
152 Commits 18 Branches 0 Tags 132 MiB
Commit Graph

94 Commits

Author SHA1 Message Date
Mark Miller 68d44bb52a Having restored the test262 sources of these to their original sputnik 
form, they now convert correctly to tests that pass our
tools/test262.py test runner. The issue for all three was non-ascii content.
 2011-09-12 08:34:41 -07:00
Mark Miller 9973643490 These are the three files that "diff" identified as "binary" files with differences from the Sputnik original. Restoring to their original Sputnik state. 2011-09-12 08:19:27 -07:00
Mark Miller 77450b53f2 Unlike the current sputnikLib.js, framework.js cannot define $ERROR 
etc, because the substitution logic in test262.py operates on the
source after prepending framework.js.

The plan is to replace sputnikLib.js with framework.js. Also, the
substitution logic in test262.py should probably be fixed to apply the
substitution before prepending.
 2011-09-11 21:45:26 -07:00
Mark Miller a2ca5b512b Adapted the sputnik command line testRunner to a command line 
testRunner, test262.py, that can run all the converted tests.
 2011-09-11 21:12:01 -07:00
Mark Miller d0f40b63a2 Updating a generated directory. 
assertTrue became assertTruthy. Canonical form of doc-comment attribute value source no longer have a leading colon and trailing semicolon. Any existing such are stripped during conversion.
 2011-09-11 21:07:23 -07:00
Mark Miller 274b5514fa As David Fugate requested, changed the conversion of ietestcenter 
style to append runTestCase(funcName); rather than
assertTrue(funcName.call(this)), giving the testing framework more
control.
 2011-09-09 14:48:37 -07:00
Mark Miller 0065b15889 Just checking in the converted files, generated using the previous commit. 2011-09-07 21:47:38 -07:00
Mark Miller ca417c93dc Now generating the format David Fugate and I agreed on this 
morning. The rewrite of "function testcase()..." now puts the
assertTrue at the bottom. Preconditions, names, and ids are
removed. And the path in the file is ignored, and is instead set
accurately according to where the file is found.
 2011-09-07 21:42:49 -07:00
Mark Miller 57c450002d Removed an invalid "var". 2011-09-07 08:52:29 -07:00
Mark Miller d6df1d4a36 Fixed a typo precodition -> precondition 2011-09-07 08:48:46 -07:00
Mark Miller bc6a3ba731 All sputnik and ietestcenter tests converted to proposed new canonical form 2011-09-06 23:35:18 -07:00
David Fugate 1f6f66cb19 https://bugs.ecmascript.org/show_bug.cgi?id=76 2011-07-18 11:08:15 -07:00
David Fugate bda89b6452 https://bugs.ecmascript.org/show_bug.cgi?id=127 2011-07-18 10:59:06 -07:00
David Fugate 5b2de8816f https://bugs.ecmascript.org/show_bug.cgi?id=126 2011-07-18 10:29:23 -07:00
David Fugate 009262deba https://bugs.ecmascript.org/show_bug.cgi?id=128 2011-07-18 09:15:03 -07:00
David Fugate 383aaca3b1 https://bugs.ecmascript.org/show_bug.cgi?id=133 2011-07-18 09:05:23 -07:00
David Fugate 9eb6c8c2d2 15.4.4.15-3-14, 15.4.4.15-3-29, and 15.4.4.15-3-8 were disabled with no reason or bug given. These actually look OK, 
and pass on all browsers...
 2011-07-08 16:02:19 -07:00
David Fugate 7ffad2be3e Several new Sputnik tests included: 
if (!strict_mode) { throw new SyntaxError('unspecified case'); }

This doesn't work for a few reasons:
1.  'strict_mode' is undefined in the test case exeuction context. That is, the test framework
    does not force the test case into strict mode
2.  The test case code looks like:
	"use strict";
	if (!strict_mode) ...
        ...
    Note that 'strict_mode' is not set before being accessed

Really the metadata for these test cases should have a "@strict" property added to instruct the test
framework *not* to run the test if an implementation doesn't support strict mode.
 2011-07-07 14:31:22 -07:00
David Fugate d848bcad16 Recent update from Sputnik has made S12.10_A3.3_T4 a valid ES5 test. Re-enabled 2011-07-07 13:42:04 -07:00
David Fugate a442fb1509 More Sputnik tests have been fixed and enabled. 2011-07-07 12:58:55 -07:00
David Fugate 314a8abb70 https://bugs.ecmascript.org/show_bug.cgi?id=12 is partially fixed. 2011-07-07 10:38:08 -07:00
David Fugate f3ed594ec4 https://bugs.ecmascript.org/show_bug.cgi?id=18 (IE Test Center tests only) 2011-07-07 10:10:32 -07:00
David Fugate c77066fc25 https://bugs.ecmascript.org/show_bug.cgi?id=118 2011-07-07 08:47:12 -07:00
David Fugate 6224968765 https://bugs.ecmascript.org/show_bug.cgi?id=120 2011-07-07 08:34:41 -07:00
David Fugate aa4b085528 https://bugs.ecmascript.org/show_bug.cgi?id=117 
Disabled 9 invalid tests.
 2011-07-06 11:00:55 -07:00
David Fugate 09ea4a8413 https://bugs.ecmascript.org/show_bug.cgi?id=61 2011-07-05 16:39:32 -07:00
David Fugate c8559941b2 https://bugs.ecmascript.org/show_bug.cgi?id=61 2011-07-05 16:36:04 -07:00
David Fugate 8b0704e64c https://bugs.ecmascript.org/show_bug.cgi?id=87 *should* in theory be fixed now. Need to test 
on the live website to be sure.
 2011-07-01 12:01:55 -07:00
David Fugate 42b534663f Added a small script, InvalidTestDetector.py, to help detect test dependencies on DOM and 
host objects (which make them invalid for test262).  Using this, I found one benign 'alert'
usage (it was never even called) and removed it.
 2011-06-30 14:31:11 -07:00
David Fugate 4cbb71f6b0 An ActiveX test slipped into IE Test Center/test262 by mistake. Removed 2011-06-30 09:59:25 -07:00
David Fugate 254821616f Added a few missing test case descriptions. 2011-06-29 12:02:57 -07:00
David Fugate 0e187575b1 Regenerated website. 2011-06-29 11:30:40 -07:00
David Fugate b78c959d2a New Sputnik 'negative' metadata that included exception type was causing problems for SputnikConverter. 
Took the easy fix and split the metadata into two: 'negative' and 'errortype'.
 2011-06-29 11:11:12 -07:00
David Fugate c52161e734 Fixed Sputnik test 'path' metadata. 2011-06-29 10:04:15 -07:00
David Fugate dce7ac2a5e Converted Sputnik's latest test case push to test262 format. 2011-06-29 09:40:07 -07:00
David Fugate e182868bad Converted Sputnik's latest test case push to test262 format. 2011-06-29 09:38:48 -07:00
David Fugate b8a44856a4 Fixed 'assertion' and 'description' metadata formatting issues (WRT SputnikConverter). 2011-06-29 09:18:48 -07:00
David Fugate 47b14845af Merged remote changes. 2011-06-28 10:43:22 -07:00
David Fugate febe8b348b Ported Sputnik changes over from the 'external' directory to 'test/suite/sputnik'. Still need to convert 
the tests over to test262 format.
 2011-06-27 16:20:31 -07:00
David Fugate 55855b285e Updated test262 with test case additions and edits from the PPB2 release of IE10. This included: 
- 22 test case additions (mostly strict mode)
- 4 test case edits
 2011-06-23 15:04:00 -07:00
David Fugate 9c0e7dd413 Test failures in the 'Run' tab now have a link to the test case's source 
similar to the 'Results' tab.
 2011-06-09 16:31:52 -07:00
David Fugate 33ba3d7621 Moved TEST_LIST_PATH from sth.js to default.html. 2011-06-07 09:48:10 -07:00
David Fugate b084094004 https://bugs.ecmascript.org/show_bug.cgi?id=103 2011-05-25 17:27:58 -07:00
David Fugate 7732e3578e More improvements regarding https://bugs.ecmascript.org/show_bug.cgi?id=33 2011-05-25 14:11:05 -07:00
David Fugate f9ec77866a Fix for https://bugs.ecmascript.org/show_bug.cgi?id=72. 2011-05-25 13:07:43 -07:00
David Fugate 0baf9ae7f6 Seems I accidentally checked in 10.4.2-2-c-1.js.orig in addition to 10.4.2-2-c-1.js. Removed 10.4.2-2-c-1.js.orig. 2011-05-20 13:48:57 -07:00
David Fugate 33c1a02fea Original test author fixed Bug #69. 2011-05-18 15:27:12 -07:00
David Fugate 623f25e341 - disabled five invalid tests 
- fixed issues in 10.6-13-a-1.js, 13.2-17-1.js, and 15.5.4.20-2-46.js.  Still have a number
  of test bugs to look into once I get more free time though
 2011-05-13 08:46:20 -07:00
David Fugate 994e6f3049 A previous check-in made today lost generation of 'N.0' test section directories for 
tests covering a given chapter, N, without delving into subsections.  This in turn
broken the Results page which was by default displaying individual results for chapters
13(.0) and 14(.0).  Fixed.
 2011-04-20 16:52:14 -07:00
David Fugate ef45786a21 A major web browser does not fire window.onerror for iframes when the iframe's document 
contains a JavaScript syntax error (major test area).  Added a workaround.
 2011-04-20 15:39:50 -07:00