Systems | Development | Analytics | API | Testing

If you recall part one of this blog post, we were going to use ChatGPT in parallel with how we would work to cover these aspects of performance testing. We left the first part of this blog post at the point at which we had compared Requirements Gathering and Risk Assessment, we will pick this post up by looking at Script Creation before concluding with Results Analysis. Our performance testing tool of choice will be JMeter.

If you believe many articles online you would believe that automation in testing will soon be defined, managed and executed by Artificial Intelligence (AI). AI is embedded in many organisations technology landscape and to think that this model will change is shortsighted. AI is here to stay undoubtedly in one form or another, but should it be responsible for the automated testing of your applications under test?

When developers try to build realistic mocks and automated tests from production network traffic, the real challenge isn’t just in the capturing—it’s in the data manipulation. Raw traffic is a chaotic sea of patterns, dynamic tokens, environment-specific secrets, and tangled dependencies that seem impossible to untangle by hand. Over my two decades of building these sytems, I learned that solving this problem requires more than brute-force parsing or ad hoc scripts.

What happens when an inquisitive, unpredictable user, without manual or training, just begins clicking and typing in your application? Will everything handle the unpredictability gracefully or crash prematurely? This chaotic scene is not hypothetical in the field of Quality Assurance (QA); it is actually an established testing technique called Monkey Testing. While structured testing is important, it often ignores the unstructured actions of actual users.

Test automation has evolved far beyond QA. Today, it plays a direct role in product speed, developer efficiency, and even customer retention. That means one thing: it’s no longer just a technical investment. It’s a financial decision. If you’re a CFO, you’ve likely seen test automation mentioned in strategy decks or budget line items. But what does the return really look like?

Artificial Intelligence (AI) is reshaping Quality Assurance (QA) by accelerating testing, improving accuracy, and uncovering insights that once required hours of manual analysis. Yet, with great capability comes great responsibility. As AI begins to influence how tests are designed, executed, and interpreted, ensuring that it’s used ethically has never been more important. Responsible AI in QA isn’t only about compliance — it’s about trust.

For Python developers, the choice of IDE isn’t just a preference — it’s a productivity multiplier. From debugging and linting to virtual environments and CI/CD automation, your IDE defines how smoothly your workflow runs. As Python continues to dominate data science, web development, and AI, PyCharm and VS Code remain the two top contenders. Both are evolving fast — but which one truly deserves the title of Best Python IDE in 2025?

‍ Why should FinTech leaders care? Consider this: around 71% of organizations have adopted microservices (partially or fully), citing gains in agility, scalability, and resilience. And when done right, microservices can decrease overhead costs by up to half and boost developer productivity by 50%.