Skip to content

Conversation

@jnyrup
Copy link
Member

@jnyrup jnyrup commented Jul 28, 2020

If a user request an unsupported test framework via app settings, FA will now throw an exception instead of trying to detect a test framework with AttemptToDetectUsingDynamicScanning.

If the requested test framework is not available the failure message will contain the missing assembly name.

In both cases the failure message will contain the names of all supported frameworks.

This fixes #1359

If a user request an unsupported test framework via app settings, FA will now throw an exception instead of trying to detect a test framework with `AttemptToDetectUsingDynamicScanning`.

If the requested test framework is not available the failure message will contain the missing assembly name.

In both cases the failure message will contain the names of all supported frameworks.
@jnyrup jnyrup merged commit 2905f23 into fluentassertions:develop Jul 29, 2020
@jnyrup jnyrup deleted the improvedTestFrameworkMessage branch July 29, 2020 08:16
@jnyrup jnyrup restored the improvedTestFrameworkMessage branch October 27, 2020 07:21
@jnyrup jnyrup deleted the improvedTestFrameworkMessage branch January 23, 2021 08:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Misleading exception message: "FluentAssertions was configured to use mstest but the required test framework assembly could not be found"

2 participants