Member Activity

Paul from WonderProxy had Bugs everywhere in stitches. Thanks for the laughs. And be sure to check how this Memory looks from your part of the world - https://wonderproxy.com/

about 1 month ago

Memory

Paul Reinheimer

earned:

Expanded the MoTaverse

Sponsors can be funny too

about 1 month ago

Community Star

Paul Reinheimer

contributed:

Sponsors can be funny too

Paul from WonderProxy had Bugs everywhere in stitches. Thanks for the laughs. And be sure to check how this Memory looks from your part of the world - https://wonderproxy.com/

about 1 month ago

Memory

Paul Reinheimer

achieved:

TestBash Trailblazer

This badge is awarded to members who have attended a TestBash event.

about 2 months ago

Badge Award

Paul Reinheimer

achieved:

99 Second Speaker

This badge is awarded to a member who has given a 99 second talk.

about 2 months ago

Badge Award

Paul Reinheimer

earned:

Contributed to TestBash

99 Second Talks – Day 2 – TestBash Brighton/MoTaCon 2025

about 2 months ago

Community Star

Paul Reinheimer

contributed:

99 Second Talks – Day 2 – TestBash Brighton / MoTaCon 2025

Celebrate the creativity and courage of testers and quality engineers as they share stories, lessons, and ideas in just 99 seconds.

about 2 months ago

TestBash Session

Paul Reinheimer

earned:

Reported a MoT Bug

Found that the team size slider did not show in Firefox

about 2 months ago

Community Star

Paul Reinheimer

is Open to Podcasting

2 months ago

Profile

Paul Reinheimer

earned:

Added a definition

Test environment

3 months ago

Community Star

Paul Reinheimer

earned:

Added a definition

Compliance testing

3 months ago

Community Star

Paul Reinheimer

achieved:

Picture Perfect

This badge is awarded to members who update their profile with a new photo.

3 months ago

Badge Award

Paul Reinheimer

achieved:

Social Connector

This badge is awarded to members who update their social links on their profile.

3 months ago

Badge Award

Paul Reinheimer

achieved:

Inclusive Companion

This badge is awarded to members who add their pronouns to their member profile, helping create a more inclusive community.

3 months ago

Badge Award

Paul Reinheimer

achieved:

Open to Opportunities

This badge is awarded to members who indicate they are open to work, writing, teaching, speaking, mentoring, CV reviewing or internships.

3 months ago

Badge Award

Paul Reinheimer

achieved:

Glossary Contributor

This badge is awarded to members who contribute a new term or an alternative definition to the software testing glossary.

4 months ago

Badge Award

Paul Reinheimer

earned:

Added a definition

Localization testing

4 months ago

Community Star

Paul Reinheimer

achieved:

TestBash Brighton 2025 Attendee

This badge is awarded to members who confirm their tickets to TestBash Brighton 2025

5 months ago

Badge Award

Paul Reinheimer

earned:

Professional Member

Was a professional member in 2025

6 months ago

Community Star

Paul Reinheimer

achieved:

Career Champion

This badge is awarded to members who have subscribed as Professional Members.

8 months ago

Badge Award

Paul Reinheimer

achieved:

Collection Curator

This badge is awarded to members who create their first collection, organising learning content for themselves or others.

8 months ago

Badge Award

Paul Reinheimer

is Open to Speak

8 months ago

Profile

Paul Reinheimer

is Open to Teach

8 months ago

Profile

Paul Reinheimer

is Open to Write

8 months ago

Profile

Paul Reinheimer

achieved:

Bio Builder

This badge is awarded to members who have updated their profile.

8 months ago

Badge Award

Paul Reinheimer

achieved:

Club Explorer

This badge is awarded to members who have signed up as a Club member.

8 months ago

Badge Award

Paul Reinheimer

achieved:

In the Loop

This badge is awarded to those who subscribe to the software testing news weekly newsletter.

8 months ago

Badge Award

Paul Reinheimer

contributed:

