Break - do not build? In fact this is not true. When your task is to check the operation of the program on incorrect data, it becomes necessary to introduce intentional damage to the files.
For OfficeRecovery,
recovering corrupted data is the main activity. Therefore, it is very important for us to have an extensive set of faulty test files. For these purposes, the FileCorrupter utility was developed, which we offer to everyone for free.
Usage example
When developing software, one often comes across situations where users complain that an application crashes when they try to open a file.
')
Often this situation arises due to incorrect data in the file. Although your program code may not be to blame for the fact that the input data has been corrupted, the best behavior on the part of the application would be to detect the invalid input data and give an adequate error message.
To make sure that your application correctly handles errors, you can suggest that it open a file that was previously corrupted with FileCorrupter.

Opportunities
FileCorrupter can “beat” files as in simple “Simple Mode” mode, where a certain percentage of file blocks are randomly beating. There is also a “Professional Mode” where you can set various parameters for damage: the value by which blocks will be rubbed, offset, etc.
Use wisely
The utility does not claim to be a complete product. It was implemented exclusively for solving internal tasks and is intended for use by professional programmers and testers who understand what they are doing.
A warning! Before you spoil the data, consider properly whether you have a backup of what you are going to spoil. OfficeRecovery is not responsible for the results of using FileCorrupter. The program is provided "as is". By downloading it, you assume full responsibility for the consequences of its use.Download:
OfficeRecovery FileCorrupter.exe, 1.7Mb .
We hope that FileCorrupter will benefit in developing your products.
Are you testing the performance of your products on invalid input data?