You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
build: Add Dockerfile for easily updating snapshots (#1071)
- Updated README to include new instructions on how to update snapshots
- Add snapshots for mac that weren't previously included
- Tested on M1 MacBook Pro
- Fixes#960
Snapshots are used by end-to-end tests to visually verify the output. Sometimes changes are made requiring snapshots to be updated. Since snapshots are platform dependent, you may need to use a docker image to [update snapshots for CI](https://playwright.dev/docs/test-snapshots). You mount the current directory into a docker image and re-run the tests from there.
117
+
Snapshots are used by end-to-end tests to visually verify the output. Sometimes changes are made requiring snapshots to be updated. Run snapshots locally to update first, by running `npm run e2e:update-snapshots`.
118
118
119
-
First start with a clean repo. `node_modules` and some other build output is platform dependent.
120
-
121
-
```
122
-
npm run clean
123
-
```
124
-
125
-
Next, start the docker image and open a bash shell inside of it:
Install npm dependencies and build the production app, pointing to an API running on your machine:
148
-
149
-
```
150
-
npm ci
151
-
VITE_CORE_API_URL=http://host.docker.internal:10000/jsapi npm run build
152
-
```
153
-
154
-
Next, run the tests and update the snapshots:
155
-
156
-
```
157
-
npm run e2e:update-snapshots
158
-
```
119
+
Once you are satisfied with the snapshots and everything is passing locally, you need to use a docker image to [update snapshots for CI](https://playwright.dev/docs/test-snapshots) (unless you are running the same platform as CI (Ubuntu)). Run `npm run e2e:update-ci-snapshots` to mount the current directory into a docker image and re-run the tests from there. **Note:** You must have [Docker installed](https://docs.docker.com/get-docker/), and `deephaven-core` must already be running on port 10000 on your local machine.
0 commit comments