<h1>What is Localisation Testing?</h1><div>Localisation testing is the process of confirming that an application behaves as expected in each supported region. These regions could be broad — such as an EU-wide version of a site — or highly specific, like a custom landing page designed only for visitors from a single city.<br><br>
</div><h2>How does a website know where the user is?</h2><div>There are two main methods:<br><br>
</div><ul>
<li>
<strong>IP Geolocation</strong><br> The website looks up the visitor’s IP address in a geolocation database to estimate their location. These databases are generally very accurate at the country level, and can sometimes narrow down to the city — though with less reliability. This method requires no input from the user.<br><br>
</li>
<li>
<strong>Browser Location API</strong><br> Modern browsers can provide precise location data using signals like GPS, nearby Wi-Fi networks, or cell towers. Unlike IP geolocation, this usually requires the user’s explicit permission before sharing.<br><br>
</li>
</ul><h2>How do websites change their content?</h2><div>Websites typically use one of three approaches:<br><br>
</div><ol>
<li>
<strong>Redirect to a country-specific TLD</strong><br> For example, a visitor from the UK navigating to example.com would be redirected to example.co.uk.<br><br>
</li>
<li>
<strong>Redirect to a region-specific path</strong><br> For example, a visitor from the UK landing on example.com would instead be taken to example.com/uk/.<br><br>
</li>
<li>
<strong>Serve location-specific content at the same URL</strong><br> In this case, the page at example.com shows different content depending on whether the visitor is in the UK or the USA — while keeping the same address.<br><br>
</li>
</ol><h2>Is this how websites decide what language to use?</h2><div>Not always. While some websites rely on location to select a language, the better approach is to respect the user’s <strong>Accept-Language header</strong>. This allows people to choose their preferred language independent of their physical location. For example:<br><br>
</div><ul>
<li>A user in the UK may prefer to browse in French.<br><br>
</li>
<li>A user in France may prefer to browse in English.<br><br>
</li>
</ul><h2>What sort of content is localised?</h2><div>The specifics depend on the site, but common examples include:<br><br>
</div><ul>
<li>Displaying GDPR cookie banners to users in Europe, but not elsewhere.<br><br>
</li>
<li>Showing region-specific content (e.g. Netflix only lists shows licensed in that region).<br><br>
</li>
<li>Adjusting pricing to reflect local currencies and market expectations.<br><br>
</li>
</ul><h2>What are the key steps in localisation testing?</h2><ol>
<li>
<strong>Identify the regions that have unique content</strong><br> You can’t test what you don’t know to look for. Start by mapping out which versions of the site exist (country, region, or city level) and what differs between them.<br><br>
</li>
<li>
<strong>Decide how to access region-specific versions of the site</strong><br> Common solutions include using proxy servers, VPNs, or test hooks built into the application that let you simulate being in a different location.<br><br>
</li>
<li>
<strong>Test from each location</strong><br> Verify that the actual behaviour matches the intended behaviour for each region. Be mindful of edge cases — for example, location-specific changes accidentally breaking other parts of the site.<br><br>
</li>
</ol> image

Localization testing

Definitions of Localization testing

9 months ago

Term

Paul Reinheimer

contributed:

Compliance testing

Definitions of Compliance testing

9 months ago

Term

Paul Reinheimer

contributed:

<div>
<strong>Testing Environments<br></strong><br>
</div><div>Many organizations maintain multiple “environments” (or “copies” of their website or product) that serve different purposes. A simple setup might include Development, QA, Staging, and Production. Larger organizations may have multiples of each, and some even run dozens or hundreds of environments in parallel as different pieces of work progress.<br><br>
</div><div>A <strong>testing environment</strong> is an environment specifically designed for testing. It contains a working copy of the system under test, along with the supporting resources needed for it to function properly. These resources are usually other “testing” versions of services, so testers can safely simulate scenarios—like checking out with a credit card—without touching real systems or data.<br><br>
</div><h3>Common challenges in testing environments</h3><ol>
<li>
<strong>Non-functional pieces</strong><br> It’s common for some parts of the site to be missing or disabled in a testing environment. Integrations may not be wired up, certain services may be too costly to replicate, or features like email delivery may be switched off to avoid accidentally contacting real users. As a result, additional test runs may be needed once code reaches production.<br><br>
</li>
<li>
<strong>Insufficient test data</strong><br> If the attached database only contains a handful of users or products, issues that occur at real-world scale may never surface. These can range from crippling performance problems to subtle UI issues that only appear when datasets are larger.<br><br>
</li>
<li>
<strong>Messy environment state</strong><br> Over time, testing environments can accumulate abandoned carts, half-finished registrations, and spam data. This “junk” makes it hard to run clean scenarios and can interfere with tests that depend on a fresh start.<br><br>
</li>
</ol><h3>Best practices for testing environments</h3><ul>
<li>
<strong>Keep them production-like.</strong> The closer an environment matches production in configuration and integrations, the more reliable the test results will be.<br><br>
</li>
<li>
<strong>Manage test data thoughtfully.</strong> Use representative data volumes and refresh it regularly to uncover performance and usability issues earlier.<br><br>
</li>
<li>
<strong>Automate resets.</strong> Provide tools or scripts to reset state between runs, ensuring cleaner, repeatable tests.<br><br>
</li>
<li>
<strong>Document differences.</strong> If certain features are intentionally disabled (e.g. email), make that clear so testers know what to expect.<br><br>
</li>
<li>
<strong>Automate test data creation.</strong> Having fresh accounts, products, or pages created at the click of a button is convenient and avoids the problem of sharing test accounts between multiple testers.<br><br>
</li>
<li>
<strong>Use realistic data.</strong> Resist the temptation to fill fields with random keystrokes. It’s much easier to spot problems when test data resembles real-world inputs. Tools like Fakery can generate meaningful fake data on demand.<br><br>
</li>
<li>
<strong>Mimic production structures.</strong> Most organizations rightly forbid using real production data in test environments. Still, it’s valuable to study complex production data and replicate its structure in development to surface issues earlier.<br><br>
</li>
<li>
<strong>Include geo-awareness.</strong> Many compliance and localization issues only appear in specific countries. Using a geo-proxy service such as WonderProxy helps ensure your test environments behave correctly for users around the world.</li>
</ul><div><br></div> image

Test environment

Definitions of Test environment

11 months ago

Term

Activity

Unify Security and Quality with Kiuwan & TestRail

All-in-One Test Automation, Powered by AI

MoT Professional Membership now includes access to all

WonderProxy helps find bugs from around the world