yujunjun/playwright
1
0
Fork 0
mirror of https://github.com/microsoft/playwright.git synced 2025-06-26 21:40:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(devops): more instructions on local development (#14607)

Browse Source
This commit is contained in:
Yury Semikhatsky 2022-06-02 17:51:07 -07:00 committed by GitHub
parent 74b846270b
commit 9f57ee337a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 28 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
browser_patches/README.md
View File

@ -41,6 +41,8 @@ This command will:
## 2. Developing a new change
### Creating new branch
You want to create a new branch off the `playwright-build` branch.
Assuming that you're under `$HOME/firefox` checkout:
@ -50,6 +52,32 @@ $ git checkout -b my-new-feature playwright-build
$ # develop my feature on the my-new-feature branch ....
```
### Building
Each browser has corresponding build script. `--full` options normally takes care of also installing required build dependencies on Linux.
```bash
./browser_patches/firefox/build.sh --full
```
### Running tests with local browser build
Playwright test suite may run against local browser build without bundling it.
```bash
# Run webkit tests with local webkit build
WKPATH=./browser_patches/webkit/pw_run.sh npm run wtest
# Run firefox tests with local firefox build on macos
FFPATH=/tmp/repackaged-firefox/firefox/Nightly.app/Contents/MacOS/firefox npm run ftest
# Run chromium tests with local chromium build on linux
CRPATH=~/chromium/src/out/Release/chrome npm run ctest
```
### Flakiness dashboard
You can look at the [flakiness dashboard](http://flaky.aslushnikov.com/) to see recent history of any playwright test.
## 3. Exporting your change to playwright repo
Once you're happy with the work you did in the browser-land, you want to export it to the `playwright` repo.