book

Software Testing Foundations, 4th Edition, 4th Edition

by Andreas Spillner, Tilo Linz, Hans Schaefer

March 2014

Intermediate to advanced

304 pages

7h 59m

English

Rocky Nook

Read now

Unlock full access

2.1 Terms and Motivation2.1.1 Error, Defect, and Bug Terminology2.1.2 Testing Terms2.1.3 Software Quality2.1.4 Test Effort2.2 The Fundamental Test Process2.2.1 Test Planning and Control2.2.2 Test Analysis and Design2.2.3 Test Implementation and Execution2.2.4 Test Evaluation and Reporting2.2.5 Test Closure Activities2.3 The Psychology of Testing2.4 General Principles of Testing2.5 Ethical Guidelines2.6 Summary
3.1 The General V-Model3.2 Component Test3.2.1 Explanation of Terms3.2.2 Test objects3.2.3 Test Environment3.2.4 Test objectives3.2.5 Test Strategy3.3 Integration Test3.3.1 Explanation of Terms3.3.2 Test objects3.3.3 The Test Environment3.3.4 Test objectives3.3.5 Integration Strategies3.4 System Test3.4.1 Explanation of Terms3.4.2 Test Objects and Test Environment3.4.3 Test Objectives3.4.4 Problems in System Test Practice3.5 Acceptance Test3.5.1 Contract Acceptance Testing3.5.2 Testing for User Acceptance3.5.3 Operational (Acceptance) Testing3.5.4 Field Testing3.6 Testing New Product Versions3.6.1 Software Maintenance3.6.2 Testing after Further Development3.6.3 Testing in Incremental Development3.7 Generic Types of Testing3.7.1 Functional Testing3.7.2 Nonfunctional Testing3.7.3 Testing of Software Structure3.7.4 Testing Related to Changes and Regression Testing3.8 Summary
4.1 Structured Group Evaluations4.1.1 Foundations4.1.2 Reviews4.1.3 The General ProcessPlanningKick-OffIndividual PreparationReview MeetingReworkFollow-Up4.1.4 Roles and ResponsibilitiesPossible difficulties4.1.5 Types of ReviewsWalkthroughInspectionTechnical ReviewInformal ReviewSelection CriteriaNotesSuccess Factors4.2 Static Analysis4.2.1 The Compiler as a Static Analysis Tool4.2.2 Examination of Compliance to Conventions and Standards4.2.3 Execution of Data Flow Analysis4.2.4 Execution of Control Flow Analysis4.2.5 Determining Metrics4.3 Summary

