To use as the Expecto test adapter, add the following dependencies to your project:
Microsoft.NET.Test.Sdk
YoloDev.Expecto.TestSdk
If you're using the dotnet CLI, and it's built in package management, the following commands can be used to achive that. References can also be added using visual studio NuGet browser, or paket.
dotnet add package Microsoft.NET.Test.Sdk
dotnet add package YoloDev.Expecto.TestSdkIn addition, it might be necessary to disable the automatic generation of
a program.fs file by msbuild, depending on your target framework. To do
so, set GenerateProgramFile to false in the fsproj file, as seen bellow:
<PropertyGroup>
<GenerateProgramFile>false</GenerateProgramFile>
</PropertyGroup>To get the tests working in the Visual Studio test explorer, it's recommended to target
netcoreapp2.2 or newer with your test projects. Others might work, but people have
had problems with them.
You can configure some of Expecto via dotnet test. dotnet test allows you to pass in RunSettings via the CLI or using a .runsettings file.
From dotnet test cli help:
RunSettings arguments: Arguments to pass as RunSettings configurations. Arguments are specified as '[name]=[value]' pairs after "-- " (note the space after --). Use a space to separate multiple '[name]=[value]' pairs. See https://aka.ms/vstest-runsettings-arguments for more information on RunSettings arguments. Example: dotnet test -- MSTest.DeploymentEnabled=false MSTest.MapInconclusiveToFailed=True
Many of the ExpectoConfig settings are settable via the CLI or using a .runsettings file. This test adapter uses the naming from Expecto's CLI arguments (without the leading --), namespaced with Expecto.. Additionally, any args that are switches must take a boolean value.
dotnet test -- Expecto.parallel=false Expecto.fail-on-focused-tests=true Expecto.stress-memory-limit=120.0
