Curriculum: Certified Software Tester (CST) 5-Days
Curriculum: Certified Software Tester (CST) 5-Days
Curriculum
Common Body of Knowledge The Certified Software Tester Program (CST) is appropriate for individuals who want
to enter the testing field or experienced Quality Assurance/Tester professionals seeking
certification. The program focuses on the concepts and application of the essential
• Control Procedures testing principles that are required to perform industry standard quality assurance
practices
• Problem Resolution
The purpose of the program is to provide the pertinent knowledge and skills for
• Reports effective Quality Assurance testing in the client/server and web environments and, to
describe the essentials of Quality, Quality Assurance (QA) and Quality Control (QC).
• Requirements There is a special emphasis on verification & validation and their relationship to testing.
Topics include such areas as test case execution on GUI and Web applications;
• Test Builds documenting and controlling testing activities with requirements trace ability matrices,
test plans, test procedures and test cases; configuration and management of online
• Test Cases defect tracking applications, categorizing, tracking and documenting software errors and,
building management reports.
• Test Execution
Duration/Dates:
Day Class 5 sessions
CERTIFIED TESTER PROFESSIONAL PROGRAM
2
CERTIFIED TESTER PROFESSIONAL PROGRAM
You Will Be Able To: • Explain the history and purpose of testing
• Define the basic testing principles
• Explain the evolution of the inspection process • Explain the key testing issues
• Explain what inspections are designed to accomplish • Define the three major testing organizations and explain
• Explain who uses inspections and why their test methodologies
• Understand the value that occurs when inspections are • Explain the different testing strategies and how they are
used used
• Explain the similarities between reviews and inspections • Explain the different testing categories, how they are used
• Name the various types of reviews and by whom
• Explain what reviews are designed to accomplish • Explain the different testing types and how they are used
• Discuss “review” critical success factors • Explain the difference between User Interfaces (UI) and
• List and describe test products that can be reviewed User Interface Controls
• List and discuss the roles and responsibilities of review
participants
Main Topics Covered:
• Discuss the basic steps of the reviews and inspections
processes and their objectives
• Six Principles of Testing
Main Topics Covered: • Testing is Fundamental
• Testing Practices and Strategies
• Reviews & Inspections – Differences, Roles & Basic • Black Box Testing
Process Steps • Unit Level Testing Model
• Differences Between Reviews & Inspections • Integration Level Testing Model
• The Inspection Process • System Level Testing Model
• Quality Assurance Inspection Objectives • Acceptance Level Testing Model
• Inspecting the Software Procedures Manual • What is a User Interface (UI)?
• Software Requirements • User Interface Controls
• Inspection Meeting Agenda • Types of Interface Controls
• The Review Process • Windows Compliance Testing (Checklist)
• Types of Reviews • Considerations for Testing User Interaction
• Components of the Review Plan • Checklist for a Good Interface
• Critical Success Factors for Reviews • Considerations for Testing Input Basics, Navigation, and
• Review Checkpoints Viewing Operations
• Considerations for Testing Windows Interface
Components
Principles of Testing • Considerations for Testing Menus, Shortcuts and
Controls
Module 2.0: Fundamentals of Testing
Module 2.1: Defects and Problems Reporting
This module provides the history and fundamentals of This module expounds on the primary goals of the tester, which is to
testing with specific emphasis on Software Testing. It also identify, classify and report errors as early as possible in the development
3
CERTIFIED TESTER PROFESSIONAL PROGRAM
life cycle. An error (issue) occurs when a program does not operate in the • Disadvantages of Using Automated Testing Tools
manner in which its user expects during the software development life
cycle. • Automated Tool Issues
• Guidelines for What to Automate
You Will Be Able To:
• Define the primary objective of the problem reporting Test Documentation Techniques
process
• Explain the fundamental principles of reporting defects Module 3.0: Project & Requirements Documentation
• Identify when and understand why problem reports
should be submitted This module introduces Project Documentation and its
• Explain what items are included in a problem report criticality within the software development process and the
• Explain why software has defects multiple purposes it serves.
• Define the major categories of software errors
• Explain the concept of severity and priority as they relate This module focuses on the two main reasons for having
to defects Requirements Documentation. The first is that the
• Explain the basic features of the Elementool defect (bug) information contained within the documented requirements
tracking tool drives the Systems Development Life Cycle activities and
these activities are essential for the software development
Main Topics Covered: and Quality Assurance processes. The second is that the
outcome of the requirements definition is a documented
agreement between the customer and the development team
• Tracking and Reporting Defects
that explicitly describes the product to be developed.
• Reporting a Software Problem
• Submitting Problem Reports
• Problem Report Content This module focuses on requirements and their relationship
• Major Categories of Software Errors to the testing and test process. It also explains how
requirements incorporate test conditions and functional
• Severity of Defects checklists to verify correct system functions.
• Priority by Severity
You Will Be Able To:
Module 2.2: Automated Testing Principles
• Explain the importance of project documentation
This module elaborates on how automated testing tools • Define the goals of documentation standards
help organizations optimize and accelerate the delivery of • Explain the various project documentation categories
applications. It also addresses the paradox in purchasing, • Define what a 'Requirement' is and its importance to
setting-up and executing an automated test environment. the QA process
• Explain what a Software Requirements Specification
In addition, this module reviews automated testing methods (SRS) Document and its importance
that allow for the quick capture and reuse of quality • Explain how and where requirements fit into the
activities to share and repeat throughout the testing life (SDLC)
cycle. • Explain how a Requirements Traceability Matrix is
used and its importance
You Will Be Able To: • Define characteristics that make requirements
testable
• Explain the key functions of an automated test tool
• Understand the advantages and disadvantages of using an
Main Topics Covered:
automated tool
• Understand the issues surrounding test automation
• Project Management Documentation:
• Understand what to automate and what not to automate
• Software Quality Assurance Documentation
• Software Configuration Management
Documentation
Main Topics Covered:
• Software Verification and Validation
Documentation
• Concepts of Automated Testing
• Requirements Documentation
• Why Automate Testing
• Design and Implementation Documentation
• Functions of Automated Test Tools
4
CERTIFIED TESTER PROFESSIONAL PROGRAM