Powered by OpenAIRE graph
Found an issue? Give us feedback
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/ ZENODOarrow_drop_down
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/
ZENODO
Report
Data sources: ZENODO
addClaim

AUTOMATION BEFORE AUTOMATION (ABA): An Intermediate Phase in Modern Software Testing

Authors: Liudas, Jankauskas;

AUTOMATION BEFORE AUTOMATION (ABA): An Intermediate Phase in Modern Software Testing

Abstract

Automation Before Automation (ABA) is introduced as a distinct intermediate phase in modern software testing, positioned between manual exploration and traditional regression automation. This whitepaper defines ABA as the automated generation and execution of exploratory, validation, robustness, and protocol‑level tests performed before long‑term automated test suites are created. It explains why ABA is increasingly relevant in teams using fuzzing, mutation tools, schema‑driven generators, and AI‑assisted testing, outlines its key characteristics, differentiates it from conventional automation, and presents a real‑world case study demonstrating its practical value for rapid defect discovery.

Powered by OpenAIRE graph
Found an issue? Give us feedback