Had an interesting battle with JMeter recently. I needed to load test on an authorized endpoint. I’m no expert on JMeter but I have a basic understanding. It didn’t look like retaining a token from an auth request was easily supported in JMeter. So here’s how I did it…..
Decided to use some spare time to revisit Blazor, particularly getting it to work with OData. Taking my inspiration from Hassan Habib and his Enabling Pagination in OData post I wanted to build upon that and modernise the approach slightly by implementing client side Blazor and bringing some of the goodies from NET5 by using a code behind approach for example.
A few weeks back I noticed that a part of the code that I’d been working on for over a year seemed to be growing in size and needed to be addressed in order to avoid future headaches and pain. The code is by no means monolithic but of a significant size to be a thing in it’s own right and not a quick 15 minute fix. I could see that action was needed in order to support future maintainability and scalability. Here’s 7 tips for refactoring…
There Were Build Errors. Would You Like To Continue And Run The Last Successful Build?
There’s scenarios where we don’t care about the Moq “It.IsAny<>” parameter value being passed into a mocked method but we need to get the value on the way out. For example, take the scenario below. I’m using SQLite to form integration tests and I need to get a handle on the generated ParentWidget.Id to tie back to my Widget FK.