Isolating dependencies in Silverlight unit tests -


i'm in process of writing lob application in silverlight , i'm little dismayed roadblocks i'm hitting unit testing.

  • prism uses lot of extension methods, static methods not mockable.
  • all mocking frameworks use dirty tricks mock non-virtual , static methods don't work in silverlight (e.g. moles, justmock. not sure typemock isolator.)

so, question:

is there strategy isolating dependencies in silverlight unit tests?

am missing something, or not thinking problem correctly? can use ui tests (such available in new vs2010 feature pack 2) work around problem?

tia

have looked @ other mvvm frameworks if have such issues prism? usually, layers of silverlight application should testable.

  • models should testable because shouldn't have ui technology
  • view models should testable because shouldn't reference on ui
  • views (xaml) declarative
  • you'll need fill gaps , write own controls, attached properties , behaviors. can @ silverlight toolkit source code see how handle testing there.

Comments

Popular posts from this blog

asp.net - repeatedly call AddImageUrl(url) to assemble pdf document -

java - Android recognize cell phone with keyboard or not? -

iphone - How would you achieve a LED Scrolling effect? -