Commit Graph

24 Commits

Author SHA1 Message Date
Jonah
7b59932b45
docs(contributing): update required node version (#29547)
Closes #29518

---------

Signed-off-by: Max Schmitt <max@schmitt.mx>
Co-authored-by: Max Schmitt <max@schmitt.mx>
2024-02-19 09:28:49 +01:00
Max Schmitt
4aa714c75d
chore(contribution guidelines): add note about filing an issue (#26716) 2023-08-26 08:13:59 +02:00
Kristo Jorgenson
a4a363f4f4
chore: upgrade @types/node to 16.x (#23429)
Co-authored-by: Max Schmitt <max@schmitt.mx>
2023-06-02 10:04:41 +02:00
Tomáš Hübelbauer
e550df060e
Enhance the forbidOnly mode message to guide the user towards the configuration option (#23146)
Hi, I am putting this PR out as a feeler to see if there's interested in
improving this error message, but the copy is by no means final and I am
open to improvement suggestions.

My intention here is to:
- Explain what a "focused item" is - that we're talking about a test and
it being focused is most likely down it using `only`
  
Are there other types of "items"? Are there other ways to make them
focused other than `only`?

- Explain why we're even in focused mode and how to control it

The default scaffolded Playwright config file includes a forbidMode
expression driven by whether `CI=1` is set.
I ran into this when trying to reproduce a CI issue locally so I had it
set and unknowingly entered focus only mode.
I wasn't aware this mode was a thing because I was using the default
configuration from `npm init` and did not familiarize myself with all
the options in it.

Is there a way to tell if we're in a TypeScript or JavaScript project in
this function? I would use that to display the configuration file name
with the right extension.

---------

Signed-off-by: Tomáš Hübelbauer <tomas@hubelbauer.net>
2023-05-25 13:32:49 -07:00
Peter Ng
253e3d2814
docs(contribution-guide): add min NPM/Node version requirement (#17754) 2022-10-04 12:17:25 +02:00
Dan Bjorge
8c7f8eda9f
docs(contributing): add instructions for testing doc changes (#15205) 2022-06-28 16:24:28 -07:00
Andrey Lushnikov
ddcce7a63a
devops: fix headlessness reporting to flakiness dashboard (#14069) 2022-05-10 09:03:47 -07:00
Zack Guo
4bbd38560a
docs(CONTRIBUTING.md): update how to run a specific test (#11697) 2022-02-01 16:08:08 -08:00
Max Schmitt
5ba7903ba0
devops: migrate from master to main branch (#10303) 2021-12-07 22:58:33 -08:00
Subramani
fb69ff30a9
docs: fix some English in CONTRIBUTING.md (#9641) 2021-10-21 08:29:12 -04:00
Dmitry Gozman
46a0213769
chore: remove internal uses of "folio" (#6931)
Replaced by "pwt" or "playwright test".
2021-06-06 22:07:07 -07:00
Sébastien Règne
d243ae7ede
doc(contribute): fix link to tests (#6499) 2021-05-11 09:27:30 -07:00
Max Schmitt
37b07adaab
docs: replace headful with headed (#6017) 2021-04-01 11:13:50 -07:00
Ross Wollman
0b6625bbad
docs: fix HEADFUL run instructions (#5980) 2021-03-29 20:04:44 -07:00
Dmitry Gozman
4ff7e1a419
chore: cleanup our build system (#4903)
- Consolidate our build and watch to a single build.js file.
- Update contributing docs.
- Remove unused scripts and package.json script entries.
2021-01-06 12:41:17 -08:00
Pavel Feldman
e0e836cb6e
doc: split classes into files (#4864) 2021-01-01 15:17:27 -08:00
Ross Wollman
e97badcca8
docs(CONTRIBUTING.md): Add build step (#2869)
* docs(CONTRIBUTING.md): Add build step

Without the build step, a fresh install without any previous
builds would get:

```
$ npm test

> playwright-internal@1.2.0-post test /Users/pw/code/playwright
> cross-env BROWSER=all node --unhandled-rejections=strict test/test.js

internal/modules/cjs/loader.js:1033
  throw err;
  ^

Error: Cannot find module '../lib/rpc/server/dispatcher'
Require stack:
- /Users/pw/code/playwright/test/environments.js
- /Users/pw/code/playwright/test/test.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:1030:15)
    at Function.Module._load (internal/modules/cjs/loader.js:899:27)
    at Module.require (internal/modules/cjs/loader.js:1090:19)
    at require (internal/modules/cjs/helpers.js:75:18)
    at Object.<anonymous> (/Users/pw/code/playwright/test/environments.js:23:34)
    at Module._compile (internal/modules/cjs/loader.js:1201:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1221:10)
    at Module.load (internal/modules/cjs/loader.js:1050:32)
    at Function.Module._load (internal/modules/cjs/loader.js:938:14)
    at Module.require (internal/modules/cjs/loader.js:1090:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/Users/pw/code/playwright/test/environments.js',
    '/Users/pw/code/playwright/test/test.js'
  ]
}
npm ERR! Test failed.  See above for more details.
```

Fixes #2868.

Co-authored-by: Andrey Lushnikov <aslushnikov@gmail.com>
2020-07-07 22:38:59 -07:00
Moshood Abidemi
dd6308ccd5
docs(CONTRIBUTING.md): fix typo in doc (#2169) 2020-05-09 17:43:24 -07:00
Vasilii Artemchuk
4c4fa8d38c
docs: some syntax fixes (#2116) 2020-05-07 12:33:35 -07:00
Arjun Attam
d354e9c21a
docs(contributing): clean up headings 2020-04-23 16:23:58 -07:00
Ross Wollman
fd17cfb5c1
docs(contributing): add info about skip and fail (#1944)
When contributing some test cases, I was a bit confused about if I should use `skip` and `fail`, the difference between the two, and how they interact with CI/CD tests passing or failing: https://github.com/microsoft/playwright/pull/1939#discussion_r413946012.

This is my attempt at explaining the difference, but feel free to edit to make it more clear and concise (and correct any inaccuracies).
2020-04-23 14:28:40 -07:00
Arjun Attam
9e9584441c
docs(troubleshooting): add dependencies for firefox and webkit (#1461) 2020-03-21 17:58:08 -07:00
Andrey Lushnikov
c881248062
docs(contributing.md): update CONTRIBUTING.md (#1286)
Fixes #1257
2020-03-07 17:29:22 -08:00
Arjun Attam
2f8049f3e4 docs: preparing readme for public release (#433) 2020-01-08 16:53:57 -08:00