Introduction

Testing is an essential activity in a software process. Planning for software testing involves establishing an overall testing strategy for a project.

The testing strategy includes organizing testing at three levels—unit, integration, and high-order. It also involves procuring tools to automate testing and identifying the people who will perform testing. In addition, planning is required for debugging—the process of diagnosing and fixing the problems detected during testing.

Software Testing Strategies course includes:

• Planning for Software Testing
• An Overview of the Testing Strategy
• Unit Testing
• Integration Testing
• High-order Testing
• Roles-and Organization for Testing
• Debugging

This course has been co-authored by the internationally recognized consultant and authority on software engineering—Dr. Roger S. Pressman.

Course Benefits

This course will enable you to:

• Explain the factors to consider for planning effective software testing.
• Explain the broad issues to consider while deciding a testing strategy for a software project.
• Explain unit testing and the aspects to consider while deciding a strategy for it.
• Explain integration testing and the aspects to consider while deciding a strategy for it.
• Explain high-order testing and the aspects to consider while deciding a strategy for it.
• Explain the role of a tester and various options for organizing the testing activity.
• Explain what debugging involves.

You receive a certificate of completion after successfully completing this course.

Content Brief

Planning for software testing starts with establishing an overall testing strategy. This provides a framework for detailed planning. The strategy specifies the manner in which unit, integration, and high-order testing will be performed. It also specifies the types of test case design techniques that will be used and the completion criteria for testing. The testing strategy also identifies the testing organization, process, and tools.

Testing should proceed from the ‘small’ to the ‘big’, that is, from unit testing through integration testing to high-order testing.

Unit testing ensures that each unit functions according to its specifications. Integration testing is performed after unit testing. It focuses on the problems related to integration of units that function correctly when used individually. An overall testing strategy defines the phases in which to integrate units for testing. After integration testing is complete and the errors detected are fixed, regression testing is required to ensure that the changes made to the software have not introduced new errors. High-order testing checks that the software meets customer requirements and that the software, along with other system elements, meets the functional, behavioral, and performance requirements.