ttwf.md

Contributing to Test262

Generally useful links:

• test262 on Github
• ES6 Specification
• ES5 Specification

Finding Projects

• Areas Needing Coverage - anything red (which is everything) can be tested.
• Bug Tracker (recently replaced by the GitHub issue tracker).
• New observable behavior of Proxies (for example)
• Talk to me!

Current ES6 Implementations

Kangax's Compatibility Table gives a high level overview of what features are implemented where, though even green items may be very incomplete.

• IE11
• Firefox Nightly
• Chrome Canary
• Traceur
• Continuum

Developing test262 tests is easier with a command-line implementation. Here are some useful ones:

• Nightly NodeJS
• Nightly JSShell (SpiderMonkey)

Contributing

Unfortunately, there are some IP issues to work out yet with ECMA regarding allowing community contributions. These should be resolved soon, but in the meantime the ideal process is unclear. The current guidance is to license put a CC0 public domain disclosure at the top of each source file.

Other than that, use the standard fork & pull request workflow. Put your tests under test/suite/es6/<feature name here>. This is temporary until a final organizational structure for ES6 is determined.

NOTE: If you are on Windows, beware of path length limitations. Best to clone to a very shallow directory.

Implementing Tests

• Example test: Sputnik-style (usually nicer for language-level tests)
• If you want to write Proxy Trap tests, this helper might be useful.
• Tests are stored under test/suite directory and should serve as good examples. Chapter 15 tests are good examples of library tests (like Arrays and Strings and such), whereas earlier chapters have more language testing.
• Running the tests is probably easiest by pasting into some browsers' dev tools. But, you can run on the command line using Python 2 by invoking python tools\packaging\test262.py --command "jsshell" es6.