Google Git
Sign in
webkit / WebKit / 1b2e43137b3fcd62dfcd0f414f887092bb574341 / . / LayoutTests / imported / w3c / web-platform-tests / css
tree: 75d5b8a5e4c62fa637bec292ff97b5fa5d740e53 [path history] [tgz]
  1. css-align/
  2. css-animations/
  3. css-backgrounds/
  4. css-box/
  5. css-cascade/
  6. css-color/
  7. css-display/
  8. css-easing/
  9. css-font-loading/
  10. css-fonts/
  11. css-grid/
  12. css-images/
  13. css-inline/
  14. css-lists/
  15. css-logical/
  16. css-masking/
  17. css-multicol/
  18. css-overflow/
  19. css-overscroll-behavior/
  20. css-position/
  21. css-properties-values-api/
  22. css-pseudo/
  23. css-scoping/
  24. css-shadow-parts/
  25. css-shapes/
  26. css-sizing/
  27. css-syntax/
  28. css-text/
  29. css-text-decor/
  30. css-transitions/
  31. css-ui/
  32. css-values/
  33. css-writing-modes/
  34. cssom/
  35. cssom-view/
  36. geometry/
  37. mediaqueries/
  38. reference/
  39. selectors/
  40. support/
  41. WOFF2/
  42. .htaccess
  43. build-css-testsuites.sh
  44. README.md
  45. requirements.txt
  46. w3c-import.log
LayoutTests/imported/w3c/web-platform-tests/css/README.md

Introduction

This directory contains testsuites for CSS WG specifications, including ones that do not strictly speaking define CSS features, e.g., Geometry Interfaces.

The directories should be named like the specification's shortname, but without any level suffix.

As the test harness relies on the largely undocumented old CSS build system, this directory has a number of test requirements specific to it:

  • support files for a given test must live in an adjacent support directory;

  • tests must have a <link rel=help> pointing to what they are testing;

  • for each spec so linked, test filenames must be unique; and

  • support and reference files must have unique filenames within the entire css directory.

vendor-imports/ Directory

vendor-imports/ is a legacy directory where third parties historically imported their tests that originate and are maintained in an external repo. Files in this directory should never be modified in this repo, but should go through the vendor's process to be imported here.

Importing Old Branches

Given an old branch in git based against the old csswg-test repository, it can be moved over to the merged repo in one of two ways:

  • (Recommended:) Rebasing on top of web-platform-tests: with the old branch checked out, run git rebase -Xsubtree=css/ origin/master (or similar, depending on the name of the upstream remote).

  • Merging to web-platform-tests: with web-platform-tests' master branch checked out, run git merge -Xsubtree=css/ my_shiny_branch (or similar, depending on the name of your branch).

If you have a branch/bookmark in Mercurial, the process is more complicated:

  1. From the Mercurial repo, run hg export --git -r 'outgoing()' > foo.patch. This will export all the changeset shown in hg log -r 'outgoing()'; it's recommended you check this is the right set of changesets before continuing!

  2. Move to the git repo, and create a new branch based on web-platform-tests' master; e.g., git checkout -b hg-import origin/master (or similar, depending on the name of the upstream remote).

  3. Download hg-patch-to-git-patch and run python2 hg-patch-to-git-patch < foo.patch > bar.patch (where foo.patch is the path to the foo.patch you exported above).

  4. Run git am --directory=css/ < bar.patch.