 |
|||||||||||||||||
| Homepage >> Service >> Software/hardware testing | |||||||||||||||||
Software/hardware TestingYUTU provides high quality, low cost, efficient testing service to help customer to find out the defects of their product and to guarantee the punctual final version release. YUTU provides software/hardware/website testing services, including (1).Function testingTo test if software, hardware, website and internal application meet with the expected functional requirements, which involved with the following procedure designed to guarantee the localized software and online help to run in the same way of original software.(2).Compatibility testingTo test normal operation of functions under different configurations: Configurations are classified according to customer’s use possibility. Configuration includes combinations of hardware, operation system and application. Compatibility testing starts when deep functional testing and function coding completed. It is composed by multiple subsets of function validation testing, to test the sensitive functional areas or which change according to operation environment (operation system, drivers, application version, etc).(3).Performance testingTo test the performance in the target scope of the product. Performance testing should be implemented as early as possible to guarantee the enough time for modifications. It is usually started when function testing completed, which is between the function coding milestone and Beta milestone.(4).Regression testingTo validate the main defects without recurrence (especially for those remained to be modified currently) and the new defects accidentally generated in code modifications, which are involved with the configurations and many functions. Regression testing can be implemented at any time, but it is better between Beta milestone and Code freeze milestone.(5).Pressure and error testing (pressure and carrying capacity testing)To test if the functions are normal in function edge scope, under abnormal operation conditions and resumption from error status. In this case, there is little possibility to find defects, so this testing is started when functions are normal, usually after Beta milestone.(6).Internationalization testingThe label of “Z Testing” is to show if it can be used all over the world. This testing is to validate if the internationalized version of the system can operates normally, if internationalized system setting is correct, if it can be normally used by internationalized users.(7).Localization testingTo test if the product can be normally used when transferred (not translated) to a version of another language. This testing includes localization support device (embedded code character string, twin byte operation system), normal operation and coherence of localized specific function (such as default paper size, time/date format, phone line characteristics, copy speed problem), appearance and localization resource (user interface, help file, report, etc.). These tests are started when user interface resource completely localized, between Beta milestone and Code freeze milestone.
|
|
||||||||||||||||
 |
|||||||||||||||||
