Testing and Tracking the performance of APIs is not a one-time activity. As the APIs are built and improved over time, we need to track them. It’s important to correlate what changes in business logic changed the performance.
Tagged: API Testing
To test SMTP integration, you can either send emails using the production SMTP or you can run a test SMTP server just for testing. But its not easy for every developer in your team to do that or make it part of your CI/CD. This is where Fake or Mock SMTP servers play a role. They can run on a developers machine and expose an SMTP endpoint to connect and send test emails. They usually have web access to view the test emails to check formatting etc, manually. Some of them also expose a web API to retrieve the content for CI/CD integration. Here are some of my favorite mock SMTP servers.
httpbin is a developer utility web application that receives a request and spits out the request data as a response. httpbin is for testing your API requests, webhook requests, etc.
I have written mock features in Karate for integration testing. Recently I wanted to run them centrally somewhere so all my testing infra can use the same set of Mocks. I wanted an easy way to launch it and maintenance-free. So I tried it with CloudRun, which can run any stateless web service. One needs to provide a container to it. That’s all.
I have love and hate relationship with asynchronous systems. I love them because the flow is natural and doesn’t waste time and resources. I hate them because it’s difficult to test and debug. The most common asynchronous system that you would have used is Webhook type. Where you get a callback from an...