1.2 10 1.2 1 10 mods info:srw/schema/1/mods-v3.5 xml 1Bierig, Ralf,1976-author.Brown, Stephen C. (Stephen Charles),1961-author.Galván, Edgar,1977-author.Timoney, Joseph,author.texttextbookenkCambridge :Cambridge University Press,2022.2022First edition.single uniteng

electronic resource

remote

1 online resource (xiii, 304 pages) : digital, PDF file(s).

computer

online resource

Software testing can be regarded as an art, a craft, and a science. The practical, step-by-step approach presented in this book provides a bridge between these different viewpoints. A single worked example runs throughout, with consistent use of test automation. Each testing technique is introduced in the context of this example, helping students see its strengths and weaknesses. The technique is then explained in more detail, providing a deeper understanding of underlying principles. Finally the limitations of each technique are demonstrated by inserting faults, giving learners concrete examples of when each technique succeeds or fails in finding faults. Coverage includes black-box testing, white-box testing, random testing, unit testing, object-oriented testing, and application testing. The authors also emphasise the process of applying the techniques, covering the steps of analysis, test design, test implementation, and interpretation of results. The book's web site has programming exercises and Java source code for all examples.Cover -- Half-title -- Title page -- Copyright information -- Contents -- Preface -- Epigraph -- Acknowledgements -- 1 Introduction to Software Testing -- 1.1 The Software Industry -- 1.1.1 Software Testing and Quality -- 1.1.2 Software Testing and Risk Management -- 1.2 Mistakes, Faults, and Failures -- 1.2.1 Mistakes -- 1.2.2 Software Faults -- 1.2.3 Software Failures -- 1.2.4 Need for Testing -- 1.3 The Role of Specifications -- 1.4 Manual Test Example -- 1.5 The Theory of Software Testing -- 1.6 Exhaustive Testing -- 1.6.1 Exhaustive Test Data -- 1.6.2 Feasibility of Exhaustive Testing -- 1.7 Test Heuristics -- 1.7.1 Random Testing -- 1.7.2 Black-Box and White-Box Testing -- 1.7.3 Experience-Based Testing -- 1.7.4 Fault Insertion -- 1.8 When to Finish Testing -- 1.9 Static and Dynamic Testing -- 1.9.1 Review-Based Techniques -- 1.9.2 Program Proving -- 1.10 Testing in the Software Development Process -- 1.11 Software Testing Activities -- 1.11.1 Analysis -- 1.11.2 Test Coverage Items -- 1.11.3 Test Cases -- 1.11.4 Test Design Verification -- 1.11.5 Test Implementation -- 1.12 Test Artefacts -- 1.13 Fault Models -- 1.14 Using this Book -- 1.14.1 Book Structure -- 1.14.2 Order of Testing -- 1.14.3 Documenting Test Design -- 1.14.4 The Programming Language -- 1.14.5 Level of Detail -- 1.14.6 Examples -- 1.14.7 Software Test Tools -- 1.15 Notes on Terminology -- 2 Equivalence Partitions -- 2.1 Testing with Equivalence Partitions -- 2.2 Example -- 2.2.1 Analysis: Identifying the Equivalence Partitions -- 2.2.2 Test Coverage Items -- 2.2.3 Test Cases -- 2.2.4 Verification of the Test Cases -- 2.3 Test Implementation and Results -- 2.3.1 Manual Test Output -- 2.3.2 Automated Test Implementation -- 2.3.3 Test Results -- 2.4 Equivalence Partitions in More Detail -- 2.4.1 Fault Model -- 2.4.2 Description.2.4.3 Analysis: Identifying Equivalence Partitions -- 2.4.4 Test Coverage Items -- 2.4.5 Test Cases -- 2.4.6 Pitfalls -- 2.5 Evaluation -- 2.5.1 Limitations -- 2.5.2 Strengths and Weaknesses -- 2.6 Key Points -- 2.7 Notes for Experienced Testers -- 3 Boundary Value Analysis -- 3.1 Testing with Boundary Value Analysis -- 3.2 Example -- 3.2.1 Analysis: Identifying the Boundary Values -- 3.2.2 Test Coverage Items -- 3.2.3 Test Cases -- 3.2.4 Verification of the Test Cases -- 3.3 Test Implementation and Results -- 3.3.1 Implementation -- 3.3.2 Test Results -- 3.4 Boundary Value Analysis in More Detail -- 3.4.1 Fault Model -- 3.4.2 Description -- 3.4.3 Analysis: Identifying Boundary Values -- 3.4.4 Test Coverage Items -- 3.4.5 Test Cases -- 3.4.6 Pitfalls -- 3.5 Evaluation -- 3.5.1 Limitations -- 3.5.2 Strengths and Weaknesses -- 3.6 Key Points -- 3.7 Notes for Experienced Testers -- 4 Decision Table Testing -- 4.1 Testing Combinations with Decision Tables -- 4.2 Example -- 4.2.1 Analysis -- 4.2.2 Test Coverage Items -- 4.2.3 Test Cases -- 4.2.4 Verification of the Test Cases -- 4.3 Test Implementation and Results -- 4.3.1 Implementation -- 4.3.2 Test Results -- 4.4 A More Detailed Look at Testing with Decision Tables -- 4.4.1 Fault Model -- 4.4.2 Description -- 4.4.3 Analysis: Developing Decision Tables -- 4.4.4 Test Coverage Items -- 4.4.5 Test Cases -- 4.4.6 Pitfalls -- 4.5 Evaluation -- 4.5.1 Limitations -- 4.5.2 Strengths and Weaknesses -- 4.6 Key Points -- 4.7 Notes for Experienced Testers -- 5 Statement Coverage -- 5.1 Introduction to White-Box Testing -- 5.2 Testing with Statement Coverage -- 5.2.1 Statement Coverage Measurement -- 5.3 Example -- 5.3.1 Analysis: Identifying Unexecuted Statements -- 5.3.2 Test Coverage Items -- 5.3.3 Test Cases -- 5.3.4 Verification of the Test Cases -- 5.4 Test Implementation and Results -- 5.4.1 Implementation.5.4.2 Test Results -- 5.5 Statement Coverage Testing in More Detail -- 5.5.1 Fault Model -- 5.5.2 Description -- 5.5.3 Analysis: Identifying Unexecuted Statements -- 5.5.4 Test Coverage Items -- 5.5.5 Test Cases -- 5.6 Evaluation -- 5.6.1 Limitations -- 5.6.2 Strengths and Weaknesses -- 5.7 Key Points -- 5.8 Notes for Experienced Testers -- 6 Branch Coverage -- 6.1 Testing with Branch Coverage -- 6.1.1 Branch Coverage Measurement -- 6.2 Example -- 6.2.1 Analysis: Identifying Untaken Branches -- 6.2.2 Test Coverage Items -- 6.2.3 Test Cases -- 6.2.4 Verification of the Test Cases -- 6.3 Test Implementation and Results -- 6.3.1 Implementation -- 6.3.2 Test Results -- 6.4 Branch Coverage in More Detail -- 6.4.1 Fault Model -- 6.4.2 Description -- 6.4.3 Goal -- 6.4.4 Analysis: Identifying Untaken Branches -- 6.4.5 Test Coverage Item -- 6.4.6 Test Cases -- 6.5 Evaluation -- 6.5.1 Limitations -- 6.5.2 Strengths and Weaknesses -- 6.6 Key Points -- 6.7 Notes for Experienced Testers -- 7 All Paths Coverage -- 7.1 Testing with All Paths Coverage -- 7.2 Example -- 7.2.1 Code Analysis -- 7.2.2 Test Coverage Items -- 7.2.3 Test Cases -- 7.2.4 Verification of the Test Cases -- 7.3 Test Implementation and Results -- 7.3.1 Implementation -- 7.3.2 Test Results -- 7.4 All Paths Coverage Testing in More Detail -- 7.4.1 Fault Model -- 7.4.2 Description -- 7.4.3 Analysis: Developing Control-Flow Graphs -- 7.4.4 Analysis: Identifying End-to-End Paths -- 7.4.5 The Possible Paths in Fault 6 -- 7.4.6 Test Coverage Items -- 7.4.7 Test Cases -- 7.5 Evaluation -- 7.5.1 Limitations -- 7.5.2 Strengths and Weaknesses -- 7.6 Key Points -- 7.7 Notes for the Experienced Tester -- 8 Black-Box and White-Box Testing -- 8.1 Comparison of Black-Box and White-Box Testing -- 8.1.1 Black-Box Testing -- 8.1.2 White-Box Testing -- 8.1.3 Errors of Omission and Commission -- 8.1.4 Usage.8.2 Black-Box Testing: Additional Matters -- 8.2.1 Strings and Arrays -- 8.2.2 Discontinuous Input Partitions -- 8.2.3 Overlapping Output Partitions -- 8.2.4 In-band Error Reporting -- 8.2.5 Handling Relative Values -- 8.2.6 Classic Triangle Problem -- 8.2.7 Testing Sequences of Inputs/State-Based Testing -- 8.2.8 Floating Point Numbers -- 8.2.9 Numeric Processing -- 8.3 White-Box Testing: Some More Techniques -- 8.3.1 Dataflow Coverage/Definition-Use Pairs -- 8.3.2 Condition Coverage -- 8.3.3 Decision Coverage -- 8.3.4 Decision Condition Coverage -- 8.3.5 Multiple Condition Coverage -- 8.3.6 Modified Condition/Decision Coverage -- 8.3.7 Test Ranking -- 8.4 Repair-Based Testing -- 8.4.1 Specific Repair Test -- 8.4.2 Generic Repair Test -- 8.4.3 Abstracted Repair Test -- 8.4.4 Example -- 8.4.5 Using Repair-Based Tests -- 9 Testing Object-Oriented Software -- 9.1 Testing in Class Context -- 9.2 Example -- 9.2.1 Analysis -- 9.2.2 Deciding on Which Methods to Test -- 9.2.3 Selecting a Test Technique -- 9.2.4 Test Coverage Items -- 9.2.5 Test Cases -- 9.2.6 Verification of the Test Cases -- 9.3 Test Implementation and Results -- 9.3.1 Test Implementation -- 9.3.2 Test Results -- 9.4 A More Detailed Look at Testing Object-Oriented Software -- 9.4.1 Object-Oriented Programming -- 9.4.2 Testing Object-Oriented Software -- 9.4.3 Fault Models -- 9.4.4 Testing in Class Context -- 9.4.5 Analysis for OO Testing -- 9.4.6 Test Coverage Items -- 9.4.7 Test Cases -- 9.4.8 Test Implementation -- 9.4.9 Overview of Advanced OO Testing -- 9.4.10 Inheritance Testing -- 9.4.11 State-Based Testing -- 9.4.12 UML-Based Testing -- 9.4.13 Built-In Testing -- 9.5 Evaluation -- 9.5.1 Limitations -- 9.5.2 Simple Typo Fault -- 9.5.3 State-Based Fault -- 9.5.4 Inheritance Fault -- 9.5.5 Strengths and Weaknesses -- 9.6 Key Points -- 9.7 Notes for Experienced Testers.10 Application Testing -- 10.1 Testing Web Applications with User Stories -- 10.2 Example -- 10.2.1 Analysis -- 10.2.2 Test Coverage Items -- 10.2.3 Test Cases -- 10.2.4 Verification of the Test Cases -- 10.3 Test Implementation and Results -- 10.3.1 Implementation -- 10.3.2 Test Results -- 10.4 Application Testing in More Detail -- 10.4.1 System Test Model -- 10.4.2 Application Test Model -- 10.4.3 System Testing and Integration Testing -- 10.4.4 Fault Models for Application Testing -- 10.4.5 Analysis -- 10.4.6 Test Coverage Items -- 10.4.7 Test Cases -- 10.4.8 Implementation -- 10.4.9 Interacting with HTML Elements -- 10.4.10 Test Output Messages -- 10.4.11 Record and Playback Testing -- 10.5 Evaluation -- 10.5.1 Limitations -- 10.5.2 Strengths and Weaknesses -- 10.6 Key Points -- 10.7 Key Differences between Unit Testing and Application Testing -- 10.8 Notes for Experienced Testers -- 11 Test Automation -- 11.1 Introduction -- 11.1.1 Interpreting Test Results -- 11.1.2 Documenting Automated Tests -- 11.1.3 Software Test Automation and Version Control -- 11.2 Test Frameworks: TestNG -- 11.2.1 A Detailed Look at a TestNG Example -- 11.3 Organising Automated Test Code -- 11.3.1 Organising TestNG Tests with an XML File -- 11.4 Setup and Cleanup Methods -- 11.5 Inline Tests vs Parameterised Tests -- 11.6 Test Coverage Measurement -- 11.7 Timeouts -- 11.8 Exceptions -- 11.9 Inheritance Testing -- 11.9.1 Using the Class Name -- 11.9.2 Inheriting Superclass Tests -- 11.9.3 Inheritance Test Selection -- 11.10 Interfacing to Web Applications -- 11.11 Interfacing to Desktop Applications -- 11.12 Interfacing to Mobile Applications -- 12 Random Testing -- 12.1 Introduction to Random Testing -- 12.2 Random Data Selection -- 12.3 Unit Test Example -- 12.3.1 Test Coverage Items -- 12.3.2 Test Cases -- 12.3.3 Test Implementation -- 12.3.4 Test Results.12.4 Application Testing Example.Ralf Bierig, Maynooth University, Stephen Brown, Maynooth University, Edgar Galván, Maynooth University, Joe Timoney, Maynooth University.Title from publisher's bibliographic system (viewed on 19 Aug 2021).Includes bibliographical references and index.Computer softwareTesting.QA76.76.T48 B54 2022005.14COM051230ISBN 9781108833349ISBN 11088333499781108976480110897648497811089740731108974074rdaUkCbUP20080420210906112358.0almafu_9961294337402883Converted from MARCXML to MODS version 3.6 using MARC21slim2MODS3-6.xsl (Revision 1.119 2018/06/21)eng info:srw/schema/1/mods-v3.5 xml 2a practical handbook /Rogers, Lauren,editor.textbibliographytextenkDuxford, England :Woodhead Publishing,2017.©201720172017single uniteng

