<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Software Quality on Romano Roth</title><link>https://romanoroth.com/en/tags/software-quality/</link><description>Recent content in Software Quality on Romano Roth</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Romano Roth</copyright><lastBuildDate>Mon, 20 May 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://romanoroth.com/en/tags/software-quality/index.xml" rel="self" type="application/rss+xml"/><item><title>App-Solutely Safe: How Banks Use Modern Software Development</title><link>https://romanoroth.com/en/blogs/app-solutely-safe-modern-banking-software/</link><pubDate>Mon, 20 May 2024 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/blogs/app-solutely-safe-modern-banking-software/</guid><description>&lt;p>Banking software must be secure, reliable, and trustworthy. But many banks still rely on traditional development methods that are slow, risky, and inefficient. In this video, I explore three modern software development practices that are fundamentally changing how banks build and deliver software: continuous deployment, test-driven development, and feature flags.&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><item><title>Satisfied end users thanks to DevOps</title><link>https://romanoroth.com/en/blogs/satisfied-end-users-thanks-to-devops/</link><pubDate>Sun, 26 Jul 2020 21:07:39 +0000</pubDate><guid>https://romanoroth.com/en/blogs/satisfied-end-users-thanks-to-devops/</guid><description>&lt;p>Companies today are confronted with the challenge of enhancing efficiency while lowering costs. Changes to products often take much too long to reach end customers on the market. A consistent DevOps approach can aid this process.&lt;/p></description></item></channel></rss>