Intro; Trademarks; Preface; Why This Book?; What Is This Book Not About?; What Is This Book About?; Acknowledgements; Contents; List of Abbreviations; 1: Fundamentals of Software Testing; 1.1 Introduction; 1.2 The Beginning: What Is Testing Really About and Why Is It So Difficult?; 1.2.1 Testing as a Unique Activity. Why Testing Is So Hard?; Example; Example; 1.2.2 Testing Finds Bugs, But This Is Just the Tip of the Iceberg; 1.2.3 Quality Control vs. Quality Assurance; 1.2.4 Itś Not About the Working Code, But a Solution to the Business Problem; 1.2.5 Your Real Boss Is Your Client; Example
1.2.6 Continuous Scale of Tests: From Confirmation to D̀irty ́TestingExample; 1.2.7 Test Redundancy Is Not Always Bad; 1.2.8 Disregarding Risk Is Risky; 1.2.9 Feedback for the Team; 1.2.10 It Is Not About Test Execution; 1.3 The Mythical Test Case; 1.3.1 A Primary Function of Test Cases; 1.3.2 When Should We Use Test Cases?; 1.3.3 Benefits from Test Cases; Example; 1.4 The Nature of Defects and the Myths About Them; 1.4.1 Defect Distribution in Time; 1.4.2 Cost of Defect Removal; 1.4.3 LOC Metric as a Defect Predictor; 1.4.4 Defect Grouping
1.4.5 Defects Resulting from Interaction of Parameters1.4.6 Module Structure vs. Defect-Proneness; Example; 1.5 Exploratory vs. Scripted: An Apparent Problem; Example; 1.6 The Ideal Testerś Skill Set; Example; 1.7 Itś All About Communication; Example; 1.8 Testing Process: Pure Abstraction or Tangible Reality?; 1.9 Models in Testing; Example; 1.10 A Bit of Philosophy: Problem of Universals from the Testerś Perspective; 2: Testing Strategies: How to Become a Better Tester?; 2.1 Introduction; 2.2 Be Inspired: What Can a Tester Learn from; 2.2.1 Philosophy; 2.2.2 Psychology
2.2.3 Economy and ManagementExample; 2.2.4 Mathematics and Logic; Example; 2.2.5 Probability and Statistics; Example; 2.2.6 Systems Science; 2.2.7 Ergonomics; 2.3 The Testerś Mind: Psychology of Testing; 2.3.1 Creativity; 2.3.2 Cognitive Bias; 2.3.3 Confirmation Bias and Wason Experiment: Software Testing as Hypothesis Testing; Example; 2.3.4 Wason Selection Test: Why Is Language So Important?; Example; 2.3.5 Cognitive Dissonance; 2.3.6 Conwayś Law; 2.3.7 Csíkszentmihlyiś Flow Model; 2.4 Useful Methodological Laws and Tools; 2.4.1 Occamś Razor
2.4.2 Descartes ́Doubt as Methodological Skepticism2.4.3 Optimization and Prioritization: Pareto 80-20 Principle; 2.4.4 Time Management: Parkinsonś Law; 2.4.5 Burchś Four Stages of Competence; 2.4.6 More Eyeballs Is Better: Linusś Law; 2.4.7 Legacy Code: Eaglesonś Law; 2.4.8 How to Hire New People: Peter Principle; 2.4.9 Meeting Facilitation: Sayreś Law; 2.4.10 Data Centralization: Ellisonś Law of Data; 2.4.11 False Sense of Security: Spaffordś Law of False Alerts; 2.4.12 Beizerś Pesticide Paradox; 2.5 Standards and Norms: Best Practices or Pure Evil?; Example

Control code: SPR1029352546

Dimensions: unknown

Extent: 1 online resource.

File format: unknown

Form of item: online

Isbn: 9783319731957

Level of compression: unknown

Media category: computer

Media MARC source: rdamedia

Media type code

Other control number: 10.1007/978-3-319-73195-7

Quality assurance targets: not applicable

Record ID: b5170947

Reformatting quality: unknown

Sound: unknown sound

Specific material designation: remote

System control number

on1029352546
(OCoLC)1029352546

Context

Context of Thinking-driven testing : the most reasonable approach to quality control, Adam Roman

Structured data from the Bibframe namespace is licensed under the Creative Commons Attribution 4.0 International License by University of Liverpool. Additional terms may apply to data associated with third party namespaces.

Context

Item

Instantiates