electronic resource

remote

1 online resource (501 pages) : color illustrations, tables.

computer

online resource

Discrimination Testing in Sensory Science: A Practical Handbook is a one-stop-shop for practical advice and guidance on the performance and analysis of discrimination testing in sensory science. The book covers all aspects of difference testing: the history and origin of different methods, the practicalities of setting up a difference test, replications, the statistics behind each test, dealing with the analysis, action standards, and the statistical analysis of results with R. The book is written by sensory science experts from both academia and industry, and edited by an independent sensory scientist with over twenty years of experience in planning, running and analyzing discrimination tests. This is an essential text for academics in sensory and consumer science and any sensory scientist working in research and development in food, home, and personal care products, new product development, or quality control. Contains practical guidance on the performance and analysis of discrimination testing in sensory and consumer science for both food and non-food products Includes the latest developments in difference testing, including both new methods and state-of-the-art approaches Features extensive coverage of analysis with a variety of software systems Provides essential insight for academics in sensory and consumer science and any sensory scientist working in research and development in food, home, and personal care products, new product development, or quality controlFront Cover -- Discrimination Testing in Sensory Science -- Related Titles -- Discrimination Testing in Sensory Science -- Copyright -- Dedication -- Contents -- List of Contributors -- Preface -- Acknowledgments -- I - Introduction to Discrimination Testing -- 1 - Introduction and History of Sensory Discrimination Testing -- REFERENCES -- FURTHER READING -- 2 - Statistics for Use in Discrimination Testing -- 1. BUSINESS RISK -- 1.1 Conventional Hypothesis Testing -- 1.1.1 The p-Value -- 1.1.2 Type I and Type II Errors -- 1.1.3 The Momentary Proportion of Discriminators -- 1.1.4 Sensory Tests for Difference in Tests Without Chance Bounds -- 1.1.5 Statistical Significance Is Not Practical Significance -- 1.1.6 Sensory Tests for Equivalency or Noninferiority -- 1.2 Reframing the Hypothesis Test Using Likelihood or Bayesian Inference -- 2. DATA ARISING FROM SENSORY DISCRIMINATION TEST METHODS -- 2.1 Classification of Methods -- 2.2 Importance of Experimental Design on Analysis -- 3. ANALYSIS OF DATA ARISING FROM TESTS WITH A CHANCE BOUND (E.G., TRIANGLE TEST) -- 3.1 Unreplicated Data -- 3.2 Replicated Data -- 3.3 Statistical Power -- 4. ANALYSIS OF DATA ARISING FROM SIMPLE CLASSIFICATION TASKS WITHOUT A CHANCE BOUND (E.G., A-NOT-A TEST) -- 4.1 Unreplicated Data -- 4.2 Replicated Data -- 4.3 Statistical Power -- 5. ANALYSIS OF DATA ARISING FROM DIFFERENCE FROM CONTROL/DEGREE OF DIFFERENCE TEST METHODS -- 6. ANALYSIS OF DATA ARISING FROM A RANKING TEST METHOD -- 7. EVALUATING SENSORY EQUIVALENCY -- 7.1 Equivalence Testing for Data Arising From Tests With a Correct Response -- 7.2 Equivalence Testing for Data Arising From Tests That Do Not Have a Correct Response -- 8. CONTEXTUALIZING SENSORY DISCRIMINATION RESULTS TO MAKE BUSINESS DECISIONS -- 9. SUMMARY -- 10. RECOMMENDED READING -- ACKNOWLEDGMENTS -- REFERENCES.3 - Deciding Which Test to Use in Discrimination Testing -- 1. THE OBJECTIVE/BUSINESS NEED -- 2. CONSIDERING ALL POSSIBLE TEST METHODS -- 3. GENERATING A HYPOTHESIS -- 4. THE ACTION STANDARD AND POSSIBLE OUTCOMES -- 5. ASSESSORS AND STATISTICAL POWER -- 5.1 Assessor Type -- 5.2 Assessor Numbers -- 5.3 Statistical Power -- 6. BUDGET -- 7. PRODUCT CONSIDERATIONS -- 7.1 Quantity of Sample Available -- 7.2 Carriers/Substrate-Complex Products -- 8. WHEN NOT TO USE DISCRIMINATION TESTING -- 9. SUMMARY -- REFERENCES -- FURTHER READING -- 4 - Applications and Limitations of Discrimination Testing -- 1. INTRODUCTION -- 2. CATEGORIZING DISCRIMINATION TESTS WITHIN SENSORY METHODOLOGY -- 3. APPLICATIONS OF DISCRIMINATION TESTS -- 3.1 Discrimination Testing in Quality Control -- 3.2 Discrimination Testing in Product Development -- 3.3 Other Applications (Special Cases) of Discrimination Tests -- 4. LIMITATIONS OF DISCRIMINATION TESTS -- 5. USING CONSUMERS IN DISCRIMINATION TESTS -- 6. APPLICATIONS AND LIMITATIONS OF COMMONLY USED DISCRIMINATION TESTS -- 6.1 Triangle Test -- 6.1.1 Applications -- 6.1.2 Limitations -- 6.2 Duo-Trio Test -- 6.2.1 Applications -- 6.2.2 Limitations -- 6.3 A-not-A -- 6.3.1 Applications -- 6.3.2 Limitations -- 6.4 Two-Out-of-Five Test -- 6.4.1 Applications -- 6.4.2 Limitations -- 6.5 Paired Comparison Tests -- 6.5.1 2-AFC -- 6.5.2 Same-Different Test -- 6.5.3 Applications -- 6.5.4 Limitations -- 6.6 Tetrad -- 6.6.1 Applications -- 6.6.2 Limitations -- 6.7 Difference From Control -- 6.7.1 Applications -- 6.7.2 Limitations -- 6.8 Ranking -- 6.8.1 Applications -- 6.8.2 Limitations -- 6.9 ABX -- 6.9.1 Applications -- 6.9.2 Limitations -- 7. CONCLUSION -- ACKNOWLEDGMENTS -- REFERENCES -- II - Methods and Analysis in Discrimination Testing: Practical Guidance.5 - Paired Comparison/Directional Difference Test/2-Alternative Forced Choice (2-AFC) Test, Simple Difference Test/ ... -- 1. INTRODUCTION -- 1.1 Overview of the Types of Paired Comparison Test -- 1.2 Application of the Test -- 1.3 Forced Choice Versus Nonforced Choice -- 1.4 Response Bias -- 1.5 One-Sided Versus Two-Sided -- 1.6 Test Sensitivity -- 1.7 Testing Difference Versus Similarity -- 1.8 Replication -- 2. SAME-DIFFERENT TEST: COMPARING TWO SAMPLES -- 2.1 Objective -- 2.2 Method Outline -- 2.3 Example of Questionnaire -- 2.4 Experimental Design -- 2.5 Assessors -- 2.6 Test Environment -- 2.7 Test Protocol -- 2.8 Data Analysis -- 2.9 Case Studies -- 3. DIRECTIONAL PAIRED COMPARISON: COMPARING TWO SAMPLES -- 3.1 Objective -- 3.2 Method Outline -- 3.3 Example of Questionnaire -- 3.4 Experimental Design -- 3.5 Assessors -- 3.6 Test Environment -- 3.7 Test Protocol -- 3.8 Data Analysis -- 3.9 Case Studies -- 4. MULTIPLE PAIRED COMPARISON: COMPARING MULTIPLE SAMPLES -- 4.1 Objective -- 4.2 Method Outline -- 4.3 Example of Questionnaire -- 4.4 Experimental Design -- 4.5 Assessors -- 4.6 Test Environment -- 4.7 Test Protocol -- 4.8 Data Analysis -- 4.9 Case Studies -- REFERENCES -- 6 - A-Not-A Test -- 1. WHAT IS THE A-NOT-A TEST? -- 2. PROCEDURE -- 2.1 Familiarization -- 2.2 Testing -- 2.3 Type of Assessors -- 3. WHEN TO USE THE A-NOT-A TEST -- 4. ANALYSIS OF A-NOT-A RESULTS -- 4.1 Chi-Squared Model -- 4.1.1 Note on Replicated Testing -- 4.2 Thurstonian Distance -- 4.2.1 Decision Rule for the "A-Not-A" -- 4.3 R-Index -- 5. CONCLUSION -- 6. CASE STUDY -- REFERENCES -- FURTHER READING -- 7 - Triangle Test -- 1. TEST PRINCIPLE -- 2. WHY AND WHEN TO USE IT -- 3. ADVANTAGES AND DISADVANTAGES -- 4. TERMS AND DEFINITIONS (BS ISO 4120) -- 4.1 Risks -- 4.1.1 Alpha Risk (α Risk) -- 4.1.2 Beta Risk (β Risk) -- 4.2 N -- 4.3 Pd -- 4.4 Action Standard.5. SETTING UP THE TEST -- 5.1 Panelists' Instructions -- 5.2 Palate Cleansers -- 5.3 "No-Difference" Option -- 5.4 Retasting Products -- 5.5 Additional Information Given to Panelists -- 5.6 Testing Environment -- 5.7 Action Standard -- 6. ASSESSORS -- 6.1 Health -- 6.2 Motivation -- 6.3 Experience Versus Inexperience -- 6.4 Training -- 6.5 Information Given -- 6.6 Number of Assessors to Invite -- 6.7 Replication -- 7. PRODUCT PREPARATION AND SERVING -- 8. TEST LAYOUT -- 8.1 Practical Example of Procedure to Set Up the Test -- 9. ANALYSIS AND REPORTING -- 9.1 Difference Testing -- 9.2 Similarity Testing -- REFERENCES -- FURTHER READING -- 8 - Two-Out-of-Five Test -- 1. INTRODUCTION -- 2. EXPERIMENTAL DESIGN -- 3. DATA ANALYSIS -- 4. ANALYSIS INTERPRETATION -- 5. TWO-OUT-OF-FIVE METHOD IN USE -- 6. HANDY HINTS -- 7. CASE STUDY 1 -- 8. CASE STUDY 2 -- REFERENCES -- 9 - Tetrad Test -- 1. WHY THE UPSURGE IN POPULARITY OF THE TETRAD? -- 2. WHEN TO USE A TETRAD -- 3. SETTING YOUR OBJECTIVE -- 4. ASSESSORS -- 5. SETTING UP THE TEST -- 5.1 Samples -- 5.2 Test Environment -- 5.3 Experimental Design -- 5.4 Test Instructions -- 5.5 Data Analysis and Interpretation -- 5.6 Reporting -- 6. CASE STUDY -- REFERENCES -- 10 - Duo-Trio -- 1. INTRODUCTION -- 2. ORIGIN -- 3. PRINCIPLE OF THE TEST -- 4. ASSESSORS -- 5. FACILITIES AND BEST PRACTICE -- 6. WHY CHOOSE A DUO-TRIO TEST -- 7. DUO-TRIO ADDITIONAL RESEARCH -- 8. STATISTICS-DEFINITIONS -- 9. CASE STUDIES -- REFERENCES -- FURTHER READING -- 11 - Difference From Control (DFC) Test -- 1. METHOD OUTLINE -- 2. WHY AND WHEN TO USE THIS METHOD -- 2.1 Consumer Testing -- 2.2 Quality Control and Quality Assurance -- 2.3 Shelf Life -- 2.4 Nonhomogeneous Samples -- 2.5 Fatigue -- 2.6 Threshold Testing -- 2.7 Product Claims -- 2.8 Screening -- 3. ADVANTAGES -- 4. DISADVANTAGES -- 5. TEST PROCEDURE -- 6. TEST LAYOUT AND SETUP.6.1 Sample Layout and Questionnaire Example -- 6.2 Sample Presentation -- 6.3 Presentation Order -- 6.4 Sample Labeling -- 6.5 Sample Assessment Procedure -- 6.6 Palate Cleanser -- 6.7 Degree of Difference Scale -- 7. ASSESSORS -- 7.1 Assessor Selection -- 7.2 Level of Training Required -- 7.3 Number of Assessors -- 8. NUMBER OF SAMPLES -- 9. PRACTICALITIES -- 10. REPORTING -- 11. CONSTRAINTS -- 12. CASE STUDIES -- REFERENCES -- 12 - Ranking Test -- 1. METHOD OUTLINE -- 2. WHY AND WHEN TO USE THIS METHOD -- 2.1 Trained Panel Testing-Assessment of Sensory Attributes -- 2.1.1 Panel Screening -- 2.1.2 Panel Training -- 2.1.3 Assessment of Panel Performance -- 2.1.4 Sample Assessment -- 2.2 Consumer Testing -- 2.3 Presorting Samples -- 2.4 Effect of Packaging -- 2.5 Threshold Testing -- 2.6 Working With Young Children -- 3. ADVANTAGES -- 4. DISADVANTAGES -- 5. TEST PROCEDURE -- 5.1 Test Layout and Setup -- 5.2 Sample Layout and Questionnaire Example -- 5.3 Sample Presentation -- 5.4 Presentation Order -- 5.4.1 Complete Block Design -- 5.4.2 Balanced Incomplete Block Design -- 5.5 Sample Labeling -- 5.6 Sample Assessment Procedure -- 5.7 Palate Cleanser -- 6. ASSESSORS -- 6.1 Assessor Selection -- 6.2 Level of Training Required -- 6.3 Number of Assessors (BS ISO 8587:2006+A1:2013, 2013) -- 7. NUMBER OF SAMPLES -- 8. PRACTICALITIES -- 9. REPORTING -- 10. CONSTRAINTS -- 11. OTHER USES -- 11.1 Flash Profiling -- 11.2 Rank-Rating -- 12. CASE STUDIES -- REFERENCES -- 13 - ABX Discrimination Task -- 1. INTRODUCTION -- 2. METHOD OUTLINE -- 3. A BRIEF HISTORY -- 4. ADVANTAGES AND DISADVANTAGES OF THE ABX DISCRIMINATION TASK -- 5. ABX DISCRIMINATION TASK METHODOLOGY -- 5.1 Products and Assessors -- 5.2 Experimental Design -- 5.3 Booth Setup and Running the Test -- 5.4 Reducing Carryover Effects Between Samples -- 5.5 To Retest or Not to Retest?.5.6 A Few Practicalities When Running the Test.edited by Lauren Rogers.Includes bibliographical references at the end of each chapters and index.TestingHandbooks, manuals, etc.Sensory discriminationTesting.TA410 .D573 2017620.110287612.8ISBN 0-08-101009-50-08-101116-4rdaMiAaPQ17072720240506012508.0almafu_9960161216002883Converted from MARCXML to MODS version 3.6 using MARC21slim2MODS3-6.xsl (Revision 1.119 2018/06/21)eng info:srw/schema/1/mods-v3.5 xml 3the agile way to quality /Baumgärtner, Manfred,author.texttextLlibres electrònicsbookszCham, Switzerland :Springer International Publishing,[2021]©20212021single uniteng

