The completed ECMAScript 6 specification will make for a daunting “to-do” list
for implementors, but the promise of June 18 (besides the
is stability. Any ambiguities one might expect from a working draft will be
resolved (we hope!), so implementors can assess the correctness of their work
objectively. And because the spec will not change from that day onward,
compliance will no longer be a moving target.
This is where Bocoup and Google come in.
We’re collaborating with the V8 team to improve Test262’s coverage of all the new functionality. The V8 project already has a good number of sweet, sweet ES6 tests (seehere andhere). To jump-start the process, we’re working to port those tests to the Test262 harness. After that, we’ll focus on writing brand new tests. We’re prioritizing the parts of the specification that are least likely to change and most likely to trip up implementors (i.e. classes, iterators, lexical scoping, etc.), but our goal is to cover as much as the specification as possible. We’ll apply our own experience learning the ropes of Test262 to improve the experience for others. This means updating the documentation when necessary and keeping an eye out for ways to optimize the development workflow.
So what can you do? For starters, you can watch this space for more info on contributing tests. If you’re feeling ambitious, consider getting your hands dirty and implement a feature or two in your favorite engine! Finally, we can’t forget that no matter how well-designed or well-tested, these features will be useless if they aren’t deployed. So please: continue encouraging adoption of the most progressive, open platforms within your company and among your friends!