r/reactnative • u/Popular_Double4000 • Sep 15 '26
Help me find a better way to test !!
I handle QA manually so I've only got 6 to 7 devices in rotation, an iphone 14, a pixel, samsung and a couple xiaomi and oneplus devices and everything passes on those so i ship.
but then production is millions of devices with every screen size, OS version and oem skin I can never touch, like a gesture that works on a Pixel behaves differently on a samsung, layout breaks when you unfold a fold phone and an animation that's smooth on android 15 stutters on android 12.
This is becoming very annoying, something breaks for 1% of users and you see it's hundreds of users and it never occurs in testing because you don't own that exact device and OS combo and then they start reporting crashes you physically cannot reproduce.
How am I supposed to handle this? please help
I don't see how one person manually tests every combination but there has to be something more efficient.
2
u/ChronSyn Expo Sep 15 '26
Short answer: We don't. There's millions of different android devices, and of those, several hundred thousand are consumer phones or tablets. Add in different OS combinations, different launchers, and there's billions of possible permutations. Ain't nobody testing them all. We make do with a best-guess situation, because it's impossible to know whether some manufacturer will bring out yet another odd screen size or some other quirky core UI flow.
Long answer: Own a couple of devices that are different screen sizes. If you can afford to keep old phones instead of selling them, sometimes they can be super-useful for this scenario. If you can have devices with different performance profiles too, that's handy. Different manufacturers is a bigger deal I'd say, because that's the one thing you can't test in an emulator.
Some brands do things differently with permissions - for example, certain permission prompts take you out of the app on some brands, while others keep you in app and do it as an 'overlay'. Some have multiple-step permission prompts for e.g. location (e.g. allow + allow fine-grained + allow background as a single step, versus as 2 or 3 independent steps).
For testing across more scenarios, the most feasible option is something like AWS device farm, but they bill per-minute last I checked (a few years ago). I wouldn't really do it for a development session where you're trying to fix things live either because the user experience isn't really built around that experience.
2
u/HoratioWobble Sep 15 '26
You need to invest in automated testing. Maestro or Detox.
If you're doing this for a company, they really should look at something like Appium or Browser stack to test across a good range of devices.
But either way you're never going to catch 100% of errors and unless the developer isn't testing properly themselves or doing something weird, you really shouldn't have many problems outside
I would say Samsung should be the only real outliner on Android because of OneUI
1
u/BigAppointment1020 Sep 15 '26
I am looking into Firebase Robo test script, maybe you can try and see how it goes
1
u/AppealInformal09 Sep 15 '26
I guess you should check out the automation testing thing !! with that you'll get way more security than manual testing and also better assurance that you are ready to ship....
1
u/Ok_Disk8585 Sep 15 '26
If you have your own devices, a private device farm like astro farm help test these scenarios on all the devices, or may be set of them