electronic resource

remote

1 online resource (xxv, 257 pages) : illustrations

computer

online resource

This book is written by testers for testers. In ten chapters, the authors provide answers to key questions in agile projects. They deal with cultural change processes for agile testing, with questions regarding the approach and organization of software testing, with the use of methods, techniques and tools, especially test automation, and with the redefined role of the tester in agile projects. The first chapter describes the cultural change brought about by agile development. In the second chapter, which addresses agile process models such as Scrum and Kanban, the authors focus on the role of quality assurance in agile development projects. The third chapter deals with the agile test organization and the positioning of testing in an agile team. Chapter 4 discusses the question of whether an agile tester should be a generalist or a specialist. In Chapter 5, the authors turn to the methods and techniques of agile testing, emphasizing the differences from traditional, phase-oriented testing. In Chapter 6, they describe which documents testers still need to create in an agile project. Next, Chapter 7 explains the efficient use of test automation, which is particularly important in agile development, as it is the main instrument for project acceleration and is necessary to support state-of-the-art DevOps approaches and Continuous Integration. Chapter 8 then adds examples from test tool practice extending test automation to include test management functionality. Chapter 9 is dedicated to training and its importance, emphasizing the role of employee training in getting started with agile development. Finally, Chapter 10 summarizes the results of the agile journey in general with a special focus on testing. To make the aspects described even more tangible, the specific topics of this book are accompanied by the description of experiences from concrete software development projects of various organizations. The examples demonstrate that different approaches can lead to solutions that meet the specific challenges of agile projects.Intro -- Foreword -- Preface -- Practical Examples -- Acknowledgments -- Contents -- About the Authors -- 1: Agile: A Cultural Change -- 1.1 The Journey to Agile Development -- 1.2 The Reasons for Agile Development -- 1.3 The Significance of the Agile Manifesto for Software Testing -- 1.4 Agile Requires a Cultural Change Among the Users -- 1.5 Consequences of Agile Development for Software Quality Assurance -- 1.5.1 Spatial Consequences -- 1.5.2 Time-Related Consequences -- Project EMIL: Cultural Change-What Agile Means -- 2: Agile Process Models and Their View on Quality Assurance -- 2.1 Challenges in Quality Assurance -- 2.1.1 Quality and Deadline -- 2.1.2 Quality and Budget -- 2.1.3 The Importance of Software Testing -- 2.1.4 Technical Debt -- 2.1.5 Test Automation -- 2.1.6 Hierarchical Mindset -- 2.2 Importance of the Team -- Project EMIL: Mindset: The Team Is Born -- 2.3 Audits for Quality Assurance in Agile Projects -- 2.3.1 Scrum -- 2.3.1.1 Sprint Review Meeting -- 2.3.1.2 Sprint Retrospective -- Project EMIL: A Retrospective -- 2.3.2 Kanban -- 2.3.2.1 Kaizen: Continuous Improvement -- 2.4 Continuous Integration -- 2.5 Lean Software Development -- 3: Organization of the Software Test in Agile Projects -- 3.1 Positioning of Test in Agile Projects -- 3.1.1 The Fundamental Test Process According to ISTQB -- 3.1.1.1 Test Planning, Monitoring, and Control -- 3.1.1.2 Test Analysis and Test Design -- 3.1.1.3 Test Implementation and Test Execution -- 3.1.1.4 Evaluating Exit Criteria and Reporting -- 3.1.1.5 Test Closure Activities -- 3.1.2 Which Test for What Purpose: The Four Test Quadrants of Agile Testing -- 3.1.2.1 First Quadrant: Technology-Oriented and Team-Supporting -- 3.1.2.2 Second Quadrant: Business-Oriented and Team-Supporting -- 3.1.2.3 Third Quadrant: Business-Oriented and Critique the Product.3.1.2.4 Fourth Quadrant: Technology-Oriented and Critique the Product -- 3.1.2.5 The Context -- 3.1.3 Tips for Software Testing from an Agile Perspective -- 3.1.4 Scaled Agile with SAFe or LeSS -- 3.1.4.1 Testing with SAFe -- 3.1.4.2 Testing with LeSS -- 3.1.5 Scalable Organization of Agile Teams -- 3.2 Practical Examples -- 3.2.1 The Role of the Tester and the Transition to ``Quality Specialist´´ at Otto.de: A Progress Report -- 3.2.2 Acceptance Test as a Separate Scrum Project/Scrum Team -- 3.2.3 Test Competence Center for Agile Projects -- 3.2.4 A Team Using the V-Model in a Health Care Environment -- Project EMIL: Definition of Done -- 4: Role of Testers in Agile Projects -- 4.1 Generalist Versus Specialist -- 4.2 The Path from the Central Test Center to the Agile Team -- 4.2.1 Tester Involvement in Traditional Teams -- 4.2.2 Approaches for Tester Integration in Agile Teams -- 4.2.2.1 The Switch from Traditional to Agile -- Hint -- 4.2.2.2 Increase in Efficiency and Effectiveness -- Pair Testing -- 4.2.2.3 Team Composition -- Practice -- Project EMIL: Role of the Tester and Quality Management -- 4.3 Challenges for Testers in the Team -- 4.3.1 Testers in the Agile Team -- 4.3.1.1 The Quality Coach -- 4.3.1.2 Tasks of Agile Testers -- 4.3.2 Timely Problem Detection -- 4.3.3 The Emergence of Technical Debts -- 4.4 Agile Teams and Testers Working Against ``Technical Debt´´ -- 4.4.1 What Is ``Technical Debt´´? -- 4.4.2 Dealing with Technical Debt -- 4.5 Experience Report: Quality Specialist at Otto.de -- 4.5.1 We Act as the Team´s Quality Coach -- 4.5.2 We Accompany the Entire Life Cycle of Each Story -- 4.5.3 We Operate Continuous Delivery/Continuous Deployment -- 4.5.4 We Balance the Different Types of Tests in the Test Pyramid -- 4.5.5 We Help the Team to Use the Right Methods for High Quality -- 4.5.6 We Are Active in Pairing.4.5.7 We Represent Different Perspectives -- 4.5.8 We Are Communication Talents -- 4.5.9 We Are Quality Specialists -- 4.6 The Challenge of Change -- 4.6.1 Starting Position -- 4.6.2 Supporting and Challenging Factors on the Way to Agile Development -- 4.6.2.1 Creativity and Flexibility -- 4.6.2.2 Stuck in Old Thought Patterns -- 4.6.2.3 Sluggishness and Lack of Flexibility -- 4.6.2.4 Work Environment -- 4.6.2.5 Changing Roles of Senior Testers/Senior Managers -- 4.7 Helpful Tips from Project and Community Experience -- 5: Agile Test Management, Methods, and Techniques -- 5.1 Test Management -- 5.1.1 Test Planning in a Traditional Environment -- Note -- 5.1.2 Test Planning in an Agile Environment -- Note -- 5.1.3 Test Plan -- Practice -- 5.1.4 Test Activities in Iteration Zero: Initialization Sprint -- 5.1.5 External Support for Test Planning -- 5.1.6 Test Estimation -- 5.1.7 Test Organization -- 5.1.8 Test Creation, Implementation, and Release -- 5.2 Test Methods in an Agile Environment -- 5.2.1 Risk-Based and Value-Based Testing -- Note -- 5.2.2 Exploratory Testing -- 5.2.3 Session-Based Testing -- Note -- 5.2.4 Acceptance Test-Driven Development -- 5.2.5 Test Automation -- 5.3 Significant Factors Influencing Agile Testing -- 5.3.1 Continuous Integration (CI) -- 5.3.2 Automated Configuration Management -- 5.4 The Special Challenges of Testing of IoT -- 5.4.1 What Is the Internet of Things? -- 5.4.2 The Challenge of Testing IoT in Agile Teams -- 6: Agile Testing Documentation -- 6.1 The Role of Documentation in Software Development -- 6.2 The Benefits of Documentation -- Project EMIL: (Test) Documentation -- 6.3 Documentation Types -- 6.3.1 Requirements Documentation -- 6.3.2 Code Documentation -- 6.3.3 Test Documentation -- 6.3.3.1 Test Case Description -- 6.3.3.2 Test Execution Documentation -- 6.3.3.3 Test Coverage -- Project EMIL: Metrics.6.3.3.4 Defect Documentation -- Project EMIL: Defect Management -- 6.3.4 User Documentation -- 6.4 The Tester as a Documenter -- 6.5 Importance of Documentation in Agile Testing -- 7: Agile Test Automation -- 7.1 The Trouble with Tools in Agile Projects -- 7.2 Test Automation: How to Approach It? -- Project EMIL: Test Automation -- 7.3 Test Automation with Increasing Software Integration -- 7.3.1 Unit Test/Component Test -- 7.3.2 Component Integration Test -- 7.3.3 System Test -- 7.3.4 System Integration Test -- 7.4 xUnit Frameworks -- Practice: Measuring Test Case Coverage -- Practice: Local Test Environment Using the Integration Test Environment -- 7.5 Use of Placeholders -- 7.6 Integration Server -- 7.7 Test Automation in Business-Oriented Testing -- Hint: Test Automation Only for User Interfaces? -- 7.7.1 Test Automation Frameworks -- 7.7.2 Agile Versus Traditional Automation of User Interactions -- 7.7.2.1 Agile Test Automation -- 7.7.2.2 Traditional Test Automation -- 7.7.3 A Typical Example: FitNesse and Selenium -- Note: Fixture Types -- 7.7.4 Behavior-Driven Development with Cucumber and Gherkin -- 7.8 Test Automation in Load and Performance Testing -- 7.9 The Seven Worst Ideas for Test Automation -- 7.9.1 Expecting Success After Just a Few Sprints -- 7.9.2 Trusting Test Tools Blindly -- 7.9.3 Considering Writing the Test Scripts as a Secondary Job -- 7.9.4 Burying the Test Data in Test Cases -- 7.9.5 Associating the Test Automation Only with UI Tests -- 7.9.6 Underestimating the Comparison with Expected Results -- 7.9.7 Accepting the (Un)testability of the Application -- 8: Use of Tools in Agile Projects -- 8.1 Project Management -- 8.1.1 Broadcom Rally -- 8.2 Requirements Management -- 8.2.1 Polarion QA/ALM -- 8.3 Defect Management -- 8.3.1 The Bug Genie -- 8.3.2 Atlassian JIRA -- 8.4 Test Planning and Control -- 8.4.1 Atlassian JIRA.8.5 Test Analysis and Test Design -- 8.5.1 Risk-Based Testing in the Tosca Test Suite -- 8.6 Test Implementation and Test Execution -- 8.6.1 Microsoft Test Manager -- 9: Education and Its Importance -- 9.1 ISTQB Certified Tester -- 9.2 Practitioner in Agile Quality (PAQ) -- 9.2.1 Motivation -- 9.2.2 Training Content -- 9.3 ISTQB Certified Tester Foundation Level Extension Agile Tester -- 9.4 Individual Trainings (Customized Trainings) -- 9.4.1 Recommended Approach for the Introduction of Agility -- 9.4.1.1 Inventory of the Actual Situation -- 9.4.1.2 Dependency Analysis -- 9.4.1.3 Define the ``New´´ Goal -- 9.4.2 Organization -- 9.4.3 Pilot Phase -- 9.4.4 Rollout in the Organization -- Hint -- 10: Retrospective -- References -- Index.Manfred Baumgartner [and five others].Includes bibliographical references and index.Computer softwareTesting.Agile software development.Programació (Ordinadors)Desenvolupament de programari.QA76.76.T48 .A355 2021005.14ISBN 3-030-73208-83-030-73209-61268112554rdaMiAaPQ22061620240708142959.0almatuudk_9922308018302884Converted from MARCXML to MODS version 3.6 using MARC21slim2MODS3-6.xsl (Revision 1.119 2018/06/21)eng info:srw/schema/1/mods-v3.5 xml 4texttextbookxx[Place of publication not identified]Addison Wesley20071st editionmonographiceng

electronic resource

remote

1 online resource (944 pages)

computer

online resource

