Inconsistent behaviour when using coverage feature.

[paro-paro]

Hi,

I am facing some inconsistent behavior when using graph test --docker --coverage feature.

By inconsistent I mean that I am getting different results on different use cases and have not being able to debug it down to an specific case. As a result, the coverage command output will not properly (and consistently) report all the handlers that are being tested within test files.

Since this info is not quite helpful, here is a "minimal" reproduction showcasing my current use case (more details in the README) where two handlers are being tested from the same test file (properly exported) and the coverage output will only report one of them.

Environment:

  "dependencies": {
    "@graphprotocol/graph-cli": "^0.69.0",
    "@graphprotocol/graph-ts": "^0.34.0",
    "matchstick-as": "^0.6.0"
  }

• macOS M2 pro

I am running graph test through docker (which is working perfectly fine) since the local os-m1-binary was not throwing any errors on failed tests (I believe this is a known issue, as stated in other issues and also the releases notes).

Any help will be appreciated (awesome tool btw)!

Thanks in advanced

[dimitrovmaksim]

Hey @paro-paro, unfortunately coverage has always been finicky because of the WASM and the way we get is is somewhat hacky and so far we haven't found a more reliable way to get the coverage.

[paro-paro]

Hi @dimitrovmaksim

Got it! Thanks a lot for the clarification.