Print DotNet Test Results even if successful (#236)

* Print DotNet Test Results even if successful

* Formatting Markdown

---------

Co-authored-by: Tom Longhurst <thomhurst@users.noreply.github.com>

Author: thomhurst

docs/_sidebar.md

@@ -10,6 +10,7 @@
   - [Execution and Dependencies](getting-started/execution-and-dependencies "Execution and Dependencies")
   - [Sharing data across modules](getting-started/sharing-data "Sharing Data amongst Modules")
   - [Storing and Retrieving Results](getting-started/storing-and-retrieving-results "Storing and Retrieving Results")
+  - [Custom commands](getting-started/custom-commands "Custom commands")
   - [Analyzers](getting-started/analyzers "Analyzers")
   - [Logging](getting-started/logging "Logging")
   - [Secrets](getting-started/secrets "Secrets")

docs/getting-started/custom-commands.md

@@ -0,0 +1,19 @@
+# Custom commands
+Many common CLI tools, such as npm, yarn, dotnet, docker, kubectl, have all had strong objects created to wrap around their CLI commands.
+
+If you want to run a command that isn't currently supported by strong objects, you can still run commands directly through the `ICommand` interface available on the `context` object within your modules.
+
+Every argument should be passed as a separate string in a collection. This allows proper formatting if there's things like spaces or quotes.
+
+## Example
+
+```csharp
+await context.Command.ExecuteCommandLineTool(new CommandLineToolOptions("dotnet")
+        {
+            Arguments = new[] { "tool", "install", "--global", "dotnet-coverage" },
+        }, cancellationToken);
+```
+
+This is the equivalent to running:
+
+`dotnet tool install --global dotnet-coverage`

src/ModularPipelines.Build/ReleaseNotes.md

@@ -1 +1 @@
-null
+*   Print DotNet Test results if successful

src/ModularPipelines.DotNet/DotNet.cs

@@ -1,6 +1,7 @@
 using System.Diagnostics.CodeAnalysis;
 using Microsoft.Extensions.Logging;
 using ModularPipelines.Context;
+using ModularPipelines.DotNet.Enums;
 using ModularPipelines.DotNet.Exceptions;
 using ModularPipelines.DotNet.Options;
 using ModularPipelines.Extensions;
@@ -86,6 +87,12 @@ public async Task<DotNetTestResult> Test(DotNetTestOptions options, Cancellation
             throw new DotNetTestFailedException(result, parsedTestResults);
         }
 
+        var success = parsedTestResults.UnitTestResults.Count(x => x.Outcome == TestOutcome.Passed);
+        var failed = parsedTestResults.UnitTestResults.Count(x => x.Outcome == TestOutcome.Failed);
+        var skipped = parsedTestResults.UnitTestResults.Count(x => x.Outcome == TestOutcome.NotExecuted);
+
+        logger.LogInformation("DotNet Test Results - Success: {Success} - Failed: {Failed} - Skipped: {Skipped}", success, failed, skipped);
+        
         return parsedTestResults;
     }