Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Rasmus Olofsson 22 posts 185 karma points c-trib
    Oct 19, 2020 @ 13:05
    Rasmus Olofsson
    0

    How to unit test with the new .Url() extension method? Throws exception and can't mock it

    The old .Url property on IPublishedContent is marked as obsolete and will dissapear. It has been replaced by an extension method in Umbraco.Web namespace.

    The old .Url property was easy to mock: content.Setup(x => x.Url).Returns(url);

    Now it doesn't work to mock the Setup of the property because it is an extension method and they can't be mocked. Using a wrapper around the extension method doesn't work either.

    If I skip setting up the extension method then my unit tests will throw a null reference exception because the UmbracoMapper lib from Andy Butland requires the Url() to be set.

    Any advice?

  • Dennis Adolfi 1072 posts 6378 karma points MVP 2x c-trib
    Feb 02, 2021 @ 05:53
    Dennis Adolfi
    100

    Hi Rasmus.

    See conversation on twitter: https://twitter.com/dadolfi/status/1355120357301231618

    To summarize:

    1. .Url() extension is not testable since it uses a static service locator without a setter so it can´t be mocked (Current.Factory).
    2. .Url has been deprecated so you can still use it but be aware in the netcore version it’s going away. It will not go away in v8 but you would have to change it if you updgrade/rebuild to v9.
    3. In Netcore version .Url() will be testable since dotnetcore has the option of passing in its dependencies which makes it easier to test.
Please Sign in or register to post replies

Write your reply to:

Draft