You are here: Wiki>Documentation Web>BestPractice>BestPracticeBugfixing (07 Jun 2013, DanielNuest)Edit Attach

Best Practice Bugfixing

Fixing a bug is a day-to-day task for developers, so we just want to agree on a very short lists of things that should accompany a bugfix.

  1. No bugfix without a Bugzilla bug report or a GitHub issue.
    We must capture our work and issue management systems are a great way to make the changes message for new releases easy to write and complete (and long!).
  2. No bugfix without a test.
    TDD rocks, every developer knows that. Adding tests when fixing bugs is a great way to create useful tests if they were missed/not written yet because you don't have to write many tests in a row but only one at a time.
    This should be enforced by code managers!
  3. Mark bug reports/issues as resolved with a reference to the commit that fixed it (easy as pie in GitHub).

See more best practices here: BestPractice.

Topic revision: r1 - 07 Jun 2013, DanielNuest
Legal Notice | Privacy Statement

This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Wiki? Send feedback