UI automation is rapidly becoming a mainstream occurrence. It’s no longer a mystical tool that no one knows how to work or implement. However, people still struggle to make it effective. It doesn’t have to be a negative experience. There are 5 common issues you can address and solve—making UI automation more effective and requiring less maintenance.
Nikolaj TolkaciovTest Lead and Team Lead
Nikolaj worked for a whole host of tech companies before joining Devbridge. He grew up dreaming of becoming a soldier or an astronaut, but when he realized there weren’t likely to be any astronaut opportunities in Lithuania, he started looking for something else to do. Nikolaj was always good at video games, and wanted to parlay that into something that he could do professionally — and that’s how he decided to study IT. He started out as the local “computer guy” in his small hometown, fixing PCs and installing software for his neighbors to earn a little pocket money, and ended up getting his bachelor’s degree in informatics engineering from the Kaunas University of Technology.
The proud father of two sons, Nikolaj finds his inspiration in spending time with family, solving challenging problems and seeking out new opportunities. His favorite book is 1984, which he loves for the way it gives you a new perspective on current events, and his favorite movie is Kickass, which he says meets all the criteria he looks for in a film. If he could have any super power, it would be the ability to know absolutely everything in the world.
You miss 100 percent of the shots you don’t take.
Developers today most likely can’t imagine not having source control and continuous integration systems. However, one area enterprises may still be struggling with is how to integrate an automated test solution for native mobile applications into a continuous integration workflow. This article provides suggestions on how to do so along with an example of how we did it at Devbridge.