-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vitest Playwright #996
Vitest Playwright #996
Conversation
Waiting on #990 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was this meant to fix #990 vitest memory? I'm still getting the error running Body Loading 2471 that doesn't occur individually.
@a-crowell Yes, partly. We can ignore it in #990 for right now. |
@a-crowell @PepperLola @Dhruv-0-Arora Can you verify that you can run unit tests with no errors? Note an extra setup command that I'm about to add to the readme and package.json:
This installs the playwright browsers. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cleared!
exporter/SynthesisFusionAddin/src/Parser/SynthesisParser/Joints.py
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good
… still runs on the browser tho.
Description
We've been bouncing around the issue of vitest running node, when we have a web app. This PR adds playwright, to run both the development server and a headless browser for running unit tests to avoid issues of node environment compilation.
Motivation
I need to update Jolt Physics and something in the recent releases changed, such that it uses a
new URL()
call for getting the path to a file. This causes issues because vitest in a jsdom environment transformsnew URL()
calls to usinghttp://
paths, and if we use the node environment, we lose access to things like thewindow
.Physics Memory
This should have a new version of the Jolt Physics package that enables memory growth and maybe increases the default size.