On Wed, 2014-09-17 at 17:28 -0700, Mike Shaver wrote:
> My experience looking for similar things for Seneca would recommend:
>
> - relatively isolated subsystem: they should have to internalize less than
> 1KLOC
> - multiple meaningful milestones
> - good existing test coverage
> - few/no spec loo
In bug 1069063[1], we have a contributor's patch for
Array.prototype.contains. While it contains (no pun intended) tests, there
are far more exhaustive tests available as contributions to test262[2].
I think we should import those tests, so the question is "how". Note that
the tests haven't yet la
2 matches
Mail list logo
