Difference between revisions of "Bug Report"
Jump to navigation
Jump to search
m |
|||
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
[[Bug]] Reports are one the most important feedback sources for a roguelike project, and are obtained from the testers and players. | [[Bug]] Reports are one of the most important feedback sources for a roguelike project, and are obtained from the testers and players. | ||
Using a collection of bug-reports, the developer is able to work in a sequential list seeking to perfect his program, thus making development of the game go faster than if the developer were to test all possible fail cases. | Using a collection of bug-reports, the developer is able to work in a sequential list seeking to perfect his program, thus making development of the game go faster than if the developer were to test all possible fail cases. | ||
| Line 5: | Line 5: | ||
Some roguelikes have websites that allow an automated bug report and [[RFE]] handling. | Some roguelikes have websites that allow an automated bug report and [[RFE]] handling. | ||
[[Category: | [[Category:Articles]] | ||
Latest revision as of 11:21, 25 October 2010
Bug Reports are one of the most important feedback sources for a roguelike project, and are obtained from the testers and players.
Using a collection of bug-reports, the developer is able to work in a sequential list seeking to perfect his program, thus making development of the game go faster than if the developer were to test all possible fail cases.
Some roguelikes have websites that allow an automated bug report and RFE handling.