144241 2015-04-26 16:32:28 -0700 Import tests from TC39 tests262 2016-08-30 11:27:27 -0700 1 1 1 Unclassified WebKit JavaScriptCore 528+ (Nightly build) Unspecified Unspecified RESOLVED DUPLICATE 157807 P2 Normal --- 1 rniwa ysuzuki benjamin darin fpizlo ggaren mark.lam msaboff ysuzuki oldest_to_newest 1088870 0 rniwa 2015-04-26 16:32:28 -0700 We should import tests from https://github.com/tc39/test262 Their tests for class syntax, for example, caught a few bugs as well as crashes! I've been using their python script to run tests as follows: ./tools/packaging/test262.py --command="/Volumes/Data/webkit/Tools/Scripts/run-jsc --no-show-dyld" after applying the following change to run-jsc: Index: Tools/Scripts/run-jsc =================================================================== --- Tools/Scripts/run-jsc (revision 183315) +++ Tools/Scripts/run-jsc (working copy) @@ -39,17 +39,23 @@ my $usage = "Usage: run-jsc [--count run_count] shell_file [file2...]"; my $count = 1; -GetOptions("count|c=i" => \$count); +my $noShowDyld = 0; +GetOptions(("count|c=i" => \$count, "no-show-dyld" => \$noShowDyld)); my $jsc = jscProductDir() . "/jsc @ARGV"; my $dyld = jscProductDir(); $ENV{"DYLD_FRAMEWORK_PATH"} = $dyld; -print STDERR "Running $count time(s): DYLD_FRAMEWORK_PATH=$dyld $jsc\n"; + +if (!$noShowDyld) { + print STDERR "Running $count time(s): DYLD_FRAMEWORK_PATH=$dyld $jsc\n"; +} + while ($count--) { - if (system("$jsc") != 0) { - last; + my $exit_code = system("$jsc"); + if ($exit_code != 0) { + exit($exit_code >> 8); } } 1089059 1 ysuzuki 2015-04-27 10:12:05 -0700 This is really exciting issue! As far as I know, we can execute each test262 test by executing it with the test harness script. So I think we can adopt test262 into JSC tests :D I'll check the current W3C test import process... 1224643 2 ysuzuki 2016-08-30 11:27:27 -0700 *** This bug has been marked as a duplicate of bug 157807 ***