Robot Test Framework for Mobile Test Automation
It’s one of those hard-to-describe bugs. You’ve created a mobile app with a checkout process for customers to purchase an item. Yet, when a tester selects an item for purchase, it doesn’t populate on the order form. When describing the bug with screenshots, text, and log events, nothing looks wrong on the surface—especially when ordering works fine for other testers. It becomes frustrating as the tester tries to explain, step by step, what’s going wrong.
Finally, a video reveals the issue. During a test with video capture, you see that the tester skipped an optional step to “select a store.” For some reason, not selecting a store affects items populating on the order form. A comparison of two video captures—one for the tester having problems and one for another tester not having problems—quickly reveals the issue. You now realize that the “select a store” step should be required, not optional. And thus, you’ve fixed the bug thanks to a video capture tool.
As described in the example above, video can be a powerful tool. Video capture during mobile app testing helps developers deal with hard-to-replicate bugs in three big ways.
Sometimes, screenshots and textual descriptions are just not enough to describe a tough bug. Video is a lifesaver—especially as this feature becomes more available to testers in cloud platforms.
Let’s look at some problematic parts of the bug testing process where a lack of video capture can add more time and energy to the process.
The process of describing a bug is time-consuming and sometimes frustrating—especially when it feels like you’re only indirectly pointing to a problem. Writing a bug description involves:
However, many bugs resist an easy explanation even with the above data. As a result, it can often take multiple descriptions and tests to figure out what’s happening.
Finding a bug sometimes parallels catching a criminal in the process of a crime. Unless you catch the criminal in the act, you must rely on indirect evidence. In the world of mobile app testing, written descriptions, screenshots, log events, and other data serve as indirect evidence of a bug “crime.”
When a bug does not occur for testers 100 percent of the time, it’s up to developers to rely on indirect evidence (such as an incorrect output) to help find the exact steps required to reproduce a bug. Indirect evidence of a bug often appears with many UI bugs that testers encounter that are not anticipated by mobile app developers.
Bugs are often easier to spot when they do not match documented requirements. But bugs independent of requirements can get shrugged off more easily if a tester points them out—especially if they are hard to pin down.
For example, a mobile app’s requirements may not state anything about how an incorrect password may give a user access to other customers’ billing information. However, if a tester runs into this problem but has trouble reproducing it, then a written description and screenshots of the bug may not be enough to quickly hone in on this unexpected problem. Video, on the other hand, can more quickly capture the bug when it happens.
Starting with our latest release, we now offer video capture. Kobiton automatically records any manual mobile app test session. After the test, you can access your video on your Session Details page and instantly watch videos of your test to help you spot bugs.
If you’re interested in trying out Kobiton’s video capture feature to see how it will help your mobile app testing, you can sign up for a free trial. Our 15-day free trial gives you access to more than just video. It also includes:
The power of video to help identify and resolve issues faster is real. As you explore your current or potential testing options, make sure video is a feature you are able to access and see the difference for yourself.