You're reading from Continuous Testing, Quality, Security, and Feedback Essential strategies and secure practices for DevOps, DevSecOps, and SRE transformations

Product type Paperback

Published in Sep 2024

Publisher Packt

ISBN-13 9781835462249

Length 350 pages

Edition 1st Edition

Languages

Python

Tools

Selenium

Concepts

Design

Author (1):

Marc Hornbeek

Preface

1. Part 1: Understanding Continuous Testing, Quality, Security, and Feedback FREE CHAPTER

2. Chapter 1: Principles of Continuous Testing, Quality, Security, and Feedback

3. Chapter 2: The Importance of Continuous Testing, Quality, Security, and Feedback

4. Chapter 3: Experiences and Pitfalls with Continuous Testing, Quality, Security, and Feedback

5. Part 2: Determining Solutions Priorities

6. Chapter 4: Engineering Approach to Continuous Testing, Quality, Security, and Feedback

7. Chapter 5: Determining Transformation Goals

8. Chapter 6: Discovery and Benchmarking

9. Chapter 7: Selecting Tool Platforms and Tools

10. Chapter 8: Applying AL/ML to Continuous Testing, Quality, Security, and Feedback

11. Part 3: Deep Dive into Roadmaps, Implementation Patterns, and Measurements

12. Chapter 9: Use Cases for Integrating with DevOps, DevSecOps, and SRE

13. Chapter 10: Building Roadmaps for Implementation

14. Chapter 11: Understanding Transformation Implementation Patterns

15. Chapter 12: Measuring Progress and Outcomes

16. Part 4: Exploring Future Trends and Continuous Learning

17. Chapter 13: Emerging Trends

18. Chapter 14: Exploring Continuous Learning and Improvement

19. Glossary and References

20. Index

21. Other Books You May Enjoy

Capability maturity levels – Continuous testing

The continuous testing CMM outlined in Figure 4.5 describes five levels of maturity for continuous testing practices:

Level 1: Manual & Unmeasured (Chaos) – Ad hoc and manual testing processes. Limited use of basic testing tools. Few if any structured metrics or KPIs for testing:
- People: Poor communication between team members. Blameful culture.
- Process: Orchestration of integration and delivery processes are manual.
- Tech: Disparate tools used by different teams. No integrated toolchain.
- Metrics: Few, if any, metrics are automated. Releases are unpredictable and error prone.
Level 2: Continuous Integration (CI) – Initial automation of some test cases. Integration of testing in the CI pipeline. Basic metrics for test coverage and effectiveness:
- People: Initial collaboration between developers and QA testers begins.
- Process: Testing processes are defined and automated for CI.
- Technology: Introduction of automated...