erkundetest

erkundentest is a software testing approach in which test design and test execution occur simultaneously, rather than following predefined test scripts. The method emphasizes exploration guided by a purpose or charter, with testers learning about the system as they test and adjusting their focus based on findings.

Origin and context: The term derives from the German words for exploration and test, and in practice erkundentest aligns closely with what is commonly called exploratory testing in English. It gained prominence in agile and fast-paced development environments, where rapid feedback is valued and requirements may evolve during a project. The approach is often described in contrast to scripted or scripted-execution testing, where all steps are predetermined in advance.

Methodology and process: Typical practice involves time-boxed testing sessions, often accompanied by a test charter that defines goals, scope, and risk areas for each session. During the session, testers explore the product, execute test ideas, observe behavior, and take notes or capture screenshots and logs. After a session, teams debrief to discuss what was learned, log defects, and decide on next steps. Tools and techniques from session-based testing and heuristic methods may be used to structure exploration and improve coverage.

Characteristics, benefits, and limitations: Erkundentest prioritizes learning, adaptability, and early defect discovery. It can uncover issues that scripted tests miss and quickly adapt to changing requirements. Limitations include potential variability in coverage and reproducibility, dependence on tester skill, and challenges in documenting exactly what was tested for audit or compliance purposes.

Applications and relation to other testing: It is frequently used in agile, DevOps, and continuous testing contexts as a complementary approach to scripted tests, risk-based testing, and formal verification. Artifacts commonly include test charters, session notes, and defect reports.