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 for null or white space string variable, I often find myself writing the same unit test 3 times but with different input for the string parameter. public class Sample { public static void RequiredStringParameter(string stringParam) { if (string.IsNullOrWhiteSpace(stringParam)) { throw new ArgumentException($”{nameof(stringParam)} is required.”); } // Logics go here } } [TestFixture] … [Read more…]
I recently have to unit test a couple classes implemented by another developer. He implements these classes as internal which causes some problems when trying to unit test them. Internal classes cannot be referenced in another project (or assemblies). First thing comes to mind is to make these classes public so they can be referenced in … [Read more…]
There are many places in the code in the project I’m working on where HttpContext.Current.User is used to get id of the currently logged in user. This can be tricky when it comes to unit testing functions using the HttpContext. One of the way to get around this is to mock the HttpContext by manually creating the identity. … [Read more…]