Rolling out Behavior-Driven Development
Even though you know BDD kind of sucks and you don’t want to...
Testing articles
View All TagsEven though you know BDD kind of sucks and you don’t want to...
In the realm of automation and QA, where attempts at precision and efficiency reign supreme, there exists a shadowy feeling lurking beneath the glossy facade of your test case management tool. As a vulnerable automation engineer with a modest amount of experience, I am going to lay bare the unspoken resentments that are plaguing your automation teams around the pretty tool.
A few years in the BDD trenches taught me why BDD is just about impractical
I have worked in various organizations with different software development pipelines as a software developer, automation engineer, test engineer, DevOps engineer, etc. In all that time, I have never seen a perfect pipeline. Now, all development pipelines have room for improvement, but I’ve never seen a genuinely bulletproof one with built-in metrics, complete and total automation, and fast feedback.
There are tons of important factors that can have a significant impact on the effectiveness and efficiency of a testing process for a modern software organization. Still, nothing can get in the way more than a terrible test case management tool.