Module 10: Redlining

Question 1

What is REDLINING?

Answer 1

This is the process by which a L/SQAT reads and reviews your bug report and requests that you modify/edit it to meet GFPQA standards and any title-specific requirements.

Question 2

What are some reasons bugs get redlined?

Answer 2

• To upgrade or downgrade a bug class
• To ensure user character and NPC name conform to title standards or a design document
• To add additional information, include title-specific developer/producer requests. This may require additional research and edits
• To correct spelling and grammar errors
• To update bug frequency

Question 3

What is the most common mistake people make when writing a bug summary?

Answer 3

TOO VAGUE

Question 4

List three tips to help you write clear bug reports.

Answer 4

• Spell check
• Correct and proper Names/Titles/Call outs
• Reference old bug reports

Question 5

What are two common bug writing mistakes that often get redlined?

Answer 5

• Misspellings
• Wrong format or information in the wrong place
• Opinions are NOT allowed

Question 6

When is it ok to omit or modify redline changes in your bug report?

Answer 6

NEVER! Always complete redlines as requested.

Question 7

Why do we do redlining?

Answer 7

To IMPROVE bug reports. This ensures our service to the developers is clear, concise, useful and makes the product better.