Testing Methodology

Last updated: 15 September 2026 (Asia/Manila)

Every guide on this site must say whether it is Tested / hands-on or Research-based. Mixing those up is a fail. We would rather ship a shorter researched piece with sources than fake a test we did not run.

There are two labels only. No third weasel label.

Related: Editorial Policy · Affiliate Disclosure · About · Contact

The two labels

Tested / hands-on. We used the product or ran the software ourselves. For Roblox Studio, that means we reproduced the steps in Studio and can point to Output, the Explorer tree, or a screenshot we actually captured. For gear, that means the unit was in our hands for the claims we make (fit, latency we measured, software we installed). A test has a date and a scope. “We tested” with no date is not a test.

Research-based. We did not run those steps. The guide is built from official docs, manufacturer specs, and named third-party reviews, each cited with a date. Research-based is a legitimate label. It is not a lesser Tested label. It is the honest one when we have not reproduced the work.

What counts as fake testing (never)

  • Calling a post Tested because we read the manual or watched a YouTube review
  • Stock photos, marketplace renders, or someone else’s Output window passed off as ours (stolen Output)
  • Invented SPL, SNR, battery-hour, or benchmark numbers (invented benches)
  • Copying a community library’s README and writing as if we ran ProfileStore or DataStore2 in our place file
  • Backdating a “last tested” line

By section

Studio. Research-based is the default until we have a repro in a dummy place. Claims about the “Enable Studio Access to API Services” toggle, DataStore wipes, or BindToClose behavior stay Research-based unless we show Output from that run. We do not test wipe logic on a live experience with real players.

Gear and creator tools. Spec sheets and named reviews can support a Research-based roundup. Comfort, mic tone, and capture latency stay qualitative unless we measured them. Product names only while Amazon/affiliate remains blocked until eligibility = YES per asset.

Game Codes. A list is only as good as its last-checked date. We do not invent active codes. Expired or unverified codes get labeled that way or stay off the page.

How a label appears

Near the top of the article: one research note. Example: “Last updated: 15 September 2026 (Asia/Manila). LegitGameplay has not hands-on tested this in Studio. Guidance is Research-based from Roblox Creator docs retrieved 15 September 2026.” If a later update adds a real dummy-place repro, we change the label and the date. We do not silently upgrade Research-based to Tested.

Money and this page

Amazon and other affiliate programs are blocked until eligibility = YES per asset. That block does not change a Tested or Research-based label. A commission never buys a Tested stamp. See Affiliate Disclosure and Editorial Policy.

Where this sits

This is a trust page. After APPROVE it may go in the footer. It does not go in Primary header chrome.

Related: Editorial Policy · Affiliate Disclosure · About · Contact