I listened to a long discussion revolving around concerns with specific tables in the database schema -- tables where the data was expected to grow rapidly. I heard how the system architect altered the design to accommodate rapid growth and heard details about the data warehousing alternatives. I said nothing.
But when I returned to test planning, I incorporated test ideas around those areas. I planned performance tests, functional tests and search testing designed to expose problems. When the system architect saw my test plan (I always share my test plans with different members of a project team and let them know my work is open for review and input), he told me I was welcome to return to any product planning meetings. Because he could see the direct benefit of "allowing" QA in early in the process, he began to advocate my attendance in meetings. After that, I didn't have to do anything else to advocate early involvement. The door had been opened.
Dig Deeper on Topics Archive
Related Q&A from Karen N. Johnson
User acceptance testing and system integration testing differ in one key way: the person who does the testing. Learn when to apply UAT vs. SIT. Continue Reading
There are so many resources out there about the ever-changing world of Web design and mobile testing, but to choose the most salient and insightful ... Continue Reading
In this expert response, consultant Karen Johnson describes strategies she uses for browser compatibility testing. Experience and knowledge of common... Continue Reading