In the the last part of our testing blog series we look at testing phases and error-tracking. It is generally advisable to plan for a minimum of three testing phases: The initial testing phase, the re-testing phase and the approval testing Phase.
In the initial testing phase, you may expect a larger quantity of failed test cases, which need to be reported for bug fixing. The system supplier then fixes the reported errors. Bug fixing time should be pre-defined in order to keep to the scheduled testing time.
Depending on the number of test cases, tracking errors and bug fixing status can become tedious and confusing in xls-tables. A web-based error tracking system is extremely helpful because everybody working with the system can enter and track errors no matter where they are located. Another plus, there is no need to write e-mails about the status of bug-fixing or track the progress manually as the system automatically informs the relevant people when there is a new error or a change in status. If you already do have an error tracking system at your company, use this. Otherwise, ask your system supplier – ideally before starting the project – if they have a usable error tracking system available.
With bugs fixed, you will start re-testing and depending on the number of errors found in your re-testing phase you might want to think about having a second re-testing round before approval. Your approval testing phase should be started when only a small number of insignificant or easy to fix errors are found and you are confident that your supplier will have everything fixed and ready for final approval.
No matter which phase of the testing project you are in, be it the creation of test scenarios and cases, the initial or following test phases: The specialists, who specified the system and/or the changes should be involved in any approval activity. Only then, it is guaranteed that the tests really check the relevant features and system behavior and the system works as it should.
Well begun is half done
Whatever you want to achieve with your translation workflow system – thoroughly planned test environments and processes will definitely help you get smooth translation workflows up-and-running. If you want to save money on the long run, you might want to think about investing more time and resources in your test management. In the end, system failure and data loss during an important localization project are not only a nuisance but can be very costly indeed.