I will test japanese localization in your saas UI
Japanese UI and i18n QA Engineer
About this Gig
Native Japanese QA with an English report. Async on Fiverr; no calls.
Checks:
- Wording, grammar, tone and consistency
- Truncation, line breaks, untranslated/hard-coded text, dates, numbers, currency, placeholders and fallbacks
- Localization spot checks for responsiveness, functionality and usability in the agreed Mac browser/viewport
- Severity, repro steps, expected/actual, wording suggestions and annotated screenshots (max 3/8/15 by package)
- Premium: Japanese-localization release-risk summary
Scope:
State = one unique page/modal/tab/error or different viewport. Flow = up to 8 actions. Characters = unique visible Japanese text. The first reached limit ends scope. Findings are up to the package maximum; fewer if fewer issues exist.
Revisions only correct factual errors/omissions in my report. New builds/screens, added scope and retesting need a new/custom order.
Excluded: full translation/code changes; exhaustive, security, performance, accessibility or legal tests; launch certification; live payments; real customer data; production writes; admin access; destructive actions. Use authorized staging/demo and synthetic data. Communication/payment stay on Fiverr.
Testing application:
Web application
Device:
Mac
FAQ
Do I need to join a call or meeting?
No. Standard orders are handled asynchronously through Fiverr messages and written requirements. I may ask short written questions if scope or access is unclear.
Do you translate the entire product?
No. This Gig is localization QA. I report issues and may suggest corrected Japanese wording. Full translation and code implementation are not included.
What counts as a state or flow?
A state is one unique page, modal, tab, error, or materially different viewport. A flow is up to 8 user actions. The first package limit reached ends the scope.
What if my scope exceeds the package limit?
Please message me before ordering. I can prepare a custom offer. Findings are capped by the package maximum and may be fewer when fewer issues are observed.
Can you test production?
Only safe, read-only checks when expressly authorized. Staging or demo access with synthetic data is preferred. No live payments, real customer data, admin access, production writes, or destructive actions.
Do you fix the code or retest a new build?
No. I provide a developer-ready report. Code changes, new screens/builds, added scope, and post-fix retesting need a separate or custom order.
