Skip to main content

Search...

Test Automation

Test automation pays off where it delivers fast, reliable feedback. Left to grow without a strategy, it gets expensive. What is worth automating in the first place is covered in the test automation guide. This hub picks up from there and collects material from practice.

The podcast episodes and articles cover automation strategy, test design and maintainability, choosing and switching tools, CI pipelines, legacy and embedded systems, and AI and agents in automation. The tool question rarely comes first: automation holds up once goals, architecture, and the team fit together.

Foundations

Articles

Many Small Loops: Feedback That Hardens Agent Output
Many Small Loops: Feedback That Hardens Agent Output

Many Small Loops: Feedback That Hardens Agent Output

Agentic QA holds up through many small feedback loops in the process instead of one big test gate at the end. Three ideas for where a team can start.

AI: Are We Solving the Problems That Matter?
AI: Are We Solving the Problems That Matter?

AI: Are We Solving the Problems That Matter?

AI generates movies and apps while teams drown in legacy code. Why we should use AI for the problems that actually hurt, not for demos.

Testing AI and Testing with AI: Rethinking Quality
Testing AI and Testing with AI: Rethinking Quality

Testing AI and Testing with AI: Rethinking Quality

AI in software testing helps with test cases, test data and error analysis. Testing AI systems means rethinking quality criteria such as data quality.

AI for Testers: Why Good Testers Won't Be Replaced
AI for Testers: Why Good Testers Won't Be Replaced

AI for Testers: Why Good Testers Won't Be Replaced

AI for testers helps with analysis, test cases, bug hunting and test data. Weak testers may lose out, good ones build AI into the way they work.

Time Wasters in Testing: Automate, Learn and Delegate
Time Wasters in Testing: Automate, Learn and Delegate

Time Wasters in Testing: Automate, Learn and Delegate

Time wasters in testing include copying test data by hand and fiddling with Word formatting. Automating, learning tools and delegating free up hours.

Testing Tools: Why Candidates Drop Off the Shortlist
Testing Tools: Why Candidates Drop Off the Shortlist

Testing Tools: Why Candidates Drop Off the Shortlist

Testing tools drop off a shortlist for simple reasons: no hands-on evaluation, unstable runs, poor process fit, pushy sales or clunky usability.

Podcast Episodes

DAST Testing with ZAP: Learn First, Then Attack
DAST Testing with ZAP: Learn First, Then Attack

DAST Testing with ZAP: Learn First, Then Attack

DAST testing with ZAP rides on existing regression tests: the proxy records the traffic, then attacks the app. DORA wants that run before each release.

Hardware-in-the-Loop Testing: Kernels on Real CPUs
Hardware-in-the-Loop Testing: Kernels on Real CPUs

Hardware-in-the-Loop Testing: Kernels on Real CPUs

A kernel has to run on every CPU generation, so hardware-in-the-loop testing puts it on real devices. Developers and CI reserve clean machines.

You Need a Test Automation Strategy Before AI
You Need a Test Automation Strategy Before AI

You Need a Test Automation Strategy Before AI

More test automation does not mean better quality. Why flaky AI tests, missing strategy, and the wrong roles quietly hollow out your test suite.

AI-Generated Code: Quality Assurance Must Keep Pace
AI-Generated Code: Quality Assurance Must Keep Pace

AI-Generated Code: Quality Assurance Must Keep Pace

More AI-generated code means more defects, and only about 30% of AI review comments help. Static analysis, test selection and reviews must scale too.

TACON in Leipzig: Case Studies on Test Automation
TACON in Leipzig: Case Studies on Test Automation

TACON in Leipzig: Case Studies on Test Automation

TACON in Leipzig gathers around 130 practitioners for two days of test automation case studies from user companies, last held in September 2026.

Pekka Klärck: Why Robot Framework Has a Generic Core
Pekka Klärck: Why Robot Framework Has a Generic Core

Pekka Klärck: Why Robot Framework Has a Generic Core

Pekka Klärck began Robot Framework as his master's thesis in 2004. Over 80 companies now back its foundation, and its generic core fits mixed stacks.

Test Automation Strategy: Start with the Problem
Test Automation Strategy: Start with the Problem

Test Automation Strategy: Start with the Problem

