QA context from my CV
Chiurika includes CMS-driven homepage content, banners, collections, promotional sections, featured products, GraphQL content fetching, and responsive storefront behavior. That makes it useful for testing both content administration and customer-facing UI.
Risk & proposed scope
The key risks are incorrect product display, broken promotional content, stale cached data, slow content loading, and layout issues across screen sizes. The proposed scope compares CMS input, API response, and rendered page output.
Example test scenarios
- Create, update, hide, and reorder homepage banners; verify public rendering.
- Publish a collection with missing image, long title, sale label, and empty product state.
- Validate GraphQL response fields against the displayed UI content.
- Resize from mobile to desktop and inspect cards, banner crop, and call-to-action placement.
- Check loading, empty, and failed API states for content sections.
Evidence & release criteria
Evidence should link CMS entry, API response, page URL, viewport size, and screenshot. Release criteria should block incorrect product details, unreadable mobile layouts, and content that cannot be safely unpublished.