<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Automated Testing Archives - The Golioth Developer Blog</title>
	<atom:link href="https://blog.golioth.io/tag/automated-testing/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.golioth.io/tag/automated-testing/</link>
	<description>Golioth, Zephyr, and IoT Development News and How Tos</description>
	<lastBuildDate>Tue, 04 Mar 2025 21:12:09 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://blog.golioth.io/wp-content/uploads/2023/09/cropped-Golioth_Symbol_Coral_RGB-1-32x32.png</url>
	<title>Automated Testing Archives - The Golioth Developer Blog</title>
	<link>https://blog.golioth.io/tag/automated-testing/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>How we use Allure Report to understand Continuous Integration Tests</title>
		<link>https://blog.golioth.io/how-we-use-allure-report-to-understand-continuous-integration-tests/</link>
		
		<dc:creator><![CDATA[Mike Szczys]]></dc:creator>
		<pubDate>Thu, 12 Dec 2024 15:47:14 +0000</pubDate>
				<category><![CDATA[Tools]]></category>
		<category><![CDATA[Allure Report]]></category>
		<category><![CDATA[Automated Testing]]></category>
		<category><![CDATA[CI]]></category>
		<category><![CDATA[HIL]]></category>
		<category><![CDATA[pytest]]></category>
		<guid isPermaLink="false">https://blog.golioth.io/?p=8339</guid>

					<description><![CDATA[<p>Allure Report is an open source tool to better understand testing outcomes. Golioth runs over 500 Hardware in the Loop tests for each pull request. Here's how we use Allure Report to make sense of it all.</p>
<p>The post <a href="https://blog.golioth.io/how-we-use-allure-report-to-understand-continuous-integration-tests/">How we use Allure Report to understand Continuous Integration Tests</a> appeared first on <a href="https://blog.golioth.io">The Golioth Developer Blog</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>Automated hardware testing using pytest</title>
		<link>https://blog.golioth.io/automated-hardware-testing-using-pytest/</link>
		
		<dc:creator><![CDATA[Mike Szczys]]></dc:creator>
		<pubDate>Thu, 04 Apr 2024 13:58:29 +0000</pubDate>
				<category><![CDATA[Tools]]></category>
		<category><![CDATA[Automated Testing]]></category>
		<category><![CDATA[Firmware]]></category>
		<category><![CDATA[hardware-in-the-loop]]></category>
		<category><![CDATA[HIL]]></category>
		<category><![CDATA[pytest]]></category>
		<guid isPermaLink="false">https://goliothblogdev.wpenginepowered.com/?p=6721</guid>

					<description><![CDATA[<p>Pytest is a framework for testing and we use it for our Firmware SDK. This post reviews setting up fixtures that connect embedded projects to pytest.</p>
<p>The post <a href="https://blog.golioth.io/automated-hardware-testing-using-pytest/">Automated hardware testing using pytest</a> appeared first on <a href="https://blog.golioth.io">The Golioth Developer Blog</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>How Golioth uses Hardware-in-the-Loop (HIL) Testing: Part 2</title>
		<link>https://blog.golioth.io/golioth-hil-testing-part2/</link>
		
		<dc:creator><![CDATA[Nick Miller]]></dc:creator>
		<pubDate>Thu, 18 Aug 2022 14:43:02 +0000</pubDate>
				<category><![CDATA[Device Management]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[Automated Testing]]></category>
		<category><![CDATA[CI/CD]]></category>
		<category><![CDATA[ESP-IDF]]></category>
		<category><![CDATA[GitHub Actions]]></category>
		<category><![CDATA[HIL]]></category>
		<category><![CDATA[Self-Hosted Runner]]></category>
		<category><![CDATA[zephyr]]></category>
		<guid isPermaLink="false">https://goliothblogdev.wpenginepowered.com/?p=2789</guid>

					<description><![CDATA[<p>Immediately test code changes on real hardware. In this hands-on post, Nick Miller discusses how to set up your own Hardware-In-The-Loop testing using GitHub Self-Hosted Runners on a Raspberry Pi with development boards plugged in. </p>
<p>The post <a href="https://blog.golioth.io/golioth-hil-testing-part2/">How Golioth uses Hardware-in-the-Loop (HIL) Testing: Part 2</a> appeared first on <a href="https://blog.golioth.io">The Golioth Developer Blog</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>How Golioth uses Hardware-in-the-Loop (HIL) Testing: Part 1</title>
		<link>https://blog.golioth.io/golioth-hil-testing-part1/</link>
		
		<dc:creator><![CDATA[Nick Miller]]></dc:creator>
		<pubDate>Tue, 09 Aug 2022 14:55:53 +0000</pubDate>
				<category><![CDATA[Device Management]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[Automated Testing]]></category>
		<category><![CDATA[CI/CD]]></category>
		<category><![CDATA[ESP-IDF]]></category>
		<category><![CDATA[GitHub Actions]]></category>
		<category><![CDATA[HIL]]></category>
		<category><![CDATA[Self-Hosted Runner]]></category>
		<category><![CDATA[zephyr]]></category>
		<guid isPermaLink="false">https://goliothblogdev.wpenginepowered.com/?p=2701</guid>

					<description><![CDATA[<p>Explain what HIL testing is, and why we use it at Golioth to continuously verify the firmware for our Zephyr and ESP-IDF SDKs.</p>
<p>The post <a href="https://blog.golioth.io/golioth-hil-testing-part1/">How Golioth uses Hardware-in-the-Loop (HIL) Testing: Part 1</a> appeared first on <a href="https://blog.golioth.io">The Golioth Developer Blog</a>.</p>
]]></description>
		
		
		
			</item>
	</channel>
</rss>
