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]: Focused Tests 🎯 #29529

Open
1 of 6 tasks
JReinhold opened this issue Nov 4, 2024 · 0 comments
Open
1 of 6 tasks

[Tracking]: Focused Tests 🎯 #29529

JReinhold opened this issue Nov 4, 2024 · 0 comments

Comments

@JReinhold
Copy link
Contributor

JReinhold commented Nov 4, 2024

πŸ§‘β€πŸ€β€πŸ§‘ Who: @JReinhold, @ndelangen and @ghengeveld

This is a tracking issue for the Focused Tests 🎯 project. The purpose of this issue is to keep tracking of the overall status of the project and tasks, and plan everything around it. This project is a continuation of #29088 and is related to #29530 and #29531.

⚠️ Problem

The new Testing Module is great for running tests across all stories in the whole project, however often you are only working on a subset of stories or components, and therefore you only need to run a specific set of tests. Only running a subset of tests will be faster than running all tests all the time.

🏁 Goals

  1. Users can run tests at the story, component, or directory level.
  2. Other test providers/addons (eg. a11y) are also able to leverage this via a new Story Actions API

🚩 Milestones

Run individual stories

  1. JReinhold ndelangen
  2. JReinhold ndelangen
  3. JReinhold ndelangen

Nice-to-haves

  1. addon: test bug ci:normal
  2. JReinhold ndelangen
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Progress
Development

No branches or pull requests

3 participants