-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
refactor(tests): move image tests from qunit to vitest #10546
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
refactor(tests): move image tests from qunit to vitest #10546
Conversation
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
It seems that you opened a PR but you didn't add a line to the changelog file
|
@@ -17,6 +17,7 @@ export default defineConfig({ | |||
test: { | |||
pool: 'vmThreads', | |||
clearMocks: true, | |||
mockReset: true, |
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.
I noticed that spies were leaking between tests which made it very hard to test something in image suite
this made some other tests to break in Itext which I adapted
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.
yeah this should be the default honestly.
return img; | ||
} | ||
|
||
export async function createImage( |
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.
I reworked these helpers a bit
because the version from qunit was a bit crazy
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.
Consider some tests are super super old and written with different expertise compared to today standards and capabilities.
Build Stats
|
|
oh boy this one was intense
moves image tests from qunit to vitest