<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>qa on Tom Hickerson's Site</title><link>https://tomhickerson.com/en/tags/qa/</link><description>Recent content in qa on Tom Hickerson's Site</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>Copyright 2023-2026</copyright><lastBuildDate>Sun, 22 Apr 2018 00:00:00 +0000</lastBuildDate><atom:link href="https://tomhickerson.com/en/tags/qa/index.xml" rel="self" type="application/rss+xml"/><item><title>Software Testing Anti-patterns · Codepipes Blog</title><link>https://tomhickerson.com/en/archives/en/2018/2018-04-22-software-testing-anti-patterns--codepipes-blog/</link><pubDate>Sun, 22 Apr 2018 00:00:00 +0000</pubDate><guid>https://tomhickerson.com/en/archives/en/2018/2018-04-22-software-testing-anti-patterns--codepipes-blog/</guid><description>&amp;ldquo;There are several articles out there that talk about testing anti-patterns in the software development process. Most of them however deal with the low level details of the programming code, and almost always they focus on a specific technology or programming language.
In this article I wanted to take a step back and catalog some high-level testing anti-patterns that are technology agnostic. Hopefully you will recognize some of these patterns regardless of your favorite programming language.</description></item></channel></rss>