Managing the Software Test Process

(CSTP #3 & 4)

This tutorial counts as training towards the Certified Software Test Professional requirements.

This one day course offers a wide variety of practical information to be used to manage the entire testing process. We will discuss what quality means in a company and how to effectively determine what to test. We will also discuss how to determine what we can skip testing based on schedules, manpower and the risk we incur by not doing the testing. In addition to determining ways to identify the quality risks, we'll also discuss the quality assurance aspects of testing, including an easy checklist to use when reviewing requirements. Test planning, test case planning and tracking, scheduling and budgeting and bug tracking will all be covered as part of a managed test process. You will leave this course with an understanding of the entire testing process and simple ideas that can easily be implemented to allow your organization to improve its professional reputation as you implement a managed test process. The instructor will use a variety of real world examples to point out the successes and possible pitfalls of the ideas presented.

1. Introduction
• Administrative stuff
• Terminology
2. Determining the quality goals
• What are the ultimate goals?
• What are management's goals?
• What are our goals?
3. Getting started without getting scared
• Figuring out where you are now
• CMMI model
• Other evaluation methods
• Making quality a company goal
• Figuring out the cost of quality
• Why do we need friends?
• What data do we need?
• Doing a quality risk analysis
4. Using requirements documents and specifications
• Participating effectively in review meetings
• Looking for the non-functional requirements
• Reviewing functional specifications
5. Creating and following test plans
• Writing a good test plan
• Scheduling and budgeting
6. Writing and tracking test cases and suites
• Using the quality risk analysis
• Designing test cases
• Tracking test cases
• Assessing test case coverage
• Breadth coverage
• Depth coverage
• Tracking test passes
• Putting the charts together
• Presenting difficult information to management
7. Managing all those bugs
• Writing a good bug report
• Assigning priority and severity
• Tracking closure status and root cause
• Reporting and trend analysis
• Managing bugs via detailed status
8. Managing the test process - in review
• Looking at what we have
• Using the information we're given
• Watching for the unexpected
9. Using people resources effectively
• Picking the right people
• Looking at skill sets
10. Planning automation (a brief look)