FluentAssertions
FluentAssertions for Unity brings expressive, readable assertions to your test suite. Based on the popular FluentAssertions 6.8.0 library, this package enables developers to write more maintainable unit tests with fluent syntax that reads like natural language. Compatible with Unity 2021.2+ and .NET Standard 2.0.
com.boundfoxstudios.fluentassertions 
Install via UPM
Add to Unity Package Manager using this URL
https://www.pkglnk.dev/fluentassertions.git#upm README Markdown
Copy this to your project's README.md
## Installation
Add **FluentAssertions** to your Unity project via Package Manager:
1. Open **Window > Package Manager**
2. Click **+** > **Add package from git URL**
3. Enter:
```
https://www.pkglnk.dev/fluentassertions.git#upm
```
[](https://www.pkglnk.dev/pkg/fluentassertions)README
Fluent Assertions for Unity
This package contains the current version of FluentAssertions 6.8.0 ready to use with Unity.
If you encouter any bugs, which are related to the package and not to FluentAssertions itself, feel free to open an issue.
For more information about FluentAssertions itself, please head over to https://fluentassertions.com.
Pre-requirements
- Unity 2021.2 or newer
- .NET Standard 2.0 scripting backend
Installation
OpenUPM
The package is available on the openupm registry. It's recommended to install it via openupm-cli.
openupm add com.boundfoxstudios.fluentassertions
Unity Package Manager
Window -> Package Manager -> + sign -> Add via git url:
https://github.com/BoundfoxStudios/fluentassertions-unity.git#upm
Setup
Then, reference FluentAssertions in your test's assembly definition and you are good to go!
Troubleshooting
If you get the following error:
The type or namespace name 'DynamicMethod' could not be found (are you missing a using directive or an assembly reference?)orThe type or namespace name 'ILGenerator' could not be found (are you missing a using directive or an assembly reference?)
then you need to define the following scripting symbol (Edit -> Project Settings -> Player -> Other Settings -> Scripting Define Symbols): NETSTANDARD2_0.
Wait for Unity to recompile, the error should be gone then.
If not, please open an issue.
Credits
All credits go to FluentAssertions for creating an excellent library to make Unit Testing more readable and maintainable.
No comments yet. Be the first!