Use Fluent Annotations disabled is ignored about unitverse HOT 7 CLOSED

Change is made in 0.108 👍

from unitverse.

I updated to the most recent version and it did solved the issue!

The Fluent Assertions are not generated anymore, when "Use Fluent Assertions" is set to "False" and "Auto-detect frameworks" is set to "True".

Good job and super fast response - I am really impressed 😲!

from unitverse.

I can't repro that, if I use the UI and turn off Fluent Assertions, I get:

await Assert.ThrowsAsync<ArgumentNullException>(() => _testClass.Method(default(IList<uint>), CancellationToken.None));

If I leave Fluent Assertions on, I get:

await FluentActions.Invoking(() => _testClass.Method(default(IList<uint>), CancellationToken.None)).Should().ThrowAsync<ArgumentNullException>();

from unitverse.

I could figure out the reason: There are FluentAssertions in one project, when the option "Auto-detect frameworks" is set to "true", the option "use Fluent Assertions" seems to be ignored.

Setting "Auto-detect frameworks" to "false", the FluentActions is not being generated.

from unitverse.

Is it possible that you are turning off Fluent Assertions, then going back to the project tab and selecting a project? Because at that point it runs auto-detection... But in the example I used I had auto-detect frameworks set to True...

from unitverse.

I think in this case it probably auto-detected when selecting a project. I am pretty sure that if you turn off FluentAssertions and then click 'OK' it will generate without FluentAssertions.

I think I might change how it operates slightly though. Currently, if you click onto a project and then onto another it uses the settings from the first project as the 'base' for auto-detection. I think it should probably use the settings that were present when you opened the dialog as the base. I'll update that.

from unitverse.

Thanks, I appreciate you taking the time to come back to me. 👍

from unitverse.