NextCommerceCo / NextCommerceCo/spark
Robustness fixtures for real-content QA
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 9h 52m
- Merged PRs (30d)
- 18
Description
Problem: Spark's robustness expectations (long product names, missing images, large variant matrices, empty collections) live in design-QA checklists, not in anything runnable. Every QA pass improvises against whatever content the dev store happens to have.
Evidence: docs/section-specs/hero-image.md:123-134 (checklist states); no fixture set or seeded catalog anywhere in the repo; .preview/ is a single gitignored file.
Done when:
- A documented fixture set exists (product and content states covering long names, missing media, variant extremes, sold-out, empty collections) with a script or guide for seeding a dev store.
- The QA checklist references fixture states by name, so two people running QA test the same things.
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 reading docs/section-specs/hero-image.md:123-134 and inspect the repository for any dev-store seeding entry points. Define named fixture states for long names, missing media, variant extremes, sold-out products, and empty collections, then provide the documented seed script or guide and update the checklist to reference those names.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 66/100