My Testing is a Reflection of My Developer's Unit Testing
Having worked with many developers in my 25-year history in Quality Assurance, when I determine my test plan, I must consider the Unit Testing my Developer has completed. Given the request for speed and agility in testing, we must consider the level of testing and experience of our developer to best plan the depth of testing and the direction of the testing we must complete. Questions I must ask myself: Do I have prior knowledge of the developer's unit testing? Is a demo from development to QA part of our team's Agile Methodology? How clearly can the developer communicate her approach to Unit Testing? And, is my developer available during my working hours if I have questions? From the answers, I can determine my test approach. My confidence in my developer's Unit Testing can guide me in how quickly I can get into complex test scenarios. We will look at each question and understand how it impacts the test plan you prepare prior to receiving the new functionality or bug that needs to be tested. By understanding what the developer has done can focus your test approach and speed your time to completion.