A practical guide for players. Check the game version and realm rules before applying recommendations.
Fill in a record someone else can use
Copy these fields into your notes and fill them with your own observations: client branch and build; date and time; class, pet and relevant talents; location; starting conditions. Leave an unknown field marked unknown. These are our suggestions for a useful report, rather than a form required by Blizzard.
For a suspected pet-panel error, write a short sequence: select the pet, open its sheet, record the displayed value, close the sheet and open it again. Add two separate lines: expected result, and observed result. This is a sample procedure to adapt, not an account of a test we carried out. State how many attempts produced the result, including attempts when nothing unusual happened.
A note to put beside the screenshot
On October 8, Blizzard called the Hunter Ferocity pet critical-chance display problem visual only. That entry is historical; it does not establish that the bug remains on October 17. It does show why the screenshot and the gameplay question belong in separate parts of a report. Compare dated known issues with the development notes for your build. For another attempt, change one condition and keep the rest. After an update, record the new build and repeat the original sequence.
Rehearse the method on our realm
TWOW.PARTY/Forever is our independent, free server for practising mechanics and checking changes available on its own version. Use a simple action there to practise writing a test another player can repeat. Start at https://twow.party/?lang=en#play; connection help is at https://twow.party/en/start. Put our realm version in the record. Its compatibility with Blizzard's current is unconfirmed, so the result cannot settle whether an official bug is present or fixed.
Sources
- WoW Forever Beta Known Issues - October 8us.forums.blizzard.com
- WoW Forever Beta Development Notes - updated October 15, staff post 6us.forums.blizzard.com
