Join the stress test. Make the short session count.

Meeting friends at the right opening matters more than designing a perfect build for a short test. Check your region first, then use the preparation sheet to spend less of the session sorting out logistics.

Regional start times: October 19–20, 2026

How long is the test, and what gets wiped?

Blizzard describes a window of a few hours without an exact closing time. Stress-test characters, including their names, are deleted when it ends; the beta then reopens. Do not use the event to reserve a launch name. This announcement does not establish a wipe of existing normal-beta characters.

Plan around a short evening rather than a permanent progression goal. If someone in your party has limited time, agree on a meeting point and a fallback activity before logging in. A useful session can be small: learning where an interaction becomes confusing is worth recording even if you never reach a dungeon.

A short-session plan that produces useful feedback

1. Establish a baseline. After entering, note your region and time. Check movement, readable text and a basic interaction before changing settings.
2. Try a social interaction. Meet a teammate and note whether the interaction is understandable. Agree before trading an item; use an expendable test item rather than something you still need.
3. Follow a compact quest loop. Accept, track, complete and return one manageable objective. Use the quest finder if you need a reference, but check the live objective before following an older record.
4. Record one clear result. Distinguish a delayed response from a permanent failure. If you repeat an action, change one variable so the result is easier to interpret.

These are suggested testing priorities, not timed instructions or a claim that every activity will be available. Avoid designing your evening around an unverified level cap or dungeon queue. A temporary test may have different access from the normal beta.

If you cannot enter, identify the failing step

Account sign-in: use the account’s official support route. Client update: read the launcher’s message before reinstalling. Realm entry: compare your region with the schedule and check current announcements. A queue or unavailable realm alone does not show that your account is ineligible.

Do not repeatedly change your password or install unofficial fixes to address a realm opening. Save the exact visible error and the time it occurred. That gives you something concrete to compare with an official incident report.

After the temporary realms close

Keep your notes outside the character. Organize them by the interaction that failed, then add the minimum steps another tester would need to understand it. Remove email addresses, account identifiers and chat from other people before sharing a screenshot.

For a normal-beta session, return to the beta access guide, class build library and session planner. Their level-30 examples describe our dated beta snapshot, not confirmed stress-test restrictions.