| | 1 | = WPT and WebKit Tests = |
| | 2 | ''by Youenn Fablet'' |
| | 3 | |
| | 4 | - I love WPT because it is freemium |
| | 5 | - WPT runs in 4 different browsers |
| | 6 | - Lots of results |
| | 7 | - Identify test areas where webkit can make things better |
| | 8 | - But… WPT need you |
| | 9 | - Sometimes you need to share the meals |
| | 10 | - `Tools/Scripts/import-w3c-tests -t web-platform-tests/myshiny-api` |
| | 11 | - `Tools/Scripts/import-w3c-tests -t web-platform-tests/myold-stuff grep -R FAIL LayoutTests/imported/w3c/wenb-platform-tests/my-old-stuff` |
| | 12 | - When you land a patch you land layout tests |
| | 13 | - Pre-requisite so that you use testharness.js |
| | 14 | - `Tools/Scripts/export-w3c-tests` |
| | 15 | - `Tools/Scripts/webkit-patch upload` |
| | 16 | - Requirements: |
| | 17 | - Have a GitHub Account |
| | 18 | - Have a fork of https://github.com/web-platform-tests/wpt on GitHub |
| | 19 | - Issues? Talk to Youenn |
| | 20 | - `testharness.js` as default framework to write LayoutTests |
| | 21 | - “Can we fix testharness.js first? |
| | 22 | - No, we should do it in parallel |
| | 23 | - Automate our import/export workflow |
| | 24 | - 7K tests being imported and re-synced by a person |
| | 25 | - |
| | 26 | Questions: |
| | 27 | |
| | 28 | What about tests for internals? |
| | 29 | |
| | 30 | - Tests using internals the script will say “no” |
| | 31 | - There is a proposal that any mocking WebDriver |
| | 32 | - Use WebDriver instead |
| | 33 | - For mouseclicks and events, use WebDriver instead |
| | 34 | - For internal APIs, push internals in WPT as well |
| | 35 | - We use internals for feature, would be useful to expose to developers |
| | 36 | - We should standardize WebDriver tests |
| | 37 | - Get other browser vendors and share internal apis for high value areas |
