Fixed GL JS documentation about running render tests

GitOrigin-RevId: 2359690a2737a8f41c9694736e5c9697c040c2e7

Author: woodroof

test/README.md

@@ -17,8 +17,8 @@ npx playwright install chromium
 To run individual tests:
  - Unit tests: `npm run test-unit -- path/to/file.test.js`
    - e.g. `npm run test-unit -- test/unit/ui/handler/scroll_zoom.test.js`
- - Render tests: `npm run test-render -- -t "render-tests/render-test-name"` where the `render-test-name` can be any substring in the `test/integration/render-tests/` subdirectories
-   - e.g. `npm run test-render -- -t "render-tests/background-color/default"` or `npm run test-render -- -t "render-tests/line"`
+ - Render tests: `npm run test-render -- -t "render-test-name"` where the `render-test-name` can be any substring in the `test/integration/render-tests/` subdirectories
+   - e.g. `npm run test-render -- -t "background-color/default"` or `npm run test-render -- -t "line"`
 
 See [`test/integration/README.md#running-specific-tests`](./integration/README.md#running-specific-tests) and [Vitest documentation](https://vitest.dev/guide/cli.html#testnamepattern).
 

test/integration/README.md

@@ -68,7 +68,7 @@ During a test run, the test harness will use Mapbox GL JS to create an `actual.p
 After the test(s) have run, you can view the render test results in
 
 ```
-open ./test/integration/render-tests/vitest/render-tests.html
+open ./test/integration/render-tests/render-tests.html
 ```
 
 or for query tests in: