Cucumber Test Explorer

Features

• Test Explorer for Cucumber

Prerequisites

• .NET Core is installed
• NUnit and MSTest requires a dotnet sdk version of >= 2.2.104.

Usage

Open your repository that has cucumber tests in it, and it should find the tests for you.

Important

This extension is a fork of formularhendry's extension and therefore I might not have updated everything correctly in the README.md, etc. It should work for only Cucumber tests, but the original extension works for all .NET Core tests.

Stopping the current test runner(s)

Press the stop button in the top menu. This also works as a reset of sorts so if the extension has managed to end up in a weird state where it thinks a test is running even though it is not or that the debugger is running even though it is not the stop button can solve these types of issues as well.

Logging

Text from the dotnet test output as well as debug info is written to the Output/Test explorer terminal window. To view the log you can access it simply by clicking the view log icon.

Keyboard shortcuts

• Run all tests, default Alt+R Alt+A

• Rerun last command, default Alt+R Alt+R

• Run test(s) in context, default Alt+R Alt+C

Known issues

Go to test does not work with multiple workspaces

This is because of limitations in the omnisharp extensions. We can only navigate to symbols which are in the currently selected workspace.

Test result is not shown in CodeLens / tree

Try and change the setting cucumber-test-explorer.pathForResultFile to point to a folder you have access right too. CodeLens functionality also requires the C# extension

No tree view or color-coded explorer for NUnit / MSTest

This requires you to run dotnet SDK version 2.2.104 or higher.

xUnit projects assembly name needs to match the test class namespace

See #201

DisplayName attribute not working for xUnit

See #56

Project discovery with UNC Paths doesn't work

See #179