Skip to content
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

Merged
merged 52 commits into from
Feb 6, 2023
Merged

Tests: Post Update Review #25417

merged 52 commits into from
Feb 6, 2023

Conversation

epreston
Copy link
Contributor

@epreston epreston commented Feb 2, 2023

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.

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.
@epreston epreston marked this pull request as ready for review February 3, 2023 04:10
Explicit block scope for variables used in supporting test code.
@epreston
Copy link
Contributor Author

epreston commented Feb 3, 2023

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.

@LeviPesin
Copy link
Contributor

Maybe you can create a new issue and write them there?

@epreston epreston changed the title Tests: Quality Review Tests: Post Update Review Feb 5, 2023
@epreston
Copy link
Contributor Author

epreston commented Feb 6, 2023

@mrdoob I'd like to get back to filling in tests. Is there anything I can do to break this up for review ?

@mrdoob mrdoob added this to the r150 milestone Feb 6, 2023
@mrdoob mrdoob merged commit 1ad78ef into mrdoob:dev Feb 6, 2023
@epreston epreston deleted the tests-quality-review branch February 6, 2023 09:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants