feat: SW-1825 stepper component#106
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
099d681 to
2488d4e
Compare
owilliams-tetrascience
left a comment
There was a problem hiding this comment.
Looks good! 🚀 I only had one small comment but overall great work
| } | ||
|
|
||
| const meta: Meta<typeof ProcessFlow> = { | ||
| title: "Patterns/ProcessFlow", |
There was a problem hiding this comment.
Can you update this to "Design patterns". This was a recent change from UX
| ); | ||
| }); | ||
|
|
||
| it("does not call onStepSelect for disabled steps", () => { |
There was a problem hiding this comment.
I thinking generally most of these test should be covered in the storybook e2e tests? are any of these redundant?
There was a problem hiding this comment.
Yes they are, but one of the actions in this repo was complaining and fialing.
54321jenn-ts
left a comment
There was a problem hiding this comment.
LGTM. It's not a blocker but two points of feedback.
It'd be nice if you used our button group in your docs if possible #100
And for the left nav be sure to name it something human readable, like Process Flow or Stepper (not ProcessFlow)
blee-tetrascience
left a comment
There was a problem hiding this comment.
Requesting changes for test scope.
| @@ -0,0 +1,406 @@ | |||
| import { flushSync } from "react-dom"; | |||
There was a problem hiding this comment.
This adds a React component test suite in jsdom while the stories already exercise the rendering and interaction paths in a real browser. Repo guidance says component behavior should live in Storybook play tests and unit tests should cover pure logic. Could we remove the duplicated component assertions and keep only tests for helpers or constants that the stories cannot cover?
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Coverage Report
File Coverage
|
||||||||||||||||||||||||||||||||||||||||||||
Summary
Type of Change
Checklist
yarn lintpassesyarn buildpassesyarn test:allpassesTesting
Verification
Screenshots