book

Software Testing Foundations, 5th Edition, 5th Edition

by Andreas Spillner, Tilo Linz

July 2021

Intermediate to advanced

340 pages

8h 47m

English

Rocky Nook

Read now

Unlock full access

2.1 Concepts and Motivations2.1.1 Defect and Fault Terminology2.1.2 Testing Terminology2.1.3 Test Artifacts and the Relationships Between Them2.1.4 Testing Effort2.1.5 Applying Testing Skills Early Ensures Success2.1.6 The Basic Principles of Testing2.2 Software Quality2.2.1 Software Quality according to ISO 250102.2.2 Quality Management and Quality Assurance2.3 The Testing Process2.3.1 Test Planning2.3.2 Test Monitoring and Control2.3.3 Test Analysis2.3.4 Test Design2.3.5 Test Implementation2.3.6 Test Execution2.3.7 Test Completion2.3.8 Traceability2.3.9 The Influence of Context on the Test Process2.4 The Effects of Human Psychology on Testing2.4.1 How Testers and Developers Think2.5 Summary

3.1 Sequential Development Models3.1.1 The Waterfall Model3.1.2 The V-Model3.2 Iterative and Incremental Development Models3.3 Software Development in Project and Product Contexts3.4 Testing Levels3.4.1 Component Testing3.4.2 Integration Testing3.4.3 System Testing3.4.4 Acceptance Testing3.5 Test Types3.5.1 Functional Tests3.5.2 Non-Functional Tests3.5.3 Requirements-Based and Structure-Based Testing3.6 Testing New Product Versions3.6.1 Testing Following Software Maintenance3.6.2 Testing Following Release Development3.6.3 Regression Testing3.7 Summary
4.1 What Can We Analyze and Test?4.2 Static Test Techniques4.3 The Review Process4.3.1 Review Process Activities4.3.2 Different Individual Review Techniques4.3.3 Roles and Responsibilities within the Review Process4.4 Types of Review4.5 Critical Factors, Benefits, and Limits4.6 The Differences Between Static and Dynamic Testing4.7 Summary
5.1 Black-Box Test Techniques5.1.1 Equivalence Partitioning5.1.2 Boundary Value Analysis5.1.3 State Transition Testing5.1.4 Decision Table Testing5.1.5 Pair-Wise Testing5.1.6 Use-Case Testing5.1.7 Evaluation of Black-Box Testing
5.2.1 Statement Testing and Coverage5.2.2 Decision Testing and Coverage5.2.3 Testing Conditions5.2.4 Evaluation of White-Box Testing5.3 Experience-Based Test Techniques5.4 Selecting the Right Technique5.5 Summary
6.1 Test Organization6.1.1 Independent Testing6.1.2 Roles, Tasks, and Qualifications6.2 Testing Strategies6.2.1 Test Planning6.2.2 Selecting a Testing Strategy6.2.3 Concrete Strategies6.2.4 Testing and Risk6.2.5 Testing Effort and Costs6.2.6 Estimating Testing Effort6.2.7 The Cost of Testing vs. The Cost of Defects6.3 Test Planning, Control, and Monitoring6.3.1 Test Execution Planning6.3.2 Test Control6.3.3 Test Cycle Monitoring6.3.4 Test Reports6.4 Defect Management6.4.1 Evaluating Test Reports6.4.2 Creating a Defect Report6.4.3 Classifying Failures and Defects6.4.4 Defect Status Tracking6.4.5 Evaluation and Reporting6.5 Configuration Management6.6 Relevant Standards and Norms6.7 Summary
7.1 Types of Test Tools7.1.1 Test Management Tools7.1.2 Test Specification Tools7.1.3 Static Test Tools7.1.4 Tools for Automating Dynamic Tests7.1.5 Load and Performance Testing Tools7.1.6 Tool-Based Support for Other Kinds of Tests7.2 Benefits and Risks of Test Automation7.3 Using Test Tools Effectively7.3.1 Basic Considerations and Principles7.3.2 Tool Selection7.3.3 Pilot Project7.3.4 Success Factors During Rollout and Use7.4 Summary
C.1 LiteratureC.2 Norms and StandardsC.3 URLs

Content preview from Software Testing Foundations, 5th Edition, 5th Edition

5Dynamic Testing

This chapter describes the process of testing software by running it on a computer. It uses examples to illustrate various ways to specify test cases and exit criteria. Dynamic testing is based on black-box, white-box, and experience-based techniques. We explain what each category means and how to choose the appropriate one for your situation.

Running the test object on a computer

When we talk about software testing, most people imagine that it involves running a program on a computer. The term “dynamic testing” helps to clarify the situation. The test object has to be executable and is fed with input data before it is run. Because low-level test objects (component and integration tests) are not usually executable, dynamic ...