<?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>pytest Archives - The Golioth Developer Blog</title>
	<atom:link href="https://blog.golioth.io/tag/pytest/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.golioth.io/tag/pytest/</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>pytest Archives - The Golioth Developer Blog</title>
	<link>https://blog.golioth.io/tag/pytest/</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>How to Publish a Summary to GitHub Actions for Zephyr/Pytest runs</title>
		<link>https://blog.golioth.io/how-to-publish-a-summary-to-github-actions-for-zephyr-pytest-runs/</link>
		
		<dc:creator><![CDATA[Mike Szczys]]></dc:creator>
		<pubDate>Thu, 24 Oct 2024 14:47:24 +0000</pubDate>
				<category><![CDATA[Zephyr]]></category>
		<category><![CDATA[CI]]></category>
		<category><![CDATA[continuous integration]]></category>
		<category><![CDATA[hardware-in-the-loop]]></category>
		<category><![CDATA[HIL]]></category>
		<category><![CDATA[Junit XML]]></category>
		<category><![CDATA[pytest]]></category>
		<category><![CDATA[summary]]></category>
		<guid isPermaLink="false">https://blog.golioth.io/?p=8148</guid>

					<description><![CDATA[<p>Both Pytest and Twister (Zephyr) can already product JUnit XML formatted test summaries. You can use these files to publish a very handy summary table for all of your continuous integration (CI) tests on GitHub.</p>
<p>The post <a href="https://blog.golioth.io/how-to-publish-a-summary-to-github-actions-for-zephyr-pytest-runs/">How to Publish a Summary to GitHub Actions for Zephyr/Pytest runs</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>
	</channel>
</rss>
