Skip to content

Create documentation of remaining frontend tests and storybooks to write #31

@illume

Description

@illume

I want you to run the coverage testing report on the frontend test and then generate a document laying out the remaining frontend/ tests that need to be written to improve test coverage.

Maybe of the tests should be storybook tests. Especially for components.

I want the document to be structured something like below. Important is that there are task checkboxes in markdown that contain the minimal information required for someone to work on the issue. Including the related files and what to do.

Also check that each component has error states that are covered(rather than just do a console.error and not show the user anything) or loading states (if the component actually loads something).

Example, but please think first how best to display this based on what you find.

## Issues by Category

### XXX

There are missing error states in this components

- [ ] Settings/PluginSettings: test coverage: `frontend/src/components/App/PluginSettings/PluginSettings.stories.tsx` - Add missing states for XXX story

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions