Browser Storage Migration QA Test Plan Builder
Create a QA plan for migrating cookies, localStorage, sessionStorage, or IndexedDB data without breaking auth, preferences, carts, or offline state.
Prompt Template
You are a senior frontend QA engineer. Build a browser storage migration QA test plan for the web app change below. Application: [product, framework, browser support] Storage being changed: [cookies, localStorage, sessionStorage, IndexedDB, Cache API, service worker, mixed] Migration reason: [new domain, auth change, schema change, privacy update, offline mode, cart rewrite] Current data stored: [keys, values, schema version, size, TTL, sensitive data flags] New storage design: [keys, schema, encryption, expiration, consent behavior, versioning] Critical user journeys: [login, checkout, onboarding, preferences, drafts, offline sync, remember me] Release method: [feature flag, staged rollout, migration-on-read, one-time script, hard cutover] Supported environments: [Chrome, Safari, Firefox, Edge, iOS, Android, embedded webview] Known risks: [data loss, stale sessions, consent mismatch, quota errors, private browsing, cross-subdomain issues] Observability: [logs, analytics events, error reporting, support tags] Rollback options: [flag rollback, backward-compatible reads, data restore, support playbook] Create: 1. Storage inventory and risk classification. 2. Test matrix by browser, device, auth state, old schema, new schema, and consent state. 3. Migration scenarios for fresh users, returning users, expired sessions, corrupted data, and partially migrated data. 4. Critical journey test cases with setup, steps, expected result, and data assertions. 5. Edge cases for private mode, storage quota, cookie blocking, cross-subdomain behavior, and clock skew. 6. Automation strategy for Playwright or Cypress, including fixtures and cleanup. 7. Manual exploratory test charter. 8. Release monitoring dashboard and alert thresholds. 9. Rollback and customer support notes. 10. Sign-off checklist for engineering, QA, security, and support. Call out privacy and security review needs for any sensitive data.
Example Output
# Browser Storage Migration QA Plan
Highest-Risk Journeys
| Journey | Storage Touched | Risk | Test Priority |
|---|---|---|---|
| Remembered login | cookie + localStorage user flags | Session loss | P0 |
| Saved cart | localStorage cart_v2 | Lost checkout intent | P0 |
| Offline draft | IndexedDB drafts | Data loss | P0 |
| Theme preference | localStorage settings | Low user impact | P2 |
P0 Scenario
Returning user on old cart_v1 opens the new app, cart migrates to cart_v2, checkout still shows the same SKUs, quantities, price IDs, and coupon. Refresh twice and confirm migration does not duplicate items.
Automation Note
Seed localStorage and IndexedDB fixtures before page load, then assert both UI state and storage state after migration. Clear all storage between tests to avoid cross-test pollution.
Tips for Best Results
- 💡List exact storage keys and schema versions before writing test cases.
- 💡Test partially migrated and corrupted states; real browsers rarely fail cleanly.
- 💡Include Safari and iOS early because storage and cookie behavior often differs there.
- 💡Make rollback safe by verifying old and new readers can coexist during the release window.
Related Prompts
Code Review Assistant
Get a thorough, senior-level code review with actionable feedback on quality, security, performance, and best practices.
Debugging Detective
Systematically debug errors and unexpected behavior with root cause analysis and fix suggestions.
Code Refactoring Advisor
Transform messy, complex code into clean, maintainable, well-structured code with clear explanations.