You can save the current record of what code has been covered to a file, and then merge that information back to the current display. This can be useful in at least two situations:
• If you are working as part of a team, each team member can test a different part of a large application and save their code coverage history to a file. These files can then be collected together and merged into one display to provide a complete picture of what code and variables have been used in an application
• You may wish to reset the counters to zero before running a test, but not want to lose your current code coverage information. You can save the current code coverage information to a file before performing the reset, then, once you have finished your test, merge the code coverage information back into the current display.