-
-
Notifications
You must be signed in to change notification settings - Fork 35.5k
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
Tests: Post Update Review #25417
Tests: Post Update Review #25417
Conversation
Use Qunit hooks to provision and cleanup global mocks.
Use Qunit hooks to provision and cleanup global mocks.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Format code for clearer error messages.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in tests.
Explicit block scope for variables used in supporting test code.
review
I've made a bunch of notes. One on this topic is about moving to vite / vitest. I'm sure you understand the benefits. Happy to reformat the tests in jest / vitest compatible units. The recent changes in the build and dropping babel (to let the final app bundler do the translation) means that this project nearly has a default vite config for a lib. Its fast, nice to have live test feedback as you develop (unit tests, preview, type checking, linting, vscode integration). Might pare nicely with the e2e puppeteer stuff. I'm not sure where these conversations happen. I've got a list of notes, questions, options. Not too fixed on any one direction except for filling in these unit tests while updating the documentation. Point me where to write them out. |
Maybe you can create a new issue and write them there? |
@mrdoob I'd like to get back to filling in tests. Is there anything I can do to break this up for review ? |
Related issue: none.
Description
This cleans up the unit tests to make them more consistent. Use Qunit hooks to provision and cleanup global mocks in Audio. Explicit block scope for variables used in tests.