CI/CD Anti-Patterns [Leanpub PDF/iPad/Kindle]

Nearly every software company claims to be “doing CI/CD,” yet many still struggle with slow releases, fragile pipelines, late discovery of defects, and a general lack of confidence in the software packages produced by the CI/CD pipeline, let alone deploying them to production.

Many of these failures can be traced to one or more of the 62 anti-patterns detailed in this book, organized into the

following categories:

Lacking real delivery
Non-Testing CI Steps
Test Automation is the Core of CI/CD
E2E Test Automation
CT Features Missing in Most CI/CD Servers
Mindset and Opinions
General Practices
Non-Functional Testing in CI/CD
CI/CD Hosting
Team Involvement
Leadership

This book will help you recognize and avoid these pitfalls, paving the way for achieving true Continuous Delivery.

- Preface
  - Purpose of the book
  - What is unique about this book?
  - Who the book is for?
  - Send me feedback
- 1:Introduction
  - 1.1:Continuous Integration (CI)
  - 1.2:Continuous Delivery and CI/CD
  - 1.3:Who does “CI/CD”?
  - 1.4:80+% of CI/CD effort is about Test Automation
  - 1.5:Continuous Testing
- 2:No Real Delivery
  - 2.1:Anti-Pattern: Unclear on delivery destination
  - 2.2:Anti-Pattern: Fear to deploy to a test-ready environment
  - 2.3:Anti-Pattern: Auto production deployment
  - 2.4:Anti-Pattern: CI/CD is disconnected from production releases
  - 2.5:Wrap-up
- 3:Non-Testing CI Steps
  - 3.1:Anti-Pattern: Not fully-automated CI steps
  - 3.2:Anti-Pattern: Manual database schema migration
  - 3.3:Anti-Pattern: CI Engineers lack automation skills
  - 3.4:Anti-Pattern: Slow compile/build/package
  - 3.5:Anti-Pattern: Fixated with code coverage
  - 3.6:Anti-Pattern: No auto-deployment to internal server environments
  - 3.7:Anti-Pattern: Lack of notification to the team about CI/CD build results
- 4:Test Automation is the Core of CI/CD
  - 4.1:Anti-Pattern: No Automated Testing in CI
  - 4.2:Anti-Pattern: Automated Test Execution Not Enabled in CI
  - 4.3:Anti-Pattern: Remove failed automated tests to pass the run
  - 4.4:Anti-Pattern: Long-Running Unit Tests in CI
  - 4.5:Anti-Pattern: Frequent Unit Test Failures in CI
  - 4.6:Anti-Pattern: Long-Running Integration Tests in CI
  - 4.7:Anti-Pattern: Automated Tests Not Run Often in CI
  - 4.8:Anti-Pattern: No Regression Testing in CI/CD
  - 4.9:Wrap-up
- 5:E2E Test Automation
  - 5.1:Anti-Pattern: No Automated Acceptance Testing in CI/CD
  - 5.2:Anti-Pattern: Sequential Executing E2E Tests in CI/CD
  - 5.3:Anti-Pattern: Avoid Running the Entire Suite—Split It into Smaller Suites
  - 5.4:Anti-Pattern: Prioritizing Tests in Execution
  - 5.5:Anti-Pattern: Fake Automated Acceptance Testing
  - 5.6:Anti-Pattern: E2E Test Scripts are Not in an Independent Git Repository
  - 5.7:Anti-Pattern: Headless Browser Testing
  - 5.8:Anti-Pattern: Long execution time > 1 hour
  - 5.9:Anti-Pattern: Parallel Execution on one machine
  - 5.10:Wrap-up
- 6:CT Features Missing in Most CI/CD Servers
  - 6.1:View Test Scripts in the CT Server Web Interface
  - 6.2:Capture Application Screenshots on E2E Test Failure
  - 6.3:Quick navigation to the failed test line
  - 6.4:Auto-Retry Failed E2E Test on Another Build Agent
  - 6.5:Manually Rerun Tests
  - 6.6:Dynamic Test Execution Ordering
  - 6.7:Distribution rules
  - 6.8:Delay completion
  - 6.9:Anti-Pattern: Being constrained by a vendor’s CI/CD server limitations and do nothing
  - 6.10:Wrap-up
- 7:Mindset
  - 7.1:Anti-Pattern: “Test Automation in CI Slows Down Development”
  - 7.2:Anti-Pattern: “Prefer expensive commercial CI/CD solutions over free open-source ones”
  - 7.3:Anti-Pattern: “API Testing as E2E Test Automation in CI/CD is Enough”
  - 7.4:Anti-Pattern: “E2E Test Automation Is Inherently Fragile, Keep Them To a Minimum”
  - 7.5:Anti-Pattern: “E2E Test Automation Is Too Expensive, So we don’t include in CI/CD”
  - 7.6:Anti-Pattern: Assuming Automated Tests Will Always Pass After Creation
  - 7.7:Anti-Pattern: “E2E Test Automation Scripts Must Use the Same Language as the Application Code”
  - 7.8:Anti-Pattern: “Set up a CI/CD Solution Takes a Long Time and Costly”
  - 7.9:Anti-Pattern: Drawn to flashy, smoke-and-mirror features like Test Replay
  - 7.10:Wrap-up
