Opencover allows hiding skipped modules by providing a `hideskipped parameter. Would be great to add this.
See https://github.com/OpenCover/opencover/wiki/Usage#console-application-usage for details.

When running build.ps1 -t Test, the following output describes the failing tests:

1. Failed : NUnit.Framework.Api.FrameworkControllerTests.ExploreTestsAction_FileNotFound_ReturnsNonRunnableSuite
   Expected: String containing "The system cannot find the file specified."
   But was: "Le fichier sp├®cifi├® est introuvable. (Exception from HRESULT: 0x80070002)"
   at NUnit.Framework.Api.Framew

We definitely should create two new guild for FsUnit site

• FsUnit + FxCheck + NUnit
• FsUnit + FsCheck + XUnit

// sideeffffect/FSharpHello#1 (comment)

It seems that some people cast the elements returned by Find and FindAll to their specific AngleSharp subtypes and then try to invoke event handlers that way. We can either warn them about their mistake thought an helpful exception or simply trigger the event handler.

Update Scenario State Management page with example from: https://gist.github.com/Suremaker/10b2f05c844fe2e657f74b647a7074be

https://docs.microsoft.com/nuget/nuget-org/deprecate-packages

Nuget.org's package deprecation functionality is now available. 😄 We should make use of it for our two deprecated packages.

I'm trying to include an NBi test project in a Visual Studio Team Services pipeline. I create a project locally using the bootstrapper, upload it to Git and I get the following output:

2018-08-06T08:56:51.7007856Z ##[section]Starting: Run Test Scenarios
2018-08-06T08:56:51.7017845Z ==============================================================================
2018-08-06T08:56:51.7018173Z

Regarding the install instructions using .NET Core templates and the package name:

Execute dotnet new -i Meissa.Windows (this will install the template)/
Execute dotnet new Meissa.Windows (this will extract all tool’s files to the folder)

The instructions should be updated as the nuget package name is Meissa.Windows64.

Thanks,
Howard

In the overview we should also have information about the Severity of each analyzer and whether we have a codefix associated with the analyzer. As this could take up most of the horizontal space we could do using icons similar to the approach taken in the README.md in https://github.com/wachulski/nunit-migrator.

Also we should perhaps partition the analyzers in index.md into sections with headi

Add Boolean silent flag - if true report log will not be written to HTML report log - same as we have in the old reporter

NUnit adds/removes command line arguments and not all of them are supported by plugin.
https://github.com/nunit/docs/wiki/Console-Command-Line
I'm interested in "--agents" and "--labels".
However instead of adding support for this specific argument I think It would be useful to have possibility to modify command line right before project.exec and inject any argument.