From 4b6c1e134b90309d8eafa1cad72e1fc413649fb1 Mon Sep 17 00:00:00 2001 From: Jatin Garg <48029724+jatgarg@users.noreply.github.com> Date: Thu, 3 Oct 2024 19:21:37 -0700 Subject: [PATCH] Update build-tools/packages/build-cli/docs/codeCoverageDetails.md Co-authored-by: Tyler Butler --- build-tools/packages/build-cli/docs/codeCoverageDetails.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/build-tools/packages/build-cli/docs/codeCoverageDetails.md b/build-tools/packages/build-cli/docs/codeCoverageDetails.md index 16db0beee1e1..576ba3b6d1ad 100644 --- a/build-tools/packages/build-cli/docs/codeCoverageDetails.md +++ b/build-tools/packages/build-cli/docs/codeCoverageDetails.md @@ -22,7 +22,7 @@ Before running coverage comparison, a baseline build needs to be determined for ### Downloading artifacts from baseline build -Once the baseline build is identified, we download the build artifacts corresponding to the `Code Coverage Report_{Build_Number}` artifact name for this build. We unzip the files, and extract the coverage metrics out of the coverage reports using the helper `getCoverageMetricsFromArtifact`. Currently, we track `lineCoverage` and `branchCoverage` as our metrics for reporting but only use `branchCoverage` for success criteria. The final structure of the extracted metrics looks like +Once the baseline build is identified, we download the build artifacts corresponding to the `Code Coverage Report_{Build_Number}` artifact name for this build. We unzip the files and extract the coverage metrics out of the coverage reports using the helper `getCoverageMetricsFromArtifact`. Currently, we track `lineCoverage` and `branchCoverage` as our metrics for reporting but only use `branchCoverage` for success criteria. The final structure of the extracted metrics looks like the following: ```typescript /**