@@ -26,7 +26,7 @@ the above evaluates the output of `docker-machine env default`.
26
26
27
27
### Step 1: Run the testing container
28
28
29
- Plotly.js uses ` docker-compose ` to ease the creation/stopping/deletion of the testing docker container.
29
+ We use ` docker-compose ` to ease the creation/stopping/deletion of the testing docker container.
30
30
31
31
Inside your ` plotly.js ` directory, run
32
32
@@ -40,8 +40,8 @@ as listed on [hub.docker.com](https://hub.docker.com/r/plotly/testbed/tags/) and
40
40
41
41
### Step 2: Run the image tests
42
42
43
- The image testing docker container allows plotly.js developers to (A ) run image
44
- comparison tests, (B ) run image export tests and (C ) generate baseline
43
+ The image testing docker container allows plotly.js developers to ([ A ] ( #a-run-image-comparison-tests ) run image
44
+ comparison tests, ([ B ] ( #b-run-image-export-tests ) run image export tests and ([ C ] ( #c-generate-or-update-existing-baseline-image ) ) generate baseline
45
45
images.
46
46
47
47
** IMPORTANT:** the image tests scripts do ** not** bundle the source files before
@@ -64,10 +64,10 @@ npm run test-image
64
64
```
65
65
66
66
which runs all image comparison tests in batch. If some tests fail, compare their outputs
67
- using ` npm run start-image_viewer ` .
67
+ by booting up the test image viewer using ` npm run start-image_viewer ` .
68
68
69
69
As an alternative to running all image comparison tests at once, you can provide
70
- a glob as argument to target one or multiple test mocks found in
70
+ a [ glob] ( https://github.com/isaacs/node-glob ) as argument to target one or multiple test mocks found in
71
71
[ ` test/image/mocks ` ] [ mocks ] .
72
72
For example,
73
73
0 commit comments