Behavior-driven development has been a buzzworthy term in the testing and development community for several years. At first glance, the elements of BDD seem simple: testing scenarios, living documentation, automation, and reports. That all sounds great, but then why isn't everyone doing it? Upon a deeper dive, it becomes obvious that the implementation of BDD needs a lot of forethought and planning, and teams must approach it for the right reasons. Christine Fisher will follow the evolution that one team is currently experiencing in their shift to BDD. BDD was selected to help them...
Christine Fisher
NAIC
Christine Fisher started her career as a high school history teacher, but a switch to software training got her started on a career path in technology, where she has held various positions in professional services and development over the past fifteen years. Currently managing a team of business analysts and software quality engineers at the National Association of Insurance Commissioners, she has found that her roots in teaching are still important to help build and develop a strong team. She's passionate about ensuring functional teams are equal members of the development team and helping define those roles as they change in a DevOps culture.