histoire-dev / histoire-dev/histoire

Add interaction testing tool plugin

Open
#343 0 comments 2 reactions 0 assignees View on GitHub
enhancement: to triage
Dominant language
TypeScript
Stars
3.6k
Forks
212
PR merge metrics
No merged PRs in 30d

Description

### Clear and concise description of the problem

I think it would be nice if Interaction testing for each component could be done easily. Vitest can be embedded more natively.
I'm assuming something like [@storybook/addon-interactions](https://github.com/storybookjs/storybook/tree/next/code/addons/interactions). This plugin have Jest as dependency.

similar to https://github.com/histoire-dev/histoire/discussions/229

### Suggested solution

If you implement it, you will need an API that allows you to add panes to the Plugin API.
https://github.com/histoire-dev/histoire/discussions/240

### Alternative

_No response_

### Additional context

_No response_

### Validations

- [X] Follow our [Code of Conduct](https://github.com/histoire-dev/histoire/blob/main/CODE_OF_CONDUCT.md)
- [X] Read the [Contributing Guidelines](https://github.com/histoire-dev/histoire/blob/main/CONTRIBUTING.md).
- [X] Read the [docs](https://histoire.dev/guide/).
- [X] Check that there isn't [already an issue](https://github.com/histoire-dev/histoire/issues) that requests the same feature to avoid creating a duplicate.

Contributor guide

Open the contributing guide

Research direction

Start with the Plugin API discussion and the Storybook addon-interactions reference linked in the issue, then review how Vitest could be embedded natively. Done means an agreed pane API and an interaction-testing plugin that enables testing for each component.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
testing, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.