Why AI Makes Migrating from Payware to Open Source Test Tools Surprisingly Affordable

The Migration Myth That’s Costing You Thousands

For years, QA teams have been stuck paying expensive licenses for proprietary test automation tools because of one persistent belief: “Migration to open-source is too expensive and risky.”

Sound familiar? You’re paying $10,000-$50,000 annually for commercial test automation tools like Tricentis Tosca, TestComplete, or Ranorex, but switching to free, open-source alternatives seems even more expensive.

We recently helped a client migrate their entire Salesforce test automation suite from Tricentis Tosca to Playwright (open-source). Their initial quote from a consulting firm? $45,000 and 14 weeks.

Using Playwright Model context protocol on my practicewebsite

Intro – What’s MCP & Why LLMs Need Model Context?

As AI agents evolve, so does their ability to interact with real-world web apps. Traditional automation relies on brittle selectors and hard-coded steps. The Model Context Protocol (MCP) which is an open standard that enables LLMs to interface with the web using structured, semantically rich data.

LLMs don’t “see” pages like humans. They rely on model context, an accessibility based snapshot of a page’s elements, roles, and structure. Instead of fuzzy screenshots, they get clear, machine-readable context. This is where Playwright-MCP shines.

From Code to Content: Automating Blog Posts with AWS Lambda

From Code to Content: Automating Blog Posts with AWS Lambda

Imagine a tool that can effortlessly transform your code snippets into full-length technical blog posts. That’s exactly what this AWS Lambda function does — automating the journey from raw code to polished content.

How It Works

Triggered with a code snippet, filename, and programming language, the Lambda function initiates a sequence of actions:

1. Title Generation & Task Initialization
   The function starts by generating a blog title and assigning a unique ID to the operation.

   2 min read

Example Azurite testing with Azure durable functions

Azurite and Durable Functions Testing Demo

In this blog post, we’re diving into a practical example that showcases how we can leverage Azure Durable Functions for orchestrating a workflow that processes invoices. Specifically, we’ll discuss generating and storing PDF invoices in Azure Blob Storage. Additionally, we’ll touch upon how Azurite, a lightweight storage emulator for Azure Storage, can be used for local development and testing purposes. This approach greatly simplifies development workflows by allowing developers to test their Azure Storage solutions locally, without the need for an actual Azure subscription during the initial development phase.

RestAssured vs Postman: When to Click, When to Code

API testing has become a fundamental part of modern software development. Whether you’re building microservices, integrating with third-party systems, or just trying to keep your backend in check, testing your APIs properly can save you a lot of time—and even more bugs.

Two tools often come up in conversations about API testing: Postman and RestAssured.NET. They’re both powerful, but designed for different workflows. If you’ve ever wondered when to use Postman and when to go with RestAssured.NET, this post will help you decide.

From 2 Days to 7 Minutes: How We Rethought Our API Testing for Azure Durable functions

You know that feeling when something technically works… but it just feels off? That’s where we were with our API testing setup. We were using Tosca to test our backend, which is built on Azure Durable Functions. It was technically doing the job—but it was slow. Really slow…. A full test cycle could take up to two days. And any time something failed, we were deep in post-deployment logs trying to figure out what went wrong. It wasn’t sustainable. Not for the team. Not for delivery. And definitely not for the pace we were trying to move at. So, we took a step back and asked: Can we do this smarter?