You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This for Windows, on Linux/Mac you would do the equivalent
$env:LLVM_PROFILE_FILE = "code_coverage.profraw"
Then run the executable.
Running the executable will generate the raw profile data for you. Then you can specify where that goes using the environment variable modification you did previously.
Convert the .prof raw data to .profdata
Using .profdata is used for processing the raw data into a report, merging that file into a more readable format. This is essentially how you'd might index it:
Code coverage is really important to know which parts of your code has been tested and which part hasnt been tested.
The goal for this task is simply to just add these instructions to the webpage specifically in the
User Guidesection for ease.Instructions for Creating a Code Coverage Report
Set Compiler Flags to Using Code Coverage
Note
I may implicitly add this to cmake-utils to implicitly add this to the CMake.
Edit environment variable
This for Windows, on Linux/Mac you would do the equivalent
Then run the executable.
Running the executable will generate the raw profile data for you. Then you can specify where that goes using the environment variable modification you did previously.
Convert the .prof raw data to .profdata
Using
.profdatais used for processing the raw data into a report, merging that file into a more readable format. This is essentially how you'd might index it:Tip
for llvm-toolchain, it would be /llvm-cov
Generating HTML Coverage Report
As soon you process the file, you should get something like
code_coverage.profdata. Then you use the commands shown below.To generate an HTML of the code coverage report that can be viewed in the browser.
If this was to be executed for TheAtlasEngine editor, it would look like: