https://aws-sensei.cloud/tags/unittest/UnitTest - Tag - AWS SenseiHugo -- gohugo.ioenThu, 06 May 2021 00:00:00 +0200https://aws-sensei.cloud/posts/2021-05-06-overridable-members/Thu, 06 May 2021 00:00:00 +0200Marcelhttps://aws-sensei.cloud/posts/2021-05-06-overridable-members/🔊 Voiced by Amazon Polly Mocking via virtual method Fake Dependencies with an Interface and Dependency Injection is easy and the usual approach. But how can you fake without Dependency Injection or an Interface. I will show you two situations that came up in production code. Factory Method The first situation is a small AWS Lambda function with an http call. We want to mock the .Net HttpClient and write a UnitTest for our Request method.https://aws-sensei.cloud/posts/2021-05-04-datetime-provider/Tue, 04 May 2021 00:00:00 +0200Marcelhttps://aws-sensei.cloud/posts/2021-05-04-datetime-provider/🔊 Voiced by Amazon Polly Our code is often time-dependent. We use the date or time to implement logic and make decisions in our code. The behavior of DateTime.Now or DateTime.UtcNow can differ due to the system, timezone and the time change (summer/winter). This means that we have to control this for our tests. Take this method for instance: public double ReturnCurrentOffset() { var result = DateTime.Now - DateTime.UtcNow; return result.https://aws-sensei.cloud/posts/2021-05-02-test-fixture-pattern/Sun, 02 May 2021 00:00:00 +0200Marcelhttps://aws-sensei.cloud/posts/2021-05-02-test-fixture-pattern/🔊 Voiced by Amazon Polly Test Fixtures Imagine your about to sit down to eat your lunch. The dirty breakfast dish is still on the table. You got three options. You can get a new plate, you can clean the old plate, or you can just eat lunch off the dirty plate. Thats it. New plate, clean plate, dirty plate. The same rules apply to tests. Transient Fresh Fixture Getting a new plate is what Meszaros calls in the book “XUnit Test Patterns” a Transient Fresh Fixture.https://aws-sensei.cloud/posts/2021-05-01-fluent-builder-pattern/Sat, 01 May 2021 00:00:00 +0200Marcelhttps://aws-sensei.cloud/posts/2021-05-01-fluent-builder-pattern/🔊 Voiced by Amazon Polly Helper methods make it easier to create test data. But they can become difficult to read over time as you need more variations of the test data to satisfy constantly evolving requirements from new tests. Let say, we have the following Customer class. public class Customer { public string Name { get; set; } public DateTime? DateOfBirth { get; set; } public string Email { get; set; } public string Address { get; set; } } In generally we create an instance of the Customer and set the respective properties as shown below.