5.1 Black Box Testing Techniques5.1.1 Equivalence Class PartitioningTest CasesDefinition of Test Exit CriteriaThe Value of the Technique5.1.2 Boundary Value AnalysisTest CasesDefinition of the Test Exit CriteriaThe Value of the Technique5.1.3 State Transition TestingTest CasesDefinition of the Test Exit CriteriaThe Value of the Technique5.1.4 Logic-Based Techniques (Cause-Effect Graphing and Decision Table Technique, Pairwise Testing)Test CasesDefinition of the Test Exit CriteriaThe Value of the TechniquePairwise Combination Testing5.1.5 Use-Case-Based TestingTest CasesDefinition of the Test Exit CriteriaThe Value of the Technique5.1.6 General Discussion of the Black Box Technique5.2 White Box Testing Techniques5.2.1 Statement Testing and CoverageTest casesDefinition of the Test Exit CriteriaThe Value of the Technique5.2.2 Decision/Branch Testing and CoverageTest CasesDefinition of the Test Exit CriteriaThe Value of the Technique5.2.3 Test of ConditionsCondition Testing and CoverageMultiple Condition Testing and CoverageCondition Determination Testing / Minimal Multiple Condition TestingTest CasesDefinition of the Test Exit CriteriaThe Value of the Technique5.2.4 Further White Box Techniques5.2.5 General Discussion of the White Box Technique5.2.6 Instrumentation and Tool Support5.3 Intuitive and Experience-Based Test Case DeterminationTest CasesDefinition of the Test Exit CriteriaThe Value of the Technique5.4 Summary
6.1 Test Organization6.1.1 Test TeamsComponent TestingIntegration TestingSystem Testing6.1.2 Tasks and Qualifications6.2 Planning6.2.1 Quality Assurance Plan6.2.2 Test Plan6.2.3 Prioritizing Tests6.2.4 Test Entry and Exit Criteria6.3 Cost and Economy Aspects6.3.1 Costs of Defects6.3.2 Cost of Testing6.3.3 Test Effort Estimation6.4 Choosing the Test Strategy and Test Approach6.4.1 Preventative vs. Reactive Approach6.4.2 Analytical vs. Heuristic Approach6.4.3 Testing and Risk6.5 Managing The Test Work6.5.1 Test Cycle Planning6.5.2 Test Cycle Monitoring6.5.3 Test Cycle Control6.6 Incident Management6.6.1 Test Log6.6.2 Incident Reporting6.6.3 Defect Classification6.6.4 Incident Status6.7 Requirements to Configuration Management6.8 Relevant Standards6.9 Summary
7.1 Types of Test Tools7.1.1 Tools for Management and Control of Testing and Tests7.1.2 Tools for Test Specification7.1.3 Tools for Static Testing7.1.4 Tools for Dynamic Testing7.1.5 Tools for Nonfunctional Test7.2 Selection and Introduction of Test Tools7.2.1 Cost Effectiveness of Tool Introduction7.2.2 Tool Selection7.2.3 Tool Introduction7.3 Summary
Test Plan IdentifierIntroductionTest Objects or ItemsFeatures to Be TestedFeatures Not to Be TestedTest Approach or StrategyAcceptance Criteria (Test Item Pass/Fail Criteria)Suspension Criteria and Resumption RequirementsTest Documentation and DeliverablesTesting TasksTest Infrastructure and Environmental NeedsResponsibilities and AuthorityStaffing and Training NeedsScheduleRisks and ContingenciesApprovalGlossary (not in IEEE829-1998, but lower case!)Test Plans According to IEEE Standard 829-2008The Master Test PlanMaster Test Plan Identifier1. Introduction1.2 Scope1.3 References1.4 System Overview and Key Features1.5 Test overview1.5.1 Organization1.5.2 Master Test Schedule1.5.3 Integrity Level Scheme1.5.4 Summary of Necessary Resources1.5.5 Responsibilities and Authority1.5.6 Tools, Techniques, Methods, and Metrics2. Details of the Master Test Plan2.1 Test Processes, Including Definition of Test Levels2.1.1 through 2.1.6 “Life cycle” Processes, i.e., Activities and Tasks2.2 Test Documentation Requirements2.3 Test Administration Requirements2.3.1 Anomaly (defect) Resolution and Reporting2.3.2 Task Iteration Policy2.3.3 Deviation Policy2.3.4 Control Procedures2.3.5 Standards, Practices, and Conventions2.4 Test Reporting Requirements3. General3.1 Glossary3.2 Document Change Procedures and HistoryThe Level Test PlanThe template from the standardGuidance for section 3.4Guidance for sections 4.1 through 4.34.1 Quality assurance procedures4.2 Metrics4.3 Test coverage
Exercises for chapter 2Exercises for chapter 3Exercises for chapter 4Exercises for chapter 5Exercises for chapter 6Exercises for chapter 7
Further Recommended LiteratureStandardsWWW Pages
Preface2 Fundamentals of Testing3 Testing in the Software Life Cycle4 Static Test5 Dynamic Analysis – Test Design Techniques6 Test Management7 Test ToolsA Test Plan According to IEEE Standard 829-1998C Exercises

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

A Test Plan According to IEEE Standard 829-1998

This appendix describes the contents of a test plan according to IEEE Standard 829-1998.¹ It can be used as a guide to prepare a test plan.

Test Plan Identifier

Specify uniquely the name and version of the test plan. The identifier must make it possible to clearly and precisely refer to this document distinct from other project documents. A standard for document identification is often given by rules set by the project archive or by the organization’s central document management. Depending on the size of the project organization, the identifier may be more or less complicated. The minimum information to be used is the name of the test plan, its version, and its status.