<?xml version='1.0' encoding='UTF-8'?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <id>https://www.luker.dev/</id>
    <title>Luker.dev Feed</title>
    <updated>2026-07-29T00:00:00+00:00</updated>
    <author>
        <name>Ryan Luker</name>
    </author>
    <link href="https://www.luker.dev/" rel="alternate"/>
    <link href="https://www.luker.dev/feed.xml" rel="self"/>
    <generator version="1.0.0">human</generator>
    <subtitle>A website that contains posts around my projects, thinkings and experiences.</subtitle>
    <entry>
        <id>https://www.luker.dev/blog/unit-testing-vscode-extensions/</id>
        <title>How to unit test vscode extensions with basic mocks</title>
        <updated>2026-07-28T00:00:00+00:00</updated>
        <author>
            <name>ryanluker</name>
        </author>
        <link href="https://www.luker.dev/blog/unit-testing-vscode-extensions/" rel="alternate"/>
        <summary>Manual import mocking with node's module caching system and basic nodejs assertions.</summary>
        <published>2019-09-30T07:00:00+00:00</published>
    </entry>
    <entry>
        <id>https://www.luker.dev/blog/testing-vscode-extensions/</id>
        <title>Testing Visual Studio Code extensions</title>
        <updated>2026-07-29T00:00:00+00:00</updated>
        <author>
            <name>ryanluker</name>
        </author>
        <link href="https://www.luker.dev/blog/testing-vscode-extensions/" rel="alternate"/>
        <summary>Real testing of vscode extensions and how to keep code quality high.</summary>
        <published>2018-06-27T07:00:00+00:00</published>
    </entry>
</feed>
