我对于单元测试和嘲笑是全新的,并且仍然在耳朵后面湿润。我正在使用Moq框架,我需要模拟一个集合,以便它产生一个具有我提供的值的成员。
有问题的集合类是System.Configuration.SettingsPropertyCollection
,其中包含SettingsProperty
个对象。
反过来,SettingsProperty
有一个Attributes
属性,返回SettingsAttributeDictionary
。
我需要我的集合才能生成一个SettingsProperty
,其System.Attribute
中有一个自定义属性(源自Attributes.SettingsAttributeDictionary
)。
我真的很想弄清楚这一点,但到目前为止无济于事。我试着伸出舌头,拉着有趣的脸,但没有任何作用。
这是我到目前为止尝试过的代码,在代码中注释的时候会抛出异常,因此测试总是会失败。
[TestMethod]
public void GetPropertySettings_Should_Return_Default_Values_When_Device_Not_Registered()
{
const string deviceName = "My.UnitTest";
const string deviceType = "Switch";
var deviceId = String.Format("{0}.{1}", deviceName, deviceType);
Mock<IProfile> mockProfile = new Mock<IProfile>();
Mock<SettingsContext> mockSettingsContext = new Mock<SettingsContext>();
// Construct a SettingsPropertyCollection populated with a single property.
// The single property will have a fixed name and default value, and will also have a single
// attribute, giving teh ASCOM DeviceId.
var deviceAttribute = new ASCOM.DeviceIdAttribute(deviceId);
var attributes = new SettingsAttributeDictionary();
attributes.Add(typeof(DeviceIdAttribute), deviceAttribute);
var settingsProperty = new SettingsProperty(SettingName, typeof(string), null, false, SettingDefaultValue, SettingsSerializeAs.String, attributes, true, true);
var propertyCollection = new SettingsPropertyCollection();
propertyCollection.Add(settingsProperty);
// Now comes the interesting part where we call our IProfile - this is where we really need Moq.
// Expectations:
// - mockProfile must have it's DeviceType set.
// - mockProfile's device type (captured in setDeviceType) must match deviceType.
// - The returned SettingsPropertyValueCollection must not be empty.
// - The returned SettingsPropertyValueCollection must have exactly one entry.
// - The entry must match the value of SettingDefaultValue.
// Expectation: IProfile must have its DeviceType set. We capture the value into setDeviceType.
var setDeviceType = String.Empty;
mockProfile.SetupSet(x => x.DeviceType).Callback(y => setDeviceType = y);
// Finally, it is time to call the method we want to test
var settingsProvider = new SettingsProvider(mockProfile.Object);
// THE NEXT LINE THROWS AN EXCEPTION
// IF I TRY TO STEP INTO IT, IT NEVER RETURNS AND THE TEST RUN JUST ENDS.
var result = settingsProvider.GetPropertyValues(mockSettingsContext.Object, propertyCollection);
// Now lets verify that everything went as expected
// First, let's test that the parsing of DeviceId was as expected: IProvider.DeviceType was set to the expected value
Assert.AreEqual(deviceType, setDeviceType);
// Then let's test that the methods of IProvider that we mocked were called
mockProfile.VerifyAll();
// With this done, let's turn to the output of the method
// Firstly, we test that the resulting collection contains exactly one item of the type SettingsPropertyValue
Assert.IsTrue(result.Count > 0);
Assert.AreEqual(1, result.Count);
Assert.IsTrue(result.OfType<SettingsPropertyValue>().Count() > 0);
// Then let's inspect the contained SettingsProviderValue further
var settingsPropertyValue = result.OfType<SettingsPropertyValue>().First();
// First IsDirty flag must never be set
Assert.IsFalse(settingsPropertyValue.IsDirty);
// The PropertyValue must be the default value we passed in
Assert.AreEqual(SettingDefaultValue, settingsPropertyValue.PropertyValue);
}
抛出的异常(由测试运行者报告)是:
测试方法ASCOM.Platform.Test.SettingsProviderTest.GetPropertySettings_Should_Return_Default_Values_When_Device_Not_Registered引发异常:System.ArgumentException:类型System.Configuration.SettingsContext实现了ISerializable,但未能提供反序列化构造函数。
答案 0 :(得分:4)
我相信您需要设置模拟SettingsProperty的Attributes属性以返回模拟的SettingsAttributeDictionary,然后然后设置模拟SettingsAttributeDictionary的索引器以返回您想要的值,例如
mockItem.SetupGet(x => x.Attributes).Returns(mockAttributes);
mockAttributes.SetupGet(x => x[It.IsAny<System.Type>()])
.Returns(deviceAttribute);
Moq使用的Castle DynamicProxy类中抛出异常。我相信这与Moq如何模拟可序列化的对象有关。如果castle无法在具有(SerializationInfo,StreamingContext)签名的可序列化对象上找到非公共构造函数,则会抛出此异常。您可以做的是更改自定义SettingsProvider的GetPropertyValues方法,以便它接受Hashtable而不是SettingsContext,并为方法调用而不是模拟SettingsContext提供模拟Hashtable。 Hashtable具有必需的构造函数,所以这可能会起作用。坚持使用SettingsContext类型的参数而不是Hashtable没有什么好处,因为SettingsContext只是简单地从Hashtable派生,即它不添加任何成员。