<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Testing on CSP Guide</title>
    <link>https://csp-guide.com/tags/testing/</link>
    <description>Recent content in Testing on CSP Guide</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 27 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://csp-guide.com/tags/testing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to Test CSP in CI/CD Pipelines: Pros, Cons, and Setup</title>
      <link>https://csp-guide.com/posts/how-to-test-csp-in-ci-cd-pipelines/</link>
      <pubDate>Sat, 27 Jun 2026 00:00:00 +0000</pubDate>
      
      <guid>https://csp-guide.com/posts/how-to-test-csp-in-ci-cd-pipelines/</guid>
      
      <description>&lt;p&gt;Content Security Policy breaks in boring, expensive ways.&lt;/p&gt;
&lt;p&gt;A marketing script gets added on Friday. A framework upgrade changes how nonces are rendered. A new inline style sneaks into production. Nobody notices until checkout metrics dip or the console fills up with CSP violations. If you only test CSP manually in the browser, you’re already behind.&lt;/p&gt;
&lt;p&gt;The good news: CSP fits nicely into CI/CD if you treat it like code instead of a one-time header tweak.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
