feat(atomic): migrate commerce facet stories to MSW#7612
Conversation
|
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
@coveo/atomic
@coveo/atomic-hosted-page
@coveo/atomic-legacy
@coveo/atomic-react
@coveo/auth
@coveo/bueno
@coveo/create-atomic
@coveo/create-atomic-component
@coveo/create-atomic-component-project
@coveo/create-atomic-result-component
@coveo/create-atomic-rollup-plugin
@coveo/headless
@coveo/headless-react
@coveo/shopify
commit: |
|
Tip All tests passed and all changes approved!🟢 UI Tests: 367 tests unchanged |
c422b14 to
9df4533
Compare
b6bdd15 to
ca260c1
Compare
2e27277 to
2edec45
Compare
62f29ce to
43e289c
Compare
2edec45 to
f6e1ac9
Compare
43e289c to
2b42b6e
Compare
f6e1ac9 to
8a0bd11
Compare
2b42b6e to
8e1816a
Compare
8a0bd11 to
cee3997
Compare
Migrate atomic-commerce-facet, atomic-commerce-facets, atomic-commerce-numeric-facet, atomic-commerce-category-facet, and atomic-commerce-timeframe-facet stories to use MockCommerceApi MSW handlers for proper API mocking. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
8e1816a to
c5f8912
Compare
Problem
Commerce storybook stories for facet components don't use MSW for API mocking, making them less reliable and harder to test in isolation.
Solution
Migrate atomic-commerce-facet, atomic-commerce-facets, atomic-commerce-numeric-facet, atomic-commerce-category-facet, and atomic-commerce-timeframe-facet stories to use
MockCommerceApiMSW handlers.Each story now:
MockCommerceApimsw: {handlers: [...commerceApiHarness.handlers]}to parametersbeforeEach: () => { commerceApiHarness.clearAll(); }for test isolation