Testing Methodology

Instant Game Zone uses several kinds of evidence depending on the question. Editorial research may rely on official or primary documentation, credible independent measurements, public structured data, and carefully classified community observations. We do not present external evidence as first-hand testing.

How we verify editorial information

  • For platform requirements, store entitlements, support policies, specifications, release status, and other changeable facts, we prefer current primary or official sources where practical.
  • Independent measurements and public data may be used when they add useful evidence. We identify the source and avoid presenting someone else’s measurements as our own.
  • Community reports are treated as directional evidence unless independently corroborated. We label them as reports and do not generalize beyond what the available evidence supports.
  • We describe something as tested, benchmarked, or directly observed by Instant Game Zone only when we actually performed that work and can state the relevant conditions.
  • When reliable sources conflict or current behavior remains uncertain, we preserve that uncertainty rather than forcing a stronger conclusion than the evidence supports.

Article-level limitations are disclosed where they materially change how a reader should interpret or act on a claim. Routine differences between sourced research and first-hand testing are handled through attribution, source links, and precise wording rather than repetitive blanket disclaimers.

Our Editorial Policy covers our broader standards for accuracy, source updates, corrections, recommendations, and commercial independence.

Formal first-party benchmarks

When Instant Game Zone publishes a formal first-party benchmark, performance numbers are only useful when the test conditions are clear. Formal benchmark records document the hardware, game, render configuration, test date, driver and operating-system context, run count, method, and measured results.

Measured results

Formal benchmark data is treated as measured data, not an estimate. Our current benchmark protocol is version IGZ-BP-0.1. The initial Windows workflow uses CapFrameX 1.9.0 and requires at least three valid measured runs for real production benchmark data.

  • Warm-up activity is excluded from measured results.
  • We do not select only the best run.
  • Average FPS is the arithmetic mean across valid measured runs.
  • 1% Low FPS is the arithmetic mean of each valid run’s CapFrameX 1% Low Average value.
  • The benchmark configuration stays fixed across the runs being compared.
  • Scene and environment conditions are kept as consistent as the test allows.
  • Raw capture evidence is retained outside the public WordPress record for audit and review.

When a test changes

Changes that materially affect the meaning or comparability of results require a methodology review rather than silently reinterpreting older measurements. Articles should identify important settings and test conditions so readers can understand what a number represents.

Guides that are not formal benchmarks

Not every guide, settings article, compatibility report, or troubleshooting article is a formal benchmark. When we make measured performance claims, we aim to make the evidence and conditions clear. Advice based on configuration, documentation, public data, or observed troubleshooting is presented as such rather than being labeled as laboratory-style benchmark data.