AION 2 Test Reports: What to Record

Use this AION 2 test report guide to record login, combat, graphics, party, network, and download findings with enough detail for a useful player report.

AION 2 Test Reports: What to Record Overview

Test coverage becomes valuable when another player can reproduce it. This page gives a report structure that works for a launch-scale test without turning one anecdote into a permanent game fact.

Confirmed Information

  • The official test schedule identifies specific windows that should be attached to reports.
  • Client version, region, and time are essential context for a test result.
  • A report should separate a crash, a balance observation, a missing feature, and a personal preference.

Player Workflow

  1. Record date, local time, region, platform, and client version.
  2. Write the shortest reproducible steps.
  3. Add expected result and actual result.
  4. Classify impact: blocked, severe, inconvenient, visual, or feedback.
  5. Remove account identifiers before sharing publicly.

Official References

FAQ

What makes an AION 2 test report useful?

A dated client, region, reproducible steps, expected result, actual result, and a clear impact classification.

Should test reports become guide facts?

Only after repeated evidence or an official confirmation. Keep reports labeled as test observations.