A test automation tool is a software testing tool that helps software testers to perform seamless automation testing. Adopting a test automation tool can leverage the automation testing process by reducing tedious manual tasks. While testing complex software at an enterprise level, a test automation tool can be very handy.
Similar to OTPs, magic links are used to authenticate users by using only the email address. It is a "one-time use URL" sent to the user’s email address, which the user can use to securely access the application. The url contains time bound and secure embed tokens which help authenticate the user without a password.
OTP or One Time Password is used to secure data and a mechanism to secure user accounts through multi-factor authentication. Most applications have multi factor authentication enabled. In such applications, besides the username and password, users also provide the OTP, which is a series of alphanumeric characters generated at random for every request. Users also use OTP as a one-time access method to log in while validating the email they used to sign up.
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.
Shopify is an ecommerce platform that allows users to create, customise and manage their online stores. It consists of inbuilt tools that assist with product listings, inventory management, managing payment gateways and more. In summary, it's an all in one platform for building and maintaining online stores.
Testing Shopify apps is similar to testing any ecommerce platform. In this blog, we will focus on designing, creating and automating test cases for a Shopify app.
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. In this blog, the focus will be on automation reports and dashboards and the key metrics that will help simplify and expedite the report analysis.
During the month of October we have expanded DevAssure's Test Automation coverage to Mobile App Automation. The feature is currently in Beta. Besides this one of the major updates also include an enhanced customizable dashboard for automation analysis.
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.