Use Vitest names for testing globals #999
Merged
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.
Vitest offers much of the functionality that Mocha does. It provides a
describe()
function,it()
, as well as hooks likebeforeEach()
andafterEach()
. However, there are some differences:before()
hook maps to VitestbeforeAll()
.after()
hook maps to VitestafterAll()
.it()
andspecify()
are synonyms. In Vitest, it'sit()
andtest()
. We usespecify()
for one test where it was awkward to start the test title with "it". I've replaced that use ofspecify()
withtest()
.A future PR will actually replace Mocha with Vitest. However, it'll reduce the size of that PR to start renaming these globals now. This PR uses Vitest names for testing globals, making replacements along the lines of what's described above. It then specifies those names in the ESLint config. Related issue: #671
What has been done to verify that this works as intended?
Testing and linting continue to pass.
Before submitting this PR, please make sure you have:
npm run test
andnpm run lint
and confirmed all checks still pass OR confirm CircleCI build passes