Skip to content
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

chore(deps): update dependency vitest to v2 #117

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 4, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vitest (source) 0.34.6 -> 2.1.5 age adoption passing confidence

Release Notes

vitest-dev/vitest (vitest)

v2.1.5

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v2.1.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v2.1.3

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v2.1.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.0

Compare Source

This release makes another big change to the Browser Mode by introducing locators API:

test('renders blog posts', async () => {
  const screen = page.render(<Blog />)

  await expect.element(screen.getByRole('heading', { name: 'Blog' })).toBeInTheDocument()

  const [firstPost] = screen.getByRole('listitem').all()

  await firstPost.getByRole('button', { name: 'Delete' }).click()

  expect(screen.getByRole('listitem').all()).toHaveLength(3)
})

You can use either vitest-browser-vue, vitest-browser-svelte or vitest-browser-react to render components and make assertions using locators. Locators are also available on the page object from @vitest/browser/context.

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v2.0.5

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v2.0.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.0.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v2.0.2

Compare Source

v2.0.1

Compare Source

   🐞 Bug Fixes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/major-testing-packages branch 17 times, most recently from a1a9316 to 6d1890f Compare December 11, 2023 11:33
@renovate renovate bot force-pushed the renovate/major-testing-packages branch 13 times, most recently from 0e996e5 to bd3bf35 Compare December 17, 2023 13:34
@renovate renovate bot force-pushed the renovate/major-testing-packages branch 7 times, most recently from 23f88db to bd7883e Compare October 14, 2024 19:41
@renovate renovate bot force-pushed the renovate/major-testing-packages branch 5 times, most recently from 492fe07 to bec29cd Compare October 20, 2024 22:38
@renovate renovate bot force-pushed the renovate/major-testing-packages branch 7 times, most recently from 508e18a to 8a13f70 Compare October 29, 2024 19:55
@renovate renovate bot force-pushed the renovate/major-testing-packages branch 4 times, most recently from 91dc282 to 683d5ee Compare November 6, 2024 03:34
@renovate renovate bot force-pushed the renovate/major-testing-packages branch 5 times, most recently from e601552 to 9724e72 Compare November 14, 2024 10:21
@renovate renovate bot force-pushed the renovate/major-testing-packages branch from 9724e72 to 646f794 Compare November 16, 2024 12:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants