1. TVT profile and its current major difficulties, bottlenecks
Translation Verification Testing (translation verification TESTING,TVT) is one of the most important tests in IBM's globalization testing, typically by translators from the TSC (translation Service Centers) and from GSSC TSE (translation Service Engineer) to complete the cooperation. TVT's main job is to verify that the translated PII (program integrated information) characters are correctly displayed in the appropriate interface after recompiling the SOFTWARE PRODUCT, building a build, or integrating with other software products. Instead of having some changes or errors. At the same time, translators make some necessary character modifications during the testing process to further improve the consistency and accuracy of the software products.
During the TVT process, translators must go through a series of steps to find the appropriate UI interface to test the PII character content appearing on each interface, which is often provided by TSE. Since a software PRODUCT is often translated into many languages, so TVT test will often need to install a variety of different languages to test the environment, many can even reach 20 languages, if a project a large number of cases, many projects are hundreds of cases, then the workload is very large. At present, there are three kinds of TVT form, the first is online form of the test, refers to the TSE personnel prepare all the case, and then the translator according to the steps indicated by the situation to run, find the corresponding interface and then do validation. The second is the screen Capture form, refers to TSE to run out of the case, and then cut the corresponding interface, and finally all cases in the form of pictures to the translator to verify. The last one is the combination of the former two, simple case by tester, the complex case by TSE help to the translator to verify the screenshot. Because if let tester directly see picture verification can greatly improve efficiency, and simple and convenient, so screenshot mode of TVT in the current GSSC Department of higher utilization rate, many case number of items often choose this model. As a result, the workload of TSE staff increased, and the same case in different language screenshots, the basic is repetitive work, and manual screenshots take into account the efficiency of the people, a day screenshot is limited, if the relevant automated screenshots can reduce the duplication of labor.
2. Screenshots of the effects and advantages of the process to play a role
The TVT process typically has a tricycle to improve the quality of the software product by making it relevant to the problem or changes that are discovered during the test. At the same time, in the process of TVT, due to the limited knowledge of product or software, translators often spend a lot of time in communication with TSE people. If you use screenshot mode directly, then all activities become very concise. Translators are responsible for translating the relevant content and verifying that the translated content appears correctly through the truncated pictures. This reduces the number of case steps between the TSE and the staff, reduces the waste of time and improves efficiency, and the translator sees a picture that is more efficient than running a case before. You can probably see more than 5 pictures in the time of running a case. In this way, the operation process of the translator becomes very simple, and compared with the previous process, it eliminates the coupling between the TSE and the lower flow. The operation is also more convenient than the TSE staff, and it does not take extra time to teach the translator how to run the case and how to solve the problem.
3. Deficiencies in the current range of automation programmes
At present, there are many automation solutions in the process of TVT, many of them have their unique performance and advantages, but they also have some limitations. For example, the use of Selenium automated screenshot scheme, the project in Browser based on the use of a significant effect, can give TSE people a lot of convenience, write a script, you can reuse, interception of many different languages of the corresponding case picture. However, compared to IBM products without Browser, Selenium is difficult to use, while many IBM products are not based on Browser, many things are based on Eclipse kernel products, such as many Rational products, so the scope of use is limited.
Part of the solution is to automate the TVT project by improving the FVT and GVT test scripts before using the project. However, since many projects themselves do not have FVT or GVT test scripts, so this kind of project can only be ignored, and after the actual project test will find that the number of projects using test scripts is not much, while there is a process of organizing, improving and debugging the script, so using this method to operate TVT Automation also has some limitations.
4. Introduction to SnagIt and integration with RFT
4.1. SnagIt Introduction
SnagIt is a very good image, video, text interception and editing software. This program captures the Windows operating system screen while editing the captured pictures. TVT Screenshots can use this tool to take a screenshot at the same time to the characters on the picture to do the corresponding tag to tester to verify.
This section mainly utilizes the RFT and snagit to use together to realize in the TVT process, as simple and convenient realization screenshot. The main principles are as follows:
Figure 1. Task process