Blurring the Line Between Developer and QA

Many QA testers are hesitant to poke their noses into the code they are testing, preferring to do black box testing instead. But what if getting a little nosey could help you save time and become a better tester? What if you could better assess risk by peeking under the covers and determine just how much testing is required for a feature? For over two decades (ouch!), Earline Deutsch has been a software developer, but in the past 18 months she switched to serving as a Software QA Engineer. In this session, she'll discuss her experiences in a whole new light from reviewing code changes to creating test plans based upon the code updates she sees. You may need some new skills, but generally you'll need to do the following:
1. Be curious, be very curious
2. Learn at least one scripting language well
3. Investigate the unit tests
4. Read the pull requests/code reviews
5. Test from a variety of perspectives