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:
“[Wellesley College] is about as meaningful to the educational process in America as a perfume factory is to the national economy.”
—Nora Ephron (b. 1941)
“It haunts me, the passage of time. I think time is a merciless thing. I think life is a process of burning oneself out and time is the fire that burns you. But I think the spirit of man is a good adversary.”
—Tennessee Williams (1914–1983)
“I wish to see, in process of disappearing, that only thing which ever could bring this nation to civil war.”
—Abraham Lincoln (1809–1865)