Mention —coverage-report for dafny test

Source/DafnyCore/Feature.cs

@@ -186,7 +186,7 @@ public enum Feature {
  [FeatureDescription("All built-in types in runtime library", "#sec-compilation-built-ins")]
  BuiltinsInRuntime,
 
- [FeatureDescription("Execution coverage report", "#sec-compilation-built-ins")]
+ [FeatureDescription("Execution coverage report", "#sec-dafny-test")]
  RuntimeCoverageReport
 }
 

docs/DafnyRef/UserGuide.md

@@ -479,6 +479,8 @@ In particular, it accepts the `--target` option that specifies the programming l
 - `--output` - gives the folder and filename root for compilation artifacts
 - `--methods-to-test` - the value is a (.NET) regular expression that is matched against the fully
  qualified name of the method; only those methods that match are tested
+- `--coverage-report` - the value is a directory in which Dafny will save an html coverage report highlighting parts of
+ the program that execution of the tests covered.
 
 The order in which the tests are run is not specified.
 
@@ -1517,7 +1519,8 @@ include a list of proof dependencies (including source location and
 description) alongside every assertion batch in the generated log
 whenever one of the two warning options above is also included. The
 latter will produce a highlighted HTML version of your source code, in
-the same format used by `dafny generate-tests --verification-coverage-report`,
+the same format used by `dafny test --coverage-report`
+and `dafny generate-tests --verification-coverage-report`,
 indicating which parts of the program were used, not used, or partly
 used in the verification of the entire program.