QA Checks

QA checks automatically scan your translations for common issues, such as placeholder mismatches, invalid ICU syntax, or exceeded length limits. These are the kinds of mistakes that are easy to overlook while translating but can crash a screen or break the layout once the app is released. Each check is configured per project, so you decide which issues are reported as warnings, which are treated as errors that block saving, and which are not checked at all.

Available QA checks

Localizely currently runs the following QA checks:

Severity levels

Each QA check runs at one of three severity levels, so you control how strictly it is enforced:

Configuring QA checks

The project owner and project admins configure QA checks on the project's Settings page. Each check has its own severity level, so you can tune the set to fit your project. All checks start at Warning by default.

Placeholder consistency, ICU syntax validity, and Tag consistency catch problems that can cause errors at runtime, so setting them to Error is usually a good idea.

Tracking QA issues

The project Dashboard includes a QA issues card that lists every type of issue currently detected in the project and how many times it occurs. It gives you a quick read on translation quality and shows what still needs attention.

Reviewing QA issues

On the Translations page, every translation with a QA issue is clearly marked. Click the marker to see exactly what triggered the warning or error, then fix it in place. You can also filter translations by QA issue and work through them one by one.

Now and then a flagged translation is actually correct. In German, for example, repeated words like die die are perfectly grammatical, and some translations keep a leading or trailing newline on purpose to preserve the page layout.

For cases like these, click Ignore this issue below the reported issue. Known exceptions then stop showing up in your issue counts, so what remains is a clean list of things that really need fixing.