Supporting feature tests directly

Jordan Harband ljharb at gmail.com
Thu Mar 26 05:11:32 UTC 2015


I don't believe test262 can yet be run in a browser (only directly against
a browser engine), nor run in ES3 browsers (so that shimmed engines can be
tested) so that doesn't yet solve my use cases, although I can't speak for
Kyle.

On Wed, Mar 25, 2015 at 9:32 PM, James Kyle <me at thejameskyle.com> wrote:

> This exists: http://test262.ecmascript.org
>
>
>
> On Wed, Mar 25, 2015 at 8:12 PM, liorean <liorean at gmail.com> wrote:
>
>> As I see it, what might be more desireable than a straight shallow
>> feature test or feature support reporting feature would be an official
>> versioned test library, possibly including tests of pure internals, and a
>> new standard api for asking the engine for the results it gets for running
>> a certain test or set of tests. The engine could then either have its
>> results collected at build time and cashed results for that particular
>> build built into the api, or allow the user to require the result of
>> getting the test and executing it live, with the issues that comes with
>> that. One possible result, except the obvious success and fail, is of
>> course that a certain test didn't exist at the time of the build and thus
>> not tested.
>>
>> Of course, the earliest something like that could be in the language
>> would be ECMAScript 7...
>>
>
>
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20150325/b2df38a2/attachment.html>


More information about the es-discuss mailing list