Audience
| X |
|
Software Process Architects |
|
√ |
|
QA/Test Managers |
|
√ |
|
Development Managers |
| X |
|
Business Analysts |
|
√ |
|
QA User Testers |
|
√ |
|
Software Developers |
| X |
|
Project Managers |
|
√ |
|
QA Code Testers |
|
X |
|
User Education Specialists |
| |
|
|
|
|
|
|
|
|
|
|
at course completion
After completing this course, students will be able to:
| » |
|
Understand software quality |
|
» |
|
Optimize collaboration with user testers |
| » |
|
Understand defects and defect causes |
|
» |
|
Make smart usage of test-driven development (TDD) |
| » |
|
Understand and apply testing techniques |
|
» |
|
Create unit, integration and system code tests |
| » |
|
Improve testability through anticipated designs |
|
» |
|
Create an automation testing strategy |
| » |
|
Determine optimal development test strategies |
|
» |
|
Select and configure unit test frameworks |
| » |
|
Understand the importance of code-level testing |
|
» |
|
Execute tests efficiently and report test results |
prerequisites
| » |
|
Basic or intermediate experience in software development |
course materials
A comprehensive workbook with knowledge material, examples, case studies, lab exercises, and references.
| course outline |
|
|
 Module 1: Fundamental Testing Concepts
| » |
|
Defects, risks, and test coverage |
| » |
|
Software testing pipeline |
| » |
|
Fundamental testing methods |
| » |
|
Test strategy and test case design |
| » |
|
Test execution, defect tracking and automation |
Module 2: Motivation for Developer Testing
| » |
|
Effectiveness of non-blackbox defect detection |
| » |
|
Defects found through developer testing only |
| » |
|
Force of combining user and developer testing |
| » |
|
Reduction of cycle time through developer testing |
Module 3: Developer Testing in the Development Life Cycle
| » |
|
Testing code versus specs |
| » |
|
Testing first or coding first |
| » |
|
Selecting test depth and test items |
| » |
|
Scheduling developer testing |
| » |
|
Evaluating developer testing effectiveness |
Module 4: Planning for Testing
| » |
|
Test strategy development |
| » |
|
Design for testability |
| » |
|
Drivers, stubs and triggers |
| » |
|
Developer testing infrastructure |
| » |
|
Debug code instrumentation |
| » |
|
Code reviews |
Module 5: Unit Testing
| » |
|
Unit testing targets and techniques |
| » |
|
What developer unit tests do and do not detect |
| » |
|
Challenge of testing in isolation |
| » |
|
Testing classes and objects |
| » |
|
Testing error conditions |
Module 6: Integration Testing
| » |
|
Integration testing targets and techniques |
| » |
|
What developer integration tests do and do not detect |
| » |
|
Choosing the combinations of test items |
| » |
|
Testing combined classes and objects |
| » |
|
Testing control flow and data flow in interfaces |
Module 7: Regression Testing
| » |
|
Causes of regressions |
| » |
|
How to build effective regression tests suites |
| » |
|
When to execute regression tests |
| » |
|
Test automation for regression testing |
Module 8: Test Management
| » |
|
Collaboration with user testers |
| » |
|
Test scheduling |
| » |
|
Test execution management |
| » |
|
Code defect reporting and tracking |
| » |
|
Test and defect metrics |
Module 9: Test Automation and Tools
| » |
|
Test automation strategies |
| » |
|
Automation types and tools |
| » |
|
Unit test frameworks |
| » |
|
Enabling test automation through design testability |
| » |
|
Code coverage tools |
| » |
|
Miscellaneous test productivity tools |
certificate
Students receive a SoftO2 Education Certificate upon completion of the course.
take this training
Contact SoftO2 Education or send the following form to register or request information.
|