Automated testing is a cornerstone of agile development. An effective testing strategy will deliver new functionality more aggressively, accelerate user feedback, and improve quality. However, for many developers, creating effective automated tests is a unique and unfamiliar challenge. xUnit Test Patterns is the definitive guide to writing automated tests using xUnit, the most popular unit testing framework in use today. Agile coach and test automation expert Gerard Meszaros describes 68 proven patterns for making tests easier to write, understand, and maintain. He then shows you how to make them more robust and repeatable--and far more cost-effective. Loaded with information, this book feels like three books in one. The first part is a detailed tutorial on test automation that covers everything from test strategy to in-depth test coding. The second part, a catalog of 18 frequently encountered "test smells," provides trouble-shooting guidelines to help you determine the root cause of problems and the most applicable patterns. The third part contains detailed descriptions of each pattern, including refactoring instructions illustrated by extensive code samples in multiple programming languages. Topics covered include Writing better tests--and writing them faster The four phases of automated tests: fixture setup, exercising the system under test, result verification, and fixture teardown Improving test coverage by isolating software from its environment using Test Stubs and Mock Objects Designing software for greater testability Using test "smells" (including code smells, behavior smells, and project smells) to spot problems and know when and how to eliminate them Refactoring tests for greater simplicity, robustness, and execution speed This book will benefit developers, managers, and testers working with any agile or conventional development process, whether doing test-driven development or writing the tests last. While the patterns and smells are especially applicable to all members of the xUnit family, they also apply to next-generation behavior-driven development frameworks such as RSpec and JBehave and to other kinds of test automation tools, including recorded test tools and data-driven test tools such as Fit and FitNesse. Visual Summary of the Pattern Language Foreword Preface Acknowledgments Introduction Refactoring a Test PART I: The Narratives Chapter 1 A Brief Tour Chapter 2 Test Smells Chapter 3 Goals of Test Automation Chapter 4 Phi...Intro -- Contents -- Visual Summary of the Pattern Language -- Foreword -- Preface -- Acknowledgments -- Introduction -- Refactoring a Test -- PART I. The Narratives -- Chapter 1. A Brief Tour -- About This Chapter -- The Simplest Test Automation Strategy That Could Possibly Work -- What's Next? -- Chapter 2. Test Smells -- About This Chapter -- An Introduction to Test Smells -- A Catalog of Smells -- What's Next? -- Chapter 3. Goals of Test Automation -- About This Chapter -- Why Test? -- Goals of Test Automation -- What's Next? -- Chapter 4. Philosophy of Test Automation -- About This Chapter -- Why Is Philosophy Important? -- Some Philosophical Differences -- When Philosophies Differ -- My Philosophy -- What's Next? -- Chapter 5. Principles of Test Automation -- About This Chapter -- The Principles -- What's Next? -- Chapter 6. Test Automation Strategy -- About This Chapter -- What's Strategic? -- Which Kinds of Tests Should We Automate? -- Which Tools Do We Use to Automate Which Tests? -- Which Test Fixture Strategy Do We Use? -- How Do We Ensure Testability? -- What's Next? -- Chapter 7. xUnit Basics -- About This Chapter -- An Introduction to xUnit -- Common Features -- The Bare Minimum -- Under the xUnit Covers -- xUnit in the Procedural World -- What's Next? -- Chapter 8. Transient Fixture Management -- About This Chapter -- Test Fixture Terminology -- Building Fresh Fixtures -- Tearing Down Transient Fresh Fixtures -- What's Next? -- Chapter 9. Persistent Fixture Management -- About This Chapter -- Managing Persistent Fresh Fixtures -- Managing Shared Fixtures -- What's Next? -- Chapter 10. Result Verification -- About This Chapter -- Making Tests Self-Checking -- State Verification -- Verifying Behavior -- Reducing Test Code Duplication -- Avoiding Conditional Test Logic -- Other Techniques -- Where to Put Reusable Verification Logic?.What's Next? -- Chapter 11. Using Test Doubles -- About This Chapter -- What Are Indirect Inputs and Outputs? -- Testing with Doubles -- Other Uses of Test Doubles -- Other Considerations -- What's Next? -- Chapter 12. Organizing Our Tests -- About This Chapter -- Basic xUnit Mechanisms -- Right-Sizing Test Methods -- Test Methods and Testcase Classes -- Test Naming Conventions -- Organizing Test Suites -- Test Code Reuse -- Test File Organization -- What's Next? -- Chapter 13. Testing with Databases -- About This Chapter -- Testing with Databases -- Testing without Databases -- Testing the Database -- Testing with Databases (Again!) -- What's Next? -- Chapter 14. A Roadmap to Effective Test Automation -- About This Chapter -- Test Automation Difficulty -- Roadmap to Highly Maintainable Automated Tests -- What's Next? -- PART II. The Test Smells -- Chapter 15. Code Smells -- Obscure Test -- Conditional Test Logic -- Hard-to-Test Code -- Test Code Duplication -- Test Logic in Production -- Chapter 16. Behavior Smells -- Assertion Roulette -- Erratic Test -- Fragile Test -- Frequent Debugging -- Manual Intervention -- Slow Tests -- Chapter 17. Project Smells -- Buggy Tests -- Developers Not Writing Tests -- High Test Maintenance Cost -- Production Bugs -- PART III. The Patterns -- Chapter 18. Test Strategy Patterns -- Recorded Test -- Scripted Test -- Data-Driven Test -- Test Automation Framework -- Minimal Fixture -- Standard Fixture -- Fresh Fixture -- Shared Fixture -- Back Door Manipulation -- Layer Test -- Chapter 19. xUnit Basics Patterns -- Test Method -- Four-Phase Test -- Assertion Method -- Assertion Message -- Testcase Class -- Test Runner -- Testcase Object -- Test Suite Object -- Test Discovery -- Test Enumeration -- Test Selection -- Chapter 20. Fixture Setup Patterns -- In-line Setup -- Delegated Setup -- Creation Method.Implicit Setup -- Prebuilt Fixture -- Lazy Setup -- Suite Fixture Setup -- Setup Decorator -- Chained Tests -- Chapter 21. Result Verification Patterns -- State Verification -- Behavior Verification -- Custom Assertion -- Delta Assertion -- Guard Assertion -- Unfinished Test Assertion -- Chapter 22. Fixture Teardown Patterns -- Garbage-Collected Teardown -- Automated Teardown -- In-line Teardown -- Implicit Teardown -- Chapter 23. Test Double Patterns -- Test Double -- Test Stub -- Test Spy -- Mock Object -- Fake Object -- Configurable Test Double -- Hard-Coded Test Double -- Test-Specific Subclass -- Chapter 24. Test Organization Patterns -- Named Test Suite -- Test Utility Method -- Parameterized Test -- Testcase Class per Class -- Testcase Class per Feature -- Testcase Class per Fixture -- Testcase Superclass -- Test Helper -- Chapter 25. Database Patterns -- Database Sandbox -- Stored Procedure Test -- Table Truncation Teardown -- Transaction Rollback Teardown -- Chapter 26. Design-for-Testability Patterns -- Dependency Injection -- Dependency Lookup -- Humble Object -- Test Hook -- Chapter 27. Value Patterns -- Literal Value -- Derived Value -- Generated Value -- Dummy Object -- PART IV. Appendixes -- Appendix A. Test Refactorings -- Appendix B. xUnit Terminology -- Appendix C. xUnit Family Members -- Appendix D. Tools -- Appendix E. Goals and Principles -- Appendix F. Smells, Aliases, and Causes -- Appendix G. Patterns, Aliases, and Variations -- Glossary.Bibliographic Level Mode of Issuance: MonographIncludes bibliographical references and index.EnglishSoftware patternsTesting.Computer software.Engineering & Applied SciencesComputer ScienceQA76.76.P37 M49 2007005.1ISBN 9780131495050ISBN 01314950549780321504807032150480197801327974670132797461154684541ocm15468454115313229031337944947PQKB16082920251214174417.0almatuudk_9923192791802884Converted from MARCXML to MODS version 3.6 using MARC21slim2MODS3-6.xsl (Revision 1.119 2018/06/21) info:srw/schema/1/mods-v3.5 xml 5how to test SaaS, PaaS & IaaS /Blokland, Kees,1962-author.Mengerink, Jeroen,author.Pol, Martin,1947-author.texttextbookcauSanta Barbara, California :Rocky Nook, Inc.,[2013]©20132013First edition.single uniteng

electronic resource

remote

1 online resource (183 p.)

computer

online resource

Everybody is confronted with cloud computing. Whether you are a user, designer, programmer, project manager, or tester, sooner or later the cloud affects your work. If you are involved in selecting or implementing services from the cloud, or in keeping them up and running, this book will prove to be an invaluable resource. Testing Cloud Services covers an extensive list of risks that arise when implementing cloud computing, including some traditional risks and some completely new ones, and provides strategies for avoiding these risks and solving problems. Every risk is connected to existing, updated, and new test measures. It is necessary to start testing during the selection of cloud services, and continue end-to-end testing even after going live, as continuity risks arise all the time. With this book in hand, you will save a lot of time and discover an effective approach to testing that can be applied in practice immediately!Intro -- Contents -- Introduction from the CEO -- Preface -- Acknowledgements -- 1 Introduction -- 2 What is Cloud Computing? -- 2.1 Essential characteristics -- On-demand self-service -- Broad network access -- Resource pooling -- Rapid elasticity -- Measured service -- 2.2 Service models -- IaaS -- IaaS examples -- PaaS -- PaaS examples -- SaaS -- SaaS examples -- 2.3 Implementation models -- Private cloud -- Community cloud -- Public cloud -- Hybrid cloud -- 3 Role of the Test Manager -- 3.1 In general -- 3.1.1 Risk analysis -- 3.1.2 Information from and agreement with the supplier -- Checklist for general supplier conditions and other sources -- Additional terms and conditions -- 3.1.3 End-to-end testing -- E2E testing is more than system integration -- The focus of the E2E test -- Creating E2E test cases -- Executing E2E test cases -- Automating the E2E test execution -- E2E regression testing -- 3.1.4 Advice -- 3.2 Tasks during selection, implementation, and production -- 3.2.1 Selection -- 3.2.2 Implementation -- 3.2.3 Production -- 3.3 Testing with the help of the cloud -- 3.3.1 Test outsourcing to the cloud with TOGA -- Initiation -- Setup -- Transition -- Operation -- 3.3.2 Crowdsourced testing -- 3.3.3 Test environments in the cloud -- Making a snapshot of the virtual environment -- Making a representative test environment -- Executing a portability test for mobile resources -- 3.3.4 Generating load -- Heavy load -- Worldwide load -- 4 From Risk to Test -- 4.1 Performance risks -- 4.2 Security risks -- 4.3 Availability and continuity risks -- 4.4 Functionality risks -- 4.5 Maintainability risks -- 4.6 Legislation and regulations risks -- 4.7 Suppliers and outsourcing risks -- 5 Test Measures -- 5.1 Testing during selection -- 5.1.1 Include cloud-related aspects -- 5.1.2 Determine completeness and controllability of selection criteria.Selection criteria for a service -- Selection criteria for a supplier -- 5.1.3 Assess services and suppliers -- Inspect specifications and terms -- Ask for references and certificates -- Perform audits and inspections -- Proof of concept -- Simulate E2E business processes -- 5.1.4 Issue selection advice -- 5.1.5 Checklist selection criteria -- 5.2 Testing performance -- 5.2.1 Load test -- 5.2.2 Stress test -- 5.2.3 Endurance test or volume test -- 5.2.4 Testing elasticity and manual scalability -- 5.2.5 Setting up test cases -- Setting up operational profiles -- Step 1: Identify the initiators of operations -- Step 2: List operations -- Step 3: Review listed operations -- Step 4: Determine the frequency of operations -- Step 5: Determine the likelihood of each operation occurring -- 5.2.6 Test cases aimed at specific bottlenecks -- 5.2.7 Including cloud aspects in test cases -- The world -- Customer's resources -- 5.2.8 Test cases for the stress test -- 5.2.9 Test cases for endurance/volume test -- 5.2.10 Test cases for elasticity -- Elasticity (automatic scalability) -- Load profile -- Boundary values -- Process -- Manual scalability -- Load profile -- Boundary values -- Process -- 5.2.11 Test setup for a performance test -- 5.2.12 Representative test environment -- 5.3 Testing security -- 5.3.1 Assessing network security -- 5.3.2 Inventorying supplier security -- Authentication -- Authorization -- Log files and audit trails -- 5.3.3 Inventorying customer security -- 5.3.4 Testing encryption -- 5.3.5 Testing authentication -- 5.3.6 Testing authorization -- 5.3.7 Testing security robustness against Internet attacks -- 5.3.8 Testing log files and audit trails -- 5.3.9 Testing security patch routines -- 5.3.10 Performing audits -- 5.4 Testing for manageability -- 5.4.1 Specifications on the supplier side -- Interface specifications.Specifications for customer resources -- Platform specifications -- Infrastructure specifications -- 5.4.2 Specifications on the customer side -- Infrastructure specifications (IaaS) -- System specifications -- Architecture documentation -- Business process documentation -- Business requirements -- 5.4.3 User documentation -- 5.4.4 Test environment availability -- Test environments in IaaS/PaaS -- Test environments of the SaaS user -- 5.4.5 Test documentation -- Customer test documentation -- Supplier test documentation -- 5.4.6 Incident management procedure -- Supplier resolves the incident -- Customer resolves the incident -- The incident will not be resolved -- 5.4.7 Change procedure and version control -- 5.4.8 Maintainability of software -- 5.5 Availability/continuity testing -- 5.5.1 Failure Mode and Effect Analysis -- 5.5.2 The role of architecture -- 5.5.3 Hardware reliability -- 5.5.4 Software reliability -- 5.5.5 Guarantees and SLAs -- Guarantees -- SLAs -- Points to note -- 5.5.6 Impact of availability mechanisms -- 5.5.7 Internet and Internet connection -- 5.5.8 Testing failover -- Failover test cases -- Specific checkpoints in failover tests -- Test management aspects for failover tests -- Process simulation -- 5.5.9 Testing working offline -- 5.6 Functionality testing -- 5.6.1 Compatibility of service with business processes -- 5.6.2 Testing service quality -- 5.6.3 Testing user-friendliness -- User documentation -- 5.6.4 Testing interfaces to other systems -- 5.6.5 Testing service configuration -- 5.6.6 Customization by the supplier -- 5.6.7 Customization by the customer -- 5.6.8 Testing web services -- WSDL -- Tools -- Test cases -- 5.6.9 Multi-platform testing -- Considerations for the supplier -- Considerations for the customer -- 5.6.10 Testing of and testing with apps -- Testing an app (on a mobile device).5.6.11 Testing for working offline -- 5.6.12 Testing for regression -- 5.6.13 Creating a test basis -- Process flows -- Use cases -- Classification tree -- CRUD -- Authorization table -- Interface specifications (agreements) -- 5.7 Testing migration -- 5.7.1 Migration test strategy -- 5.7.2 Minimal interruption of business processes -- Trial migration -- 5.7.3 Correct data migration in IaaS and PaaS -- 5.7.4 Correct data conversion with SaaS -- Do conversion rules work correctly? -- Does the conversion work properly on the input data? -- Is there any data lost? -- Are any partially completed transactions lost? -- During and after conversion, does any sensitive data remain available? -- Is too much data being transferred to the service through migration? -- 5.7.5 Migration performance -- 5.7.6 Data cleanup -- 5.7.7 Test environment migration -- 5.7.8 Parallel runs and trial runs -- 5.8 Testing due to legislation and regulations -- 5.8.1 Inventory of legislation and regulations -- Privacy legislation -- Data location -- Additional agreements -- Other legislation -- Other obligations -- Conflicting laws and rules -- Impending laws and rules -- 5.8.2 Checking for legislation and regulations -- 5.9 Testing in production -- 5.9.1 Continuity in production in the case of changes -- Changes in the service -- Changes in other systems -- Changes at the supplier -- Changes in the business processes -- Growth -- Changes in connected resources -- Changes to the Internet -- Conclusion -- 5.9.2 Measuring guarantees -- Availability -- Performance -- Scalability -- Security -- 5.9.3 Original selection criteria evaluation -- 5.9.4 Practical points to note -- (E2E) Regression test -- Measurement methods for KPIs -- 6 Completion -- Glossary -- Index.Kees Blokland, Jeroen Mengerink, Martin Pol.Includes index.EnglishCloud computing.Application softwareTesting.QA76.585 .B56 2013004.67/82COM051330 COM000000 COM052000 COM060000 COM060090ISBN 9781937538385ISBN 1937538389ISBN 9781492000037ISBN 14920000359781492000044149200004397814920000201492000027864886642ocn864886642rdaMiAaPQ25111120251111135608.0almatuudk_9923196678502884Converted from MARCXML to MODS version 3.6 using MARC21slim2MODS3-6.xsl (Revision 1.119 2018/06/21)eng info:srw/schema/1/mods-v3.5 xml 6learn and implement techniques for building robust test automation frameworks /Sambamurthy, Manikandan,author.texttextbookenkBirmingham, England :Packt Publishing, Limited,[2023]©202320231st ed.single uniteng

