Скачать или смотреть How to Use FluentAssertions Without Throwing Exceptions

Discover how to utilize `FluentAssertions` effectively in test harnesses without triggering exceptions, providing clear output for QA teams.
---
This video is based on the question https://stackoverflow.com/q/62664989/ asked by the user 'Vaccano' ( https://stackoverflow.com/u/16241/ ) and on the answer https://stackoverflow.com/a/62675195/ provided by the user 'Dennis Doomen' ( https://stackoverflow.com/u/253961/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: FluentAssertions without exceptions?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Using FluentAssertions Without Exceptions: A Guide for QA Teams

When building a test harness, especially for non-programmers like a QA team, clarity and simplicity are paramount. Those who are deep into the programming realm often rely on FluentAssertions, a popular .NET library for writing clean and readable unit tests. However, one troublesome aspect can arise when test assertions lead to exceptions, potentially making it harder for non-developers to understand the output. This begs the question: Is there a way to get helpful output from FluentAssertions without encountering exceptions?

The Problem at Hand

For those in a quality assurance environment, automating manual tests while maintaining clarity can be challenging. A team member expressed concern over their need for a user-friendly output from FluentAssertions during testing. They wanted to avoid the noise created by exceptions, primarily due to two reasons:

Clarity: Non-programmer QA team members need to easily interpret test results without confusion.

Simplicity: Reducing the complexity of test code helps prevent misunderstandings.

Solution Overview

Fortunately, there are a couple of solutions within the FluentAssertions framework that allow for generating fluent messages without throwing exceptions. Here’s how to accomplish this:

1. Customize Exception Handling

One workaround involves modifying how FluentAssertions handles exceptions. By replacing the property responsible for throwing exceptions, you tailor the reporting. This approach lets you define custom behavior for output instead of allowing the default exception management to take over.

Implementation Steps:

Replace the Services.ThrowException property with a custom behavior.

This behavior could output messages in a format that's friendly to your QA team.

2. Use AssertionScope's Discard Method

Another effective technique is to utilize the AssertionScope class's Discard method. This allows you to collect assertions without triggering exceptions, meaning you can still gather useful information about what failed, while simply discarding the exceptions.

How to Use Discard Method:

Wrap your assertions within an AssertionScope.

Instead of allowing an exception to be thrown, instruct the method to discard the exceptions and instead log or return a string with the assertions' results.

Here's a small example of what that could look like:

[[See Video to Reveal this Text or Code Snippet]]

Summary and Final Thoughts

By implementing these strategies, you can not only retain the power of FluentAssertions but also enhance the usability of your test harness for non-technical users. Whether you choose to customize exception handling or utilize the AssertionScope's Discard method, you can create a more straightforward and less confusing experience for your QA team.

Remember, at the end of the day, clear communication in testing is crucial. Utilizing these methods, you can ensure that your QA team receives the information they need without the complications of exceptions.

Now you’re ready to incorporate these features into your testing harness! Happy testing!