Mobile Labs was recently asked to weigh in on Dev Test Ops in a piece by the SD Times and it got us thinking: We need to put together the Top 5 Dev Test Ops Tips to help your testing efforts.
1. Make A Plan
Which devices are you going to test on? For how long? What are you testing for? Why? You won’t have (good) answers for any of these unless you do your research first. It’s important to know what devices your customers or desired customers are using. If 60% use Androids and 40% use iPhones then you should divvy up your testing time proportionately and further break that up by specific device. What about where crashes and bugs happen most often? If you know exactly where problems occur in your app, you can spend more time testing those specific areas to reduce the greatest instances of problem. Apps drive revenue so by eliminating the largest concentration of bugs in the app, you can impact revenue the most.
By getting some data first you can significantly improve your testing speed and effectiveness.
2. Automation and Continuous Testing Is Key
When it comes down to it, automation is no longer optional: it’s simply not feasible to manually test dozens of devices enough times in a time and cost effective manner. Manual testing is absolutely a critical component of testing, but automation will let you run test cycles more effectively. After the automated cycles are complete, you can then go perform manual testing to fine tune your testing.
There’s also a debate on how much testing is too much testing? If you get too bogged down in the testing, you may not have enough time to roll out the fixes you discovered you needed during your testing! It’s always better to test too much than not enough, but you always be testing. And Mobile Labs make it easy with a tool like deviceConnect! Only functional testing doesn’t cut it anymore which is why you need to always be testing for ways to improve performance and UX.
3. Test on Real Devices
Emulators can’t catch everything. Not only are emulators not always 100% perfect in replicating the device’s software, they can’t catch bugs that exist in the communication between hardware and software and the device. In addition, you can’t get a true idea of the UX when using an emulator. Emulators can be a useful tool, but they cannot be the only way you test.
4. Balance Speed and Quality
It’s imperative to be agile and roll out releases, but you must never sacrifice quality for speed. Apps generate revenue and if a buggy, poor performing app gets released, this not only affects your app reputation but your brand reputation as well and most importantly, your bottom line.
Releasing a poorly tested app puts you into a constant cycle of catch up: new app or updated gets released, bugs are found, test for the cause of the bugs, roll out updates fast to keep people happy and repeat.
Avoid that all together and always test thoroughly before rolling out.
Always, always, always analyze your results before recommending or making changes. The more data you have (see point #1) the more you can improve your testing in the future. And when recommending or making changes, be sure to be surgical so that you prevent over correcting bugs and causing new problems.
Don’t forget to check out our eBook on Amazon, Enterprise Mobile App Development & Testing: Challenges to Watch Out For in 2017 !
To read our latest posts, click here!
To see the full article we were featured in, click here!