electronic resource

remote

1 online resource (276 pages)

computer

online resource

Understand test automation and implement it in Web, Mobile, and APIs effectively Key Features Learn how to automate your tests with the help of practical examples Understand how to bridge the gap between testing and test automation Explore test automation strategies for different platforms Book Description This book helps you build a better understanding of test automation and aids in bridging the gap between testing and test automation. The book has been divided into three sections with the first section focusing on preparing you for testing and test automation fundamentals. By the end of this section, you'll have an understanding of some common automation terms, definitions, and roles. The second section covers the practical implementation of test automation for mobile, web, API and performance. The third section will help you understand how test automation works with CI/CD, and explore the common issues and pitfalls when executing test automation. By the end of this book, you'll have a better understanding of automation, addressing the common pain points and best practices around test automation. What you will learn Gain a solid understanding of test automation Understand how automation fits into a test strategy Explore essential design patterns for test automation Design and implement highly reliable automated tests Understand issues and pitfalls when executing test automation Discover the commonly used test automation tools/frameworks Who this book is for This book is for manual testers who want to enter the field of test automation and developers who want to learn more about test automation.Cover -- Title Page -- Copyright and Credits -- Contributors -- Table of Contents -- Preface -- Part 1: The Basics -- Chapter 1: Introduction to Test Automation -- Getting familiar with software testing -- Knowing the importance of testing -- Tasks involved in testing -- Testing in an world -- Defect management in testing -- Shift-Right and Shift-Left propositions -- Quality and DevOps -- Challenges in testing -- Test early, test often -- Understanding test automation -- Agile test automation -- Test automation challenges -- Finding and handling regression bugs -- Test automation metrics -- Exploring the roles in quality engineering -- Test automation engineer -- SDET -- Familiarizing yourself with common terminologies and definitions -- Summary -- Questions -- Chapter 2: Test Automation Strategy -- Technical requirements -- Knowing your test automation strategy -- Test automation objectives -- Gathering management support -- Defining the scope of test automation -- Test automation environment -- Implementing an Agile test automation strategy -- Reporting the test results -- Devising a good test automation strategy -- Selecting the right tools and training -- Standards of the test automation framework -- Testing in the cloud -- Understanding the test pyramid -- Unit/component tests -- Integration/API tests -- E2E/System/UI tests -- Structuring the test cycles -- Familiarizing ourselves with common design patterns -- Using design patterns in test automation -- Summary -- Questions -- Chapter 3: Common Tools and Frameworks -- Technical requirements -- The basic tools for every automation engineer -- The CLI -- Git -- Common test automation frameworks -- Selenium -- Appium -- Cypress -- JMeter -- AXE -- Choosing the right tool/framework -- Selecting a performance testing tool -- Selecting an API testing tool -- Selecting a web testing tool.Mobile -- Common considerations -- Summary -- Questions -- Part 2: Practical Affairs -- Chapter 4: Getting Started with the Basics -- Technical requirements -- Getting more familiar with Git -- Committing a change -- Resolving merge conflicts -- Additional Git commands -- Using an IDE -- Choosing an IDE -- Downloading and setting up VS Code -- Introduction to JavaScript -- Why learn JavaScript? -- Running a JavaScript program -- JavaScript basics -- Summary -- Questions -- Chapter 5: Test Automation for Web -- Technical requirements -- Why Cypress? -- Installing and setting up Cypress -- Creating your first test in Cypress -- Creating arrow functions in JavaScript -- Creating callback functions in JavaScript -- Writing our first spec -- Becoming familiar with the spec structure -- Executing our first spec -- Employing selectors and assertions -- Working with selectors -- Asserting on selectors -- Intercepting API calls -- Additional configurations -- Considerations for web automation -- Limitations of Cypress -- Web automation considerations -- Summary -- Questions -- Chapter 6: Test Automation for Mobile -- Technical requirements -- Getting to know Appium -- What is Appium? -- Advantages of using Appium -- Knowing WebdriverIO and its advantages -- Setting up Appium and WebdriverIO -- Appium installation -- Configuring an Android emulator -- Configuring WebdriverIO with Appium -- WebdriverIO Android configuration -- Appium Inspector installation and configuration -- Writing our first mobile test -- JavaScript functions with async/await -- First Appium/WebdriverIO test -- Key considerations for mobile automation -- Areas of complexity -- iOS-specific considerations -- Optimizing our mobile automation framework -- Summary -- Questions -- Chapter 7: Test Automation for APIs -- Technical requirements -- Getting started with Postman.Basics of REST API testing -- Downloading the Postman application -- Creating and managing workspaces -- Sending GET and POST requests -- Making a GET API request -- Making a POST API request -- Organizing API requests using collections -- Writing automated API tests -- Using snippets for asserting an API response -- Understanding Postman variables -- Chaining API requests -- Various ways to execute tests -- Key considerations for API automation -- Effective API test automation -- Testing GraphQL versus REST APIs -- Summary -- Questions -- Chapter 8: Test Automation for Performance -- Technical requirements -- Getting started with JMeter -- What is JMeter and how does it work? -- Installing JMeter -- Automating a performance test -- Building and running our first performance test -- Working with assertions -- Working with tests via the command line -- Using the HTTP(S) Test Script Recorder -- Java essentials for JMeter -- A quick introduction to Java -- Using the JSR233 assertion -- Considerations for performance testing -- Summary -- Questions -- Part 3: Continuous Learning -- Chapter 9: CI/CD and Test Automation -- Technical requirements -- What is CI/CD? -- CI/CD process -- CI basics -- CD and deployment pipeline -- Test automation strategies for CI/CD -- Unit/component tests -- API tests -- E2E tests (API and UI) -- Smoke tests -- Addressing test failures -- GitHub Actions CI/CD -- Summary -- Questions -- Chapter 10: Common Issues and Pitfalls -- Recurrent issues in test automation -- Unrealistic expectations of automated testing -- Inadequate manual testing -- Not focusing on automating the right things -- A lack of understanding of the system under test -- Overlooking test maintenance -- Not choosing the right tools -- Under-investing in test environments -- Taking a siloed approach -- Not taking a lean approach.Not having a plan for test data needs -- Test automation anti-patterns -- Coding and design anti-patterns in test automation -- Process-oriented anti-patterns in test automation -- Summary -- Questions -- Appendix A: Mocking API Calls -- How API mocking works -- Mocking API calls using Postman -- Considerations for API mocking -- Summary -- Assessments -- Chapter 1, Introduction to Test Automation -- Chapter 2, Test Automation Strategy -- Chapter 3, Common Tools and Frameworks -- Chapter 4, Getting Started with the Basics -- Chapter 5, Test Automation for Web -- Chapter 6, Test Automation for Mobile -- Chapter 7, Test Automation for APIs -- Chapter 8, Test Automation for Performance -- Chapter 9, CI/CD and Test Automation -- Chapter 10, Common Issues and Pitfalls -- Index -- Other Books You May Enjoy.Manikandan Sambamurthy.Includes index.Computer softwareTestingAutomation.QA76.754 .S263 2023929.605ISBN 9781804615492ISBN 1804615498978180461967418046196711356574652rdaMiAaPQ23020420230204164953.0almatuudk_9923197727702884Converted from MARCXML to MODS version 3.6 using MARC21slim2MODS3-6.xsl (Revision 1.119 2018/06/21)eng info:srw/schema/1/mods-v3.5 xml 7Winteringham, Mark,author.Gregory, Janet,writer of foreword.Crispin, Lisa,writer of foreword.textbibliographytextnyuShelter Island, New York :Manning Publications Co.,[2022]©202220221st edition.single uniteng

electronic resource

remote

1 online resource (228 pages)

computer

online resource

