Auto-tools/Projects/web-platform-tests: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Add project page for web-platform-tests)
 
(Add difficulty:easy links)
Line 27: Line 27:
= Bugs =
= Bugs =


Because a lot of the project is developed "upstream" on GitHub, not all of the bugs are in bugzilla.mozilla.org. Some useful links to find bugs are:
Because a lot of the project is developed "upstream" on GitHub, not all of the bugs are in bugzilla.mozilla.org.
 
== Good First Bugs ==
 
These tend to be labeled with difficulty:easy on GitHub:
 
* [https://github.com/w3c/web-platform-tests/labels/difficulty%3Aeasy web-platform-tests]
* [https://github.com/w3c/wptrunner/labels/difficulty%3Aeasy wptrunner]
* [https://github.com/w3c/wptserve/labels/difficulty%3Aeasy wptserve]
 
== Full Bug Lists ==


* [https://bugzilla.mozilla.org/buglist.cgi?list_id=11729743&resolution=---&classification=Components&query_format=advanced&component=web-platform-tests&product=Testing Bugzilla]
* [https://bugzilla.mozilla.org/buglist.cgi?list_id=11729743&resolution=---&classification=Components&query_format=advanced&component=web-platform-tests&product=Testing Bugzilla]

Revision as of 18:59, 12 January 2015

Overview

web-platform-tests is a testsuite designed for cross-browser testing of web features like CSS and DOM APIs.

The aim of this project is to allow us to run the full set of web-platform-tests in gecko, and create an easy workflow for contributing back to the upstream.

Source and Documentation

The overall web-platform-tests project is hosted on github and documented at testthewebforward.org. This site contains notes on how to run and write tests.

The tool we use for running the tests is wptrunner, which is documented on readthedocs.

The tests use a custom web server, wptserve, which also has documentation on readthedocs.

Gecko-specific integration lives in-tree and is documented in some README files.

Future Project Goals

  • Improved support for upstreaming tests from gecko directly into the upstream repository.
  • Support reliable testing in automation for debug builds.
  • Allow running CSS tests using wptrunner.
  • More sophisticated reftest matching for cases where deterministic pixel equality isn't achievable.

Bugs

Because a lot of the project is developed "upstream" on GitHub, not all of the bugs are in bugzilla.mozilla.org.

Good First Bugs

These tend to be labeled with difficulty:easy on GitHub:

Full Bug Lists