Skip to content

docs: add tip for using HTML reporter on CI#10023

Open
hi-ogawa wants to merge 12 commits intovitest-dev:mainfrom
hi-ogawa:docs/zipview-ci-report-viewer
Open

docs: add tip for using HTML reporter on CI#10023
hi-ogawa wants to merge 12 commits intovitest-dev:mainfrom
hi-ogawa:docs/zipview-ci-report-viewer

Conversation

@hi-ogawa
Copy link
Copy Markdown
Collaborator

@hi-ogawa hi-ogawa commented Mar 30, 2026

Description

I added a general CI usage of HTML reports as example, then did a small mention of https://zipview.hiro18181.workers.dev/ We could tweak zipview and host under vitest.dev domain, but not sure if it can improve the experience in a meaningful way.

EDIT: Now the code lives in https://github.com/vitest-dev/viewer and available in https://viewer.vitest.dev/

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

  • It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
  • Ideally, include a test that fails without this PR but passes with it.
  • Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.
  • Please check Allow edits by maintainers to make review process faster. Note that this option is not available for repositories that are owned by Github organizations.

Tests

  • Run the tests with pnpm test:ci.

Documentation

  • If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

  • Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

hi-ogawa and others added 2 commits March 30, 2026 12:45
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…ipview

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@netlify
Copy link
Copy Markdown

netlify bot commented Mar 30, 2026

Deploy Preview for vitest-dev ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 87f8ebd
🔍 Latest deploy log https://app.netlify.com/projects/vitest-dev/deploys/69c9f6c2fc9fba0008fe5f15
😎 Deploy Preview https://deploy-preview-10023--vitest-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify
Copy link
Copy Markdown

netlify bot commented Mar 30, 2026

Deploy Preview for vitest-dev ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 49e4c16
🔍 Latest deploy log https://app.netlify.com/projects/vitest-dev/deploys/69ca4a012f31790008d7f891
😎 Deploy Preview https://deploy-preview-10023--vitest-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

…term

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@hi-ogawa hi-ogawa marked this pull request as ready for review March 30, 2026 04:16
@hi-ogawa hi-ogawa changed the title docs: add tip for using HTML reports as CI artifacts docs: add tip for using HTML reporter on CI Mar 30, 2026
docs/guide/ui.md Outdated
path: html/

- name: Report summary
run: echo "[View HTML report on Zipview](https://zipview.hiro18181.workers.dev/?url=${{ steps.upload-report.outputs.artifact-url }})" >> $GITHUB_STEP_SUMMARY
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't we host it in our docs? zipview.vitest.dev

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It maybe simpler to use https://vitest.dev/zipview. Let me test a bit.

Copy link
Copy Markdown
Member

@sheremet-va sheremet-va Mar 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, I think it should be published and hosted by us, not the external website. Just redirecting it doesn't solve the issue

It should be under our domain is the point I am making

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cf79c50 This isn't 30x redirection though. It's served directly on https://deploy-preview-10023--vitest-dev.netlify.app/zipview/

Anyways, I can move it to vitest netlify account and also repo https://github.com/hi-ogawa/zipview to under https://github.com/vitest-dev

What do we need to do for these?

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.

feat: hosted viewer for HTML report artifacts (zero-install, browser-only)

3 participants