The canvas element is a part of HTML5 that allows for dynamic, scriptable rendering of 2D shapes and bitmap images. The objects inside a canvas are not accessible using the DOM hence element locators like ID, CSS, Xpath, classname etc cannot be used to locate and interact with the objects on canvas. The only way to perform automation on a canvas is to use the coordinates in the view port of the browser to interact with the objects in the canvas.
Mobile app automation often requires multiple services and libraries to be set up and platform-specific SDKs to be installed. Appium and WebdriverIO provide an interface to build tests that can run in both Android and iOS just by changing capabilities. In spite of the powerful interfaces, often mobile app automation projects are not set up to make use of this to full potential. Let's look at how to setup abstractions and reuse most of the automation scripts for Andorid and iOS app testing.
Test automation enables engineers to validate and test features and bug fixes at a faster rate. Test automation is primarily useful for regression testing. But is it enough to develop the automation scripts alone? Test automation is incomplete without reporting. Test automation reports help QA engineers to analyse the test results in a cumulative manner, specifically failures, and validate if they are actual issues or flaky tests.
That need has only grown. Teams now ship multiple pull requests per day — often with code written or assisted by AI — and need reports that answer a sharper question: did this specific change break real user behaviour? DevAssure O2, our autonomous testing agent, was built with that in mind: every run produces a detailed HTML report with session recordings, step-level pass/fail, and bug analysis you can open locally or attach to a PR check.
In this blog, the focus is on automation reports and dashboards — the key metrics that simplify report analysis, how open-source tools handle reporting, and how DevAssure O2 and the DevAssure platform deliver it end to end.
Applications that use chrome extensions to perform certain functionalities are difficult to test and automate because every test case would need the chrome extension to be loaded on the browser. In automation testing, every browser is loaded with a new context. In this blog we will learn how to load and add chrome extensions in test automation using playwright, selenium and a no code automation solution like DevAssure.
For all the tools being used, we will be automating a test case where an ad blocker extension will be added and we will be validating if the ad is not loading.
UI Automation is always challenging. Some of the reasons include
And because of the complexity involved in automating the interactions with the components and the data associated with them, the tests are not stable, meaning that they don't fail or pass consistently. With UI Automation, unstable tests are a huge pain, because a lot of manual intervention would be required to check if it's an actual failure and identify why it failed now and not during the previous run, based on this a fix to make the test stable needs to be identified.
A test management tool helps test engineers manage test cases throughout the development and testing cycle. This blog outlines some of the top test management tools available today.
API or Application programming interface is a set of rules that enables software programs or modules to communicate with each other. API testing is a type of software testing involving the testing of such rules. These rules serve as integration points between different modules within an application and also with 3rd party applications. In order to ensure the application functions seamlessly it is important to test the functionality, reliability, performance and security of the APIs.
This blog talks about test driven development as well as its importance. Moreover, it also elaborates test driven development with examples.
Two years ago, the best we could offer developers was a faster way to write test scripts. Record your actions, generate a script, maintain it when the UI changes, debug it when it breaks.
That model is reaching its limits.
In 2026, AI coding tools write 20% or more of new code at companies like Google and Microsoft. Developers ship multiple PRs per day. Release cycles have compressed from weeks to days. And the old approach — write scripts, maintain scripts, fix flaky scripts — can't keep pace with how fast code moves.
DevAssure started as a low-code test automation platform. We built a recorder, a visual test builder, self-healing locators, and test data management. Hundreds of teams used it to automate faster than they could with Selenium or Playwright alone.
But we kept hearing the same thing from our users:
"The automation is faster, but we're still spending 30–40% of our time maintaining tests."
That feedback led us to rethink the problem entirely. The result is O2 Agent — an autonomous testing agent that reads your code changes, generates targeted tests, and executes them in a real browser. No scripts. No selectors. No maintenance.
This post introduces what DevAssure O2 is, how it works, and why we built it.