| Who Sholud Attend |
|
Individuals who desire to reinforce their skills, knowledge, and capacity to understand the Certified Software Tester Common Body of Knowledge in preparation for pursuing CSTE certification.
|
| |
| Workshop Objectives |
The CSTE Exam Study Course is presented in a way that reinforces current knowledge, re-introduces concepts that may not be used everyday, explains the rationale for use, and highlights sample questions, both multiple choice and essay type responses. After the completion of the course, the participants would be able to:
- Use a systematic approach to effective software testing.
- Plan and manage the entire testing process based on risk planning
- Gain a better control over the test activities and the quality of the software product.
- Understand quality assurance aspects of testing
- Write a test plan, what needs to go into an effective plan, and how to implement it.
- Understand and appreciate the steps involved in test design
- Understand and practice the test case design techniques
- Understand and appreciate the importance of metrics in the test management process.
- Understand Testing as defined by Software Standards and models
- Understand the steps involved in Test Process Improvement
|
| CSTE Preparatory Workshop (Three-day Training) |
|
The Program is a mix of instructor led and self
paced learning, designed to enable the participants
discuss and assimilate the concepts involving application
of Project management concepts / techniques specified
in the PMBOK® Guide (Third Edition)
and supplementary material required for the PMP®
examination.
To enable a
thorough grasp of the concepts taught in the classroom,
the Program has been broken down into several sections
around the PMBOK® Guide Knowledge
Areas. Each section covers definitions, examples,
exercises and memory joggers to facilitate the learning
and application of the contents.
|
| |
| Workshop
Pre-requisites |
| 2006 CSTE Body of Knowledge |
| Knowledge Category 1- Software Testing Principles and Concepts |
The “basics” of software testing are represented by the vocabulary of testing, testing approaches, methods and techniques as well as the materials used by testers in performing their test activities. Specifically, this knowledge category will address:
- Testing Techniques
- Levels of Testing
- Testing Different Types of Software
- Independent Testing
- Vocabulary
- The Multiple Roles of Software Testers
- Testers Workbench
- The “V” Concept of Testing
|
| Knowledge Category 2 - Building the Test Environment |
The test environment is comprised of all the conditions, circumstances, and influences surrounding and affecting the testing of software. The environment includes the organization’s policies, procedures, culture, attitudes, rewards, test processes, test tools, methods for developing and improving test processes, management’s support of software testing, as well as any test labs developed for the purpose of testing software and multiple operating environments.
This category also includes assuring the test environment fairly represents the production environment to enable realistic testing to occur. Specifically this knowledge category will address:
- Knowledge of Test Process Selection and Analysis
- Test Tools
- Management Support for Effective Software Testing
|
| Knowledge Category 3 - Managing the Test Project |
Software testing is a project with almost all the same attributes as a software development project. Software testing involves project planning, project staffing, scheduling and budgeting, communicating, assigning and monitoring work and ensuring that changes to the project plan are incorporated into the test plan. Specifically this knowledge category will address:
- Test Administration and Organizational Structure
- Personal and Organizational Effectiveness
- Leadership
|
| Knowledge Category 4 - Test Planning |
Testers need the skills to plan tests, including the selection of techniques and methods to be used to validate the product against its approved requirements and design. Test planning assesses the business and technical risks of the software application, and then develops a plan to determine if the software minimizes those risks. Test planners must understand the development methods and environment to effectively plan for testing, including regression testing. Specifically this knowledge category will address:
- Prerequisites to Test Planning
- Test Planning Entrance Criteria
|
Knowledge Category 5 - Executing the Test Plan |
The skills needed to execute tests, design test cases; use test tools; and monitor testing to ensure correctness and completeness. Specifically this knowledge category will address:
- Test Design and Test Data/Scripts Preparation
- Performing Tests
- Defect Tracking
- Testing Software Changes
|
Knowledge Category 6 - Test Status, Analysis and Reporting |
The testers need to demonstrate the ability to develop testing status reports. These reports should show the status of the testing based on the test plan. Reporting should document what tests have been performed and the status of those tests. To properly report status, the testers should review and conduct statistical analysis on the test results and discovered defects. The lessons learned from the test effort should be used to improve the next iteration of the test process.
Metrics of Testing Metrics specific to testing include data collected on testing, defect tracking, and software performance. Use quantitative measures and metrics to manage the planning, execution, and reporting of software testing, should focus on whether test objectives and goals are being reached.
- Test Status Reports
- Final Test Reports
|
Knowledge Category 7 - User Acceptance Testing |
The objective of software development is to develop the software that meets the true needs of the user, not just the system specifications. To accomplish this, testers should work with the users early in a project to clearly define the criteria that would make the software acceptable in meeting the user needs. As much as possible, once the acceptance criterion has been established, they should integrate those criteria into all aspects of development. This same process can be used by software testers when users are unavailable for test; when diverse users use the same software; and for beta testing software.
- Concepts of Acceptance Testing
- Roles and Responsibilities
- Acceptance Test Planning Process
- Acceptance Test Execution
|
| Knowledge Category 8 - Testing Software Developed by Outside Organizations |
Many organizations do not have the resources to develop the type and/or volume of software needed to effectively manage their business. The solution is to obtain or contract for software developed by another organization. Software can be acquired by purchasing off the shelf software (COTS) or contracting for all or parts of the software development to be done by outside organizations, often referred to as outsourcing. Software testers need to be involved in the process of testing software acquired from outsourcers. Specifically, this category addresses:
- The difference in testing software developed in-house versus software developed by outside organizations.
- Differences between testing software developed in-house and software developed by outside organizations.
Selection Process for Acquired Software:
- Testing Acquired Software
- Testers Involvement in Testing Changes for Purchased/Contracted Software
|
Knowledge Category 9 - Testing Software Controls and the adequacy of Security Procedures |
The software system of internal control includes the totality of the means developed to ensure the integrity of the software system and the products created by the software. Controls are employed to control the processing components of software, assure that software processing is in accordance with the organization's policies and procedures, and according to applicable laws and regulations. Software systems are divided into two parts, the part that performs the processing and the part that controls processing. The control part includes a system of controls as well as the means employed to assure processing cannot be penetrated by outside sources. This category addresses all the components of the software system of internal control and security procedures.
- Principles and Concepts of a Software System of Internal Control and Security
- Testing the System of Internal Controls
- Testing the Adequacy of Security for a Software System
|
Knowledge Category 10 - Testing New Technologies |
Testers require skills in their organization’s current technology, as well as a general understanding of the new information technology that might be acquired by their organization. This knowledge category addresses:
- An Understanding of the New Testing Challenges with These Technologies
- Evaluating New Technologies to Fit into the Organization’s Policies and Procedures
|
| |