<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>VSCode Dev on Andrew Walsh</title><link>http://awalsh128.com/tags/vscode-dev/</link><description>Recent content in VSCode Dev on Andrew Walsh</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><copyright>© 2026 Andrew Walsh</copyright><lastBuildDate>Sat, 01 Aug 2026 16:28:39 -0700</lastBuildDate><atom:link href="http://awalsh128.com/tags/vscode-dev/feed.xml" rel="self" type="application/rss+xml"/><item><title>Testing framework for VSCode extension development</title><link>http://awalsh128.com/vscode-ext-dev-and-testing/</link><pubDate>Sat, 01 Aug 2026 00:00:00 -0700</pubDate><guid>http://awalsh128.com/vscode-ext-dev-and-testing/</guid><description>&lt;p&gt;I created a VSCode extension recently (&lt;a href="https://github.com/awalsh128/vscode-keep-sorted" target="_blank" rel="noreferrer"&gt;awalsh128/vscode-keep-sorted&lt;/a&gt;)&#10;and learned a lot of lessons trying to set up the test environment. What I wanted was:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Tests that run against a real VSCode instance, not mocks.&lt;/li&gt;&#10;&lt;li&gt;An immutable test workspace, so every test starts from the same files.&lt;/li&gt;&#10;&lt;li&gt;A log file per test, so I can see what the extension did when a test fails.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&#10;&lt;h2 class="relative group"&gt;Principles&#10; &lt;div id="principles" class="anchor"&gt;&lt;/div&gt;&#10; &#10; &lt;span&#10; class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;&#10; &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#principles" aria-label="Anchor"&gt;#&lt;/a&gt;&#10; &lt;/span&gt;&#10; &#10;&lt;/h2&gt;&#10;&lt;p&gt;Some things I learned the hard way about testing extensions.&lt;/p&gt;</description></item></channel></rss>