Skip to content
Snippets Groups Projects
  1. Apr 27, 2017
  2. Apr 20, 2017
  3. Mar 06, 2017
  4. Mar 01, 2017
  5. Feb 07, 2017
  6. Nov 22, 2016
  7. Oct 19, 2016
  8. Jun 21, 2016
  9. Apr 18, 2016
    • jugglinmike's avatar
      Add documentation on interpreting tests (#508) · a657b64a
      jugglinmike authored
      The project's CONTRIBUTING.md was written with test authors in mind. It
      contains details on non-technical metadata (e.g. "author" and "es6id"),
      helper function usage, and preferred code structure. In addition, it
      elides certain low-level technical details on the requirements for the
      runtime environment.
      
      Introduce a new document targeted towards those executing the tests.
      Formalize all expectations regarding how the runtime environment should
      be defined, how metadata should be interpreted, and how results should
      be understood. This information has overlap with the CONTRIBUTING.md
      file, but it also contains details that are irrelevant to test authors.
      
      This document can serve as a more formal contract between Test262 and
      the implementors who consume it. This allows Test262 to unambiguously
      document future modifications to the formal requirements which in turn
      supports consumers who maintain their own test harnesses.
      a657b64a
Loading