Autonomous testing is here (?)


Filip Hric

21th January 2025

AUTONOMOUS TESTING

Hello Reader,
The idea of autonomous testing has been popping out in my network a lot lately. Is it the future of QA, or just another buzzword? I recently started a poll on this, and the results were split: while some are excited about its potential, others remain skeptical. Let’s unpack the discussion.

"Autonomous" aims to be the next revolution of testing after test automation. Before, test automation would take away the repetitive parts of testing. It would be strong in areas where people were weak and would get tired. Autonomous testing aims to be strong even in areas where people were previously strong. Supporters believe that AI-powered tools can massively improve testing, especially for smoke and exploratory tests. As some commenters say, the promise is there, but we are not quite there yet.

Not everyone is sold on the idea. Skeptics point out that for complex setups AI still falls short. Especially when testing more complex web applications that require complicated data setup. Demos that we see are nice, but that’s just demos.

While fully autonomous testing might not replace traditional methods yet, its potential for growth is intriguing. As AI improves, the key will be balancing automation with human oversight to ensure quality and reliability.

What’s your take on autonomous testing? Is it a "yay" or "nay" for you? Let me know—I’d love to hear your perspective!


Blogposts, discussions, events

Windsurf is the iPhone of AI code editors

It's cheaper than Cursor too, but is it better overall? Go check out Steve Sewell's review.

​Read more →​

Colombo Quality Camp

I'm looking forward to my first speaking engagement this year. Join Quality Week '25 by Colombo Quality Camp from February 17th to 21st. Explore insightful sessions led by experts on the latest advancements in software testing.

​Read more →​

99 Cypress tips

I'm still preparing a special course for you! It will feature bite-sized advice to help you master configuration, API testing, advanced networking, DOM manipulation, performance, and debugging in Cypress. Stay tuned!

​Read more →​


Test automation tip - upload a file through API

Testing API with Cypress is simple an fun. But when trying to upload a file through API, things get a bit more complicated. Here’s an example of how to achieve this. You can read more about this in my blog.

 1  cy.fixture('logo.png', 'binary').then( image => {
 2    const blob = Cypress.Blob.binaryStringToBlob(image, 'image/png');
 3    const formData = new FormData();
 4    formData.append('image', blob, 'logo.png');
 5  
 6      cy.request({
 7        method: 'POST', 
 8        url: '/api/upload',
 9        body: formData,
10        headers: {
11          'content-type': 'multipart/form-data'
12        },
13      })
14    })

Meme of the week


Filip Hric

Teaching testers about development, and developers about testing

filip@filiphric.sk, Senec, Slovakia 90301
​Unsubscribe · Preferences​

Filip Hric

Sign up for weekly tips on testing, development, and everything related. Unsubscribe anytime you feel like you had enough 😊

Read more from Filip Hric

Hello Reader, If you’ve been reading this newsletter for a while, you know that quality engineering is the hill I’ll always choose to stand on. And this week, I get to share something personal that ties directly into that. I’m joining Qodo I’ve been following Qodo for almost a year now, and I’ve been getting more and more impressed every day. So I’m thrilled to share that I’m joining Qodo as a DevRel engineer. Qodo is an enterprise multi-agent platform for AI-driven code reviews. As AI...

Hey Reader, An interesting thought is popping up in conversations around AI agents: the environment around the thing matters more than the thing itself. Last week I read about Harness engineering and it felt very familiar. As if it was tapping into instincts I already had. If you’ve ever debugged a flaky test only to find the problem was in the setup, not the assertion, that instinct will feel natural. But at the same time it also feels like an unfamiliar territory. It borrows the same...

Hello Reader, AI can generate code, arguably with a pretty decent quality. That’s not news anymore. The question that’s been forming in my head all week is different: how do we decide what should go into production? Writing code is not the hard part (arguably, it never was). The hard part is making sure the right code ships and the wrong code doesn’t. And right now, that selection problem is becoming the defining challenge of AI-assisted development. Last week has definitely showed this....