On 2014/09/18 15:15:50, domenic wrote:
> As this is a new unapproved feature, this needs intent-to-implement
mail.
Will send
> I guess this is the first time when somebody add test262 tests first and
patch
later, but I think we still want some tests in our tree (under
test/mjsunit/harmony)
I would really like us to break out of the pattern of creating our own
tests
separate from the vendor-independent ones. I am hoping we can pioneer that
process here. I am also going to be investigating improvements to test262
to
make writing tests there as easy as mjsunit ones (e.g. adding assert
helpers).
That is worthwhile (and I think that would be great in ideal world) but it
suffers from a couple of issues:
1. Currently, we do not run test262 tests on dev machines during
development,
relying on mjsunit for smoke testing (we run test262 on waterfall though)
2. Without seeing the tests, it is hard to evaluate the coverage this CL
has.
https://codereview.chromium.org/579973002/
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
