anchor.diff:  
   <figure>
     <img src="/assets/images/blog/add-performance-testing/soak-test.jpg"
  -    alt="Soak Testing" title="Soak Testing">
  +    alt="Parallel Pipeline for Soak Testing" title="Soak Testing">
   </figure>
   
   ## Run them on every build
  
positive.code: 
  <figure>
    <img src="/assets/images/blog/add-performance-testing/stress-test.jpg"
      alt="Load Testing" title="Load Testing">
  </figure>
  
  ### Soak testing
  
negative.code: author: Ken Mugrage
  excerpt: "Performance testing as part of a Continuous Delivery (CD) pipeline is rare. The intent of this article is to provide you with some pointers on the types of testing you can do on a regular basis, and to give some strategies for implementation."
  title_tag_of_header: "Add performance testing to your Continuous Delivery pipeline | GoCD Blog"
  meta_description: "Types of performance testing you can do on a regular basis, and strategies for implementation."
  meta_keywords: "performance testing, delivery pipelines, deployment pipelines, continuous delivery, types of performance testing, load testing, spike testing, stress testing, soak testing, memory leaks, software testing"
  summary_image: "/assets/images/blog/add-performance-testing/add-performance-testing-to-your-continuous-delivery-pipeline.jpg"
  tags: It's Not CD if You Can't Deploy Right Now
  ---
  