WPF MVVM - Unit Testing a command - Private vs Public methods?

c# wpf unit-testing mvvm icommand
michael picture michael · Jul 28, 2011 · Viewed 7.9k times · Source

Basically, If I use MVVM and expose public ICommands, should my delegates be public or private?

Answer

Dan J picture Dan J · Jul 28, 2011

I would make them private - they aren't part of your class's public interface, that's what the public ICommand properties are for.

Related questions

WPF MVVM Light unit testing ViewModels

I am not a regular with the MVVM pattern and this is basically my first time playing with it. What I used to do ("normal" WPF), was creating my Views with a Business layer and perhaps a datalayer (which usually …

Read More
Using the WPF Dispatcher in unit tests

I'm having trouble getting the Dispatcher to run a delegate I'm passing to it when unit testing. Everything works fine when I'm running the program, but, during a unit test the following code will not run: this.Dispatcher.BeginInvoke(new …

Read More
Moq + Unit Testing - System.Reflection.TargetParameterCountException: Parameter count mismatch

I'm tring to use a lambda with a multiple-params function but Moq throws this exception at runtime when I attempt to call the mock.Object.Convert(value, null, null, null); line. System.Reflection.TargetParameterCountException: Parameter count mismatch The code is: …

Read More