如果沒有為可譯性做早期設計就在事后進行翻譯/本地化，那么我們只有對所有的東西進行徹底的再測試。(一致同意) 這時，基線語言自動化腳本就體現出很重要的價值。
33. We disagreed with the following statement: It is important to regress all bugs in a localized version and, to the extent done in the baseline version, to extend automated tests to establish the same baseline for each language. (7 no, 1 yes.)
我們不贊成下面的說法：按照基線版本中的樣子回歸本地化版本中的所有bug，以及通過擴展自動化測試為每種語言建立相同的基線版本都很重要。(7票反對，1票贊成)
34. The kinds of bugs likely to arise during a well-planned localization are unlikely to be detected by baseline regression tests. (9 yes, 0 no).
在規劃良好的本地化過程中，可能會增加一些不容易被基線回歸測試探測到的bug。(9票贊成，0票反對)
35. We didn’t vote on these points, but I’ll insert them here because they provoked thought and discussion (and because I think Marick’s on the right track.) Brian Marick suggested that in planning for automated localization testing, we should be thinking in terms of several distinguishable classes of tests. Here are some examples:
我們沒有對下面的觀點投票，但是我還是在這里列出它們，因為它們能引起思考和討論(還因為我認為Marick的想法在正軌上)。Brian Marick建議在規劃自動化本地化測試時，應該考慮一些可區別種類的測試。下面是一些例子：
· Language-independent automated tests, such as (in many but not all cases) printer configuration tests, other configuration / compatibility tests, and tests of compatibility with varying paper sizes.
語言獨立的自動化測試，例如(在很多但不是所有情況下)，打印機配置測試，其它配置/兼容性測試，以及不同紙張大小的兼容性測試。
· Specific-language automated tests, if these are worthwhile. If you expect to keep selling new releases of your product in French, German, and Spanish versions, you might find value in creating some French-specific, German-specific, and Spanish-specific automated tests.
如果覺得值得的話，可以使用特定語言的自動化測試。如果你希望繼續出售新產品的法文版、德文版以及西班牙文版，你會發現創建法文、德文以及西班牙文自動化測試是很有價值的。
· Most tests that are language specific will probably best be handled by manual localization testing.
特定語言的大多數測試有可能被手動本地化測試處理好。
· International-specific tests that are handled by automation. These tests check the translatability and localizability of the software. For example, you might provide dummy translations that use strings that are too long, too short, etc. You might provide text that will be hyphenated differently in different countries.
特殊國際化測試能夠被自動化。這些測試將檢查軟件的譯本和本地化情況。例如，你可以用很長或很短的字符串提供虛假譯文。你也可以提供不同國家中用不同連字符連接的文本。
· Cheaply localizable tests. Marick’s expectation is that this class is small. However, some tests aren’t concerned with the strings used or the screens displayed. For example, stress tests to find memory leaks depend on repeated executions of some functions, but the text and graphics on display might not matter. Localization of some of these tests, to the minimum degree necessary to make them useful, will be easy.
簡易本地化測試。Marick希望這是一類小型測試。但是，一些測試并不與字符串或屏幕顯示有關。例如，強力測試能否找出內存泄露取決于一些函數的反復執行，而這與顯示文本和圖形沒有關系。把這類測試按照使它們可用的最低程度本地化來將會很容易。
The bottom line is that even if you have an extensive suite of automated tests for an English language product, this might not speed you very much when testing a translation.
本地化的底線是，即使你為一個英文版產品創建一個自動化測試擴展套件，它也能夠讓你非常迅速地測試一個譯本。
文章來源于領測軟件測試網 http://www.kjueaiud.com/