A test automation strategy starts with the problem, not the tool. Map current and target state on the test pyramid; the gap is your scope of work.

End-to-End Testing Framework: Start with Requirements
End-to-End Testing Framework: Start with Requirements

End-to-End Testing Framework: Start with Requirements

Choosing an end-to-end testing framework starts with needs like Safari support, speed and mobile emulation. Cypress, Playwright, Nightwatch compared.

Cypress to Playwright: Migrate Critical Paths First
Cypress to Playwright: Migrate Critical Paths First

Cypress to Playwright: Migrate Critical Paths First

Switching test automation frameworks mid-product is messy, yet a Cypress to Playwright move works. Pricing forced it, AI translated the tests.

System Knowledge Catches What AI Misses in Grown Code
System Knowledge Catches What AI Misses in Grown Code

System Knowledge Catches What AI Misses in Grown Code

For software testing, AI pays off in test data and document analysis. In grown systems, testers' system and domain knowledge still catch side effects.

Quality as an Attitude: Making Testing a Team Habit
Quality as an Attitude: Making Testing a Team Habit

Quality as an Attitude: Making Testing a Team Habit

Quality as an attitude beats test case checklists. Good testing needs solid methods, automation and trust in the people who vouch for the results.

Playwright vs Cypress vs WebdriverIO: A Clear Verdict
Playwright vs Cypress vs WebdriverIO: A Clear Verdict

Playwright vs Cypress vs WebdriverIO: A Clear Verdict

Playwright vs Cypress vs WebdriverIO on four criteria: why Playwright wins new projects, where WebdriverIO trails, and when a switch isn't worth it.

Migrating from Cypress to Playwright: The Real Effort
Migrating from Cypress to Playwright: The Real Effort

Migrating from Cypress to Playwright: The Real Effort

Migrating from Cypress to Playwright took a team over a year alongside daily QA. The main hurdles: session handling, request interception, legacy tests.

CI/CD Pipelines in Embedded C: Tests as a Safety Net
CI/CD Pipelines in Embedded C: Tests as a Safety Net

CI/CD Pipelines in Embedded C: Tests as a Safety Net

CI/CD pipelines for embedded C at Marquardt run on CMake, Google Test and generated mocks. Every bug fix starts with a test that reproduces the bug.

Quality in Software Development Is Now a Team Task
Quality in Software Development Is Now a Team Task

Quality in Software Development Is Now a Team Task

Quality in software development moved from a late test phase to a team task. Now AI forces the question many teams never answered: what is quality?

Form Testing: Model-Based Test Data via SMT Solver
Form Testing: Model-Based Test Data via SMT Solver

Form Testing: Model-Based Test Data via SMT Solver

Form testing for over 255 tax form variants across 16 states: an SMT solver derives valid test data from the model and exposes contradictory rules.

Choosing an E2E Testing Framework: Requirements First
Choosing an E2E Testing Framework: Requirements First

Choosing an E2E Testing Framework: Requirements First

Choosing an E2E testing framework starts with your own requirements, such as Safari support or speed. Why Playwright led a comparison of five tools.

Exploration and AI: Human Context Can't Be Replaced
Exploration and AI: Human Context Can't Be Replaced

Exploration and AI: Human Context Can't Be Replaced

AI speeds up routine work, but exploration needs human context it lacks. Quality stays hard to sell, so testers should pair with developers and network.

BDD Scenarios: Gherkin Written Afterwards Is Not BDD
BDD Scenarios: Gherkin Written Afterwards Is Not BDD

BDD Scenarios: Gherkin Written Afterwards Is Not BDD

BDD scenarios look simple, but Gherkin without real team conversations costs more than it brings. Why five to seven steps keep a scenario readable.

Selenium Automation Testing: A Browser Tool First
Selenium Automation Testing: A Browser Tool First

Selenium Automation Testing: A Browser Tool First

In Selenium automation testing, Selenium only drives the browser. Good selectors, page objects and the vendor drivers in Selenium 4 keep tests stable.

AI Test Automation: Machine Learning Finds Root Causes
AI Test Automation: Machine Learning Finds Root Causes

AI Test Automation: Machine Learning Finds Root Causes

AI test automation turns 200 failed tests into seven real causes. Machine learning groups failures by root cause and frees testers to write new tests.