An informal and intuitive type of Software testing that is performed without a plan or documentation.
- Methodologien: Kunden & Marketing, Ergonomie, Produktdesign
Ad-Hoc Testing

Ad-Hoc Testing
- Agile Methodik, Kontinuierliche Verbesserung, Prozessverbesserung, Qualitätssicherung, Qualitätskontrolle, Qualitätsmanagement, Risikomanagement, Software-Prüfung, Validierung
Zielsetzung:
Wie es verwendet wird:
- Testers use their knowledge of the application to find bugs by randomly testing different parts of the system. It is often performed when there is limited time for formal testing.
Vorteile
- Can uncover bugs that are missed by formal testing, requires minimal preparation, and can be performed at any stage of the development cycle.
Nachteile
- Bugs found can be difficult to reproduce, the effectiveness depends heavily on the tester's skill, and it provides no formal documentation.
Kategorien:
- Projektmanagement, Qualität
Am besten geeignet für:
- Finding defects quickly when there is limited time for structured testing.
Ad-Hoc Testing is often utilized in industries such as software development, mobile applications, and consumer electronics, where rapid iterations and continuous feedback are paramount. This method suits project phases characterized by time constraints, such as during the final stages of development or when preparing for product launches, where there may be insufficient time for comprehensive formal testing. Participants in this approach typically include developers, testers, and sometimes even end-users who possess firsthand knowledge of the system. Their understanding of the application allows them to leverage intuition and experience in identifying potential issues that structured tests might overlook. This testing methodology is particularly advantageous in agile environments, where iterative cycles require quick adjustments based on user feedback. Common applications range from validation of new features to regression testing during ongoing updates. Given its adaptability, Ad-Hoc Testing can also serve as a valuable debugging strategy for exploratory testing sessions, where testers investigate the application without predefined scripts, enabling them to discover unexpected defects that might occur under real-world usage scenarios. While it may lack the thoroughness of formal testing procedures, its ability to deliver immediate results makes it an appealing choice when deadlines loom and teams seek to mitigate risks quickly.
Die wichtigsten Schritte dieser Methodik
- Identify key areas of the application that require testing.
- Randomly select functions or features to explore within the identified areas.
- Execute tests in an exploratory manner, varying inputs and interactions.
- Document unexpected behavior, errors, or inconsistencies encountered.
- Iterate through different paths and scenarios to uncover additional issues.
- Use experience and intuition to guide the testing focus during execution.
- Engage with different platforms and configurations if applicable.
Profi-Tipps
- Incorporate exploratory testing techniques to focus on high-risk areas based on your domain knowledge and application logic.
- Utilize past bug reports and trends to inform ad-hoc testing sessions, targeting previously problematic features or components.
- Encourage collaboration among testers to share findings immediately, leveraging diverse viewpoints for deeper exploration.
Verschiedene Methoden lesen und vergleichen, Wir empfehlen die
> Umfassendes Methoden-Repository <
zusammen mit den über 400 anderen Methoden.
Ihre Kommentare zu dieser Methodik oder zusätzliche Informationen sind willkommen auf der Kommentarbereich unten ↓ , sowie alle ingenieursbezogenen Ideen oder Links.
Verwandte Artikel
Management der Produktionsabläufe (MOM)
Fertigungsausführungssystem (MES)
Produktionslenkungsplan
Manuelle Prüfung
Bewertungsbögen für die manuelle Handhabung (MAC)
ManTRA (Instrument zur Risikobewertung manueller Tätigkeiten)