So what exactly is the difference between KDT and BDT?
If we go googling, we will eventually see that: Data Driven Testing (DDT) - test data is "independent" from code; Keyword Driven Testing (KDT) - test steps and test data are "independent" from code; Behaviour Driven Testing (BDT) - cool business oriented syntax! Engage your shareholders!! Best approach since sliced bread!!! When you actually write the definitions back to back you can clearly see that any KDT framework is also DDT, and any BDT is also KDT and DDT. So what separates BDT from KDT? The cool syntax (given-when-then), which is usually the first thing mentioned, doesn't actually do much. If you transform your keyword from <user clicks button> to <when jimmy clicks the button>, you will not actually add any value. BDT has two closely related features that both give the same benefit - test cases are more readable and more maintainable. You could say it's the OOP of test automation if you were feeling generous. The first...