js editor
Web development
By default the Coverage Profiler application runs in a separate window. You can reconfigure it to run inside the main Visual FoxPro window by changing the Environment Option. In the Coverage Profiler Options dialog box, change the Environment selection from Coverage frame to FoxPro frame, and then restart the Coverage Profiler.
You can also use the Coverage Profiler Options dialog box to modify the following Coverage Profiler characteristics.
| Characteristic | Description |
|---|---|
|
Add-Ins |
Specifies whether Add-Ins are registered in the Coverage Profiler as they are used. For more information, see the section, "." |
|
Coverage Marks |
Specifies whether the Coverage Profiler marks code that is run or code that is not run. Specifies the character(s) used to mark code. Specifies when code is marked. |
|
Fonts |
Specifies the fonts used in the Coverage Profiler as code and in displays. |
|
Smart Pathing |
Specifies whether Coverage Profiler automatically seeks files in previously specified locations. |
|
Start Mode |
Specifies whether Coverage Profiler opens in Coverage or Profile Mode. |
Ensuring Relevance in the Coverage Profiler
To help ensure that the files processed by the Coverage Profiler are the correct files:
-
Set your project directory as the default before you start coverage logging so that the referenced files are relative.
-
Avoid renaming objects dynamically. The Coverage Profiler will not find objects if you rename them at run time.
-
Avoid using source files with exactly the same root name, even with different extensions. Internally, the Coverage Profiler cannot distinguish between them.
-
Make sure that your project contains only the correct versions of much-modified files.
-
Make sure your project does not contain multiple copies of a file in subdirectories.
-
Perform a compile for the coverage run:
-
Make sure Debug information is in your application.
-
Turn Encrypt OFF.
-
Use RECOMPILE or Build All to force a fresh compile of all source code.
-
Perform the compile immediately before the coverage run so that you know that the source code exactly matches the object code.
-
Make sure Debug information is in your application.
Some lines in code, such as comments, DEFINE CLASS and ELSE statements, and lines within TEXT ... ENDTEXT do not appear in coverage logs because they are not even potentially executable. Also, lines broken by continuation symbols (semicolons) are considered as a single line of code and marked only on the last line.