-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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(reporters): summary
option for verbose
and default
reporters
#6893
Open
AriPerkkio
wants to merge
5
commits into
vitest-dev:main
Choose a base branch
from
AriPerkkio:feat/reporter-something-new
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
feat(reporters): summary
option for verbose
and default
reporters
#6893
AriPerkkio
wants to merge
5
commits into
vitest-dev:main
from
AriPerkkio:feat/reporter-something-new
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
AriPerkkio
commented
Nov 11, 2024
✅ Deploy Preview for vitest-dev ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
@vitest/browser
@vitest/coverage-istanbul
@vitest/expect
@vitest/coverage-v8
@vitest/mocker
@vitest/pretty-format
@vitest/runner
@vitest/snapshot
@vitest/spy
@vitest/ui
@vitest/utils
vite-node
vitest
@vitest/web-worker
@vitest/ws-client
commit: |
AriPerkkio
force-pushed
the
feat/reporter-something-new
branch
7 times, most recently
from
November 11, 2024 19:17
5629c8f
to
9f5803e
Compare
sheremet-va
reviewed
Nov 11, 2024
AriPerkkio
force-pushed
the
feat/reporter-something-new
branch
2 times, most recently
from
November 12, 2024 09:49
0e315ff
to
77e34b2
Compare
Merged PR that affects the output: #6805 (it now prints a |
AriPerkkio
force-pushed
the
feat/reporter-something-new
branch
3 times, most recently
from
November 14, 2024 13:39
b7a381c
to
db6ec84
Compare
AriPerkkio
force-pushed
the
feat/reporter-something-new
branch
from
November 14, 2024 14:54
db6ec84
to
4509988
Compare
4 tasks
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
stdout
andstderr
to main thread tinylibs/tinypool#104Adds new
summary: boolean
option forverbose
anddefault
reporters. This option enables test summary that is shown below test results. This option is enabled by default. I would not consider this as breaking change, rather as bug fix for issues linked above.Running Vitest's
test/core
tests - left one ismain
, right one is this PR:vitest-reporter-before-and-after.webm
Most of the changes are related to
listRenderer.ts
removal. This is replaced withwindowedRenderer.ts
. After this PR we should do similar changes fordotRenderer
andtableRenderer
, and remove wholelog-update
from Vitest core.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:
.