Ensure your web APIs are consistent and bug-free by implementing an automated testing process. In Testing Web APIs you will: Design and implement a web API testing strategy Set up a test automation suite Learn contract testing with Pact Facilitate collaborative discussions to test web API designs Perform exploratory tests Experiment safely in a downloadable API sandbox environment Testing Web APIs teaches you to plan and implement the perfect testing strategy for your web APIs. In it, you'll explore dozens of different testing activities to help you develop a custom testing regime for your projects. This practical book demystifies abstract strategic concepts by applying them to common API testing scenarios, revealing how these complex ideas work in the real world. You'll learn to take a risk-driven approach to API testing, and build a strategy that goes beyond the basics of code and requirements coverage. Your whole team will soon be involved in ensuring quality! About the Technology Web APIs are the public face of your application, and they need to be perfect. Implementing an automated testing program is the best way to ensure that your web APIs are production ready. About the Book Testing Web APIs is a unique and practical guide, from the initial design of your testing suite through techniques for documentation, implementation, and delivery of consistently excellent APIs. You'll see a wide range of testing techniques, from exploratory to live testing of production code, and how to save time with automation using industry-standard tools. This book helps take the hassle out of API testing. What's Inside Design and implement a web API testing strategy Set up a test automation suite Contract testing with Pact Hands-on practice in the downloadable API sandbox About the Reader For dedicated software QA and testers, or experienced developers. Examples in Java. About the Author Mark Winteringham is the OpsBoss at Ministry of Testing, where he teaches many aspects of software testing. Quotes.Intro -- inside front cover -- Testing Web APIs -- Copyright -- dedication -- contents -- front matter -- foreword -- preface -- acknowledgments -- about this book -- Who should read this book -- How this book is organized: A road map -- Prerequisites -- About the code -- liveBook discussion forum -- about the author -- about the cover illustration -- Part 1 The value of web API testing -- 1 Why and how we test web APIs -- 1.1 What's going on in your web APIs? -- 1.1.1 Complexity within web APIs -- 1.1.2 Complexity across many web APIs -- 1.2 How does testing help us? -- 1.2.1 Imagination -- 1.2.2 Implementation -- 1.2.3 The value of testing -- 1.2.4 Being strategic with API testing -- Summary -- 2 Beginning our testing journey -- 2.1 Introducing our product -- 2.1.1 Introducing our sandbox API -- 2.2 Familiarizing ourselves with restful-booker-platform -- 2.2.1 Researching the product -- 2.2.2 Researching beyond the product -- 2.3 Capturing our understanding -- 2.3.1 The power of models -- 2.3.2 Building our own models -- 2.4 Congratulations-you're testing! -- Summary -- 3 Quality and risk -- 3.1 Defining quality -- 3.1.1 Quality characteristics -- 3.1.2 Getting to know our users -- 3.1.3 Setting quality goals for our strategy -- 3.2 Identify risks to quality -- 3.2.1 Learning to identify risk -- 3.2.2 Headline game -- 3.2.3 Oblique testing -- 3.2.4 RiskStorming -- 3.3 A strategy's first steps -- 3.3.1 Picking the right approach for testing a risk -- Summary -- Part 2 Beginning our test strategy -- 4 Testing API designs -- 4.1 How do we test API designs? -- 4.1.1 Tools for questioning -- 4.1.2 Expanding your API design-testing techniques and tools -- 4.2 Using API documentation tools to test designs -- 4.2.1 Documenting APIs with Swagger/OpenAPI 3 -- 4.2.2 Beyond documentation -- 4.3 Encouraging teams to test API designs.4.3.1 Getting buy-in and initiating opportunities to test API designs -- 4.3.2 Taking advantage of existing sessions -- 4.3.3 Establishing your own sessions -- 4.4 Testing API designs as part of a testing strategy -- Summary -- 5 Exploratory testing APIs -- 5.1 The value of exploratory testing -- 5.1.1 The testing cycle in exploratory testing -- 5.2 Planning to explore -- 5.2.1 Generating charters -- 5.2.2 Charters and exploratory testing sessions -- 5.2.3 Organizing our exploratory testing -- 5.3 Exploratory testing: A case study -- 5.3.1 Beginning the session -- 5.3.2 Knowing when something isn't right -- 5.3.3 Coming up with ideas for testing -- 5.3.4 Using tools -- 5.3.5 Note-taking -- 5.3.6 Knowing when to stop -- 5.3.7 Running your own exploratory testing session -- 5.4 Sharing your discoveries -- 5.5 Exploratory testing as part of a strategy -- Summary -- 6 Automating web API tests -- 6.1 Getting value from automation -- 6.1.1 The illusion of automation -- 6.1.2 Automation as change detection -- 6.1.3 Letting risk be our guide -- 6.2 Setting up a Web API automation tool -- 6.2.1 Dependencies -- 6.2.2 Structuring our framework -- 6.3 Creating automated API checks -- 6.3.1 Automated check 1: A GET request -- 6.3.2 Automated check 2: A POST request -- 6.3.3 Automated check 3: Combining requests -- 6.3.4 Running your automated tests as integration tests -- 6.4 Utilizing automation in our strategy -- Summary -- 7 Establishing and implementing a testing strategy -- 7.1 Establishing a strategy for our context -- 7.1.1 Identifying what's a priority -- 7.1.2 Different strategies for different contexts -- 7.2 Turning a testing strategy into a testing plan -- 7.2.1 Understanding your context's testability -- 7.2.2 Organizing and documenting a plan -- 7.2.3 Executing and reflecting on a plan -- 7.2.4 Evolving our strategy -- Summary.Part 3 Expanding our test strategy -- 8 Advanced web API automation -- 8.1 Acceptance test-driven development -- 8.1.1 Setting up an automated acceptance testing framework -- 8.1.2 Creating our failing automated check -- 8.1.3 Getting our automated check to pass -- 8.1.4 Beware of traps -- 8.2 Web API mocking -- 8.2.1 Getting set up -- 8.2.2 Building our mocked check -- 8.3 Running as part of a pipeline -- 8.3.1 Integrated with codebase -- 8.3.2 Separate to codebase -- Summary -- 9 Contract testing -- 9.1 What contract testing is and how can it help -- 9.2 Setting up a contract testing framework -- 9.2.1 Introducing Pact -- 9.3 Building a consumer contract test -- 9.3.1 Adding Pact to our class -- 9.3.2 Building the consumer check -- 9.3.3 Setting up and publishing to a Pact Broker -- 9.4 Building a provider contract test -- 9.4.1 Building the provider contract test -- 9.4.2 Testing out a change -- 9.5 Contract testing as part of a testing strategy -- Summary -- 10 Performance testing -- 10.1 Planning a performance test -- 10.1.1 Types of performance tests -- 10.1.2 Types of measurements for performance tests -- 10.1.3 Establishing performance testing goals and key performance indicators (KPIs) -- 10.1.4 Creating user flows -- 10.2 Implementing a performance test -- 10.2.1 Setting our performance testing tool -- 10.2.2 Building our performance test script -- 10.3 Executing and measuring a performance test -- 10.3.1 Preparing and executing our performance test -- 10.3.2 Analyzing results -- 10.4 Setting performance testing expectations -- Summary -- 11 Security testing -- 11.1 Working with threat models -- 11.1.1 Creating a model -- 11.1.2 Discovering threats with STRIDE -- 11.1.3 Creating threat trees -- 11.1.4 Mitigating threats -- 11.2 Applying a security mindset to our testing -- 11.2.1 Security testing in testing API design sessions.11.2.2 Exploratory security testing -- 11.2.3 Automation and security testing -- 11.3 Security testing as part of a strategy -- Summary -- 12 Testing in production -- 12.1 Planning out testing in production -- 12.1.1 What to track -- 12.1.2 Service-level objectives -- 12.1.3 Service-level agreements -- 12.1.4 Service-level indicators -- 12.1.5 What to save -- 12.2 Setting up testing in production -- 12.2.1 Setting up a Honeycomb account -- 12.2.2 Adding Honeycomb to APIs -- 12.2.3 Advanced querying -- 12.2.4 Building SLO triggers -- 12.3 Taking testing in production further -- 12.3.1 Testing with synthetic users -- 12.3.2 Testing hypotheses -- 12.4 Expanding your strategy by testing in production -- Summary -- Appendix A. Installing the sandbox API platform -- A.1 Setting up restful-booker-platform -- index -- inside back cover.Mark Winteringham ; foreword by Janet Gregory and Lisa Crispin.Includes bibliographical references and index.Application program interfaces (Computer software)Testing.Web applicationsTesting.QA76.76.A63 .W568 2022005.3ISBN 9781617299537ISBN 16172995379781638351535163835153813517484231354573301rdaMiAaPQ23040520230405142210.0almatuudk_9923197536202884Converted from MARCXML to MODS version 3.6 using MARC21slim2MODS3-6.xsl (Revision 1.119 2018/06/21)eng info:srw/schema/1/mods-v3.5 xml 8Wang, Weiyong,author.Kodur, Venkatesh,author.texttextbookenkLondon, England :Academic Press,2020.20201st ed.single uniteng

electronic resource

remote

1 online resource (466 pages)

computer

online resource

Material Properties of Steel Fire Conditions is a major new contribution on how to understand the material properties of steel in fires.The application of new types of steel and development of sophisticated codes of practice has grown dramatically in recent years, making this a timely resource on the topic.Front Cover -- MATERIAL PROPERTIES OF STEEL IN FIRE CONDITIONS -- MATERIAL PROPERTIES OF STEEL IN FIRE CONDITIONS -- Copyright -- Contents -- Author profiles -- Preface -- ABOUT THE BOOK -- CONTENTS AND COVERAGE -- TARGET AUDIENCE -- Acknowledgments -- List of symbols -- 1 - Introduction -- 1.1 Initial consideration -- 1.2 High strength steel -- 1.3 Applications of high strength steel in building structures -- 1.4 Fire hazard and effect of fire on steel structures -- 1.5 State of the art -- 1.5.1 Mechanical properties of high strength steel at elevated temperatures -- 1.5.2 Mechanical properties of high strength steel after fire exposure -- 1.5.3 Creep strain of high strength steel at elevated temperatures -- 1.5.4 Fire resistance investigation on high strength steel structures -- 1.6 Test methods -- 1.6.1 Thermal properties tests -- 1.6.1.1 Thermal conductivity -- 1.6.1.2 Specific heat -- 1.6.2 Tensile strength test at elevated temperature -- 1.6.2.1 Brief introduction on tensile testing -- 1.6.2.2 Tensile test at elevated temperature -- 1.6.3 Creep test at elevated temperature -- 1.6.3.1 Creep phenomenon -- 1.6.3.2 Creep test at elevated temperature -- 1.7 Book scope -- References -- 2 - Thermal properties of steel at elevated temperature -- 2.1 Introduction -- 2.2 Thermal properties of high strength bolt steel -- 2.2.1 Test procedures -- 2.2.2 Test results -- 2.2.3 Comparison of measured properties with published data -- 2.2.4 High-temperature property relations -- 2.3 Thermal expansion of mild steel -- 2.4 Specific heat of mild steel -- 2.5 Thermal conductivity of mild steel -- 2.6 Density -- References -- 3 - Tensile test on steels at elevated temperatures -- 3.1 Introduction -- 3.2 Mechanical properties of high strength Q460 steel -- 3.2.1 Test setup -- 3.2.2 Test specimen -- 3.2.3 Test procedure -- 3.2.4 Test results.3.2.4.1 Yield strength and ultimate strength -- 3.2.4.2 Elastic modulus -- 3.2.5 Prediction equations -- 3.3 Mechanical properties of high strength Q690 steel -- 3.3.1 Test setup -- 3.3.2 Test specimen -- 3.3.3 Test procedures -- 3.3.4 Test results -- 3.3.4.1 Stress-strain curves at elevated temperatures -- 3.3.4.2 Yield stress -- 3.3.4.3 Ultimate stress -- 3.3.4.4 Elastic modulus -- 3.3.4.5 Specimen failure -- 3.3.5 Proposed stress-strain curves -- 3.3.6 Prediction equations -- 3.4 Mechanical properties of high strength S460 steel -- 3.4.1 Test device -- 3.4.2 Test material and specimen -- 3.4.3 Test method -- 3.4.4 Test procedure -- 3.4.5 Experimental results -- 3.5 Mechanical properties of high strength S690 steel -- 3.5.1 Test device -- 3.5.2 Test material and specimen -- 3.5.3 Test method -- 3.5.4 Test results -- 3.5.5 Comparison and analysis -- 3.6 Mechanical properties of high strength S960 steel -- 3.6.1 Test material -- 3.6.2 Test results -- 3.6.2.1 Stress-strain curves -- 3.6.2.2 Failure mode -- 3.6.2.3 Elastic modulus -- 3.6.2.4 Yield strength -- 3.6.2.5 Ultimate strength -- 3.6.3 Predictive equations -- 3.6.3.1 Elastic modulus -- 3.6.3.2 Yield strength -- 3.6.3.3 Ultimate strength -- 3.7 Mechanical properties of BISPLATE 80 steel -- 3.7.1 Experimental investigation -- 3.7.1.1 Testing device -- 3.7.1.2 Test specimen -- 3.7.2 Testing procedure -- 3.7.2.1 Steady-state test -- 3.7.2.2 Transient-state test -- 3.7.3 Thermal elongation in transient-state test -- 3.7.4 Determination of strength and elastic modulus -- 3.7.4.1 Elastic modulus -- 3.7.4.2 Ultimate strength -- 3.8 Mechanical properties of high strength A572 steel -- 3.8.1 Test equipment -- 3.8.2 Test procedure -- 3.8.3 Tensile strength at elevated temperatures -- 3.8.4 Proposed reduction factors for strength and elastic modulus.3.9 Mechanical properties of high strength steel RQT-S690 -- 3.9.1 The test device -- 3.9.2 Tested materials and specimen -- 3.9.3 The test methods -- 3.9.4 Test results -- 3.9.4.1 General descriptions -- 3.9.4.2 Determination of characteristic strength and elastic modulus -- 3.9.4.3 Strengths -- 3.9.4.4 Elastic modulus -- References -- 4 - Residual mechanical properties of steels after fire exposure -- 4.1 Introduction -- 4.2 Residual properties of hot-rolled Q420 steel -- 4.2.1 Specimen details -- 4.2.2 Test equipment and procedure -- 4.2.3 Failure modes -- 4.2.4 Stress-strain relationships -- 4.2.5 Elastic modulus -- 4.2.6 Yield stress -- 4.2.7 Tensile strength -- 4.2.8 Ductility -- 4.3 Residual properties of high strength Q460 steel -- 4.3.1 Experimental program -- 4.3.1.1 Test specimen -- 4.3.1.2 Test setup -- 4.3.1.3 Heating and cooling procedures -- 4.3.2 Test results -- 4.3.2.1 Visual observation -- 4.3.2.2 Stress-strain curves -- 4.3.2.3 Residual yield strength -- 4.3.2.4 Residual ultimate strength -- 4.3.2.5 Elastic modulus -- 4.3.2.6 Ultimate elongation -- 4.3.3 Proposed equations -- 4.3.3.1 Yield strength -- 4.3.3.2 Ultimate strength -- 4.3.3.3 Elastic modulus -- 4.3.3.4 Ultimate elongation -- 4.4 Residual properties of high strength Q690 steel -- 4.4.1 Specimen details -- 4.4.2 Heating and cooling -- 4.4.3 Tension setup and procedures -- 4.4.4 Test results -- 4.4.4.1 Temperature evolution -- 4.4.4.2 Color spectrum and failure mode -- 4.4.4.3 Stress-strain relationships -- 4.4.4.4 Yield and tension strength -- 4.4.4.5 Elastic modulus -- 4.4.4.6 Ratio of ultimate elongation -- 4.4.5 Proposed prediction equations -- 4.4.5.1 Yield strength -- 4.4.5.2 Tension strength -- 4.4.5.3 Elastic modulus -- 4.4.5.4 Ultimate elongation -- 4.5 Residual properties of high strength S460 steel -- 4.5.1 Experimental investigation.4.5.1.1 Test material and specimen -- 4.5.1.2 Test equipment and procedure -- 4.5.2 Experimental results -- 4.5.2.1 Elastic modulus -- 4.5.2.2 Yield strength -- 4.5.2.3 Ultimate strength -- 4.5.2.4 Ductility -- 4.5.3 Predictive equations for residual properties -- 4.5.3.1 Elastic modulus -- 4.5.3.2 Yield strength -- 4.5.3.3 Ultimate strength -- 4.6 Residual properties of high strength S690 steel -- 4.6.1 Test material and specimen -- 4.6.2 Test equipment and procedure -- 4.6.3 Experimental results -- 4.6.3.1 Elastic modulus -- 4.6.3.2 Yield strength -- 4.6.3.3 Ultimate strength -- 4.6.3.4 Ductility -- 4.6.4 Predictive equations for residual properties -- 4.6.4.1 Elastic modulus -- 4.6.4.2 Yield strength -- 4.6.4.3 Ultimate strength -- 4.7 Residual properties of high strength S960 steel -- 4.7.1 Test specimen and equiment -- 4.7.2 Experimental results -- 4.7.2.1 Postfire stress-strain relationships -- 4.7.2.2 Elastic modulus -- 4.7.2.3 Yield strength -- 4.7.2.4 Ultimate strength -- 4.7.2.5 Failure mode -- 4.7.3 Predictive equations for residual properties -- 4.7.3.1 Elastic modulus -- 4.7.3.2 Yield strength -- 4.7.3.3 Ultimate strength -- 4.8 Residual properties of high strength A572 steel -- 4.8.1 Test equipment -- 4.8.2 Test procedure -- 4.8.3 Residual strength -- 4.8.4 Temperature-dependent mechanical properties of A572 steel -- 4.8.5 Proposed reduction factors for residual strength properties -- 4.9 Residual properties of high strength RQT-S690 high strength steel -- 4.9.1 The test device -- 4.9.2 Tested materials and specimens -- 4.9.3 Test results -- 4.9.3.1 General descriptions -- 4.9.3.2 Analysis of the deterioration of mechanical properties -- 4.9.3.3 The influence of repeated heating -- 4.9.4 Test specimens -- 4.9.5 Testing method -- 4.9.5.1 Heat-up tests -- 4.9.5.2 Cooling tests -- 4.9.6 Results and discussion.4.9.6.1 General descriptions -- 4.9.6.2 Stress-strain curves -- 4.9.6.3 Strength -- 4.9.6.4 Ductility -- 4.9.6.5 Comparison with grade 800 high strength steel -- 4.9.7 Predictive equations -- 4.10 Residual properties of GLG460, GLG550, GLG650, and GLG835 steel -- 4.10.1 Test material and specimens -- 4.10.2 Test equipment and procedure -- 4.10.3 Experimental results -- 4.10.3.1 Thermochromism of steel tie rods -- 4.10.3.2 Failure modes of test specimens -- 4.10.3.3 Stress-strain relationships -- 4.10.3.4 Elastic modulus -- 4.10.3.5 Yield strength -- 4.10.3.6 Ultimate strength -- 4.10.3.7 Ductility -- 4.10.3.8 Effects of cyclic heating and cooling -- 4.10.4 Predictive equations for the postfire residual mechanical properties -- 4.10.4.1 Residual elastic modulus -- 4.10.4.2 Residual yield strength -- 4.10.4.3 Residual ultimate strength -- References -- 5 - Creep behavior of steels at elevated temperatures -- 5.1 Introduction -- 5.2 Typical creep-time curve -- 5.3 Creep behavior of high strength Q460 steel -- 5.3.1 Test setup -- 5.3.2 Test specimens -- 5.3.3 Test procedure -- 5.3.4 Creep-time curves at various stress levels -- 5.3.5 Creep-time curves at various temperatures -- 5.3.6 Rupture of specimens -- 5.3.7 Proposed creep model -- 5.3.7.1 Fields and Fields model -- 5.3.7.2 ANSYS model -- 5.4 Creep behavior of high strength Q690 steel -- 5.4.1 Test setup -- 5.4.2 Test specimens -- 5.4.3 Test procedures -- 5.4.4 Test results -- 5.4.5 Comparison with other steels -- 5.4.6 Creep model -- 5.5 Creep behavior of ASTM A572 steel -- 5.5.1 Test specimens -- 5.5.2 Test setup -- 5.5.3 Test procedure -- 5.5.4 Room temperature stress-strain response -- 5.5.5 Creep response at elevated temperatures -- 5.5.6 Creep response at various stress levels -- 5.5.7 Design recommendations -- 5.6 Creep buckling of high strength Q460 steel columns.5.6.1 Specimen preparation.Weiyong Wang and Venkatesh Kodur.Fire resistant materials.SteelThermal properties.Steel, Structural.Building, Fireproof.TH1065 .W364 2020eb620.11217620.171797801281330330128133031978012813302601281330231127927981rdaMiAaPQ19120920250416110502.0almafu_9960074557002883Converted from MARCXML to MODS version 3.6 using MARC21slim2MODS3-6.xsl (Revision 1.119 2018/06/21)eng info:srw/schema/1/mods-v3.5 xml 9Voinov, Vasilij G.othBalakrishnan, N.othNikulin, Michail S.othtextTextElectronic booksbookneXA-NLAmsterdamAcademic Press2013First editionsingle uniteng