- 8:General Practices
  - 8.1:Anti-Pattern: Not the exact the same release package for different target environments.
  - 8.2:Anti-Pattern: Underinvesting in CI/CD Hardware
  - 8.3:Anti-Pattern: Automating the Tear Down and Setup of the CI Servers Daily
  - 8.4:Anti-Pattern: No Admin Access for Developers and Testers in CI/CD
  - 8.5:Anti-Pattern: Only limited to execute one specific type of automated tests in one language
  - 8.6:Anti-Pattern: A Single CI/CD Server Serving the Entire Company/Division
  - 8.7:Anti-Pattern: No Daily Builds
  - 8.8:Anti-Pattern: No incremental version or build number during internal testing
  - 8.9:Anti-Pattern: Commit-Driven CI/CD Triggers
  - 8.10:Anti-Pattern: Sending Real Emails Out During Test execution in CI/CD
- 9:Non-Functional Testing
  - 9.1:Anti-Pattern: No Continuous Performance Testing
  - 9.2:Anti-Pattern: No Continuous Load Testing
  - 9.3:Wrap-up
- 10:CI/CD Hosting
  - 10.1:Anti-Pattern: Neglecting the Needs of E2E Test Automation
  - 10.2:Anti-Pattern: Falling for flashy but useless features in cloud testing platforms but miss the big picture
  - 10.3:Anti-Pattern: Completely unaware of or blindly exlcuding on-premise Setup
  - 10.4:Wrap-up
- 11:Team Involvement
  - 11.1:Execute Individual Tests via the CT Server Web Interface
  - 11.2:Data Preparation for User Acceptance Testing
  - 11.3:Self-help Utilities that whole team can use on the CT Server
  - 11.4:Generate a Traceability Matrix
  - 11.5:Anti-Pattern: Non-Tech Team Members Not Using CI/CD Server
  - 11.6:Anti-Pattern: Only One Run Configuration
  - 11.7:Case Study: A bug-fixing cycle in a team with real CI/CD
  - 11.8:Real CI/CD Boots Customers’ Trust and Confidence in the team
- 12:Leadership
  - 12.1:Anti-Pattern: Failing to Recognize the Great Benefits of Real CI/CD
  - 12.2:Anti-Pattern: Lack Team-Wide Training on CI/CD Process
  - 12.3:Anti-Pattern: Developers delay fixing newly discovered defects by Continuous Testing
  - 12.4:Anti-Pattern: Stuck with One CI Vendor or One Person
  - 12.5:Anti-Pattern: Assuming Existing Staff Can Deliver Real CI/CD and E2E Automation with a New Product
  - 12.6:Anti-Pattern: Fixated with All-in-one CI/CD. Two Stage CI → CD Often Better
- Afterword
  - My CI/CD Formula
  - How many E2E Tests in CI/CD are enough?
  - My Continuous Testing Lab Setup
- Appendix I: Anti-Patterns List
- Appendix II: CI Steps
- Resources
  - Books
  - Tools
  - Blog
- References

The Leanpub 60 Day 100% Happiness Guarantee

Within 60 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.

Now, this is technically risky for us, since you'll have the book or course files either way. But we're so confident in our products and services, and in our authors and readers, that we're happy to offer a full money back guarantee for everything we sell.

You can only find out how good something is by trying it, and because of our 100% money back guarantee there's literally no risk to do so!

So, there's no reason not to click the Add to Cart button, is there?

See full terms...

Earn $8 on a $10 Purchase, and $16 on a $20 Purchase

We pay 80% royalties on purchases of $7.99 or more, and 80% royalties minus a 50 cent flat fee on purchases between $0.99 and $7.98. You earn $8 on a $10 sale, and $16 on a $20 sale. So, if we sell 5000 non-refunded copies of your book for $20, you'll earn $80,000.

(Yes, some authors have already earned much more than that on Leanpub.)

In fact, authors have earned over $14 million writing, publishing and selling on Leanpub.

Learn more about writing on Leanpub

Free Updates. DRM Free.

If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).

Most Leanpub books are available in PDF (for computers) and EPUB (for phones, tablets and Kindle). The formats that a book includes are shown at the top right corner of this page.

Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.

Write and Publish on Leanpub

You can use Leanpub to easily write, publish and sell in-progress and completed ebooks and online courses!

Leanpub is a powerful platform for serious authors, combining a simple, elegant writing and publishing workflow with a store focused on selling in-progress ebooks.

Leanpub is a magical typewriter for authors: just write in plain text, and to publish your ebook, just click a button. (Or, if you are producing your ebook your own way, you can even upload your own PDF and/or EPUB files and then publish with one click!) It really is that easy.

Learn more about writing on Leanpub

CI/CD Anti-Patterns

You pay

Author earns

...Or Buy With Credits!

About

Share this book

Categories

Feedback

Author

Contents

Get the free sample chapters

The Leanpub 60 Day 100% Happiness Guarantee

Earn $8 on a $10 Purchase, and $16 on a $20 Purchase

Free Updates. DRM Free.

Write and Publish on Leanpub