Debugging pattern
From Quire, the open reference·Set of steps to correct a software bug·1 min read
A debugging pattern describes a generic set of steps to rectify or correct a bug within a software system. It is a solution to a recurring problem that is related to a particular bug or type of bug in a specific context.
A bug pattern is a particular type of pattern. The original concept of a pattern was introduced by the architect Christopher Alexander as a design pattern.
Some examples of debugging patterns include:
- Eliminate noise bug pattern – Isolate and expose a particular bug by eliminating all other noise in the system. This enables you to concentrate on finding the real issue.[1]
- Recurring bug pattern – Expose a bug via a unit test. Run that unit test as part of a standard build from that moment on. This ensure that the bug will not recur.
- Time-specific bug pattern – Expose the bug by writing a continuous test that runs continuously and fails when an expected error occurs. This is useful for transient bugs.
See also#edit
References#edit
- ^ Kouame, Kadjo; Ezzati-Jivan, Naser; Dagenais, Michel R. (June 2015). "A Flexible Data-Driven Approach for Execution Trace Filtering". 2015 IEEE International Congress on Big Data. pp. 698–703. Bibcode:2015bigd.conf..113K. doi:10.1109/BigDataCongress.2015.112. ISBN 978-1-4673-7278-7. Trace filtering actually eliminates outlier trace events and noise, and highlights a selected set of trace data based on either the type of events, timestamps, process name, event arguments or even the priority or importance of an event.
External links#edit
- A Pattern Language for Software Debugging Archived 2021-12-02 at the Wayback Machine (PDF)
This article is mirrored from “Debugging pattern” on English Wikipedia, revision 1374393898, written by Wikipedia's contributors and licensed CC BY-SA 4.0. Editing it here creates a Quire copy with its own history.
Synced with Wikipedia revision 1374393898 · just now