Product testing
Testing Methodology
This page explains how GeoBoost evaluates product-specific claims. It does not claim that every round, browser state, or future game-site version will behave identically.
Test scope
Checks use the current stable GeoBoost build in Chrome on supported private, practice, or testing modes. Ranked and competitive modes are outside the intended-use test scope.
What is checked
| Area | Check | Passing result |
|---|---|---|
| Round detection | Open a fresh supported round and request identification | The current round is detected without reusing a prior result |
| Location result | Compare returned coordinates and readable location with the active round data | The response belongs to the active round |
| Map interaction | Run map preview, movement, and placement where supported | The map moves and places within the active game interface |
| Access state | Check free limits, Pro restore, and expired access | The interface matches the server entitlement |
Supported sites
GeoGuessr, OpenGuessr, WorldGuessr, FreeGuessr, and Geotastic are checked separately because their interfaces and supported features differ. A successful check on one site is not treated as proof for another.
Known limitations
- Game-site updates can temporarily break detection or map controls.
- Not every mode exposes the same round data or map interface.
- Readable place names depend on reverse-geocoding availability.
- No result is presented as a guarantee for future site versions.
Reporting a failure
Send the game site, mode, extension version, Chrome version, expected behavior, and a screenshot to [email protected].