chore: migrate type tests to TSTyche assertions (part one)#6726
Merged
mcollina merged 5 commits intoJun 7, 2026
Conversation
Signed-off-by: mrazauskas <tom@mrazauskas.de>
mrazauskas
commented
May 18, 2026
4 tasks
4 tasks
Tony133
approved these changes
May 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Following up on #6532
Split from #6525
This PR follows up on #6532 and migrates assertions in the following types of tests to TSTyche:
For the second part of migration see #6727. Hopefully, a smaller PR makes it easier to review the changes.
Changes
A few notes on the changes made:
tsdassertions, the expected value comes first (differently from JavaScript assertions), so I had to swap expected and actual like here:.toBe()instead of.toBeAssignableTo()(assignability can be assumed)@ts-expect-errorwith.not.toBeCallableWith()(improves readability)Checklist
npm run test && npm run benchmark --if-presentand the Code of conduct