Can't extend FakedService with Fake It Easy testing functionalities about fake-xrm-easy HOT 7 CLOSED

Could you post a unit test of what you are trying to do please?

from fake-xrm-easy.

Is this enough or would like the setup of the FakedContext too?

[TestMethod]
        public void UpdateCurrentParentAccountChangesNothing()
        {
            // Arrange
            this.parentAccount["statuscode"] = new OptionSetValue((int)StatusCode.Current);

            // Act
            this.context.ExecutePluginWith<UpdateAccount>(this.pluginContext);

            // Assert
            var account = (from a in this.context.CreateQuery("account")
                           where a.Id == this.parentAccount.Id
                           select a).FirstOrDefault();

            A.CallTo(() => this.service.Update(A<Entity>.Ignored)).MustNotHaveHappened();
            Assert.IsNotNull(account);
            Assert.IsTrue(account.GetAttributeValue<OptionSetValue>("statuscode").Value == (int)StatusCode.Current);
        }

from fake-xrm-easy.

Ok, I know what you mean know :)

At the minute those extensions are managed internally by the framework. They are not exposed, cause the intent of framework is to have these mocks already done and to write unit tests pretty much like if you were writing CRM customizations.

For example, there is a mock already for the Update message.

So, I suppose in that example, if what you need is to make sure the account attribute wasn't updated, it would be enough with these 2 asserts you had:

    Assert.IsNotNull(account);
    Assert.IsTrue(account.GetAttributeValue<OptionSetValue>("statuscode").Value == (int)StatusCode.Current);

from fake-xrm-easy.

Another thing, I saw you are keeping an instance of the context outside your unit test? This is not ideal, because the context keeps you entities in memory, a unit test execution could affect other tests if you share the same instance. Better to instantiate a context per test, so that the tests will be repeatable.

from fake-xrm-easy.

Thank you for your response! That makes sense however it does prevent us from achieving the code coverage that we want. I will keep that in mind. I'm not used to unit testing, so thank you for the advice.

from fake-xrm-easy.

You're very welcome 👍

from fake-xrm-easy.

@hsouth95 maybe is a bit too late for this... but never say never!

As other users requested this, now the service is a singleton instance so, you could things like this from now on:

A.CallTo(() => this.service.Create(A.Ignored)).MustNotHaveHappened();

from fake-xrm-easy.