FluentAssert | Fluent interface for C # NUnit assertions | Assertion library

I am trying to write a set of tests for an API which returns a result in the following form

I did a recent migration of my company's legacy app from packages.config to PackageReferences. We have 5 projects: the main ASP.NET web app, a SQL connector model project, an xUnit test project, a FluentAssertions test project, and a SpecFlow project (and no I did not set this all up). My current goal was to move all of the packages.config to properly use NuGet in PackageReference in the csproj files for an eventual move from .NET Framework 4.6.1 to .NET Core. Unfortunately, we are not ready for such a move yet.

I have done the migration for all the projects. With some fiddling, all of them build and most run correctly. Our web project builds and runs (we still need proper smoke testing but it looks good so far). Our FluentAssertions and XUnit projects also build and run all of their tests flawlessly. We do have some warnings, but there is less of them then there was before this migration.

What is not working is the SpecFlow tests. Specifically, the SpecFlow tests are not being populated in the Test Explorer automatically in Visual Studio 2019. They were before this migration. We need these tests to run (for now) in our automated build process. We are fixing our technical debt in stages.

I have investigated online for the past couple of days and can make the following claims about our SpecFlow project:

1. We have NUnit3 added in the Extensions and it appears to be "functioning". Same with SpecFlow for Visual Studio 2019 extension.
2. We have all of the NUnit3, MSTest, and SpecFlow NuGet packages from before the migration (in the same versions) as NuGet references post-migration.
3. If I run the tests from the project's context menu, it says there are 0 tests run.

With FluentAssertions 6 it seems you can longer verify if in a object graph if an Enum is equivalent to a string. Source: https://fluentassertions.com/upgradingtov6

I have a test fixture for my CompositionRoot static class that pretty much just enumerates my Autofac IContainer's services and attempts to instantiate them. If it can instantiate them, that's a test pass. The goal is to ensure I did not forget to register new interfaces with my Autofac container.

However, some types that are registered consume types in their constructors that are not intended to be, or cannot be, registered with Autofac. For example I have a class that takes a string in its constructor. The way I inject this class into my code base is:

I came to know that through FluentAssertions library we can combine multiple assertion in a single like. Just want to know if below 2 assert can be combined in a single line?

I feel like I'm taking crazy pills here... but how can I compare two JsonDocuments (or JsonElements or what have you) for JSON equality, i.e. same keys with same values?

To limit the scope, the ability to perform this comparison in a unit test is sufficient unto the day.

I have a unit test in which I want to compare the result of a function that returns a JsonDocument to some expected value. Things that don't work include using FluentAssertions.Json (because my type is not JObject), and comparing the value of GetRawText because I don't care about the whitespace.

I guess I could write the strings out and re-serialize them or something but this honestly feels like such a hack that I must be doing something wrong.

I understand the business logic of comparing them, I have seen the other questions like this and this. The first is much more in keeping with what I want, it's just an embarrassing result for C#... The second is not what I need at all.

Good day/evening! I am trying to do a test program in xUnit with the following code in Visual Studio Code:

The following Func delegate throws an ArgumentNullException:

I'm using xUnit and FluentAssertions to write an integration test to validate that our models are correctly mapped. We have dozens of EF contexts and for each context, there are one or more DbSet<> properties like this: