Skip to content

iDARMS Website Acceptance Tests

Test series: WEB-01 to WEB-22 (includes WEB-09A)
Objective: Validate that the public iDARMS website (iprs_website) matches the approved G2C layout, interaction patterns, form behaviours, portal handoffs, and desktop Lighthouse expectations before release.

Execution ownership

Recommended owners: Communications/web content owner; Customer Service observer; UX/visual reviewer; Performance reviewer

Prerequisites: Approved website build/URL, supported desktop browser at 1440×900, access to Chrome Lighthouse (desktop preset), and the evidence folders under docs/assets/.

Execution control

Use the approved public/UAT website URL only. Mask personal data in any form submissions. For core pages, attach one full-page cycle screenshot per route under docs/assets/Website/page-load/*_desktop-full.webp. Performance keeps Lighthouse ring/metrics proofs under docs/assets/Website/lighthouse/*.webp. Chrome/Interactions and Forms/Auth Handoffs do not embed screenshots.

Feature overview

The public website is the Government-to-Citizen marketing and guidance surface. Acceptance covers:

  • Core pages for every primary menu route against full-page desktop baselines.
  • Chrome and interactions for dual header, CTAs, FAQ/partners/newsroom controls, and footer.
  • Forms and auth handoffs for Contact and Objection validation, plus Ratepayer Portal entry links.
  • Performance for desktop Lighthouse rings and load stability gates.

Detailed steps, scenario tables, and seeded evidence live in the module pages linked below.

Coverage summary

Test ID Feature Scenario Priority Detail page
WEB-01 Core pages Home full-page layout Critical Core Pages
WEB-02 Core pages How to Register full-page layout Critical Core Pages
WEB-03 Core pages Impact full-page layout Critical Core Pages
WEB-04 Core pages Reports full-page layout Critical Core Pages
WEB-05 Core pages Newsroom full-page layout High Core Pages
WEB-06 Core pages About full-page layout High Core Pages
WEB-07 Core pages Contact Us full-page layout High Core Pages
WEB-08 Chrome Dual header, active nav, sticky scroll Critical Chrome and Interactions
WEB-09 Chrome Primary CTA button states Critical Chrome and Interactions
WEB-09A Auth handoff How to Register → portal registration Critical Forms and Auth Handoffs
WEB-10 Forms Contact form validation High Forms and Auth Handoffs
WEB-11 Forms Objection form validation High Forms and Auth Handoffs
WEB-12 Interactions FAQ and Reports accordions High Chrome and Interactions
WEB-13 Interactions Partners and Newsroom filters Medium Chrome and Interactions
WEB-14 Chrome Footer full-bleed and links Medium Chrome and Interactions
WEB-15 Performance Home Lighthouse rings Critical Performance
WEB-16 Performance How to Register Lighthouse rings High Performance
WEB-17 Performance Impact Lighthouse rings High Performance
WEB-18 Performance Reports Lighthouse rings High Performance
WEB-19 Performance Newsroom Lighthouse rings Critical Performance
WEB-20 Performance Load stability / CLS Critical Performance
WEB-21 Performance About Lighthouse rings High Performance
WEB-22 Performance Contact Lighthouse rings High Performance

Website menu inventory

Nav label Route Detail case
HOME / WEB-01
HOW TO REGISTER /HowtoRegister WEB-02
IMPACT /Impact WEB-03
REPORTS /Reports WEB-04
NEWSROOM /Newsroom WEB-05
About /About WEB-06
Contact / Help & Support /Contact_us WEB-07

WEB-01 — Home full-page layout

Field Value
Priority Critical
Test action Open Home at 1440×900 and compare to the approved baseline. Detailed scenarios are in Core Pages.
Expected result Dual header, hero, bands, partners, FAQ, and footer match the baseline hierarchy and brand tokens.
Execution result PASS
Evidence reference assets/Website/page-load/home_desktop-full.webp
Defect reference None

Tester notes

Manual cycle 2026-08-03. Desktop Chrome ~1440×900. Full-page Home captured; dual header, hero with Register Now CTA, pillars, testimonials, partners, teal app band, FAQ, and footer present and intact. Compared against cycle proof / approved hierarchy — PASS.

WEB-02 — How to Register full-page layout

Field Value
Priority Critical
Test action Open How to Register and confirm layout plus Start Registration handoff. Detailed scenarios are in Core Pages and WEB-09A.
Expected result Page matches baseline; Start Registration opens https://ratepayer.idarms.cisstaging.com/auth/register.
Execution result PASS
Evidence reference assets/Website/page-load/howto-register_desktop-full.webp
Defect reference None

Tester notes

Manual cycle 2026-08-03. Desktop Chrome. Full-page HowtoRegister layout confirmed. Start Registration opened https://ratepayer.idarms.cisstaging.com/auth/register in a new tab — PASS.

WEB-03 — Impact full-page layout

Field Value
Priority Critical
Test action Open Impact and compare hero, contribution, and donut/legend sections to baseline. See Core Pages.
Expected result Donut and legend remain aligned and readable; hero contrast meets the visual standard.
Execution result PASS
Evidence reference assets/Website/page-load/impact_desktop-full.webp
Defect reference None

Tester notes

Manual cycle 2026-08-03. Impact full-page: hero, contribution tiles, donut/legend, and footer intact and readable — PASS.

WEB-04 — Reports full-page layout

Field Value
Priority Critical
Test action Open Reports and confirm sidebar plus accordion content. See Core Pages.
Expected result Forms/Acts sidebar and Taxpayer Checklist accordions render without hero-only capture errors.
Execution result PASS
Evidence reference assets/Website/page-load/reports_desktop-full.webp
Defect reference None

Tester notes

Manual cycle 2026-08-03. Reports full-page: REPORTS active nav, sidebar + accordion two-column layout, footer intact — PASS.

WEB-05 — Newsroom full-page layout

Field Value
Priority High
Test action Open Newsroom and confirm bulletin, featured story, and filters. See Core Pages.
Expected result Featured card and filter chrome match baseline; active nav is NEWSROOM.
Execution result PASS
Evidence reference See Core Pages / cycle proof
Defect reference Insert ID or None

Tester notes

Record actual result, browser/build, and any variance.

WEB-06 — About full-page layout

Field Value
Priority High
Test action Open About and confirm sticky/section nav and Explore CTA. See Core Pages.
Expected result About structure and sticky nav remain usable at desktop width.
Execution result DEFERRED
Evidence reference See Core Pages / cycle proof
Defect reference Insert ID or None

Tester notes

Deferred to next phase per product owner alignment; out of scope for current website-only validation.

WEB-07 — Contact Us full-page layout

Field Value
Priority High
Test action Open Contact Us and confirm the form card layout. Validation detail is in WEB-10.
Expected result Form card shows labelled fields, required markers, and full-width Send Message.
Execution result PASS
Evidence reference assets/Website/page-load/contact_desktop-full.webp
Defect reference None

Tester notes

Manual cycle 2026-08-03. Contact Us full-page: heading, form card with labels/*, Send Message, and footer intact; floats do not block submit — PASS.

WEB-08 — Dual header, active nav, sticky scroll

Field Value
Priority Critical
Test action Confirm utility bar, main nav underline, and sticky LOGIN/REGISTER. See Chrome and Interactions.
Expected result Dual chrome remains intact; only the current route is underlined.
Execution result PASS
Evidence reference None (image evidence removed; results recorded in tester notes)
Defect reference None

Tester notes

Manual cycle 2026-08-03. Dual chrome intact; REPORTS active underline confirmed; sticky header keeps LOGIN/REGISTER visible after scroll (sticky fix applied in iprs_website Header) — PASS.

WEB-09 — Primary CTA button states

Field Value
Priority Critical
Test action Exercise default/hover/focus/active/disabled-or-loading for primary CTAs. See Chrome and Interactions.
Expected result Action cyan and deep navy CTAs keep distinct fills; disabled controls are not activatable.
Execution result PASS
Evidence reference None (image evidence removed; results recorded in tester notes)
Defect reference None

Tester notes

Manual cycle 2026-08-03. LOGIN/REGISTER default+hover confirmed. Register Now!!! hover made distinct (navy → cyan + scale) in iprs_website HeroSection; retested — PASS. Hand cursor retained as correct CTA affordance.

WEB-09A — How to Register → portal registration handoff

Field Value
Priority Critical
Test action Click Start Registration and confirm the Ratepayer Portal registration URL opens in a new tab. See Forms and Auth Handoffs. Continue registration under RPP-AUTH-05.
Expected result Destination is https://ratepayer.idarms.cisstaging.com/auth/register with target="_blank".
Execution result PASS
Evidence reference None (image evidence removed; results recorded in tester notes)
Defect reference None

Tester notes

Manual cycle 2026-08-03. Start Registration opened https://ratepayer.idarms.cisstaging.com/auth/register in a new tab; HowtoRegister tab remained open — PASS.

WEB-10 — Contact form validation

Field Value
Priority High
Test action Run required, invalid-email, filled, and submit workflows with approved fixtures. See Forms and Auth Handoffs.
Expected result Field-scoped errors appear; valid submit clears the form (as-built); message delivery remains BLOCKED until an API exists.
Execution result PASS
Evidence reference None (image evidence removed; results recorded in tester notes)
Defect reference WEB-FORM-01 (delivery BLOCKED — no API/toast); phone skip WEB-FORM-02

Tester notes

Manual cycle 2026-08-03. Required blanks and qa-tester@invalidInvalid email address confirmed. Valid path clears form with no success toast (as-built); delivery BLOCKED — PASS for website validation scope.

WEB-11 — Objection form validation

Field Value
Priority High
Test action Run objection form workflows on /HowtoRegister. See Forms and Auth Handoffs.
Expected result Required and email errors are clear; valid submit clears silently (as-built); delivery BLOCKED.
Execution result PASS
Evidence reference None (image evidence removed; results recorded in tester notes)
Defect reference WEB-FORM-01 (delivery BLOCKED); phone asterisk WEB-FORM-03

Tester notes

Manual cycle 2026-08-03. Required + invalid-email confirmed. Phone left blank OK. Valid submit clears with no toast; delivery BLOCKED — PASS for website validation.

WEB-12 — FAQ and Reports accordions

Field Value
Priority High
Test action Expand/collapse FAQ and Reports accordions. See Chrome and Interactions.
Expected result Section-only proofs show expanded content without wrong hero crops.
Execution result PASS
Evidence reference None (image evidence removed; results recorded in tester notes)
Defect reference Insert ID or None

Tester notes

Record actual result, browser/build, and any variance.

WEB-13 — Partners and Newsroom filters

Field Value
Priority Medium
Test action Toggle Public/Private partners and Newsroom filters. See Chrome and Interactions.
Expected result Active pill colours and filtered content update correctly.
Execution result DEFERRED
Evidence reference None (image evidence removed; results recorded in tester notes)
Defect reference Insert ID or None

Tester notes

Deferred to next phase per product owner alignment; out of scope for current website-only validation.

Field Value
Priority Medium
Test action Confirm navy full-bleed footer and key links. See Chrome and Interactions.
Expected result Footer is full-bleed navy, not a boxed card; links resolve.
Execution result DEFERRED
Evidence reference None (image evidence removed; results recorded in tester notes)
Defect reference Insert ID or None

Tester notes

Deferred to next phase per product owner alignment; out of scope for current website-only validation.

WEB-15 — Home Lighthouse rings

Field Value
Priority Critical
Test action Run desktop Lighthouse on Home against Tier B gates. See Performance.
Expected result Hard gates hold; Perf/LCP within Tier B regression limits.
Execution result FAIL
Evidence reference assets/Website/lighthouse/home_rings.webp; home_metrics.webp
Defect reference Home a11y below interim gate; Perf below baseline−5; LCP optimization still open

Tester notes

Manual cycle 2026-08-03. Desktop Lighthouse on http://127.0.0.1:3000/. Scores: Perf 46, A11y 83, BP 100, SEO 100; FCP 0.3s, LCP 10.7s, TBT 910ms, CLS 0. FAIL — A11y 83 < interim gate 85; Perf 46 < baseline−5 (48). LCP within baseline×1.10 (11.33s) but still > 4.0s (keep optimization defect).

WEB-16 — How to Register Lighthouse rings

Field Value
Priority High
Test action Run desktop Lighthouse on How to Register (Tier A). See Performance.
Expected result Hard gates hold; Perf/LCP/TBT within Tier A rules or linked defect.
Execution result DEFERRED
Evidence reference See Performance
Defect reference Insert ID or None

Tester notes

Deferred to next phase per product owner alignment; out of scope for current website-only validation.

WEB-17 — Impact Lighthouse rings

Field Value
Priority High
Test action Run desktop Lighthouse on Impact (Tier A). See Performance.
Expected result Hard gates hold; Perf/LCP/TBT within Tier A rules or linked defect.
Execution result DEFERRED
Evidence reference See Performance
Defect reference Insert ID or None

Tester notes

Deferred to next phase per product owner alignment; out of scope for current website-only validation.

WEB-18 — Reports Lighthouse rings

Field Value
Priority High
Test action Run desktop Lighthouse on Reports (Tier A). See Performance.
Expected result Hard gates hold; Perf/LCP/TBT within Tier A rules or linked defect.
Execution result DEFERRED
Evidence reference See Performance
Defect reference Insert ID or None

Tester notes

Deferred to next phase per product owner alignment; out of scope for current website-only validation.

WEB-19 — Newsroom Lighthouse rings

Field Value
Priority Critical
Test action Run desktop Lighthouse on Newsroom (Tier B). See Performance.
Expected result Hard gates hold; Perf/LCP within Tier B regression limits.
Execution result FAIL
Evidence reference assets/Website/lighthouse/newsroom_rings.webp; newsroom_metrics.webp
Defect reference Perf below floor; LCP beyond baseline×1.10; TBT above interim 1,200 ms

Tester notes

Manual cycle 2026-08-03. Desktop Lighthouse on /Newsroom. Scores: Perf 36, A11y 93, BP 96, SEO 100; FCP 0.4s, LCP 10.4s, TBT 3,120 ms, CLS 0. FAIL — Perf 36 < floor 45; LCP 10.4s > baseline×1.10 (~7.8s); TBT 3,120 ms > 1,200 ms interim. Hard gates A11y/BP/SEO/CLS held.

WEB-20 — Load stability (first paint vs content ready / CLS)

Field Value
Priority Critical
Test action Hard-refresh Home and Newsroom; confirm no layout jump and CLS ≤ 0.10. See Performance.
Expected result CLS ≤ 0.10; no severe layout jump between first paint and content ready.
Execution result PASS
Evidence reference CLS from WEB-15/WEB-19 Lighthouse metrics (home_metrics.webp, newsroom_metrics.webp)
Defect reference None

Tester notes

Manual cycle 2026-08-03. Home and Newsroom hard refresh — no header/hero/CTA jump. CLS 0 on both Lighthouse strips — PASS.

WEB-21 — About Lighthouse rings

Field Value
Priority High
Test action Run desktop Lighthouse on About (Tier A). See Performance.
Expected result Hard gates hold; Perf/LCP/TBT within Tier A rules or linked defect.
Execution result DEFERRED
Evidence reference See Performance
Defect reference Insert ID or None

Tester notes

Deferred to next phase per product owner alignment; out of scope for current website-only validation.

WEB-22 — Contact Lighthouse rings

Field Value
Priority High
Test action Run desktop Lighthouse on Contact (Tier A). See Performance.
Expected result Hard gates hold; Perf/LCP/TBT within Tier A rules or linked defect.
Execution result DEFERRED
Evidence reference See Performance
Defect reference Insert ID or None

Tester notes

Deferred to next phase per product owner alignment; out of scope for current website-only validation.