Software Testing Exam  >  Software Testing Notes  >  Chapter-13-Software-Testing-Strategies--

Chapter-13-Software-Testing-Strategies-- - Software Testing PDF Download

Download, print and study this document offline
Please wait while the PDF view is loading
 Page 1


Chapter 13 
Software Testing Strategies 
 
 
   
- A strategic approach to testing 
- Test strategies for conventional software 
- Test strategies for object-oriented software 
- Validation testing 
- System testing 
- The art of debugging 
 
 
(Source: Pressman, R. Software Engineering: A Practitioner’ s Approach.  McGraw-Hill, 2005) 
Page 2


Chapter 13 
Software Testing Strategies 
 
 
   
- A strategic approach to testing 
- Test strategies for conventional software 
- Test strategies for object-oriented software 
- Validation testing 
- System testing 
- The art of debugging 
 
 
(Source: Pressman, R. Software Engineering: A Practitioner’ s Approach.  McGraw-Hill, 2005) 
2 
Introduction 
• A strategy for software testing integrates the design of software test 
cases into a well-planned series of steps that result in successful 
development of the software 
• The strategy provides a road map that describes the steps to be taken, 
when, and how much effort, time, and resources will be required 
• The strategy incorporates test planning, test case design, test execution, 
and test result collection and evaluation 
• The strategy provides guidance for the practitioner and a set of 
milestones for the manager 
• Because of time pressures, progress must be measurable and problems 
must surface as early as possible 
Page 3


Chapter 13 
Software Testing Strategies 
 
 
   
- A strategic approach to testing 
- Test strategies for conventional software 
- Test strategies for object-oriented software 
- Validation testing 
- System testing 
- The art of debugging 
 
 
(Source: Pressman, R. Software Engineering: A Practitioner’ s Approach.  McGraw-Hill, 2005) 
2 
Introduction 
• A strategy for software testing integrates the design of software test 
cases into a well-planned series of steps that result in successful 
development of the software 
• The strategy provides a road map that describes the steps to be taken, 
when, and how much effort, time, and resources will be required 
• The strategy incorporates test planning, test case design, test execution, 
and test result collection and evaluation 
• The strategy provides guidance for the practitioner and a set of 
milestones for the manager 
• Because of time pressures, progress must be measurable and problems 
must surface as early as possible 
A Strategic Approach to Testing 
Page 4


Chapter 13 
Software Testing Strategies 
 
 
   
- A strategic approach to testing 
- Test strategies for conventional software 
- Test strategies for object-oriented software 
- Validation testing 
- System testing 
- The art of debugging 
 
 
(Source: Pressman, R. Software Engineering: A Practitioner’ s Approach.  McGraw-Hill, 2005) 
2 
Introduction 
• A strategy for software testing integrates the design of software test 
cases into a well-planned series of steps that result in successful 
development of the software 
• The strategy provides a road map that describes the steps to be taken, 
when, and how much effort, time, and resources will be required 
• The strategy incorporates test planning, test case design, test execution, 
and test result collection and evaluation 
• The strategy provides guidance for the practitioner and a set of 
milestones for the manager 
• Because of time pressures, progress must be measurable and problems 
must surface as early as possible 
A Strategic Approach to Testing 
4 
General Characteristics of 
Strategic Testing 
• To perform effective testing, a software team should conduct effective 
formal technical reviews 
• Testing begins at the component level and work outward toward the 
integration of the entire computer-based system 
• Different testing techniques are appropriate at different points in time 
• Testing is conducted by the developer of the software and (for large 
projects) by an independent test group 
• Testing and debugging are different activities, but debugging must be 
accommodated in any testing strategy  
 
Page 5


Chapter 13 
Software Testing Strategies 
 
 
   
- A strategic approach to testing 
- Test strategies for conventional software 
- Test strategies for object-oriented software 
- Validation testing 
- System testing 
- The art of debugging 
 
 
(Source: Pressman, R. Software Engineering: A Practitioner’ s Approach.  McGraw-Hill, 2005) 
2 
Introduction 
• A strategy for software testing integrates the design of software test 
cases into a well-planned series of steps that result in successful 
development of the software 
• The strategy provides a road map that describes the steps to be taken, 
when, and how much effort, time, and resources will be required 
• The strategy incorporates test planning, test case design, test execution, 
and test result collection and evaluation 
• The strategy provides guidance for the practitioner and a set of 
milestones for the manager 
• Because of time pressures, progress must be measurable and problems 
must surface as early as possible 
A Strategic Approach to Testing 
4 
General Characteristics of 
Strategic Testing 
• To perform effective testing, a software team should conduct effective 
formal technical reviews 
• Testing begins at the component level and work outward toward the 
integration of the entire computer-based system 
• Different testing techniques are appropriate at different points in time 
• Testing is conducted by the developer of the software and (for large 
projects) by an independent test group 
• Testing and debugging are different activities, but debugging must be 
accommodated in any testing strategy  
 
5 
Verification and Validation 
• Software testing is part of a broader group of activities called verification 
and validation that are involved in software quality assurance 
• Verification (Are the algorithms coded correctly?) 
– The set of activities that ensure that software correctly implements a specific 
function or algorithm 
• Validation (Does it meet user requirements?) 
– The set of activities that ensure that the software that has been built is 
traceable to customer requirements 
Read More

FAQs on Chapter-13-Software-Testing-Strategies-- - Software Testing

1. What is software testing and why is it important?
Ans. Software testing is the process of evaluating a software application or system to identify any defects or errors. It is important because it helps ensure that the software meets the desired quality standards, functions as intended, and provides a positive user experience.
2. What are the different types of software testing strategies?
Ans. There are several types of software testing strategies, including unit testing, integration testing, system testing, acceptance testing, and regression testing. Each strategy focuses on different aspects of the software and is used at different stages of the software development process.
3. What is the difference between manual testing and automated testing?
Ans. Manual testing is the process of manually executing test cases and evaluating the software's behavior. It requires human intervention and is time-consuming. On the other hand, automated testing involves using tools and scripts to execute test cases, making it faster and more efficient. Automated testing is often used for repetitive tasks and regression testing.
4. How can test coverage be improved in software testing?
Ans. Test coverage refers to the extent to which the software has been tested. It can be improved by identifying and creating test cases for all possible scenarios, including both positive and negative scenarios. Test coverage can also be improved by using techniques such as equivalence partitioning, boundary value analysis, and decision table testing.
5. What are the advantages of implementing a structured software testing process?
Ans. Implementing a structured software testing process offers several advantages. It helps identify defects and errors early in the development process, reducing the cost and effort required for fixing them later. It also improves the overall quality and reliability of the software, enhances user satisfaction, and ensures compliance with quality standards. Additionally, a structured testing process helps in effective collaboration among the development and testing teams.
Download as PDF
Explore Courses for Software Testing exam
Related Searches

Sample Paper

,

Exam

,

Semester Notes

,

Previous Year Questions with Solutions

,

mock tests for examination

,

ppt

,

Important questions

,

Extra Questions

,

past year papers

,

Chapter-13-Software-Testing-Strategies-- - Software Testing

,

Chapter-13-Software-Testing-Strategies-- - Software Testing

,

shortcuts and tricks

,

Chapter-13-Software-Testing-Strategies-- - Software Testing

,

pdf

,

Summary

,

practice quizzes

,

Free

,

video lectures

,

MCQs

,

Objective type Questions

,

Viva Questions

,

study material

;