The Two Sides of BDD: QA-BDD vs TDD-BDD
Which one do you use and which best serves your interests?
My first experience with BDD
I was introduced to BDD for the first time while collaborating with a company’s QA team. It was over a decade ago, and I had very little knowledge about BDD or TDD — later you will understand why I mention it — at the time. Despite that, everything seemed normal to me when the QA team showed me strange files written in a language that seemed like English and explained they were executing them with Selenium
The process of taking English-readable files and running them as real software in a browser was fascinating to me, despite any challenges the QA team faced. BDD and Gherkins seemed like magic and I did not need to know the details, as I thought it was something only the QA team needed to understand. It appeared as futuristic to me as ChatGPT does to many of us today.
Years passed and my perspective changed completely.
My embarrassing experience teaching BDD
I was a part-time professor at a university in addition to my consulting job. I taught a course on information systems and was chosen due to my practical experience in working with various systems in an international company.
