When you are looking at complex translation workflow systems with a high degree of process automation, testing becomes an essential part of the implementation process.
By this, you can thoroughly check all required functions, fix errors and optimize the system before going live.
A new translation workflow system is usually implemented by the company’s IT department. Standard features are combined with customer-specified features in order to meet the special needs of the company. While the standard features do not need to be tested, all customized features have to be thoroughly tested and approved by the specialists’ team. It is only the people who specified the system’s behavior and features who really know what the system should and should not do. With regard to the complex interplay between a substantial number of interfaces (as web portals, authoring systems, publishing systems, terminology management systems), a proper functioning of all components is of high importance. The worst thing that could happen is that you go live with the system and the essential process steps do not work as expected. In this case, you lose data, time and Money.
For testing, a different environment than the production environment is necessary. The environments are usually implemented by the IT department of the company. They are worth the effort because they save time and money at the long term. At the beginning of a project, testing can be performed on an integration environment. There, the system is thoroughly checked and when all functions are working properly it can be updated to the production environment. At a later stage in the project, when updating the system becomes a necessary and regular task, it is very advisable to implement a third environment, the testing environment. There, all new functions can be tested without effecting the integration environment which should remain close to the production Environment.
Image source: Foreman
Workflow Test Management Part II: Test procedure will be posted soon!