Changes between Version 13 and Version 14 of TesterDocumentation
- Timestamp:
- 08/08/11 12:29:41 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TesterDocumentation
v13 v14 95 95 96 96 Note that if you're testing out a ''new feature'' or trying to ''reproduce a bug'', we'd like to have both ''success'' and ''failure reports''. 97 98 If the bug you've found is a regression and you want to see it fixed as soon as possible, you can help by doing a ''Git bisect''. This technique is described here: 99 100 * [http://book.git-scm.com/5_finding_issues_-_git_bisect.html Finding Issues - Git Bisect] 101 * [http://progit.org/book/ch6-5.html Debugging with Git] 102 103 If you manage to find the commit that caused the regression, fixing it is ''much'' easier for the developers.