Logo Questions Linux Laravel Mysql Ubuntu Git Menu

AutoFixture in F# UnitTest Project Not Displaying Unit Tests in Test Explorer

I have a Visual Studio 2012 Project and the following NuGet Packages installed:

  • AutoFixture with Auto Mocking using Moq
  • Autofixture with xUnit.net data theories
  • AutoFixture
  • Moq
  • xUnit.net: Extensions
  • xUnit.net: Runners
  • xUnit.net

Given the following contrived Logger class (Logger.fs):

namespace FUnit

type public ILoggerContext =
    abstract member LogPath :string

type public LoggerContext (logPath :string) =
    member val LogPath = logPath with get, set

    interface ILoggerContext with
        member this.LogPath = this.LogPath

type public Logger () =
    member this.Log (context: ILoggerContext) value =
        System.String.Format("Logged {0} to {1}.", value, context.LogPath)

and the following unit test:

namespace FUnit.Test

open FUnit

type public Math_Add() = 

    member this.``Should Output Value And Path`` (path :string) =
        let context = new LoggerContext(path)
        let logger = new Logger()

        let expected = System.String.Format("Logged value to {0}.", path)
        let actual = logger.Log context "value"

        Xunit.Assert.Equal<string>(expected, actual)

The Test Explorer does not recognize the unit test after ensuring I'm showing all tests and building the project. The project builds correctly with no errors or warnings in the Build, General, or Test output logs.

If I replace the current Theory and AutoData attributes with an Fact attribute, the test shows up.

Is AutoFixture supported in F# test projects? Can anyone else replicate this and know what I'm doing wrong?

like image 966
Joshua Belden Avatar asked Mar 25 '23 02:03

Joshua Belden

1 Answers

I think this is an issue with conflicting versions of Xunit.Extensions used by Ploeh.Autofixture.Xunit and the test runner.

If you run the tests using Xunit's runners then you should see an exception complaining about not being able to find a specific version of Xunit.Extensions.

You can fix this by adding binding redirects to your test projects app.config. Since you're using NuGet you can have it generate the binding redirects by running this in the Package Manager Console for your test project.


You can then tweak the generated binding redirects in app.config to be more specific if you want.

Once you rebuild the project you should see the test appear in VS Test Explorer.

like image 55
Leaf Garland Avatar answered Apr 25 '23 12:04

Leaf Garland