Difference between revisions of "Debugging patterns"
From Wiki @ Karl Jones dot com
Karl Jones (Talk | contribs) (Created page with "In software engineering, a '''debugging pattern''' is a software design pattern which rectifies or corrects a bug within a software system. It...") |
Karl Jones (Talk | contribs) (→See also) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 10: | Line 10: | ||
* 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. | * 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. | ||
| − | * Recurring Bug Pattern - Expose a bug via | + | * Recurring Bug Pattern - Expose a bug via [[unit testing]]. 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. | * 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 == | == See also == | ||
| + | * [[Architectural pattern (computer science)]] | ||
* [[Software design patterns]] | * [[Software design patterns]] | ||
Latest revision as of 14:48, 20 September 2016
In software engineering, a debugging pattern is a software design pattern which rectifies or corrects 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.
Description
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.
- Recurring Bug Pattern - Expose a bug via unit testing. 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
External links
- Debugging patterns @ Wikipedia
