Allow specifying a mapping with source paths for locations in coverage reports

[m-Peter]

Description

Having AddressLocation or StringLocation in coverage reports, is not usable when trying to use these reports with standard tools, such as LCOV. The file path is what is needed to exploit the existing tools dealing with the LCOV format.

The flow.json config file, already defines the source file for all contracts involved in a dApp, e.g.:

{
  "contracts": {
    "ApprovalVoting": {
      "source": "contracts/ApprovalVoting.cdc",
      "aliases": {
        "testing": "0000000000000007"
      }
    },
    "ArrayUtils": {
      "source": "contracts/ArrayUtils.cdc",
      "aliases": {
        "testing": "0000000000000007"
      }
    },
    "FooContract": {
      "source": "contracts/FooContract.cdc",
      "aliases": {
        "testing": "0000000000000007"
      }
    },
    "StringUtils": {
      "source": "contracts/StringUtils.cdc",
      "aliases": {
        "testing": "0000000000000007"
      }
    }
  }
}

---

• Targeted PR against master branch
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work
• Code follows the standards mentioned here
• Updated relevant documentation
• Re-reviewed Files changed in the Github PR explorer
• Added appropriate labels

[codecov]

Codecov Report

All modified lines are covered by tests ✅

Comparison is base (735a071) 79.38% compared to head (6b9d9f2) 79.41%.
Report is 2 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2859      +/-   ##
==========================================
+ Coverage   79.38%   79.41%   +0.02%     
==========================================
  Files         334      334              
  Lines       78826    78930     +104     
==========================================
+ Hits        62576    62680     +104     
+ Misses      13944    13943       -1     
- Partials     2306     2307       +1     

Flag	Coverage Δ
unittests	79.41% <100.00%> (+0.02%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files	Coverage Δ
runtime/coverage.go	94.13% <100.00%> (+0.32%)	⬆️

... and 6 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[turbolent]

Great idea! Only have one concern regarding location clashes

[SupunS]

👍

[SupunS]

👏

[turbolent]

Nice!