This post is a reblog from Serghei Moret, who is my colleague at XING. Serghei is an awesome test automation engineer developing really helpful solutions for our mobile app environment for iOS and Android. Lately he started to write on his own blog http://www.waysoftesting.com/. In his first post he is writing about “How to convince your colleagues to write Automated Tests or why would you use Cucumber as an Automation Tool”.
I really like the first post from Serghei and I want to help him spread the word about his blog and about his work and effort he is putting in mobile test automation. If you haven’t seen his blog, check it out.
Here is a short excerpt of the blog, the full article can be found here.
How to convince your colleagues to write automated tests? I think that a lot of people have asked this question and probably already found a dozen of correct and incorrect answers. In this article I’ll try to describe the way, how the automation framework was successfully implemented for several teams in different companies. Also I’ll speak about the reasons why you might use Cucumber in a wrong way. […]
After several tool evaluations, a key question appears: who is writing tests? From my personal opinion, developers shouldn’t write automation tests. Test engineers are the persons who can design good test ideas and also add details to it while writing an automation script. From my experience, developers are not the right persons to write automation, as mostly their tests end up in checking happy paths. Fortunately, other team members have agreed with it. So, having that clear I started thinking about the Cucumber. […]
You’ll say that Cucumber shouldn’t be used like that? Yes, I know. In the beginning we tried to make tests compact and readable but that made our step definitions full of duplicated actions, as we have thousands of page objects and long UI flows. So, we chose maintainability over readability.[…]