Functional Coverage Map
Around 70% of storefront functionality is automated
The Schippers automation suite covers the MS Schippers hycommerce storefronts (NL, BE, FR, DE) with 197 automated test cases across 22 specs. Core shopping — home, navigation, search, catalog, product detail, cart, comparison, account and login — is solidly covered, backed by real-authentication end-to-end checkout journeys and a data-driven API contract layer. Coverage intentionally thins toward the edges: checkout payment variety, My Schippers depth, the knowledge centre, promotions logic, loyalty, and customer-service / returns flows.
01Coverage by functional area
Each area is scored on how much of its real customer-facing functionality is exercised by automated tests. Covered ≥ 75%, Partial 20–74%, None not yet automated.
02What is strongly covered
The suite is deepest where it matters most — the revenue-critical shopping path and the real B2B ordering journeys.
✔ Core shopping path
~168 store-scoped smoke cases verify render, navigation and interactivity across the NL/BE/DE storefronts — home, nav, search, catalog, cart and comparison.
✔ Real-auth e2e journeys
End-to-end login through the identity provider, including valid and invalid credentials for both NL and BE storefronts.
✔ Multi-method checkout
Real orders across Adyen, invoice re-order, and PGA direct-debit via sales-admin impersonation — not just a single happy path.
✔ Licence-gated purchasing
Validated both ways: restricted add-to-cart is blocked, and registration with a licence-to-buy SKU is exercised.
✔ API contract suite
Data-driven checks across 10 endpoints with status, content-type, JSON-path, exact-value, array-minimum and cross-path assertions.
✔ Cart mechanics
Auto-open, badge count, quantity edits, removal, subtotal maths, route-reload persistence and the checkout login gate.
✔ Resilient search
Autocomplete, brand/category/SKU queries, and nonsense/empty-query route resilience.
✔ Favorites full CRUD
Create, rename and delete provide one deep authenticated My-Account flow beyond section-header checks.
✔ Cloudflare Access gate
A service-token reachability pre-flight protects the acceptance environment before every run.
03Gaps & what is missing
The remaining ~30% is a prioritised backlog. These are the highest-value flows not yet automated.
- Payment variety — only four happy-path e2e orders; no Adyen decline / 3DS challenge, payment-method switching, or address / shipping-option variation.
- Order-history depth — order-list filtering, invoice download / PDF, and reorder beyond the single last-order path are untested.
- PDP variants — variant / size SKU selection (footwear "maat 43", cloth sizes) is a core catalog feature that is not asserted.
- B2B pricing correctness — personalised prices (persoonlijke prijzen, excl. BTW) are never asserted for logged-in customers, only the presence of the login control.
- Knowledge centre — brand pages (MS Gold, HyCare, The Schippers Group), HyCare concept page, downloads, campaigns / magazines, and the kleurensysteem article are largely uncovered.
- Loyalty (AGROW) — enrolment, benefit application and newsletter subscription confirmation are checked only at link / CTA level.
- HyCare portal depth — HyCare Digital pest-monitoring is limited to two impersonation-based e2e cases.
- Promotions logic — free-gift callouts (Gratis drukspuit), web-deal badge eligibility and deal totals are only spot-checked.
- Multi-locale depth — locale routing and DE-store functional depth are untested beyond presence smoke.
- My Schippers data flows — order / invoice / returns pages are validated at section-header level only.
04Test layers & execution matrix
Coverage is delivered through three layers, executed across a browser × storefront matrix.
| Layer | Specs | What it verifies |
|---|---|---|
| Smoke | 14 | BDD-style specs (thin test-cases delegating to step-definitions) verifying render, navigation and interactivity per storefront. |
| E2E | 7 | Full business journeys spanning multiple pages with real authentication via the identity provider. |
| Integration | 1 | Data-driven API contract tests — one spec reads 10 CSV fixtures and generates a contract check per endpoint. |
Browser & storefront matrix
Every applicable spec runs across four browser engines and four storefronts, giving up to sixteen project combinations per suite.
05How coverage is measured
The headline percentage is a weighted estimate of automated functional coverage, not raw test count.
We enumerate the customer-facing functional areas of the storefront (from the live schippers.nl navigation and the hycommerce storefront surface), then map every automated test case to the area it exercises. Each area is scored on the share of its real behaviours that are asserted. Areas are weighted by business importance — the revenue-critical shopping path counts for more than long-tail content — so the overall figure reflects protection of what matters, landing at approximately 70%.
06Coverage on the live storefront
Captured from the acceptance storefront (store-nl.acceptance.store.hycommerce.schippers.cloud)
— the same environment the automated suite drives. The overlays map each area of the real UI to
its automation status:
Product detail page
Title, article number and the quantity + add-to-cart action are covered. Colour & size variant selection, bulk / tier (Staffelprijzen) & personalised B2B pricing, and customer reviews are not yet automated.
Cart & checkout
Cart contents — line item, image, price, quantity and stock — are covered. Coupon / voucher codes, delivery-option selection and the downstream payment flow (which sits behind the login gate) are not yet automated.
