It does,  as it is expected that obsolete methods can use other obsolete methods ;-)

Mark Seemann <notifications@github.com> wrote:



In Src/AutoFixtureUnitTest/BooleanSwitchTest.cs:

>              // Exercise system
> -            bool result = sut.CreateAnonymous();
> +            bool result = sut.Create();


Yes, it's beginning to look good :)

Does adding the [Obsolete] attribute to the unit test method suppress compiler warnings? I've never considered that option before.

Normally, what I do is surround the offending method call with pragma directives, e.g.

#pragma warning disable 618
            object result = sut.CreateAnonymous<object>();
#pragma warning restore 618


—
Reply to this email directly or view it on GitHub<https://github.com/AutoFixture/AutoFixture/pull/91/files#r3653385>.