Supporting multiple ECMAScript test suites

[Norbert Lindenberg]

test262 isn't a single test suite anymore: Right now there are three different test suites in the repository - ECMA-262 conformance, ECMA-262 best practices, and ECMA-402 conformance. Soon we may want to fork off an ES6 test suite as well.


What should the web site look like that provides access to three or more different test suites? Right now, you see
  http://test262.ecmascript.org
and you don't see
  http://test262.ecmascript.org/testcases_intl402.html
  http://test262.ecmascript.org/testcases_bestPractice.html

I propose we rename the site to
  http://tests.ecmascript.org
and then have
  http://tests.ecmascript.org/
as a welcome page with links to:
  http://tests.ecmascript.org/ecma-262/
  http://tests.ecmascript.org/ecma-262-bp/
  http://tests.ecmascript.org/ecma-402/
Later we'll add
  http://tests.ecmascript.org/ecma-262-6ed/
which will eventually become the new
  http://tests.ecmascript.org/ecma-262/


What should the corresponding bug database buckets look like? Right now, there's a
  Test262 | Test suite for Ecma-262 implementations
product with components
    Test Harness | The infrastructure for running test262 tests
    Test262 website | The test262.ecmascript.org website
    Tests | The individual tests that make up the test262 suite

I propose we change this to
  Test Suites | Test suites for ECMAScript implementations
    Test Harness | The infrastructure for running tests,
                   including the tests.ecmascript.org web site
    ECMA-262 Tests | The individual tests for ECMA-262
                     (Language Specification) conformance
    ECMA-402 Tests | The individual tests for ECMA-402
                     (Internationalization API) conformance


Comments?

Thanks,
Norbert