Curiously nashorn does not appear in the URL when selecting all engines:

https://test262.fyi/#|v8,v8_exp,sm,sm_exp,jsc,hermes,qjs,libjs,libjs_bc,chakra,graaljs,xs,rhino,boa,engine262,babel

rhino does but is not visible as a checkable entry. Neither seem to be included in the results anywhere

You already know what this is about, just making a tracking issue :)

The way LibJS does it is just appending to an ever growing JSON file, which in hindsight is not really that scalable - especially not when you have results for 10 different engines.

This could either be tracking the total score, or even per-file results to see when certain engines implemented certain features.

Hey there! What would it take to add QuickJS-NG to the mix?

We've made significant improvements over the OG to make it close to ES2023 in features.

A common use case is seeing what the results of one specific engine are, which currently requires manually unselecting all other engines. There should either be a button to unselect all, or something like Alt+click unselecting all but the clicked checkbox.

Useful for identifying what tests use a lot of time (differing for each engine)

https://github.com/tc39/proposal-decorators

Using <th>+onclick is not keyboard-accessible, nor does it allow me to open multiple ones in a new tab but forces awkward back and forth navigation.

(these:)

Having the versions auto-select on click is a nice touch, but I don't really see a need to disable selection page-wide. Sometimes I just want to copy a filename or something :)

Hermes has two experimental options that can potentially improve the results: --block-scoping and -Xes6-class. How difficult would it be to pass them?

FWIW, it looks not exactly trivial. I think hermes is invoked from https://github.com/CanadaHonk/test262.fyi/blob/78cb8ddcf97cb42c3c40117d35bc6d484caf0437/.github/workflows/run.yml and I don't see an obvious way to pass special arguments there (but I know nothing about Git workflows). Perhaps an easier alternative would be to create a wrapper shell-script and invoke that?

Theirs: 86.37%
Ours: 85.21%

https://github.com/tc39/proposal-resizablearraybuffer

E.g. https://test262.fyi/#built-ins/undefined|libjs, when navigated to directly.

Oddly it seems to work sometimes, but not all of the time...

https://test262.fyi/#|v8_exp

See https://test262.fyi/#language/line-terminators|libjs,porffor

eg https://github.com/tc39/test262/blob/9e03c403e73341658d8d485a673798ae61f6f94a/test/language/line-terminators/comment-multi-ps.js

https://github.com/tc39/proposal-promise-with-resolvers

For example 15.1.1.3-2.js - https://test262.fyi/#built-ins/undefined|libjs vs https://libjs.dev/test262/per-file/?path=test%2Fbuilt-ins%2Fundefined

https://test262.fyi/#|sm_exp

new error, Error: can't open : No such file or directory on all tests

See also https://github.com/graalvm/graaljs/blob/master/CHANGELOG.md

https://test262.fyi/#|sm_exp

Error: Invalid long option: --enable-array-grouping

All implementations of the Import Attributes proposal use an older syntax, from when the proposal was called Import Assertions, and do not support the new syntax yet. It would be good to use the old name on the website, to avoid confusion.

Doesn't need to be the default but would be nice as an option IMO :)

I.e. turning this...	...into this

For example https://test262.fyi/#language/module-code or https://test262.fyi/#language/import, may or may not be fixed by CanadaHonk/eshost#1 or CanadaHonk/eshost#2.

I'm using firefox. The browser navigation buttons update the URL but not the page contents.

I just found out that Array.prototype.filter() has ~230 tests (that's a low hanging fruit if I've ever seen one!) and thought it would be very useful to see at a glance how many tests are in each subdirectory. If there's a space concern it would still be useful as a tooltip.

(scrollbar not visible because modern UI)

https://github.com/tc39/test262/blob/0a6dabf1e2f672c4b587f1774e3a4cc624cee5e6/test/language/line-terminators/S7.3_A6_T4.js

SWC throws a syntax error when parsing this code (as expected), but it's marked as failing at https://test262.fyi/#language/line-terminators|babel,swc,sucrase.

It seems that at least in some cases, warnings produced by hermes are being treated as errors by the test runner, causing it to assume that a test has failed when it has actually passed. For example this one: https://github.com/tc39/test262/blob/46fc2814306c75f671924c6830346bf76b3ac30b/test/language/line-terminators/S7.3_A5.4.js

When executed with Hermes, it produces two warnings but otherwise completes successfully.

$ hermes t.js
t.js:11:1: warning: Direct call to eval(), but lexical scope is not supported.
eval("/*\u2029 multi line \u2029 comment \u2029*/");
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
t.js:15:1: warning: Direct call to eval(), but lexical scope is not supported.
eval("/*\u2029 multi line \u2029 comment \u2029 x = 1;*/");
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

How difficult would it be to pass -w (to suppress all warnings) to the hermes CLI?

https://test262.fyi/#|sm_exp

Error: Invalid long option: --enable-array-grouping

When clicking on a proposal, show a page filtered with only tests for it shown instead of just going to the proposal repo.

Makes selecting them with doubleclick for copy/paste trigger the checkbox unnecessarily.

We run test262 on Babel and core-js regularly, and it would be very nice to show the results on https://test262.fyi.

I just noticed that our test262 runner on CI is completely broken and it's not reporting results, but for the purpose of this issue let's assume that it works, while I fix it 😅

We run test262 on every commit, and store the result in a test262-result artifact -- you can find the last one https://github.com/babel/babel/actions/runs/5179541745.

We run tests by compiling them to ES5 using Babel, injecting the core-js polyfill, and running the resulting code in a very old version of Node.js (0.10) which only supported ES5. This means that our test results aren't significant for pre-ES6 behavior, but they are useful for features introduced since then.

We use https://github.com/babel/babel-test262-runner/ to run them, which produces tap output. The readme doesn't mention it, but it's possible to specify the path to a different test262 checkout using the TEST262_PATH=.... env variable.

This might be a SM bug?

This is no longer accurate:

ESNext is now ES2025, i.e. edition 16: tc39/ecma262@d502ea4