Show when user can't connect because of a bad token (#2105)
* Reapply "Add ping pong health, remove a timeout interval, fix up netwo… (#1771)
This reverts commit 1913519f68.
* Fix build errors
* Add new error states to network status notification
* Remove unused variable
* Refactor to use Context API for network status
* Don't do any stream events if network is not ok
* Catch LSP errors on bad auth
* Show when authentication is bad (cookie header only)
* Fix formatting
* Fix up types
* Revert awaiting on lsp failure
* Fix tsc
* wip
* wip
* fmt
* Fix typing
* Incorporate ping health; yarn make:dev; faster video stream loss notice
* A snapshot a day keeps the bugs away! 📷🐛 (OS: ubuntu)
* run ci pls
* run ci pls
* A snapshot a day keeps the bugs away! 📷🐛 (OS: ubuntu)
* run ci pls again
* Remove unused variables
* Add new instructions on running Playwright anywhere
* Please the Playwright. Praise the Playwright.
* Correct a vitest
* A snapshot a day keeps the bugs away! 📷🐛 (OS: ubuntu)
* ci again
* Fix tests unrelated to this PR
* Fix flakiness in for segments tests
* Bump to 2 workers
* fmt
* A snapshot a day keeps the bugs away! 📷🐛 (OS: ubuntu)
* fmt
* fmt
* Fixups
* A snapshot a day keeps the bugs away! 📷🐛 (OS: ubuntu)
* ci
* Set workers to 1
* Wait for network status listeners before connecting
* Fix initial connection requirements and trying 2 workers again
---------
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
			
			
This commit is contained in:
		
							
								
								
									
										36
									
								
								README.md
									
									
									
									
									
								
							
							
						
						
									
										36
									
								
								README.md
									
									
									
									
									
								
							@ -197,28 +197,32 @@ For more information on fuzzing you can check out
 | 
			
		||||
 | 
			
		||||
### Playwright
 | 
			
		||||
 | 
			
		||||
First time running plawright locally, you'll need to add the secrets file
 | 
			
		||||
For a portable way to run Playwright you'll need Docker.
 | 
			
		||||
 | 
			
		||||
After that, open a terminal and run:
 | 
			
		||||
 | 
			
		||||
```bash
 | 
			
		||||
touch ./e2e/playwright/playwright-secrets.env
 | 
			
		||||
printf 'token="your-token"\nsnapshottoken="your-snapshot-token"' > ./e2e/playwright/playwright-secrets.env
 | 
			
		||||
docker run --network host  --rm --init -it playwright/chrome:playwright-1.43.1
 | 
			
		||||
```
 | 
			
		||||
 | 
			
		||||
and in another terminal, run:
 | 
			
		||||
 | 
			
		||||
```bash
 | 
			
		||||
PW_TEST_CONNECT_WS_ENDPOINT=ws://127.0.0.1:4444/ yarn playwright test --project="Google Chrome" <test suite>
 | 
			
		||||
```
 | 
			
		||||
 | 
			
		||||
An example of a `<test suite>` is: `e2e/playwright/flow-tests.spec.ts`
 | 
			
		||||
 | 
			
		||||
YOU WILL NEED A PLAYWRIGHT-SECRETS.ENV FILE:
 | 
			
		||||
 | 
			
		||||
 | 
			
		||||
```bash
 | 
			
		||||
# ./e2e/playwright/playwright-secrets.env
 | 
			
		||||
token=<your-token>
 | 
			
		||||
snapshottoken=<your-snapshot-token>
 | 
			
		||||
```
 | 
			
		||||
then replace "your-token" with a dev token from dev.zoo.dev/account/api-tokens
 | 
			
		||||
 | 
			
		||||
then:
 | 
			
		||||
run playwright
 | 
			
		||||
 | 
			
		||||
```
 | 
			
		||||
yarn playwright test
 | 
			
		||||
```
 | 
			
		||||
 | 
			
		||||
run a specific test suite
 | 
			
		||||
 | 
			
		||||
```
 | 
			
		||||
yarn playwright test src/e2e-tests/example.spec.ts
 | 
			
		||||
```
 | 
			
		||||
 | 
			
		||||
run a specific test change the test from `test('...` to `test.only('...`
 | 
			
		||||
(note if you commit this, the tests will instantly fail without running any of the tests)
 | 
			
		||||
 | 
			
		||||
 | 
			
		||||
		Reference in New Issue
	
	Block a user