There's infrastucture work to be done to let the test262 test harness run tests as modules. Again, the test262 github is the right place to discuss that issue.
As for the matter of this "missing" coverage: in their V8 implementation, the code generated for modules simply isn't that different from the code generated for other JS code. So while this might be a nice sanity check to have in the fture, it's not something that I'd expect to actually provide much more value in the "code coverage" sense. On Wed, Jun 21, 2017 at 1:04 PM, PhistucK <phist...@gmail.com> wrote: > Will it be a lot of effort to just run the tests and create a list of > failures? I can go over a manageable part of them and see if something > looks fishy. > > > ☆*PhistucK* > > On Wed, Jun 21, 2017 at 9:07 PM, <n...@chromium.org> wrote: > >> I expect a significant number of tests will fail due to the different >> semantics, thus it would take a lot of time to evaluate the results. >> >> >> On Wednesday, June 21, 2017 at 7:49:29 PM UTC+2, PhistucK wrote: >>> >>> Since this (intent) is a big feature, I think it would be appropriate to >>> run the entire suite in a module scope before it is shipped. >>> Do you think it would take a lot of work to do that? >>> >>> >>> ☆*PhistucK* >>> >>> On Wed, Jun 21, 2017 at 8:27 PM, Adam Klein <ad...@chromium.org> wrote: >>> >>>> On Wed, Jun 21, 2017 at 9:44 AM, PhistucK <phist...@gmail.com> wrote: >>>> >>>>> Has anyone run the full test262 test suite within a module scope, just >>>>> to make sure all of the ordinary features work there the same? >>>>> (I understand that from a point of view of an implementor, this might >>>>> seem unnecessary, because it is the same engine, but who knows, it may >>>>> uncover hidden peculiarities in the engine) >>>>> >>>> >>>> I don't know if anyone has done such a thing, but test262 does already >>>> include metadata that allows tests to be run in strict mode, sloppy >>>> (non-strict) mode, or both; I could imagine it being extended to make it >>>> easy for test runners to run tests as modules as well. >>>> github.com/tc39/test262/issues would be the place to raise that >>>> feature request. >>>> >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "blink-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to blink-dev+unsubscr...@chromium.org. >> To view this discussion on the web visit https://groups.google.com/a/ch >> romium.org/d/msgid/blink-dev/a0cfab54-5c05-4c81-8a60-a73576 >> 2922ce%40chromium.org >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/a0cfab54-5c05-4c81-8a60-a735762922ce%40chromium.org?utm_medium=email&utm_source=footer> >> . >> > > -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
