Quality for DevOps teams

Part 6 Quality measures and skills 257
35 Description of quality measures 258
35.1 Root cause analysis 258
35.2 Specification and Example (SaE) 259
35.3 Test-driven development 265
35.4 Pair programming 267
35.5 Pairing 268
35.6 Reviewing 269
35.7 Test design techniques 270
35.8 Feature toggles 271
35.9 Monitoring of product quality 273
35.10 Parallel testing 274
36 Personal, interpersonal and team skills 276

Part 7 Test varieties 285
37 Make sure there is variety in your testing 286
38 Performance testing 294
39 Usability testing 306
40 Security testing 314
41 Maintainability testing 321
42 Mutation testing tests the test 325

Part 8 Test design 331
43 The many aspects of creating tests and exploring a test object 332
43.1 Two distinct ways of preparing and performing tests 333
43.2 Experience-based testing 333
43.3 Coverage-based testing 334
43.4 Always combine experience- and coverage-based testing 337
44 Test design entities 338
45 Test approaches applied 343
45.1 Coverage-based testing 343
45.2 Process-oriented test design 345
45.3 Condition-oriented test design 345
45.4 Data-oriented test design 346
45.5 Appearance-oriented test design 347
45.6 Selecting and combining approaches and techniques 347
46 There are many techniques, which one to use? 350
46.1 No risk – no test – no development 352
46.2 Example case: “The magic boat ride in TestLand” 352
46.3 Process-oriented testing: path coverage 353
46.4 Condition-oriented test design 358
46.5 Data-oriented testing with EP and BVA 362
46.6 Data combination test 366
46.7 Syntactic testing 370
46.8 Code coverage in many different intensities 371
47 Experience-based testing 376
47.1 Experience-based testing approaches 376
47.2 Checklist 379
47.3 Error guessing 381
47.4 Exploratory testing 383
47.5 Crowd testing 390
47.6 What are heuristics and when to use them? 394
48 Is there any value in unstructured testing? 398

Appendix: Quality characteristics and non-functional testing 404

References 415
Index 423