<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Quality Assurance on Romano Roth</title><link>https://romanoroth.com/en/tags/quality-assurance/</link><description>Recent content in Quality Assurance on Romano Roth</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Romano Roth</copyright><lastBuildDate>Mon, 28 Aug 2023 19:15:31 +0000</lastBuildDate><atom:link href="https://romanoroth.com/en/tags/quality-assurance/index.xml" rel="self" type="application/rss+xml"/><item><title>DevOps in an Embedded World: Challenges for Embedded and IoT Devices</title><link>https://romanoroth.com/en/blogs/devops-in-an-embedded-world-challenges-for-embedded-and-iot-devices/</link><pubDate>Mon, 28 Aug 2023 19:15:31 +0000</pubDate><guid>https://romanoroth.com/en/blogs/devops-in-an-embedded-world-challenges-for-embedded-and-iot-devices/</guid><description>&lt;p>Embedded and IoT devices are becoming increasingly popular in today&amp;rsquo;s world. These devices are used in various industries, such as healthcare, manufacturing, consumer goods and home automation. Ensuring the quality of these devices is crucial to ensure their reliability, safety, and functionality. But how to do that?&lt;/p></description></item><item><title>Back to the future of software development</title><link>https://romanoroth.com/en/blogs/back-to-the-future-of-software-development/</link><pubDate>Tue, 03 Jan 2023 23:00:00 +0000</pubDate><guid>https://romanoroth.com/en/blogs/back-to-the-future-of-software-development/</guid><description>&lt;p>By &lt;a href="https://www.linkedin.com/in/piawiedermayer" target="_blank" rel="noreferrer">Pia Wiedermayer&lt;/a> and &lt;a href="https://www.linkedin.com/in/romanoroth/" target="_blank" rel="noreferrer">Romano Roth&lt;/a>&lt;/p>
&lt;p>In many organizations and projects, software development involves numerous employees and machines performing tasks separately. This approach results in problems. Here&amp;rsquo;s how going back to the original way of developing software and building an organic digital factory can help.&lt;/p></description></item><item><title>What is Test End to End? | SAFe® DevOps Health Radar</title><link>https://romanoroth.com/en/blogs/what-is-test-end-to-end-safe-devops-health-radar/</link><pubDate>Sun, 19 Sep 2021 18:26:16 +0000</pubDate><guid>https://romanoroth.com/en/blogs/what-is-test-end-to-end-safe-devops-health-radar/</guid><description>&lt;p>In this article, I explain what Test End to End means within the SAFe® DevOps Health Radar and why it is essential for delivering high-quality software. Please note that everything discussed here is under the license of Scaled Agile, and that the Scaled Agile Framework is a framework to be used as a toolbox. Take out what fits your needs or what solves your problem.&lt;/p></description></item><item><title>Test automation with Behavior-Driven Development (BDD)</title><link>https://romanoroth.com/en/blogs/test-automation-with-behavior-driven-development-bdd/</link><pubDate>Sat, 20 Feb 2021 20:44:14 +0000</pubDate><guid>https://romanoroth.com/en/blogs/test-automation-with-behavior-driven-development-bdd/</guid><description>&lt;p>Automating tests is a complex and demanding task. The iterative approach in the development process also means that the automated tests have to be continuously adapted. Behaviour-driven development (BDD) can be used to simplify and speed up test automation.&lt;/p></description></item><item><title>What is the difference between traditional testing and agile testing?</title><link>https://romanoroth.com/en/blogs/what-is-the-difference-between-traditional-testing-and-agile-testing/</link><pubDate>Wed, 27 Jan 2021 21:32:09 +0000</pubDate><guid>https://romanoroth.com/en/blogs/what-is-the-difference-between-traditional-testing-and-agile-testing/</guid><description>&lt;p>&lt;figure>&lt;img
 class="my-0 rounded-md"
 loading="lazy"
 decoding="async"
 fetchpriority="auto"
 alt=""
 width="1280"
 height="720"
 src="https://romanoroth.com/images/blog/what-is-the-difference-between-traditional-testing-and-agile-testing-inline-1_hu_b37e149e5374da49.jpg"
 srcset="https://romanoroth.com/images/blog/what-is-the-difference-between-traditional-testing-and-agile-testing-inline-1_hu_b37e149e5374da49.jpg 800w, https://romanoroth.com/images/blog/what-is-the-difference-between-traditional-testing-and-agile-testing-inline-1.jpg 1280w"
 sizes="(min-width: 768px) 50vw, 65vw"
 data-zoom-src="https://romanoroth.com/images/blog/what-is-the-difference-between-traditional-testing-and-agile-testing-inline-1.jpg">&lt;/figure>
&lt;/p>
&lt;p>When we are talking about traditional testing, we are talking about the V-model which is used in waterfall projects. We do requirement engineering, we write down features for our software, then we break them down and then write stories which are then given to the developer to implement this story. The developer then codifies this and then writes unite tests and integration tests.&lt;/p></description></item></channel></rss>