Unit Testing a WCF RIA DomainService: Part 3, The DomainServiceTestHost

re: Unit Testing a WCF RIA DomainService: Part 3, The DomainServiceTestHost

Remco Blok — Tue, 19 Jun 2012 13:00:38 GMT

Thanks Kyle. I got it working. I was a bit confused at first about the ChangeSetEntry class Id property. I first thought this was the primary key of the entity in the changset entry, but if I understand it correctly these id's are generated on the client for each new changeset to allow associations in a changeset entry to reference the changeset that is the other side of the association, correct? It will also specify an order I assume in which the entries in a changeset need to be processed on the server, correct?

re: Unit Testing a WCF RIA DomainService: Part 3, The DomainServiceTestHost

kylemc — Thu, 14 Jun 2012 15:02:05 GMT

@Remco

Composition is one of those scenarios that didn't make the initial cut. Unfortunately I don't have sample lying around of the verbose way to test. Essentially you'll have to call DomainService.Submit with a ChangeSet. To do that you need to do a number of things.

(1) Write an IServiceProvider

(2) Create a DomainServiceContext

(3) Create a DomainService

(4) Call DomainService.Initialize

(5) Call DomainServiceDescription.GetDescription

(6) Create a ChangeSetEntry for each parent and child entity

(7) Create a ChangeSet containing those entries

(8) Call DomainService.Submit

Sorry for the inconvenience, but I hope this starts you in the right direction.

re: Unit Testing a WCF RIA DomainService: Part 3, The DomainServiceTestHost

Remco Blok — Thu, 14 Jun 2012 07:58:46 GMT

Hi Kyle,

I use composition and can't get it to work with the DomainServiceTestHost. When you say 'there may still be a few edge cases for association and composition change sets that are not supported', do you mean composition is not supported at all or only certain edge cases of composition? Say I have the following Update method:

public void UpdateLogbook(Logbook currentLogbook)

{

var originalLogbook = this.ChangeSet.GetOriginal(currentLogbook);

if (originalLogbook == null)

{

this.Context.Logbooks.Attach(currentLogbook);

}

else

{

this.Context.AttachAsModified(currentLogbook, originalLogbook);

}

foreach (var logbookEntry in

this.ChangeSet.GetAssociatedChanges(currentLogbook, logbook => logbook.LogbookEntries))

{

var operation = this.ChangeSet.GetChangeOperation(logbookEntry);

switch (operation)

{

case ChangeOperation.Insert:

this.Context.AttachAsAdded(logbookEntry);

break;

case ChangeOperation.Update:

this.Context.AttachAsModified(logbookEntry, this.ChangeSet.GetOriginal(logbookEntry));

break;

case ChangeOperation.Delete:

this.Context.AttachAsDeleted(logbookEntry);

break;

}

How can I use the DomainServiceTestHost to test adding a new LogbookEntry to the Logbook.LogbookEntries collection? The following test method, which I expected not to work, throws an exception.

[TestMethod]

public void GivenNewLogbookEntryWhenInsertingThenShouldAddLogbookEntry()

{

var logbookEntry = new LogbookEntry();

LogbookEntry addedLogbookEntry = null;

this.domainContextMock.Setup(t => t.AttachAsAdded(It.IsAny<LogbookEntry>())).Callback<LogbookEntry>(t => addedLogbookEntry = t);

this.domainServiceTestHost.Insert(logbookEntry);

Assert.AreSame(logbookEntry, addedLogbookEntry);

}

I suspect I'll need to manually create a ChangeSet somehow and submit that. Could you provide some guidance on that please?

re: Unit Testing a WCF RIA DomainService: Part 3, The DomainServiceTestHost

Simon — Fri, 02 Mar 2012 11:12:50 GMT

Hi Kyle,

Yes indeed it does thanks

I just added a new reposity for EF and injected that instead of your mock repository, and all good

Thanks again

re: Unit Testing a WCF RIA DomainService: Part 3, The DomainServiceTestHost

kylemc — Mon, 27 Feb 2012 18:00:28 GMT

@Simon

I think I addressed your concern about how to use repositories in this post (blogs.msdn.com/.../unit-testing-a-wcf-ria-domainservice-part-2-the-repository-pattern.aspx). It shows both test and production-focused implementations.

Also, the full source for this sample is available on code.msdn (code.msdn.microsoft.com/Unit-Testing-a-WCF-RIA-a39a700e).

re: Unit Testing a WCF RIA DomainService: Part 3, The DomainServiceTestHost

Simon C — Mon, 27 Feb 2012 14:46:10 GMT

Hi Kyle,

This is an excellent post which successfully consolidates concepts/patterns that are loosely explain elsewhere with reference to WCFRIA.

I modified the source so that the repository got data from a real db, via the Entity Framerwork, in essence returning 'real' book entities. This was done by refactoring the method (public MockBookRepository()), and essentially allowed me to switch to 'real' entities once I have successfully tested with mock entities.

This is great as it allows a staged development whereby I can move to real entities once i am happy that everything works with test data.

What I am having problems with is getting the update/insert/delete to work in the same way, i.e. adjuting the update so this updates the entities in the entity framework, as opposed to the mock in house repositor.

This would make the frameowkr great as could do all CRUD testing with mock data and then switch to the real data context (ef and database) once testing was successfull.

Can you please advise as to how this can be done please?

re: Unit Testing a WCF RIA DomainService: Part 3, The DomainServiceTestHost

kylemc — Sat, 12 Nov 2011 00:31:55 GMT

@Alan

When you use the repository pattern, it's best not to use the wizard. There's enough that's significantly different that it would just be a waste of your time. That pattern's not a necessity for testing, though. It's just a common approach to abstracting your tests from a database. As an alternative approach, you could use standard generated code and just make sure to point it at a test database. There are a number of options that I outlined in this series, but there's nothing forcing you to use them in any specific combination.

re: Unit Testing a WCF RIA DomainService: Part 3, The DomainServiceTestHost

Alan Rutter — Thu, 10 Nov 2011 01:25:08 GMT

I am researching using WCF RIA Services for some upcoming work and was concerned about testing. This is an excellent series of articles. There appears to be a lot of modifications to the DomainService as generated by the Domain Service Wizard - I am concerned that whenever our database/model changes, does this mean we cannot use the wizard or have to manually update the generated files?

re: Unit Testing a WCF RIA DomainService: Part 3, The DomainServiceTestHost

kylemc — Tue, 20 Sep 2011 15:35:42 GMT

@William

I don't have any particular recommendations. I always start at a page like silverlight.net and go from there.

re: Unit Testing a WCF RIA DomainService: Part 3, The DomainServiceTestHost

william simons — Tue, 13 Sep 2011 20:29:07 GMT

Thanks for your posts they are always very educational! Did you ever think about writing a book about mvvm, design patterns, prism, unity or mef using dependency injection.

Do you have any favorite books that you could reccommend?