Due to unexpected circumstances there was an urgent need for a fast working tool. This tool had to easily capture and process the needs of clients. Centralisation of information was even more vital. Next to this, data was already coming in at a fast pace, which put high pressure on the delivery.
Recently, I was working on a project where I needed to retrieve the access token from HttpContext and use this token to perform an HTTP request to get additional user info from an OpenID Connect (OIDC) UserInfo endpoint.
All this logic was encapsulated in a single service class.
Unit testing this class was giving me all sorts of issues and headaches, so I decided to document my findings and share them with you.
Across the web you read a lot of tutorials, papers and documentation about the Specification Pattern which seem to often contradict themselves in the use of it. The most familiar way this pattern is known is like in the paper from Martin Fowler and Eric Evans
When I was working on a project, lots of events needed to be sent from a client to a server. And then back to some clients. These events had to be accessible at multiple places on these clients. I was in need of a versatile architecture to handle real time events sent from a server.