stacklok / stacklok/toolhive-studio
[Task] Have a more sophisticated way to test "toast messages"
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 167
- Forks
- 24
- Avg merge
- 11h 32m
- Merged PRs (30d)
- 91
Description
right now, whenever a test needs to verify what toast messages were displayed, we need to add a new manual mock in each test file.
There should be a super easy and standardized way of doing this without a lot of extra code/boilerplate.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the test files that manually mock toast messages and compare how each mock is used. Define completion as a shared, standardized way for tests to verify displayed toast messages without repeated per-file boilerplate, supported by relevant test coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100