Test Automation Basics

Welcome to part 2 of the anti-pattern series. And I can't wait to start because I am beginning this article with a very famous BDD testing and collaboration tool Cucumber. Let's jump right into it. Cucumber in Every Recipe Before I say anything, I want you to read this - "If you need a testing tool for driving a mouse and a keyboard, don't use Cucumber. There are other tools to do this with far less abstraction and typing overhead than Cucumber." -Aslak Hellesøy, creator of Cucumber So if you are not following the process of BDD in your product development, then there exists one anti-pattern that is undoubtedly going to give you a hard time to achieve benefits from test automation success. And it is using Cucumber or other similar styling tools.  And if you want to review your decision, you can do it now. If you are already too deep into it, consider starting a new suite for future testing. Getting up and running with a suite does not take time. Even if it did, it

I have just finished jotting down all the  Anti-Patterns  that I have come across during my assignments and  Best Practices  that I have adopted to make my tests run on cloud and with distinguishing quality. And if I talk about all of them,  I honestly don't know how long this article is going to be.   Therefore just like the title, I will, in this article, discuss habits that keep you away from keeping code hygiene and make your automation starve for love and respect.  So lets' start without any further ado. Borrowing Existing Frameworks Well, it's not hidden from anyone. We have heard this before from someone that they have got a fantastic Test Automation framework  for our new project  from another team. With such suggestions, it's easy to convince the team because we crave for being efficient, and it points to the definite time-saving scheme. Let me assure you, its a trap. It not only takes time for the team to understand the complete architectur