It's a fact of life that we often have to write automated UI tests for features that have defects, or that interact with 3rd party APIs that aren't returning the right responses, or for items that we know aren't working right. When the team has decided that the behavior isn't going to be fixed, what's an automation engineer to do? Let the tests fail? Not write them? Champion harder for the defects? Jenny suggests writing your tests to pass. By creating tests that pass on the current expected behavior (the defect), we are in a perfect position to tell when the defect is resolved, or the api...
Jenny Bramble
Senior Software Test Engineer
WillowTree Apps
Jenny Bramble came up through support and DevOps, cutting her teeth on that interesting role that acts as the 'translator' between customer requests from support and the development team before diving headlong into her career as a tester. Her love of support and the human side of problems lets her find a sweet spot between empathy for the user and empathy for her team. She's done testing, support, or human interfacing for most of her career. She finds herself happiest when she's making an impact on other people--whether it's helping find issues in applications, speaking at events, or just grabbing coffee and chatting.