Closed AmoebaChant closed 1 month ago
Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s). To prevent this PR from going to the changelog marked it with the "skip changelog" label.
Snapshot stored with reference name: refs/pull/15121/merge
Test environment: https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15121/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15121/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/15121/merge https://sandbox.babylonjs.com/?snapshot=refs/pull/15121/merge https://gui.babylonjs.com/?snapshot=refs/pull/15121/merge https://nme.babylonjs.com/?snapshot=refs/pull/15121/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/15121/merge#BCU1XR#0
WebGL2 visualization test reporter:
Visualization tests for WebGPU (Experimental) Important - these might fail sporadically. This is an optional test.
I use the Jest Runner VSCode extension, which lets you run or debug individual suites or tests. It's the only Jest test runner VSCode extension that has worked reliably for me across many different repos. This is what it looks like in VSCode (see the Run|Debug
CodeLens annotations by the red lines I drew next to them):
If no one has a strong preference for a different extension, maybe we should add this one (
firsttris.vscode-jest-runner
) to extensions.json
?
Let s check both with Raanan tomorrow :-) honestly no prefs but love that we make testing/debugging tests easier
I love both methods. I personally use command line to run tests, but would be great to support all methods, as long a they don't collide. Let's add the extension to the recommended extensions as it can be very helpful, and get this also merged as well, so people can still select a file to test without installing the extension
This VSCode launch config will build then run just the unit test file current selected in VSCode, making it easier to iterate quickly on a single unit test file.