| commit | 3e38d4736fd14ae29a07e90cf3388a20229976d5 | [log] [tgz] |
|---|---|---|
| author | Frederic Wang <fred.wang@free.fr> | Thu Aug 03 16:08:12 2023 |
| committer | moz-wptsync-bot <wptsync@mozilla.com> | Fri Aug 04 09:28:11 2023 |
| tree | 29000498505a48524400d6a16a1607f3c016270a | |
| parent | 56b76abba070ac91e80e40aabdd3d8a9ac868ef1 [diff] |
Export more table-related tests to WPT. * whitespace-trim-*: These tests are testing whitespace trimming in token elements but that's not described in MathML Core. Move them into internal WPT tests. * table-width-1,2,3,4: These tests verify that the intrinsic width is properly calculated so that MathML content don't overflow in tables. One of them is related to whitespace trimming, so extract it to internal WPT test. * test_bug330964.html: Convert this to a testharness test and move it into internal WPT test (this is testing mtable attributes that are not part of MathML Core). * semantics-4: Restore the original testcase and move it into internal WPT test with a failure annotation for now (as written it uses mtable@width attribute which is not part of MathML Core anyway). For details, see bug 1846930. * dir-6a: This was introduced in bug 330964 and involves table attributes that are not part of MathML Core. * css-spacing-1.html: This was introduced by bug 1187673 but is already covered by default-properties-on-the-math-root.html. * columnlines/rowlines: Tests for columnlines/rowlines attributes that are not part of the current version of MathML core. Move them to mozilla/tests/mathml/tables. Use Ahem for rowlines/columnlines-3* to make them more robust per bug 1309426. * mstyle-2: extract the case for mtable@align test to internal WPT mstyle-align.html since align is not part of MathML Core. Differential Revision: https://phabricator.services.mozilla.com/D185270 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1846945 gecko-commit: eb5aa026f738693b722af7b32caea4b100df2cdb gecko-reviewers: emilio
The web-platform-tests Project is a cross-browser test suite for the Web-platform stack. Writing tests in a way that allows them to be run in all browsers gives browser projects confidence that they are shipping software that is compatible with other implementations, and that later implementations will be compatible with their implementations. This in turn gives Web authors/developers confidence that they can actually rely on the Web platform to deliver on the promise of working across browsers and devices without needing extra layers of abstraction to paper over the gaps left by specification editors and implementors.
The most important sources of information and activity are:
wpt:matrix.org matrix channel; includes participants located around the world, but busiest during the European working day.If you'd like clarification about anything, don't hesitate to ask in the chat room or on the mailing list.
Clone or otherwise get https://github.com/web-platform-tests/wpt.
Note: because of the frequent creation and deletion of branches in this repo, it is recommended to “prune” stale branches when fetching updates, i.e. use git pull --prune (or git fetch -p && git merge).
See the documentation website and in particular the system setup for running tests locally.
The wpt command provides a frontend to a variety of tools for working with and running web-platform-tests. Some of the most useful commands are:
wpt serve - For starting the wpt http serverwpt run - For running tests in a browserwpt lint - For running the lint against all testswpt manifest - For updating or generating a MANIFEST.json test manifestwpt install - For installing the latest release of a browser or webdriver server on the local machine.wpt serve-wave - For starting the wpt http server and the WAVE test runner. For more details on how to use the WAVE test runner see the documentation.On Windows wpt commands must be prefixed with python or the path to the python binary (if python is not in your %PATH%).
python wpt [command]
Alternatively, you may also use Bash on Ubuntu on Windows in the Windows 10 Anniversary Update build, then access your windows partition from there to launch wpt commands.
Please make sure git and your text editor do not automatically convert line endings, as it will cause lint errors. For git, please set git config core.autocrlf false in your working tree.
The master branch is automatically synced to wpt.live and w3c-test.org.
Save the Web, Write Some Tests!
Absolutely everyone is welcome to contribute to test development. No test is too small or too simple, especially if it corresponds to something for which you've noted an interoperability bug in a browser.
The way to contribute is just as usual:
git checkout -b topic../wpt lint as described above.If you spot an issue with a test and are not comfortable providing a pull request per above to fix it, please file a new issue. Thank you!