It’s very common that we assert if two objects are equivalent in unit tests. Using FluentAssertion, this looks like the following
|
1 |
actual.ShouldBeEquivalentTo(expected); |
However, there are times where you want to exclude certain properties when comparing objects. This might be because the value of the property cannot be predicted or you just don’t want to include … [Read more…]
This post is part of a series of blog posts about bad codes or bad practices I’ve come across. Note that this is my personal opinion and some of the things I mention could be debatable. Post 1: Code review, why it matters Post 2: Not including JS, CSS and static content files in project Post … [Read more…]
I have a submit model with a property of type decimal that represents a percentage. I use the range attribute to only allow values from 0 to 100. I have a unit test where I use the Validator to test this validation on the submit model. However, when I pass in an input that’s outside the … [Read more…]
I tend to name my unit tests with the following convention: NameOfMethod_Inputs_Should_ExpectedResult For example, I have a method called Multiply which multiplies two integer parameters. If I have a test case to test this method with 2 integers 3 and 4, the test would be called Multiply_3_And_4_Should_Be_12 This has been working well for me until I recently come … [Read more…]
When unit testing a service, I tend to have a base class where I do all the setting up/initialisation. For each method in the service, I’d have a separate unit test class which derives from the base class. For example, if I want to unit test two methods GetAllNews and GetNewsById in SampleNewsService, I’ll have a SampleNewsServiceTestsBase … [Read more…]