Open sheremet-va opened 3 hours ago
The custom type is identical to the test type; the only difference is that it's initiated by calling getCurrentSuite().task(). Users of the API can attach their own custom properties to differentiate between built-in tests and custom tests.
test
getCurrentSuite().task()
Custom
'test'
No response
We might also be able to remove the type = 'custom' before Vitest 3 🤔 (By replacing it with type = 'test') I am not sure how breaking it is 🤔
type = 'custom'
type = 'test'
Clear and concise description of the problem
The custom type is identical to the
test
type; the only difference is that it's initiated by callinggetCurrentSuite().task()
. Users of the API can attach their own custom properties to differentiate between built-in tests and custom tests.Suggested solution
Custom
type now in 2.2'test'
in 2.3Custom
in Vitest 3Alternative
No response
Additional context
No response
Validations