Comments on: Leveraging expression trees to unit test ViewModel classes

By: Jeremy

Jeremy — Thu, 01 Apr 2010 06:29:04 +0000

Thanks Fred to the feedback. Code simple is now fixed !

By: The Morning Brew - Chris Alcock » The Morning Brew #566

The Morning Brew - Chris Alcock » The Morning Brew #566 — Wed, 24 Mar 2010 07:52:03 +0000

[...] Leveraging expression trees to unit test ViewModel classes – Jeremy Alles looks at how you can use Expression Trees to shorten the code required to test view model properties, working from the verbose manual method, to his expression tree method. Full source is provided. [...]

By: Fred POINDRON

Fred POINDRON — Tue, 23 Mar 2010 17:13:31 +0000

Very cool Jérémy !
For sure, I’ll try this code in my next test project.
I think there’s a small error in your third source code sample:

vm.PropertyChanged += (s, e) => propertyChanged = e.PropertyName == “newName”

must be changed to

vm.PropertyChanged += (s, e) => propertyChanged = e.PropertyName == “Name”;

Good work !

Fred

By: Jeremy

Jeremy — Tue, 23 Mar 2010 15:39:28 +0000

Thank you for the feedback Thomas

Yes I could have done an extension method. Is it possible to do that on an interface (INotifyPropertyChanged) and not on a type ?

By: Thomas Levesque

Thomas Levesque — Tue, 23 Mar 2010 15:27:09 +0000

Cool stuff, thanks !

Just an idea : for more convenience, why not declare the TestHelper.TestProperty method as an extension method ? This would make the unit test code even simpler :

vm.TestProperty(v => v.IsSelected);