Functional Testing

Functional testing is conducted to test whether customer’s software, website or internal applications satisfy the expected functional needs. It involves a series of processes especially designed to make sure that the localized software, online help and the software of the original version are run in the same way. 

Compatibility Testing

Compatibility testing is conducted to verify normal operation of the functions in different configurations: Configurations are grouped into a list of hierarchy in accordance with the customer’s usage possibility. They include different combinations of hardware, operating systems and application software. Compatibility testing is conducted after the completion of depth function verification and the completion milestone of functional codes. Compatibility testing is made up of several function verification test subsets. It focuses on the tests on the functional areas that are sensitive or will be changed with the operating system (for example, in the cases of changes in the versions of the operating systems, drivers and application software).

Performance Testing

These tests are conducted to verify the performance of the products within the decided target range. Performance testing should be conducted as early as possible in order to make sure that there will be enough time for adjustment. Often, performance testing is implemented between the completion of the milestone of functional codes and the Beta milestone, commonly after functional testing is completely finished.

Regression Testing

Regression testing is conducted to verify those main faults that don’t appear any more (especially those that have been left to be repaired in the current stage) and the new faults that accidentally appear when you are modifying codes. All those faults are related to many configurations and functions. Regression testing can be conducted at any time. But it is mostly important that the test is conducted between the Beta milestone and the freezing of the code milestone.

Pressure and Error Testing

Pressure and error testing is conducted to verify whether the functions are in normal operation in those cases of recovery within the marginal functional range, under normal running conditions and under different error conditions. In those cases, there is little possibility that the faults can be found. Thus this kind of testing is conducted after the functions are in normal operation, which is generally after the Beta milestone.

Internationalization Testing

It is generally labeled with a “Z Testing”, and is used to verify whether the products can be used worldwide. This testing is conducted to verify whether the internationalized version of the system is in normal operation; whether the settings of the internationalized system are correct; and whether those settings can be normally used by internationalized users.

Localization Testing

Localization testing is conducted to verify whether the products can be put into normal operation after they are transformed (not translated) into another language version. Localization testing is conducted to verify localization supports (embedded code strings and DB operating systems); the normal operation and consistency of the specific functions customized for localization (such as default paper size, time/date format, line features and copy speed barrier); and the contents of the appearance and localization resources, such as user interfaces, help files, reports and so on. These tests are conducted after the user interface resources are fully localized, which is especially between the Beta milestone and the freezing of the code milestone.