Architecting for testing and continuous delivery

Most organizations want faster, more-incremental delivery of their applications, but fragile tests and complex continuous delivery pipelines often make this difficult. What if the problem isnt the pipeline but the architecture of the system? Ken Mugrage details the architectural choices that will help you enable stable tests and faster pipelines.

When creating a continuous delivery pipeline, many strive only to automate what they’re already building instead of taking another look at old assumptions. When your goal is to deploy once a quarter, you may choose an architecture with tightly coupled services or components. If your goal is to be able to deploy on demand, this same architecture may be getting in your way. Join Ken Mugrage to discover how changing the architecture of your system to enable faster delivery can be more beneficial and stable than trying to automate deployment for systems that weren’t designed for it. Closely related to the ability to deploy the application on demand is the ability to make sure it’s doing what we expect it to every time. Acceptance tests, especially when browser based, are often considered so fragile that many organizations have simply stopped doing them. Ken shows you how to make architectural decisions that will make it easier to write and maintain quality-acceptance tests.