Skip to content

Document the test-running architecture in more detail, and perhaps put the tests on GitHub? #3196

Description

@ExplodingCabbage

Although I can see what feature tests you guys are using by viewing the source at http://tests.caniuse.com/, it's not a wholly obvious or convenient way to view the tests, and the only contributing method described at http://tests.caniuse.com/submit.html is to email in tests. Wouldn't it be better for tests to be part of this repository, and for new tests to be submitted by PR? This would make the process more visible and permit more discussion.

It would also be useful for contributors to know what system you have (if any) for running the tests on old browsers. The "about" at http://tests.caniuse.com/ suggests that the test suite is for testing upcoming browsers, which implies to me that you don't have a mechanism for running all tests across old browsers (using a tool like Sauce Labs), and that as such adding a test for a feature won't be sufficient to automatically generate a historical support table... but I'm not sure if I'm inferring too much. It would be nice to have this point spelt out explicitly.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions