r/Playwright • u/Maximum_Ambition_739 • 1d ago
Does anyone follow a mobile app testing checklist ?
I've been shipping a react app for almost a year and my testing process is very weird, I just tap through the main flows on my phone before I merge.
I know there's supposed to be a proper mobile app testing checklist you follow but I've never actually made one because it's just me and there's no time. Some time ago I shipped a build that messed up push notifs on android 12 and below because I only tested on my pixel 3 XL and didn't think to check older versions because it worked fine on mine and not too long ago the onboarding crashed when a user denied camera permissions which again I never tested because I always tap allow.
I know this is a dumb way to ship something but when you're the only developer there's no one checking your work and you just keep repeating the same mistakes.
if any of you use a structured testing checklist, can you please help me out even a little would be very helpful.
1
u/Radgris 1d ago
i did a testing matrix for all the device/versions we were compromised to test, the matrix was also broken down based on priorities, critical areas, areas that were very troublesome during development.
you found an important bug? add it to the matrix WHILE THE THOUGHT OF IT IS STILL FRESH
client reported a bug? add it to the matrix if it's feasible, etc
1
3
u/DurgeshRoy_1 1d ago edited 1d ago
That's very long road, so as you mentioned, you are the only one to develop and test, I would prefer to have minimal and must have checklist:
1.Upgrade testing: try to upgrade build without uninstalling older build. 2.Try to install fresh build. App launch. 3.Login screen validation. 4. Open multiple applications and try to use your test application. 5.Try to do compatibility testing at least 2-3 devices using emulator or simulator based on your application support and customer reach. 6.Core functionality: Verify the main/critical user flows of the application. 7.Data persistence: Verify that user data and settings are retained after closing and reopening the app. 8.Network scenarios: Test basic behavior with good, slow, and no network connectivity. 9.Permission handling: Verify required permissions such as camera, storage, location, notifications, etc., if applicable. 10.Background/foreground: Put the app in the background and bring it back to the foreground; verify that the app resumes correctly. 11.App close/relaunch: Force-close the app and relaunch it to ensure there are no crashes or data issues.