You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As @justingrant pointed out on #218 our runtest262.mjs script doesn't really have test coverage, and as the underlying test runner ends up with more features it would be good to verify that the command wiring there works.
One potential solution could be to have another CI run that:
runs test262 and verifies the output contains markers indicating that the runner actually ran some (all?) tests.
runs test262 with a set glob and verifies that only those tests ran
maybe runs the --help integration and verifies something from there?
The text was updated successfully, but these errors were encountered:
As @justingrant pointed out on #218 our runtest262.mjs script doesn't really have test coverage, and as the underlying test runner ends up with more features it would be good to verify that the command wiring there works.
One potential solution could be to have another CI run that:
--help
integration and verifies something from there?The text was updated successfully, but these errors were encountered: