Process
A typical bug report progression of testing process is seen below:
- Identification. Incorrect program behaviour is analyzed and identified as a bug.
- Reporting. The bug is reported to the developers using a defect tracking system. The circumstances of the bug and steps to reproduce are included in the report. Developers may request additional documentation such as a real-time video of the bug's manifestation.
- Analysis. The developer responsible for the bug, such as an artist, programmer or game designer checks the malfunction. This is outside the scope of game tester duties, although inconsistencies in the report may require more information or evidence from the tester.
- Verification. After the developer fixes the issue, the tester verifies that the bug no longer occurs. Not all bugs are addressed by the developer, for example, some bugs may be claimed as features (expressed as "NAB" or "not a bug"), and may also be "waived" (given permission to be ignored) by producers, game designers, or even lead testers, according to company policy.
Read more about this topic: Game Testing
Famous quotes containing the word process:
“come peace or war, the progress of America and Europe
Becomes a long process of deterioration—”
—Robinson Jeffers (1887–1962)
“Experiences in order to be educative must lead out into an expanding world of subject matter, a subject matter of facts or information and of ideas. This condition is satisfied only as the educator views teaching and learning as a continuous process of reconstruction of experience.”
—John Dewey (1859–1952)
“The invention of photography provided a radically new picture-making process—a process based not on synthesis but on selection. The difference was a basic one. Paintings were made—constructed from a storehouse of traditional schemes and skills and attitudes—but photographs, as the man on the street put, were taken.”
—Jean Szarkowski (b. 1925)