Skip to main content

Repackaging Old Ideas in New Bottles: Is This Innovation?

The software testing industry seems to have a recurring habit of rediscovering established practices, giving them fashionable new names, and presenting them as the next big innovation. I find myself wondering: are we actually advancing the discipline, or just reinventing its vocabulary?

1. Shift-left Testing – Discovering What We Already Knew?

Reviewing requirements before development, identifying ambiguities in acceptance criteria, involving testers early, preparing test cases before implementation, and identifying defects as early as possible have been established software engineering and testing practices for decades. There is nothing particularly revolutionary about these activities. Yet, suddenly, we have a fashionable new term for them: Shift-left Testing. Are we really discovering something new, or simply giving established practices a new name and presenting them as the next big thing? Good testing has always been about preventing defects rather than waiting for them to appear in a finished product. Changing the terminology doesn't make the underlying principle an innovation.

2. Low-code/No-code Automation – Déjà Vu?

Remember keyword-driven automation? The promise was that testers without programming skills could create automated tests using predefined keywords, while someone else maintained the underlying implementation. Fast-forward to today, and we have low-code and no-code automation platforms promising essentially the same thing, now with visual interfaces and AI thrown into the mix. Of course, the technology has evolved, but the fundamental principle hasn't changed: somebody still has to implement and maintain the underlying automation, whether through conventional programming, AI generated code or an abstraction layer. Hiding the code doesn't eliminate the need for engineering. It simply moves the complexity elsewhere.

Repackaging old ideas in new bottles and calling them innovation – is that really progress?

Comments

Popular posts from this blog

Verify email confirmation using Selenium WebDriver

Note: If you are new to java and selenium then start with selenium java training videos .   How to Verify Email Confirmation Using Selenium 4 and JavaMail (2026 Guide) Email confirmation is a critical part of most registration flows — account activation, password reset, multi-factor authentication, and onboarding. Every automation engineer eventually faces the same challenge: How do you verify an email confirmation link inside a Selenium test without making it slow and flaky? The wrong instinct is to automate Gmail's UI with Selenium. It's fragile, slow, and breaks constantly. The right approach: Use Selenium for browser automation Use JavaMail (IMAP) to read the email directly Extract the confirmation link Continue the test in Selenium Why Not Automate Gmail UI With Selenium? Automating the Gmail UI means logging in, searching, clicking a message, and parsing content from a third-party interface that changes frequently. This leads to: Flaky...

Using xPath to reach parent of an element

I generally prefer CSS selectors over XPath when writing Selenium locators. CSS selectors are concise, readable, and usually provide everything I need. However, there are situations where XPath is a better fit—particularly when I need to navigate through an element's hierarchy, such as moving from an element to its parent, grandparent, or sibling. This post shows one such real-world example. The Problem I came across a situation where I needed to click a link based on the value of an input field. The HTML structure contained multiple similar groups of elements. The input field and the link I wanted to click were not directly related, but they shared a common parent structure. In the following example above, the input element is highlighted, and I need to click the corresponding anchor ( <a> ) element . The challenge is that there may be multiple similar structures on the page. I therefore need to locate the link relative to the particular input element rather than using a f...

Real Time JMeter Result Using Backend Listener

Since JMeter 2.13 Backend Listener has been available to create real time graph of JMeter Test. Following tutorial explain the entire process in detail. At the end of this tutorial you would be able to create JMeter Live Test Result dashboard similar to following - This tutorial borrows information from many sources and my own experiments with JMeter live reporting dashboard. I have added source of information wherever applicable But before we can build such a snazzy JMeter Live Reporting dashboard we need to understand two more components - influxDB (a time series database) and Grafana Dashboard This is a big tutorial, so take deep breath :-) and follow on. Once you complete set up specified in this tutorial then you can watch JMeter Training Video Tutorial to watch this in action. What is Time Series Database? A time series is a sequence of data points , typically consisting of successive measurements made over a time interval . Examples of time ...