electronic resource

remote

Online Ressource

Computermedien

Online-Ressource

Chi-Squared Goodness of Fit Tests with Applications provides a thorough and complete context for the theoretical basis and implementation of Pearson's monumental contribution and its wide applicability for chi-squared goodness of fit tests. The book is ideal for researchers and scientists conducting statistical analysis in processing of experimental data as well as to students and practitioners with a good mathematical background who use statistical methods. The historical context, especially Chapter 7, provides great insight into importance of this subject with an authoritative author team. This reference includes the most recent application developments in using these methods and models. Systematic presentation with interesting historical context and coverage of the fundamentals of the subjectPresents modern model validity methods, graphical techniques, and computer-intensive methodsRecent research and a variety of open problemsInteresting real-life examples for practitionersHalf Title; Title Page; Copyright; Dedication; Contents; Preface; A Historical Account; Pearson's Sum and Pearson-Fisher Test; 2.1 Pearson's chi-squared sum; 2.2 Decompositions of Pearson's chi-squared sum; 2.3 Neyman-Pearson classes and applications of decompositions of Pearson's sum; 2.4 Pearson-Fisher and Dzhaparidze-Nikulin tests; 2.5 Chernoff-Lehmann theorem; 2.6 Pearson-Fisher test for random class end points; Wald's Method and Nikulin-Rao-Robson Test; 3.1 Wald's method; 3.2 Modifications of Nikulin-Rao-Robson Test; 3.3 Optimality of Nikulin-Rao-Robson Test3.4 Decomposition of Nikulin-Rao-Robson Test3.5 Chi-Squared Tests for Multivariate Normality; 3.5.1 Introduction; 3.5.2 Modified chi-squared tests; 3.5.3 Testing for bivariate circular normality; 3.5.4 Comparison of different tests; 3.5.5 Conclusions; 3.6 Modified Chi-Squared Tests for The Exponential Distribution; 3.6.1 Two-parameter exponential distribution; 3.6.2 Scale-exponential distribution; 3.7 Power Generalized Weibull Distribution; 3.7.1 Estimation of parameters; 3.7.2 Modified chi-squared test; 3.7.3 Evaluation of power3.8 Modified chi-Squared Goodness of Fit Test for Randomly Right Censored Data3.8.1 Introduction; 3.8.2 Maximum likelihood estimation for right censored data; 3.8.3 Chi-squared goodness of fit test; 3.8.4 Examples; 3.9 Testing Normality for Some Classical Data on Physical Constants; 3.9.1 Cavendish's measurements; 3.9.2 Millikan's measurements; 3.9.3 Michelson's measurements; 3.9.4 Newcomb's measurements; 3.10 Tests Based on Data on Stock Returns of Two Kazakhstani Companies; 3.10.1 Analysis of daily returns; 3.10.2 Analysis of weekly returns; Wald's Method and Hsuan-Robson-Mirvaliev Test4.1 Wald's method and moment-type estimators4.2 Decomposition of Hsuan-Robson-Mirvaliev test; 4.3 Equivalence of Nikulin-Rao-Robson and Hsuan-Robson-Mirvaliev tests for exponential family; 4.4 Comparisons of some modified chi-squared tests; 4.4.1 Maximum likelihood estimates; 4.4.2 Moment-type estimators; 4.5 Neyman-Pearson classes; 4.5.1 Maximum likelihood estimators; 4.5.2 Moment-type estimators; 4.6 Modified chi-squared test for three-parameter Weibull distribution; 4.6.1 Parameter estimation and modified chi-squared tests; 4.6.2 Power evaluation; 4.6.3 Neyman-Pearson classes4.6.4 Discussion4.6.5 Concluding remarks; Modifications Based on UMVUEs; 5.1 Tests for Poisson, binomial, and negative binomial distributions; 5.2 Chi-squared tests for one-parameter exponential family; 5.3 Revisiting Clarke's data on flying bombs; Vector-Valued Tests; 6.1 Introduction; 6.2 Vector-valued tests: an artificial example; 6.3 Example of Section 2.3 revisited; 6.4 Combining nonparametric and parametric tests; 6.5 Combining nonparametric tests; 6.6 Concluding comments; Applications of Modified Chi-Squared Tests7.1 Poisson versus binomial: Appointment of judges to the US Supreme CourtMachine generated contents note: 1.A Historical Account2.Pearson's Sum and Pearson-Fisher Test -- 2.1.Pearson's chi-squared sum -- 2.2.Decompositions of Pearson's chi-squared sum -- 2.3.Neyman-Pearson classes and applications of decompositions of Person's Sum -- 2.4.Pearson-Fisher and Dzhaparidze-Nikulin tests -- 2.5.Chernoff-Lehmann Theorem -- 2.6.Pearson-Fisher test for random class end points -- 3.Wald's Method and Nikulin-Rao-Robson Test -- 3.1.Wald's Method -- 3.2.Modifications of Nikulin-Rao-Robson test -- 3.3.Optimality of Nikulin-Rao-Robson test -- 3.4.Decomposition of Nikulin-Rao-Robson Test -- 3.5.Chi-squared tests for multivariate normality -- 3.5.1.Introduction -- 3.5.2.Modified chi-squared tests -- 3.5.3.Testing for bivariate circular normality -- 3.5.4.Comparison of different tests -- 3.5.5.Conclusions -- 3.6.Modified chi-squared tests for the exponential distribution -- 3.6.1.Two-parameter exponential distribution -- 3.6.2.Scale-exponential distribution -- 3.7.Power generalized Weibull distribution -- 3.7.1.Estimation of parameters -- 3.7.2.Modified chi-squared test -- 3.7.3.Evaluation of power -- 3.8.Modified chi-squared goodness of fit test for randomly right censored data -- 3.8.1.Introduction -- 3.8.2.Maximum likelihood estimation for right censored data -- 3.8.3.Chi-squared goodness of fit test -- 3.8.4.Examples -- 3.9.Testing normality for some classical data on physical constants -- 3.9.1.Cavendish's measurements -- 3.9.2.Millikan's measurements -- 3.9.3.Michelson's measurements -- 3.9.4.Newcomb's measurements -- 3.10.Tests based on data on stock returns of two Kazakhastani companies -- 3.10.1.Analysis of daily returns -- 3.10.2.Analysis of weekly returns -- 4.Wald's Method and Hsuan-Robson-Mirvaliev Test -- 4.1.Wald's method and moment-type estimators -- 4.2.Decomposition of Hsuan-Robson-Mirvaliev test -- 4.3.Equivalence of Nikulin-Rao-Robson and Hsuan-Robson-Mirvaliev tests for exponential family -- 4.4.Comparisons of some modified chi-squared tests -- 4.4.1.Maximum likelihood estimates -- 4.4.2.Moment-type estimators -- 4.5.Neyman-Pearson classes -- 4.5.1.Maximum likelihood estimators -- 4.5.2.Moment-type estimators -- 4.6.Modified chi-squared rest for three-parameter Weibull distribution -- 4.6.1.Parameter estimation and modified chi-squared tests -- 4.6.2.Power evaluation -- 4.6.3.Neyman-Pearson classes -- 4.6.4.Discussion -- 4.6.5.Concluding remarks -- 5.Modifications Based on UMVUEs -- 5.1.Test for Poisson, binomial, and negative binomial distributions -- 5.2.Chi-squared test for one-parameter exponential family -- 5.3.Revisiting Clarke's data on flying bombs -- 6.Vector-Valued Tests -- 6.1.Introduction -- 6.2.Vector-valued tests: An artificial example -- 6.3.Example of Section 2.3 revisited -- 6.4.Combining nonparametric and parametric tests -- 6.5.Combining nonparametric tests -- 6.6.Concluding comments -- 7.Applications of Modified Chi-Squared Tests -- 7.1.Poisson versus binomial: Appointment of judges to the US supreme court -- 7.1.1.Introduction -- 7.1.2.Data to be analyzed -- 7.1.3.Statistical analysis of the data -- 7.1.4.Revisiting the analyses of Wallis and Ulmer -- 7.1.5.Comments about King's exponential Poisson regression model -- 7.1.6.Concluding remarks -- 7.2.Revisiting Rutherford's data -- 7.2.1.Analysis of the data -- 7.2.2.Concluding remarks -- 7.3.Modified tests for the logistic distribution -- 7.4.Modified chi-squared -- 7.4.1.Introduction -- 7.4.2.The NRR, DN and McCulloch tests -- 8.Probability Distributions of Interest -- 8.1.Discrete probability distributions -- 8.1.1.Binomial, geometric, and negative binomial distributions -- 8.1.2.Multinomial distribution -- 8.1.3.Poisson distribution -- 8.2.Continuous probability distributions -- 8.2.1.Exponential distribution -- 8.2.2.Uniform distribution -- 8.2.3.Triangular distribution -- 8.2.4.Pareto model -- 8.2.5.Normal distribution -- 8.2.6.Multivariate normal distribution -- 8.2.7.Chi-square distribution -- 8.2.8.Non-central chi-square distribution -- 8.2.9.Weibull distribution -- 8.2.10.Generalized power Weibull distribution -- 8.2.11.Birnbaum-Saunders distribution -- 8.2.12.Logistic distribution -- 9.Chi-Squared Tests for Specific Distributions -- 9.1.Test for Poisson, binomial, and "binomial" approximation of Feller's distribution -- 9.2.Elements of matrices K, B, C, and V for the three-parameter Weibull distribution -- 9.3.Elements of matrices J and B for the generalized power Weibull distribution -- 9.4.Elements of matrices J and B for the two-parameter exponential distribution -- 9.5.Elements of matrices B, C, K, and V to test the logistic distribution -- 9.6.Testing for normality -- 9.7.Testing for exponentiality -- 9.7.1.Test of Greenwood and Nikulin (see Section 3.6.1) -- 9.7.2.Nikulin-Rao-Robson test (see Eq. (3.8) and Section 9.4) -- 9.8.Testing for the logistic -- 9.9.Testing for the three-parameter Weibull -- 9.10.Testing for the power generalized Weibull -- 9.11.Testing for two-dimensional circular normality.V. Voinov, M. Nikulin, N. BalakrishnanIncludes bibliographical references and index. - Description based on print version recordOnline-Ausg.Chi-square testDistribution (Probability theory)distribution (statistics-related concept)Distribution (Théorie des probabilités)Test du khi-carréQA277.3519.56519.5/6*62G1062-0262-01ISBN 1299196144ISBN 0123971942Druck-AusgabeISBN 0123971942https://zbmath.org/?q=an:1276.620270123971942978012397194497812991961481299196144829455684842859899https://www.sciencedirect.com/science/book/9780123971944http://www.sciencedirect.com/science/book/9780123971944https://zbmath.org/?q=an:1276.62027rakwbDE-62714050920251225212035.0gbv_1656130289Converted from MARCXML to MODS version 3.6 using MARC21slim2MODS3-6.xsl (Revision 1.119 2018/06/21)ger info:srw/schema/1/mods-v3.5 xml 10practical aspects /Homès, Bernard,author.textbibliographytextenkJohn Wiley & Sons, Inc.London, England ;Hoboken, New Jersey :ISTE Ltd :John Wiley & Sons, Inc.,[2022]©20222022single uniteng

