SpecFlow steps generation and general Rider changes

In May of this year, I wrote an article on how to get JetBrains Rider to generate SpecFlow files. The biggest problem I still had back then was that I couldn’t generate the step definitions. I finally found a workaround so I don’t need to use Visual Studio anymore.

Continue reading “SpecFlow steps generation and general Rider changes”


Injecting AutoMapper profiles in tests

In the newer services at my client, AutoMapper is used to map DTO‘s to database objects and back. Because mocking a mapping isn’t obvious, a lot of behaviour wasn’t tested and that’s unacceptable. Let’s find out how to properly inject an IMapper with actual mappings.

Continue reading “Injecting AutoMapper profiles in tests”

Patterns and disciplines from a proof of concept – Part 5

While I worked at my previous employer, I build a proof of concept to improve their ability to search. I will rebuild that proof of concept and I’ll highlight all the patterns and principles I used to build this code. All code related to this proof of concept can be found in a repository on my Github account.

In this fifth and last part, I’ll talk about additional benefits that this implementation can use.

Continue reading “Patterns and disciplines from a proof of concept – Part 5”

Boxing impact on string concatenation

Recently I went to a session given by Maarten Balliauw about memory management. In that talk, he mentioned the effect boxing and unboxing has on performance. He also talked about how a lot of strings can affect memory management. This got me thinking on the impact of boxing and unboxing when I format strings. What kind of impact does it have?

Continue reading “Boxing impact on string concatenation”

Tests ran multiple times on the CI server

A while ago, colleagues and I encountered strange behaviour on our Continuous Integration server: several tests were run twice.

The problem was caused by a test project that was referenced in another test project because of some infrastructure code that was reused. Probably a Visual Studio or ReSharper suggestion of “Would you like to reference ClassX from Project.Y” and somebody just clicked “accept” or maybe even ReSharpers auto resolve all references of pasted code. This caused a test assembly to be loaded twice and thus the tests were discovered twice. Assemblies should not be carelessly referenced.

We solved it by putting all general purpose infrastructure code into a separate assembly that can be safely referenced throughout all the test projects. Case closed.