Progressive Web App Testing Checklist
Progressive web apps promise native-like experiences on the web, but AI-generated PWA code often has broken service workers, no offline support, and installation issues. This checklist ensures your PWA meets the standards that browsers and users expect.
Last updated: 2026-03-14
Installation
Web app manifest is complete and valid
Verify the manifest.json includes name, icons, start_url, display mode, and theme colors with correct values.
Install prompt appears on eligible browsers
Visit the app in Chrome and verify the install prompt or button appears for adding to home screen.
Installed app opens in standalone mode
Install the PWA and verify it opens in its own window without the browser address bar.
App icon and name display correctly after install
Check the home screen or app drawer and verify the correct icon and name appear for the installed PWA.
Offline Support
App displays content when offline
Disconnect from the internet and verify the app shows cached content or a meaningful offline page rather than a browser error.
Previously visited pages are available offline
Visit several pages while online, go offline, and verify those pages are still accessible from the cache.
Offline actions are queued for sync
Perform actions like form submissions while offline and verify they complete when the connection is restored.
Online/offline transition is smooth
Toggle connectivity and verify the app handles transitions without crashing, losing data, or showing confusing errors.
Cache is updated when new content is available
Update content on the server and verify the cached version updates on the next online visit.
Service Worker
Service worker registers without errors
Check the browser DevTools Application tab and verify the service worker is registered and active.
Service worker updates are applied correctly
Deploy a new service worker version and verify the update is installed and activated on the next visit.
Cache strategy is appropriate for each resource type
Verify that static assets use cache-first, API calls use network-first, and the strategy matches each resource's needs.
Service worker does not serve stale content indefinitely
After deploying updates, verify that users eventually receive the new content rather than cached old versions.
Push Notifications
Permission prompt appears at an appropriate time
Verify the notification permission prompt appears after user engagement, not immediately on first visit.
Notifications are received when the app is in the background
Send a push notification while the app is minimized and verify it appears in the system notification center.
Clicking a notification opens the correct page
Click a received notification and verify it opens the app to the relevant content, not just the home page.
Notification preferences can be managed
Verify users can control which notifications they receive and that their preferences are respected.
Frequently Asked Questions
Do all browsers support PWA features?
Chrome and Edge have the best PWA support. Safari supports service workers and offline capability but has limitations with push notifications and install prompts. Firefox supports core PWA features but removed the install button on desktop.
Is a service worker required for a PWA?
Yes. A service worker is required for PWA installation and offline functionality. At minimum, it should cache the app shell and provide an offline fallback page.
Let human testers run through this checklist for you
Submit your app and our testers will find the bugs you missed. Starting at €15 per test.
Related checklists
Mobile Responsive Testing Checklist
Mobile responsive testing checklist for AI-generated web apps. Verify layouts, touch interactions, and performance across devices and screen sizes.
Read morePerformance Optimization Testing Checklist
Performance testing checklist for AI-built web apps. Cover page load speed, runtime performance, asset optimization, and server response times.
Read moreCross-Browser Testing Checklist
Cross-browser testing checklist for AI-generated web apps. Verify compatibility across Chrome, Firefox, Safari, and Edge with layout and feature checks.
Read more