electronic resource

remote

1 online resource (306 pages)

computer

online resource

As a society today, we are so dependent on systems-of-systems that any malfunction has devastating consequences, both human and financial. Their technical design, functional complexity and numerous interfaces justify a significant investment in testing in order to limit anomalies and malfunctions. Based on more than 40 years of practice, this book goes beyond the simple testing of an application - already extensively covered by other authors - to focus on methodologies, techniques, continuous improvement processes, load estimates, metrics and reporting, which are illustrated by a case study. It also discusses several challenges for the near future. Pragmatic and clear, this book displays many examples and references that will help you improve the quality of your systemsof-systems efficiently and effectively and lead you to identify the impact of upstream decisions and their consequences. Advanced Testing of Systems-of-Systems 2 deals with the practical implementation and use of the techniques and methodologies proposed in the first volume.Cover -- Title Page -- Copyright Page -- Contents -- Title Page -- Copyright Page -- Contents -- Dedication and Acknowledgments -- Preface -- Chapter 1. Test Project Management -- 1.1. General principles -- 1.1.1. Quality of requirements -- 1.1.2. Completeness of deliveries -- 1.1.3. Availability of test environments -- 1.1.4. Availability of test data -- 1.1.5. Compliance of deliveries and schedules -- 1.1.6. Coordinating and setting up environments -- 1.1.7. Validation of prerequisites - Test Readiness Review (TRR) -- 1.1.8. Delivery of datasets (TDS) -- 1.1.9. Go-NoGo decision - Test Review Board (TRB) -- 1.1.10. Continuous delivery and deployment -- 1.2. Tracking test projects -- 1.3. Risks and systems-of-systems -- 1.4. Particularities related to SoS -- 1.5. Particularities related to SoS methodologies -- 1.5.1. Components definition -- 1.5.2. Testing and quality assurance activities -- 1.6. Particularities related to teams -- Chapter 2. Testing Process -- 2.1. Organization -- 2.2. Planning -- 2.2.1. Project WBS and planning -- 2.3. Control of test activities -- 2.4. Analyze -- 2.5. Design -- 2.6. Implementation -- 2.7. Test execution -- 2.8. Evaluation -- 2.9. Reporting -- 2.10. Closure -- 2.11. Infrastructure management -- 2.12. Reviews -- 2.13. Adapting processes -- 2.14. RACI matrix -- 2.15. Automation of processes or tests -- 2.15.1. Automate or industrialize? -- 2.15.2. What to automate? -- 2.15.3. Selecting what to automate -- Chapter 3. Continuous Process Improvement -- 3.1. Modeling improvements -- 3.1.1. PDCA and IDEAL -- 3.1.2. CTP -- 3.1.3. SMART -- 3.2. Why and how to improve? -- 3.3. Improvement methods -- 3.3.1. External/internal referential -- 3.4. Process quality -- 3.4.1. Fault seeding -- 3.4.2. Statistics -- 3.4.3. A posteriori -- 3.4.4. Avoiding introduction of defects -- 3.5. Effectiveness of improvement activities.3.6. Recommendations -- Chapter 4. Test, QA or IV&amp -- V Teams -- 4.1. Need for a test team -- 4.2. Characteristics of a good test team -- 4.3. Ideal test team profile -- 4.4. Team evaluation -- 4.4.1. Skills assessment table -- 4.4.2. Composition -- 4.4.3. Select, hire and retain -- 4.5. Test manager -- 4.5.1. Lead or direct? -- 4.5.2. Evaluate and measure -- 4.5.3. Recurring questions for test managers -- 4.6. Test analyst -- 4.7. Technical test analyst -- 4.8. Test automator -- 4.9. Test technician -- 4.10. Choose our testers -- 4.11. Training, certification or experience? -- 4.12. Hire or subcontract) -- 4.12.1. Effective subcontracting -- 4.13. Organization of multi-level test teams -- 4.13.1. Compliance, strategy and organization -- 4.13.2. Unit test teams (UT/CT) -- 4.13.3. Integration testing team (IT) -- 4.13.4. System test team (SYST) -- 4.13.5. Acceptance testing team (UAT) -- 4.13.6. Technical test teams (TT) -- 4.14. Insourcing and outsourcing challenges -- 4.14.1. Internalization and collocation -- 4.14.2. Near outsourcing -- 4.14.3. Geographically distant outsourcing -- Chapter 5. Test Workload Estimation -- 5.1. Difficulty to estimate workload -- 5.2. Evaluation techniques -- 5.2.1. Experience-based estimation -- 5.2.2. Based on function points or TPA -- 5.2.3. Requirements scope creep -- 5.2.4. Estimations based on historical data -- 5.2.5. WBS or TBS -- 5.2.6. Agility, estimation and velocity -- 5.2.7. Retroplanning -- 5.2.8. Ratio between developers - testers -- 5.2.9. Elements influencing the estimate -- 5.3. Test workload overview -- 5.3.1. Workload assessment verification and validation -- 5.3.2. Some values -- 5.4. Understanding the test workload -- 5.4.1. Component coverage -- 5.4.2. Feature coverage -- 5.4.3. Technical coverage -- 5.4.4. Test campaign preparation -- 5.4.5. Running test campaigns -- 5.4.6. Defects management.5.5. Defending our test workload estimate -- 5.6. Multi-tasking and crunch -- 5.7. Adapting and tracking the test workload -- Chapter 6. Metrics, KPI and Measurements -- 6.1. Selecting metrics -- 6.2. Metrics precision -- 6.2.1. Special case of the cost of defaults -- 6.2.2. Special case of defects -- 6.2.3. Accuracy or order of magnitude? -- 6.2.4. Measurement frequency -- 6.2.5. Using metrics -- 6.2.6. Continuous improvement of metrics -- 6.3. Product metrics -- 6.3.1. FTR: first time right -- 6.3.2. Coverage rate -- 6.3.3. Code churn -- 6.4. Process metrics -- 6.4.1. Effectiveness metrics -- 6.4.2. Efficiency metrics -- 6.5. Definition of metrics -- 6.5.1. Quality model metrics -- 6.6. Validation of metrics and measures -- 6.6.1. Baseline -- 6.6.2. Historical data -- 6.6.3. Periodic improvements -- 6.7. Measurement reporting -- 6.7.1. Internal test reporting -- 6.7.2. Reporting to the development team -- 6.7.3. Reporting to the management -- 6.7.4. Reporting to the clients or product owners -- 6.7.5. Reporting to the direction and upper management -- Chapter 7. Requirements Management -- 7.1. Requirements documents -- 7.2. Qualities of requirements -- 7.3. Good practices in requirements management -- 7.3.1. Elicitation -- 7.3.2. Analysis -- 7.3.3. Specifications -- 7.3.4. Approval and validation -- 7.3.5. Requirements management -- 7.3.6. Requirements and business knowledge management -- 7.3.7. Requirements and project management -- 7.4. Levels of requirements -- 7.5. Completeness of requirements -- 7.5.1. Management of TBDs and TBCs -- 7.5.2. Avoiding incompleteness -- 7.6. Requirements and agility -- 7.7. Requirements issues -- Chapter 8. Defects Management -- 8.1. Defect management, MOA and MOE -- 8.1.1. What is a defect? -- 8.1.2. Defects and MOA -- 8.1.3. Defects and MOE -- 8.2. Defect management workflow -- 8.2.1. Example -- 8.2.2. Simplify.8.3. Triage meetings -- 8.3.1. Priority and severity of defects -- 8.3.2. Defect detection -- 8.3.3. Correction and urgency -- 8.3.4. Compliance with processes -- 8.4. Specificities of TDDs, ATDDs and BDDs -- 8.4.1. TDD: test-driven development -- 8.4.2. ATDD and BDD -- 8.5. Defects reporting -- 8.5.1. Defects backlog management -- 8.6. Other useful reporting -- 8.7. Don't forget minor defects -- Chapter 9. Configuration Management -- 9.1. Why manage configuration? -- 9.2. Impact of configuration management -- 9.3. Components -- 9.4. Processes -- 9.5. Organization and standards -- 9.6. Baseline or stages, branches and merges -- 9.6.1. Stages -- 9.6.2. Branches -- 9.6.3. Merge -- 9.7. Change control board (CCB) -- 9.8. Delivery frequencies -- 9.9. Modularity -- 9.10. Version management -- 9.11. Delivery management -- 9.11.1. Preparing for delivery -- 9.11.2. Delivery validation -- 9.12. Configuration management and deployments -- Chapter 10. Test Tools and Test Automation -- 10.1. Objectives of test automation -- 10.1.1. Find more defects -- 10.1.2. Automating dynamic tests -- 10.1.3. Find all regressions -- 10.1.4. Run test campaigns faster -- 10.2. Test tool challenges -- 10.2.1. Positioning test automation -- 10.2.2. Test process analysis -- 10.2.3. Test tool integration -- 10.2.4. Qualification of tools -- 10.2.5. Synchronizing test cases -- 10.2.6. Managing test data -- 10.2.7. Managing reporting (level of trust in test tools) -- 10.3. What to automate? -- 10.4. Test tooling -- 10.4.1. Selecting tools -- 10.4.2. Computing the return on investment (ROI) -- 10.4.3. Avoiding abandonment of tools and automation -- 10.5. Automated testing strategies -- 10.6. Test automation challenge for SoS -- 10.6.1. Mastering test automation -- 10.6.2. Preparing test automation -- 10.6.3. Defect injection/fault seeding.10.7. Typology of test tools and their specific challenges -- 10.7.1. Static test tools versus dynamic test tools -- 10.7.2. Data-driven testing (DDT) -- 10.7.3. Keyword-driven testing (KDT) -- 10.7.4. Model-based testing (MBT) -- 10.8. Automated regression testing -- 10.8.1. Regression tests in builds -- 10.8.2. Regression tests when environments change -- 10.8.3. Prevalidation regression tests, sanity checks and smoke tests -- 10.8.4. What to automate? -- 10.8.5. Test frameworks -- 10.8.6. E2E test cases -- 10.8.7. Automated test case maintenance or not? -- 10.9. Reporting -- 10.9.1. Automated reporting for the test manager -- Chapter 11. Standards and Regulations -- 11.1. Definition of standards -- 11.2. Usefulness and interest -- 11.3. Implementation -- 11.4. Demonstration of compliance - IADT -- 11.5. Pseudo-standards and good practices -- 11.6. Adapting standards to needs -- 11.7. Standards and procedures -- 11.8. Internal and external coherence of standards -- Chapter 12. Case Study -- 12.1. Case study: improvement of an existing complex system -- 12.1.1. Context and organization -- 12.1.2. Risks, characteristics and business domains -- 12.1.3. Approach and environment -- 12.1.4. Resources, tools and personnel -- 12.1.5. Deliverables, reporting and documentation -- 12.1.6. Planning and progress -- 12.1.7. Logistics and campaigns -- 12.1.8. Test techniques -- 12.1.9. Conclusions and return on experience -- Chapter 13. Future Testing Challenges -- 13.1. Technical debt -- 13.1.1. Origin of the technical debt -- 13.1.2. Technical debt elements -- 13.1.3. Measuring technical debt -- 13.1.4. Reducing technical debt -- 13.2. Systems-of-systems specific challenges -- 13.3. Correct project management -- 13.4. DevOps -- 13.4.1. DevOps ideals -- 13.4.2. DevOps-specific challenges -- 13.5. IoT (Internet of Things) -- 13.6. Big Data.13.7. Services and microservices.Bernard Homes.Includes bibliographical references and index.Computer softwareTesting.QA76.754 .H664 2022929.605Homes, BernardNewark : John Wiley & Sons, Incorporated,c2023ISBN 97817863075079781394188482139418848X9781394188468139418846310.1002/97813941884821371296200rdaMiAaPQ23041220230921194454.0almatuudk_9923020004802884Converted from MARCXML to MODS version 3.6 using MARC21slim2MODS3-6.xsl (Revision 1.119 2018/06/21)eng