Ale, music and enjoying life.
Postman Testing – Chaining Requests From one Request to Another
The Issue
I’d like to run a full suite of Postman tests are part of a CD pipeline into pre-production to indicate any issues and stopping the deployment of the API further. I’d built up 200+ Postman tests to cover standard CRUD operations on a number of resources. The tests were checking the POST responses for certain eleements returned in the body, 200 responses etc. Similar for PUTS, PATCHES and GETS. However, it would be nice to create a resource then reference this resource across all API operations for that resource.
Entity Framework Core: A second operation started on this context before a previous operation completed
Working with EF Core across multiple controller services I was receiving the following Entity Framework Core: A second operation started on this context before a previous operation completed. The link for StackOverflow talks about ensuring your dbContext is correctly injected into the ServiceCollection which mine was. A bit of headscratching I was thinking that my foreach loop look fine there was nothing too crazy/costly happening. Then I realised the objects I was looping over hadn’t terminated with a ToList() or similar. Once I added the ToList() the context returned the scope and happy days!
Azure API Management Template Parameters Used In The UriTemplate Must Be Defined In The Operation, And Vice-Versa
On updating Azure API Management with a new OpenAPI definition file I received the following error: “Azure API Management Template Parameters Used In The UriTemplate Must Be Defined In The Operation, And Vice-Versa”. A fair bit of head-scratching ensued, due to the error message not giving too much away, (which Operation? I’ve 100s of them!) and also being a bit flippant (“vice-versa” <– sass!). Also, I always check that my OpenAPI document conforms and plays nicely with the online Swagger editor. So what gives?
Remote Working Tools – Introducing Cloud Winch
Migrate your home drives to One Drive for Business. A gateway tool to the cloud!
Upgrade to dotnet 3.1 from 2.2 causes foreign key conflicts
EF Core 3+ Breaking Changes 🙂
Just following on from my web api/swagger/data .net core 2.2 to 3.1 upgrade and here. I hit another blocker just as everything was going so smoothly!. Basic functional testing on the API was going well until I noticed some POST operations failing with “ERROR The INSERT statement conflicted with the FOREIGN KEY constraint <FK>. The conflict occurred in database “DATABASE”, table “dbo.<tablename>”, column ‘<column name>’. “