Monthly Archives: January 2006

do you want to refine your code for performance and ensure that you've adequately tested the code?

the easiest way to track wich lines of code have been executed and how long it took to execute them is logging code coverage information.

this information can help you identify areas of code that aren't being executed and therefore aren't being tested, as well as areas of the code that you might want to fine tune for performance.

you can toggle coverage logging on and off programmatically (at design time and runtime) by using the set coverage to command.

you could, for example, include… Continue reading