-
-
Notifications
You must be signed in to change notification settings - Fork 176
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
✨(vitest) Introduce new built-in fuzz
#4200
base: main
Are you sure you want to change the base?
Conversation
The new built-in is `fuzz`. It came out of a discussion started on Vitest's official repository. Compared to previously proposed `it.prop` and related, it uses the APIs offered by Vitest to plug itself. It feels more aligned with the phylosophy currently adopted by the Vitest with a dedicated keywork per kind of runner. It will probably replace the `it.prop` and related really soon.
Still to do in order to merge this PR:
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 7927040:
|
Codecov Report
@@ Coverage Diff @@
## main #4200 +/- ##
=======================================
Coverage 94.71% 94.71%
=======================================
Files 210 210
Lines 5958 5958
Branches 1370 1370
=======================================
Hits 5643 5643
Misses 299 299
Partials 16 16
Flags with carried forward coverage won't be shown. Click here to find out more. |
The new built-in is
fuzz
. It came out of a discussion started on Vitest's official repository.Compared to previously proposed
it.prop
and related, it uses the APIs offered by Vitest to plug itself. It feels more aligned with the phylosophy currently adopted by the Vitest with a dedicated keywork per kind of runner.It will probably replace the
it.prop
and related really soon.Category:
Potential impacts: