# Write tests in your team's own language

> Tests in Spanish, Vietnamese or German, with the plan and results in that language and the screen's text kept as it is. Two real runs, and the lesson one of them taught.

By Jason Nguyen, Founder, Testsy. Published 2026-11-21. https://testsy.dev/blog/write-tests-in-your-teams-own-language/

## The people who know the app best

In many teams the person who knows every flow of the product is not a developer, and not writing English all day: a support lead in Madrid, a product owner in Ho Chi Minh City, a QA analyst in São Paulo. Scripted test tools ask them to work in English and in code. So the knowledge stays in a spreadsheet of manual checks.

A Testsy test is a description of what a person does and what must be true. It can be in [any language](https://testsy.dev/docs/write-a-test/): the plan (steps, checks, questions) comes back in the language you wrote in, and so do the results, each check and its reason. What the tester saw is never translated: values, button labels and quotes stay exactly as they appeared on the screen.

## Two runs in Spanish

We wrote a test in Spanish for the selection page of our practice site: switch notifications on, accept the terms, choose a size, a plan and a country, set a quantity and move a slider to 80.

The second run passed with every check in Spanish, and the slider read exactly 80. The picture at the top of this page is the top of its result: the test's Spanish title, the verdict and the headline in Spanish.

![The checks, in Spanish, each with the reason it passed. The values in the summary stay in English, as the page shows them.](https://testsy.dev/blog/img/web-es-exact-checks.webp)

Open [the run](https://app.testsy.dev/share/AhXMaFu1YnevO3NZWgD65I5s6Y1X6LWp) (live until 18 February 2027).

## What the first run taught us

The first run passed too, and it should not have. We had written the slider's tolerance clumsily: "vale cualquier valor a 2 o menos de 80", meant as "anything within 2 of 80". The plan read it as "80 or less", and the run accepted a Volume of **50**, the slider's starting value, as a pass.

![The first run's checks. The plan turned our tolerance into "80 or less" and the check passed on Volume 50.](https://testsy.dev/blog/img/web-es-loose-checks.webp)

Everything needed to catch it was on the page: the check says "se permite cualquier valor de 80 o menos" and the reason names the value it decided on, "Volume 50". We rewrote the line as "entre 78 y 82, ambos incluidos" and the next run moved the slider to 80 and checked it. [Open the first run](https://app.testsy.dev/share/Valxxms_j9K3Odg3n2CoLOPRwd4G_d9x) to see it for yourself.

The lesson holds in every language, English included:

- **Give ranges as two numbers.** "Between 78 and 82" cannot be read two ways.
- **Read the plan before you save it.** The checks are written back in your words; a check that says something you did not mean is the moment to fix it ([review the plan](https://testsy.dev/docs/write-a-test/)).
- **Read the value a check passed on.** A pass with a surprising value is a test to rewrite, not a result to trust. More on that in [Flaky tests and what a verdict should say](https://testsy.dev/blog/flaky-tests-and-what-a-verdict-should-say/).

## Tips for writing in your language

- **Quote the screen as it is.** If the button says "Save" on an English site, write "Save", even inside a sentence in Spanish. The tester looks for what you quote.
- **Mix freely.** A Vietnamese sentence with the English names of menu items is fine.
- **Test the translated site in its language too.** If your site has a Spanish version, a test written in Spanish reads naturally against it; see [Test a multilingual site and its language switcher](https://testsy.dev/blog/test-a-multilingual-site-and-its-language-switcher/).

The rest of the Testsy app, menus and buttons, is in English.

This post is part of [Release testing for product teams](https://testsy.dev/blog/release-testing-for-product-teams/).
