120 e-Business Globalization Solution Design Guide
2. Test environment building
When coding is complete, the testing team sets up the test environment with the aid of the
coding team. The test environment should be identical to that of the actual application
runtime environment.
3. Testing focuses
During the testing period, open and instant communications between the coding and
testing teams are absolutely essential. Whenever the testing team finds any problem, it
should inform the coding team immediately so that it can make a fix as soon as possible.
In our working example, testing focused on the following:
– Function testing
– Translation testing
– Globalization feature testing
– Linguistic service testing
– Browser testing
– Usability testing
In the following sections, these six testing focuses are explained in detail.
16.1 Function testing
One advantage of a well-designed and developed globalized application is that function
testing is unnecessary for every localized version. Since all language versions use the same
set of programs (the Single Executable
1
), we have good reason to assume that a localized
version should work exactly in the same way as the source language product in business
functions. Therefore, only the source language version must undergo all function testing
cases in order to ensure basic functional competence.
The following example from Our Global Travel Shanghai Demo testing checks whether the Air
Ticket Search function works correctly in the source language version:
1. Start your browser and visit Our Global Travel Shanghai Demo home page.
2. Verify that the home page is displayed.
3. From the home page, click the Flights link on the menu bar.
4. Verify that the Flight Search page is displayed as shown in Figure 16-1 on page 121.
1
See 15.1, “Single Executable” on page 92.