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

[Tracking]: Test Polish 💅 #30746

Open
2 of 27 tasks
JReinhold opened this issue Mar 4, 2025 · 0 comments · May be fixed by #30773
Open
2 of 27 tasks

[Tracking]: Test Polish 💅 #30746

JReinhold opened this issue Mar 4, 2025 · 0 comments · May be fixed by #30773
Assignees
Labels

Comments

@JReinhold
Copy link
Contributor

JReinhold commented Mar 4, 2025

Stakeholders: @JReinhold, @yannbf, @ghengeveld

This is a tracking issue for the Test Polish project. The overall goal of the project is to polish up the new Testing-features, including improving existing features, introducing new minor ones, and fixing bugs.

Milestones 🚩

Update Testing Module UI

Owner: @ghengeveld

  • Update sidebar context menu
  • Update testing module UI
  • Make Coverage status update on watched changes
  • Bring back green border UI for changing settings. Note: May depend on Change Test Provider Architecture milestone
  • Add tooltips
  • Navigate to panel on status click
  • Add pulsing status when running stories
  • Update docs with new screenshots (@kylegach)

Handle unhandled errors

Owner: @yannbf

  • Research if Vitest v3 already solves this problem
  • Research how this will be surfaced to the user (UI?) - does it fit with the existing error UI we have in SB?
  • Experiment with the fix proposed by Tom in the GH issue, discover edge cases
  • Addon Test: Improve unhandled error messages #30754

Experimental CDP functionality

Owner: @yannbf

  • Write recipe
  • Write RFC including the recipe
  • Add telemetry to collect metric on the recipe usage

Change Status Architecture

Owner: @JReinhold

  • Add new Status Store
  • Add useStatusStore manager-hook
  • Update Addon Test to use new Status Store
  • Update VTA to use new Status Store
  • Remove existing Status API
  • Write migration notes

Change Test Provider Architecture

Owner: @JReinhold

  • Add new Test Provider Store
  • Addon Test: Migrate pending/running/etc. state to internal (existing) store
  • Addon Test: Replace test progress handling with direct calls to Status Store
  • VTA: Migrate pending/running/etc. state to internal store
  • VTA: Replace test progress handling with direct calls to Status Store
  • Remove existing Test Provider API (except for render and sidebarContextMenu)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

3 participants