So far, test automation has been synonymous with programming. Why? Because all available test automation frameworks and tools are dictating it.

Selenium WebDriver is great for automating browsers, but as a stand-alone automation tool it has some limitations. This post compares script-based Selenium automation with LEAPWORK web automation.

Artificial Intelligence (AI) is an intriguing – and sometimes intimidating – phenomenon. It is no longer the stuff of a faraway future. With headlines warning about job elimination, it is only natural for professionals in any industry to think about how AI will affect their work.

By taking a look at how Robotics Process Automation (RPA) is defined, we find obvious similarities with the concept of visual GUI / UI test automation.

The size and complexity of Salesforce means that many repeatable tasks are performed manually by sales reps, marketeers and managers over and over every day. In a medium-sized company, it's not unusual to have manual workflows that take hundreds of hours to perform daily, which could (and quite possibly, should) be automated.

Driving automation in LEAPWORK with pre-defined data from an Excel file is easy with the Read Excel block. But sometimes you need more real-time access.

Are you doing test automation on web applications? We're about to boost your productivity so much your boss will think you're cheating.

Heavy customization combined with mandatory upgrades put a lot of pressure on functional and regression testing of ServiceNow implementations around the world.

For technical reasons, Microsoft Dynamics applications are difficult to automate. In this post, we will show how to easily automate processes in Dynamics, whether it is for testing purposes or for business automation.

A demonstration of how to iterate through found content with LEAPWORK's Selenium-based web automation capabilities.

I want to talk about something that's causing a lot of confusion and frustration for testers around the world as they start their test automation journey: Using record and playback tools and why you most likely should avoid them.

Automated functional testing and live monitoring of business-critical desktop and web applications built with technologies such as SAP, Microsoft .NET, Salesforce, ServiceNow, WordPress, and many others is a considerable challenge for traditional, code-based test automation tools.

Measuring elapsed time can be a key component in test automation. For instance, a business requirement may state that a search query must not take more than 5 seconds to respond with results. Although there are dedicated performance testing and monitoring tools such as dynaTrace on the market which can provide detailed insights, LEAPWORK can easily be used to do sanity checks on business transactions using the Stopwatch building block.

Sometimes, user interface elements on screen can change size, color or shape depending on their state. For instance, a button might change from blue to green to signal something to the user.

Here's an example of how to automate a web application with LEAPWORK.

The "Read Excel" block in LEAPWORK is a major step forward for data-driven test automation, making it very easy to parameterize and drive automation cases with structured and tabular data.

LEAPWORK has a unique, built-in ability to loop through any images, text and numbers that has been found on-screen, allowing for very quick and visual creation of even highly complex automation tasks.

Dates and timestamps are important in most test automation scenarios. For instance, when testing user sign-up flows, entering a birthday or social security number is often required. Or when validating expiration dates during web content testing, generating a date/time value exactly one week from today might be needed.

Test automation is all about stretching your limited resources to do more in a shorter amount of time.

Testing and "quality assurance" are key processes in software development, accounting for up to 40% of development spending. That's because bugs are extremely costly to fix after software has shipped, compared to catching them early and so everyone needs a proactive approach to manage risk and quality. That means testing and re-testing for all changes made. The problem is, testing software is difficult.