Names and their readings
A Japanese form asks for the family name first: 姓 then 名, or one 氏名 field written 山田 直樹. Most also ask how the name is read, as furigana, because the same kanji can be read in more than one way:
- フリガナ or カナ asks for katakana: ヤマダ ナオキ.
- ふりがな or ひらがな asks for hiragana: やまだ なおき.
- セイ and メイ are the family name’s and the given name’s readings, in two boxes.
- 半角カナ asks for half-width katakana: ヤマダ ナオキ.
Make the test account with Japan as its country, in the app’s New address or with country: "JP" for agents and tests. Its persona gets a name from Japanese lists, and every reading field gets that name’s reading in the kana and width it asks for. The app shows the reading beside the name, for copying.
Check that the app:
- keeps the family name first wherever it shows the name, in emails too
- sorts and searches by the reading, not the kanji, where it lists people
- accepts a long reading, such as ササキ ショウタ, and a short one, such as アヤ
Full width and half width
Japanese text comes in two widths. Full-width (全角) letters and digits, such as 220, are what the Japanese keyboard types by default. Half-width (半角) ones are the usual 220. A field often says which it wants: 全角, 半角数字 or 半角英数字.
Proxy Mail QA follows what the field says, in names, readings and guessed details such as the postcode and building: a 郵便番号(全角) field gets 220-0011. For your own tests, try the width the field doesn’t ask for as well:
- Full-width digits in a postcode or phone field. Many forms convert them when the field loses focus. Check that the app stores the half-width form, or explains what it wants.
- A full-width space between names. Check that 山田 直樹 is stored the same as 山田 直樹, or the app treats them as two different people.
- Half-width katakana in a フリガナ field. Either accept it and convert it, or say the field wants full-width katakana.
The unusual names list has full-width letters, half-width katakana and a full-width space between names as values to paste.
The address from the postcode
Most Japanese forms fill 都道府県 and 市区町村 from the 郵便番号 as it’s typed, with a library such as yubinbango or ajaxzip3. The test account’s address agrees with its postcode: 220-0011 is 神奈川県 横浜市西区 高島, from Japan Post’s data, with a made-up block number and building, so nothing is ever sent to a real door.
For agents and tests, type the postcode before the rest of the address, then fill 番地 and 建物名. form_values says this beside a Japanese postcode field.
Test what happens when the lookup can’t run as well: a postcode the library doesn’t know, a slow network, and a person who types the address before the postcode.
LINE sign-in
LINE is widely used in Japan, and many apps offer LINEでログイン. LINE Login uses OpenID Connect: ask for openid profile email to get an ID token with the person’s LINE profile (LINE Login documentation).
Testing before release. A new LINE Login channel starts in Developing status, and then only people with the channel’s Admin or Tester role can sign in with it (roles). Invite your testers by email from the channel’s Roles tab. Each one signs in to the LINE Developers Console with a LINE account, so use LINE accounts your team controls for testing, never a customer’s. Each environment’s callback URL must be registered on the channel’s LINE Login tab, and the redirect_uri your app sends has to match one. If the console doesn’t take your local address, use an HTTPS tunnel.
The email address. LINE gives an email address only to channels that have applied for the email permission (Basic settings, OpenID Connect, Apply, with a screenshot of the screen that tells people why you collect it), and only when the request includes the email scope. Not every LINE account has an email address registered, either. So an app that needs an email after LINE sign-in should ask for one and confirm it. That’s the step to test with Proxy Mail QA:
- Sign in with a test LINE account.
- When the app asks for an email address, give it a Proxy Mail QA address.
- Fill the code or open the link from the email, in the page with Chrome or with
wait_for_codefor an agent. - Check the account now has that address, and that signing in with LINE again finds the same account rather than making a second one.
Also test:
- Cancel on LINE’s consent screen. The app should come back to its sign-in page with a clear message, not an error page.
- The add friend option. With
bot_prompt, LINE offers to add your LINE Official Account as a friend, on the consent screen (normal) or on a screen after it (aggressive) (add friend option). Sign in once adding the account and once without: the app should work the same both ways. - The profile after sign-in. A LINE display name is a nickname, not a legal name. If the app needs 姓, 名 and their フリガナ, it should ask for them after LINE sign-in, and the test account’s Japanese persona fills them.
Email in Japanese
Verification and reset emails in Japanese are read like any others: the code after 認証コード or 確認コード, the link, and how long it lasts (10分以内). Check that the subject and sender name read well in Japanese mail apps, and that the email isn’t only an image.