lostluck commented on issue #21392:
URL: https://github.com/apache/beam/issues/21392#issuecomment-1408710509

   Go coverage is pretty easy to get, as it's built into the existing tools. 
https://go.dev/blog/cover. It's not mentioned in Beam docs because it's not a 
beam doc specific issue, since it's so well integrated into Go.
   
   Running the unit tests for a whole package in VSCode with the official Go 
plugin will by default provide code coverage, providing a percentage for the 
package, and line by line highlighting of covered lines.
   
   My recommendation though is to pick a different package for which to add 
more tests. The direct runner replacement I'm working on will make it much much 
easier to get better coverage numbers for the graphx and exec packages, and 
that should be landing soon! :D


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to