I've recently upgraded my site from U6 to U7 and, so far, I've found the ability to unit test my code has been severely hampered.

The introduction of extension methods and internal constructors in parts of the codebase I've been talking to has made mocking and testing practically impossible in some cases, whereas I had a nearly 90% coverage in Umbraco 6. This seems like a really nasty step backward.

I used to be able to set expected property values in my test using a test extension method. Since upgrading to U7 I now find that every time .HasProperty() is called on an item of content it calls through to the ContentType object like this...

    /// <summary>
    /// Gets a value indicating whether the content has a property identified by its alias.
    /// </summary>
    /// <param name="content">The content.</param>
    /// <param name="alias">The property alias.</param>
    /// <returns>A value indicating whether the content has the property identified by the alias.</returns>
    /// <remarks>The content may have a property, and that property may not have a value.</remarks>
    public static bool HasProperty(this IPublishedContent content, string alias)
    {
        return content.ContentType.GetPropertyType(alias) != null;
    }

This is in an extension method, so I can't mock it directly. OK, so the next thing I try and do is mock ContentType, but ContentType is of type PublishedContentType and implements no interfaces, so I try to create a fake but there are no public constructors.

This is a bit of a nightmare to say the least so, in order to test my code I can no longer use the 'HasProperty' method at all, so instead I have to use 'GetProperty' and check it's null just so my test will work.

I'm not sure whether this is the best place to air this, but it would be much more helpful to keep classes like this open so at least you leave some route to enable proper testing.