I am exploring the possibility of measuring test coverage using the Test Manager and Profiler tools. It appears there are some significant limitations. Has anyone been successful trying to use these tools?
Here are my observed limitations. Am I misunderstanding anything?
* Profiler only works for one "run cycle". Even warm resets will clear the coverage calculations. Thus, all tests would have to manually reset values when complete to prevent contamination to other tests.
* It is not possible to see which statements were/weren't executed. One would have to use the flow control tool which cannot be used in conjunction with the Profiler, and must be viewed in realtime.
* The profiler control cannot be automated and therefore must be executed through a manual procedure.
Thank you!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am exploring the possibility of measuring test coverage using the Test Manager and Profiler tools. It appears there are some significant limitations. Has anyone been successful trying to use these tools?
Here are my observed limitations. Am I misunderstanding anything?
* Profiler only works for one "run cycle". Even warm resets will clear the coverage calculations. Thus, all tests would have to manually reset values when complete to prevent contamination to other tests.
* It is not possible to see which statements were/weren't executed. One would have to use the flow control tool which cannot be used in conjunction with the Profiler, and must be viewed in realtime.
* The profiler control cannot be automated and therefore must be executed through a manual procedure.
Thank you!