<?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 Mathias WOLFF</title><link>https://www.blog-des-telecoms.com/tags/testing/</link><description>Recent content in Testing on Mathias WOLFF</description><generator>Hugo</generator><language>fr-FR</language><copyright>&lt;a href="https://www.blog-des-telecoms.com"&gt;Blog des télécoms&lt;/a&gt; © 2009 - 2026 by &lt;a href="https://www.linkedin.com/in/mathias-wolff-47a7941/"&gt;Mathias WOLFF&lt;/a&gt; is licensed under &lt;a href="https://creativecommons.org/licenses/by-nc-sa/4.0/"&gt;CC BY-NC-SA 4.0&lt;/a&gt;&lt;img src="https://mirrors.creativecommons.org/presskit/icons/cc.svg" style="max-width: 1em;max-height:1em;margin-left: .2em;"&gt;&lt;img src="https://mirrors.creativecommons.org/presskit/icons/by.svg" style="max-width: 1em;max-height:1em;margin-left: .2em;"&gt;&lt;img src="https://mirrors.creativecommons.org/presskit/icons/nc.svg" style="max-width: 1em;max-height:1em;margin-left: .2em;"&gt;&lt;img src="https://mirrors.creativecommons.org/presskit/icons/sa.svg" style="max-width: 1em;max-height:1em;margin-left: .2em;"&gt;</copyright><lastBuildDate>Sun, 10 May 2026 17:39:31 +0200</lastBuildDate><atom:link href="https://www.blog-des-telecoms.com/tags/testing/index.xml" rel="self" type="application/rss+xml"/><item><title>Étendre pi-secured-setup : écrire ses propres Guards et Scanners</title><link>https://www.blog-des-telecoms.com/blog/etendre-pi-secured-setup-ecrire-guards-scanners/</link><pubDate>Sat, 09 May 2026 10:00:00 +0200</pubDate><guid>https://www.blog-des-telecoms.com/blog/etendre-pi-secured-setup-ecrire-guards-scanners/</guid><description>&lt;p&gt;Dans l&amp;rsquo;article précédent, j&amp;rsquo;ai présenté &lt;strong&gt;pi-secured-setup&lt;/strong&gt; — une extension pi qui ajoute des Guards, des Scanners et un audit trail à votre agent de code IA. Elle est livrée avec des defaults pertinents : application de frontière, globbing de chemins protégés, classification de commandes bash, rédaction de secrets, vérification de skills.&lt;/p&gt;
&lt;p&gt;Mais chaque projet a des risques uniques. Un shop Terraform n&amp;rsquo;a pas les mêmes règles qu&amp;rsquo;un monorepo Node.js. Une équipe avec des exigences de conformité strictes n&amp;rsquo;a pas la même granularité d&amp;rsquo;audit qu&amp;rsquo;un développeur solo.&lt;/p&gt;</description></item><item><title>Extending pi-secured-setup: Writing Custom Guards and Scanners</title><link>https://www.blog-des-telecoms.com/en/blog/extending-pi-secured-setup-writing-custom-guards-scanners/</link><pubDate>Sat, 09 May 2026 10:00:00 +0200</pubDate><guid>https://www.blog-des-telecoms.com/en/blog/extending-pi-secured-setup-writing-custom-guards-scanners/</guid><description>&lt;p&gt;In the previous article, I introduced &lt;strong&gt;pi-secured-setup&lt;/strong&gt; — a pi extension that adds Guards, Scanners, and an audit trail to your AI coding agent. It ships with sensible defaults: boundary enforcement, protected path globbing, bash command classification, secret redaction, skill verification.&lt;/p&gt;
&lt;p&gt;But every project has unique risks. A Terraform shop needs different rules than a Node.js monorepo. A team with strict compliance requirements needs different audit granularity than a solo developer.&lt;/p&gt;</description></item></channel></rss>