-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
feat(ui): insert message "no tests found" in ui #7366
Merged
hi-ogawa
merged 2 commits into
vitest-dev:main
from
DevJoaoLopes:feature/insert-no-tests-found-ui
Feb 3, 2025
Merged
feat(ui): insert message "no tests found" in ui #7366
hi-ogawa
merged 2 commits into
vitest-dev:main
from
DevJoaoLopes:feature/insert-no-tests-found-ui
Feb 3, 2025
Conversation
This file contains 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
✅ Deploy Preview for vitest-dev ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
6 tasks
hi-ogawa
reviewed
Feb 3, 2025
DevJoaoLopes
force-pushed
the
feature/insert-no-tests-found-ui
branch
from
February 3, 2025 00:42
2f35df6
to
94e35c6
Compare
DevJoaoLopes
commented
Feb 3, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
hi-ogawa
approved these changes
Feb 3, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
hi-ogawa
changed the title
feat (ui): insert message "no tests found" in ui
feat(ui): insert message "no tests found" in ui
Feb 3, 2025
renovate bot
added a commit
to mmkal/expect-type
that referenced
this pull request
Feb 3, 2025
##### [v3.0.5](https://github.com/vitest-dev/vitest/releases/tag/v3.0.5) ##### 🚀 Features - **ui**: Insert message "no tests found" in ui - by [@DevJoaoLopes](https://github.com/DevJoaoLopes) in vitest-dev/vitest#7366 [<samp>(92da4)</samp>](vitest-dev/vitest@92da490bd) ##### 🐞 Bug Fixes - Validate websocket request - by [@hi-ogawa](https://github.com/hi-ogawa) and [@AriPerkkio](https://github.com/AriPerkkio) in vitest-dev/vitest#7317 [<samp>(191ef)</samp>](vitest-dev/vitest@191ef9e34) - Don't toggle cli cursor on non-TTY - by [@AriPerkkio](https://github.com/AriPerkkio) in vitest-dev/vitest#7336 [<samp>(3c805)</samp>](vitest-dev/vitest@3c8050e69) - **vite-node**: Differentiate file url with hash and query - by [@hi-ogawa](https://github.com/hi-ogawa) in vitest-dev/vitest#7365 [<samp>(926ca)</samp>](vitest-dev/vitest@926ca9546) ##### [View changes on GitHub](vitest-dev/vitest@v3.0.4...v3.0.5)
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.
Description
closes #7256
no_tests_found.webm
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
pnpm-lock.yaml
unless you introduce a new test example.Tests
pnpm test:ci
.Documentation
pnpm run docs
command.Changesets
feat:
,fix:
,perf:
,docs:
, orchore:
.