by admin | Sep 27, 2021 | Selenium Testing, Blog, Latest Post |
In Selenium 4, the WebDriver bidirectional (BiDi) protocol has been implemented. First of all, you should know why WebDriver needs the BiDi protocol. First, the Selenium WebDriver client library sends HTTP command requests to a server. The received requests are then processed by the server. Once the server is ready with the response, it will send the response to the client.
So the Selenium WebDriver Remote server does not send any HTTP response or message to the client until it receives an HTTP request.
In the above diagram, the client sends a request and the server responds. The client does not kill the connection with the server until the response for a command request is received. Selenium WebDriver has more than 60 endpoints to communicate with a remote server.
Why BiDi Protocol?
The WebDriver Bi-Directional protocol allows both the client and the server to send & receive requests and responses. But we have enough HTTP commands to send requests to the server. Then why do we need the BiDi protocol? To understand this, you need to know some features which are available in Selenium 4.
- Listening DOM events
- Capture & send JS Errors and Console messages to client
- Record Traffic
- Access to native devtools protocol
Let’s take sending console messages to the client as an example. If a webpage has 100 console log messages, then the server needs to establish 100 HTTP connections and moreover, the server cannot send a response without a valid request from the client.
Even if the selenium developers tried to implement this feature with an HTTP connection, the server wouldn’t be able to handle multiple requests simultaneously. That is the reason why the BiDi protocol has come into the picture.
What is BiDi Protocol?
BiDi is a web-socket protocol. Websocket is an event-driven protocol. Let’s say the Selenium client wants JavaScript error messages from the browser. Whenever JavaScript errors are notified by the browser to the server, the error messages will be sent to the client. So the server will send the error message only when there is an error. This is called the event-driven protocol.
In the below diagram, you can see that server is sending the WebSocket URL to the client in the new session endpoint response. So any commands other than HTTP server endpoints will be communicated using the WebSocket URL.
When the client needs the JavaScript console error logs, then it should subscribe to the server so that the Selenium Server will send the error messages to the client from the browser.
Refer to the below snippet. The client subscribes to the Browser Log messages. So whenever any log message is added in DevTools, the server will send the message.
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;
import org.openqa.selenium.devtools.DevTools;
import org.openqa.selenium.devtools.Log;
import org.slf4j.*;
public class Selenium4Devtools {
final static Logger logger = LoggerFactory.getLogger(Selenium4Devtools.class);
public static void main(String args[]){
System.setProperty("webdriver.chrome.driver", "drivers/chromedriver.exe");
WebDriver driver = new ChromeDriver();
try{
DevTools devTools = ((ChromeDriver)driver).getDevTools();
devTools.createSession();
devTools.send(Log.enable());
devTools.addListener(Log.entryAdded(), entry -> logger.error(entry.asSeleniumLogEntry().getMessage()));
driver.get("https://www.codoid.com");
}
catch(Exception e){
e.printStackTrace();
}
finally {
driver.quit();
}
}
}
Conclusion
As a leading automated functional testing services company, we have explored many Selenium 4 features, and the WebDriver BiDi protocol is certainly an interesting topic. It is pivotal for every automation tester to be familiar with the internal processes of Selenium.
by admin | Sep 29, 2021 | E-Learning Testing, Blog, Latest Post |
Creating responsive content is always the recommended way irrespective of the platform you are creating it for. But when it comes to content on the LMS, the importance is a notch higher as many eLearning courses are now available on smartphones and tablets as well. The unexpected pandemic has only given more reasons for you to make your content responsive. To begin with, the number of people taking eLearning courses went up. They did so with the devices they had in hand. So the already difficult challenge of formatting the content to fit across different screen sizes and form factors got a lot harder. But even without the pandemic, testing your LMS to see if the content is responsive has always been a primary focus. So let’s take a look at a few vital tips that you can follow to make the job easier.
The LMS Choice
Choosing the right LMS provider for the job is the first step and a very important step as well. But how will you know if you have the right one? The best option here is to analyze the LMS features and verify if it will be helpful in building and delivering content that can be optimized for mobile or tablet users. We should also verify if the LMS provider will be able to provide the instructors and course designers with the required tools to create responsive content. Not all tools work in all use cases, which is why the LMS providers should have the expertise to choose the tools that will be apt for your needs. The reason we’re starting with these factors is that the content creation process itself should start with the end goal in mind.
Curating Responsive Content
So with the first step, we have made sure that the instructors and the content designers have the best tools at their disposal to get the job done. Now we have to implement the best practices to ensure that the curated content is responsive. For the content to look clean and organized across all screen sizes, we can assign a limited word count for the instructor when it comes to written content. Likewise, we can limit the image size and advise the designers to work accordingly. We will be tasked with different challenges when it comes to video content. In case the user has low internet speeds, then videos will have a tough time loading. So we have to make sure the instructor creates a transcript of the video.
Test Strategy
Creating a test strategy from the learner’s viewpoint helps us understand their expectations better. So your test strategy should align with those expectations and the initial goals defined at the start of the development process. The test strategy shouldn’t just focus on the content’s accuracy. Rather, the performance of the platform should also be tested without fail. So it is imperative to check how well the content performs in different devices under different scenarios.
Let’s say the content fits perfectly but takes a lot of time to load. That shouldn’t be a pass when testing to see if the content is responsive. Instead, we have to make sure there is no loss in usability. So before you start developing our test strategy, make sure to receive all the documentation and go through it thoroughly. It will help you get a crystal clear understanding of each module or component’s purpose.
Conclusion
Although these are valuable tips you can follow to ensure that your content is reactive, it is vital for the LMS to make it as easy as it can be for learners to submit feedback if or when they face any issues. As a leading e-learning testing company, we never overlook the fact that content will constantly be added to the LMS. So we have used the feedback and our own test reports to streamline the process and set ourselves on a path of continuous improvement.
by admin | Sep 23, 2021 | Automation Testing, Blog, Latest Post |
Going all hands on deck for every project to reach the market early is not always a great choice. We have to use the resources efficiently by using automation to eliminate the need for human intervention or supervision in as many tasks as possible. Not all project are alike and so the need for automation tools also vary on a project-to-project basis. As a leading QA Company, we focus on providing the best software test automation services using the aptest tools for the specific needs of our clients. So with that expertise to back us up, we have curated this specialized list of the top 10 automation testing tools you would need for various needs.
Selenium
When it comes to web application testing, Selenium is hands down the best option out there. There will be no Top 10 automation testing tools list without Selenium as well. But what makes Selenium so good? Selenium is so widely supported that you can use it to perform testing across numerous browsers on different platforms like Windows, Mac, and Linux as well. Selenium is also compatible with a vast number of programming languages like Java, Python, C#, Groovy, and the list keeps going. Now we know what makes Selenium good, so let’s see what makes Selenium undeniably great.
Selenium makes it possible to perform parallel test execution, which in turn will reduce the test execution times greatly. Apart from saving invaluable time, it is also helpful in creating the most complex and advanced automation scripts to meet your demand. In addition to having such benefits of its own, Selenium integrates well with other software testing tools to make the experience even smoother. We started this list with Selenium as it is also a base for many other testing tools that are available.
Appium
Like how Selenium is for web application testing, Appium is for mobile automation testing. Be it hybrid or native mobile applications developed for iOS & Android, Appium’s ease of use and high compatibility make the process automation testing a breeze. If you’re wondering how then the answer is that Appium doesn’t require SDK or recompilation of the app to test native apps. So you can use the test practices, frameworks, and tools of your choice and be in full control of the entire process.
Cypress
The primary advantage of using Cypress is that it paves the path for efficient end-to-end testing and therefore increasing its scope from being just a tool for automation. Debuggability is the standout feature of Cypress due to its many unique features like,
1. Cypress provides us with human-readable errors and makes stack traces easily accessible.
2. Cypress has the ability to take snapshots of the tests as they run. So you will be able to use the command log to see what exactly happened at every step along the way.
3. Never go out of sync as Cypress neither sleeps your tests nor adds unnecessary waits.
4. Finally, its real-time reloads enable easier implementation of changes to the tests as Cypress will reload automatically whenever any change is made.
FlaUI
FlaUI is a UI-based automation library that can help test applications that run on Windows OS. It has a large library that covers almost every single library used in the Microsoft UI Automation Test Library. FlaUI is the tool look to go with if you are looking to automate win32, WinForms, WPF, and even Windows Store apps by capitalizing on the available libraries. If you feel this tool would be useful to you and unsure of how to use it. We have a great blog that clearly explains how we can make full use of the tool.
Postman
In this Top 10 automation testing tools list, we have seen tools for specific tasks thus far. Likewise, let’s take a look at a couple of options for testing APIs which is always not an easy job to do. Postman’s API testing tool helps you set up automated tests without breaking a sweat. But the benefits don’t end there as they can also be used to aggregate the tests and requests that you have created into one automated test sequence. Postman even has common JavaScript snippets that can come in handy to test without writing any code for general use cases. By creating test suites we will be able to organize a set of our requests in Postman Collections, which in turn helps you run and automate a series of those requests. So Postman makes it very simple to run and manage your test workflow.
SoapUI
SoapUI is a headless functional testing application that is best suited for testing API and services. Even if you’re just starting out with API testing SoapUI makes it easy for you as it has a resource center to guide you. It supports various protocols and collections like REST, SOAP, GraphQL, JMS, and so on. Its drag and drop feature is a great way to accelerate script development. So with the rising need for API testing, SoapUI becomes an integral part of your CI/CD pipeline and delivers software as fast as possible.
BrowserStack
One of the primary objectives of automation testing is to reduce the effort spent on repetitive tasks. Testing across different device and software combinations is one such scenario, and this cloud-based solution is a tool we can’t afford to miss. First of all, with BrowserStack in the picture, you need not worry about having all the hardware to pull off large-scale testing. But most importantly, you can use the ‘automate’ feature in BrowserStack to run tests in parallel across so many devices with various combinations at lightning speeds. There is no room for any compromise as we can even simulate network conditions, IP geology, and GPS geolocation.
Ranorex
Ranorex Studio is a great all-in-one option as it can be used in almost all use cases as it can be used to test desktop, web, and mobile apps. It is very apt for beginners due to its codeless click-and-go interface that makes things so simple. But with a full IDE, it is powerful enough even for the experts of the trade. It has a shareable object repository, it enables highly reliable object identification even in the case of web elements with dynamic IDs. Apart from that, Ranorex also has the various features we have seen in the previous tools like recording and playing the tests, easy integration with other testing tools, code reusability, and so on.
TestComplete
Just as the name suggests, TestComplete is another all-in-one solution that offers great value by having the ability to test desktop, mobile, and web applications. Similar to Ranorex, we will be able to use it without writing even a single line of code. It can even be used to write complex automated test scripts in the same fashion. Using TestComplete we can run functional UI tests in parallel either using the cloud or your local machine. Since it can blend seamlessly with other tools you might use, TestComplete would make for a great asset to have to achieve continuous testing. That is why TestComplete makes its way to this list of the Top 10 automation testing tools.
CucumberStudio
With the primary focus on the end-user experience, Cucumber is a Behavior Driven Development (BDD) tool that has a lot of pros on its side. CucumberStudio promises a living document as your BDD documentation always stays up to date with seamless Git integration. It boosts collaboration with highly refined and readable executable specifications that everybody can understand easily. An added advantage that comes along with it is the higher visibility of the testing activities for the stakeholders. Another area where enhanced collaboration has a visible advantage is in drafting test scripts as a collective effort of testers and developers.
Conclusion
As stated earlier, the need for automation tools does vary with each project. But at the same time, these 10 automation testing tools cover some of the most common use cases as we have seen tools that have their own specialty. We hope we have covered a wide range of tools that would benefit you in the future. As a forerunner in the industry who provides test automation as a service, we will continue on a journey of continuous learning & improvement by exploring many more tools.
by admin | Sep 20, 2021 | Automation Testing, Blog, Latest Post |
The need for automation in testing has been on the rise as more and more companies adopting for it which has also increased the demand. Going from being a manual tester to an automation test engineer doesn’t just happen in a snap. It is a process that takes time and requires a lot of disciplined effort. But at the same time, it is not like you will transition yourself into doing something totally irrelevant. As a leading manual QA testing company, we firmly believe the objective of both manual testing & automation testing to be the same, and that both are quintessential. So a good understanding of manual testing can help lay the groundwork for what is to come in the future. In this blog, we will be covering the automation tester skills that you should concentrate on to make a smooth and successful transition from Manual Testing.
Understanding the need
But before we head over to see what the must-have qualities of an automation test engineer are, let’s first understand the need for automation testing. The rise of the agile software development process has radically increased the rate at which software is developed. So automation testing has become the solution to meet the ever-growing demand as it is very much efficient in performing repetitive tasks over and over again. Now that we know the purpose of automation testing, we will be able to get a better picture of the focus points needed for this transition and understand them better as well.
Coding is the Key
There is just no other way to put it. Coding is one of the must-have automation tester skills when it comes to automation testing and there is no workaround that will let you bypass it. If you are considering tools that claim to perform codeless automation, we assure you that it is not a viable option. Learning to code is the first step that you have to take and there might be difficulties here as you might feel as though you are starting everything from scratch again despite being a manual tester all this while. But the actual situation here is that you are a software tester and you are just adding a new skillset.
Coding is the key to a successful automation career and so make sure you are familiar with concepts like Object-Oriented Programming, JavaScript, HTML Basics, Coding design patterns, and so on. The lingering question in your mind would be about what programming languages you must focus on. The answer to that question is Python, Java, JavaScript, XML, CSS, (C, C++ & C#), SQL, and Perl in no particular order. Do a bit of groundwork and find out which of these languages you have easier access to learn about and start your learning journey.
Tools and Frameworks to Explore
Learning the programming languages is a good first step, but it is by no means the only step you would have to take to hone your automation tester skills and fully transition into an automation testing engineer. You can further simplify the automation process with the help of the numerous open-source tools and frameworks that are available in the market. Once you have learned the various programming languages, you will be in a position to write effective automation scripts that can be implemented in such tools to get the job done. Selenium is one of the most renowned tools that every automation tester would use to automate the web application testing with their scripts. Likewise, Appium is a great option for mobile automation testing, Postman for API testing, and the list keeps going. Read our blog that covers the top 10 automation tools to get a better idea of what these tools can do.
Take the hassle out of the development process by using effective automation frameworks like Nightwatch.JS, Cucumber, and Protractor. Such tools will be instrumental in making your test suites easy to maintain, data handling, increasing code reusability, and so on.
The Automation Testing Life Cycle
We will not be taking a step-by-step walkthrough of the Automation Testing Life Cycle (ATLC) methodology. Rather, we would be bringing to light a few things about it that you should know to begin with. Deciding which test cases should be automated is the first and foremost aspect of this methodology. Just because we can do something, doesn’t necessarily mean we have to do it. The same applies to automation testing as well. You have to make sure you’ve understood the product and the requirements well enough to run a risk analysis. Based on that analysis, you should implement automation only in places you deem to be necessary.
This decision plays a pivotal role in the test strategy that you will be implementing in the ATLC. Once you have narrowed down the test cases you should automate, you can then pick the automation tools that you will be needing to complete the task. Few tools are open-source, few are not. So you would have to also plan the predicted cost and calculate the estimated ROI to make sure your decision to automate was correct. If there is no scope of ROI, then it would be probably best to review the initial decision. After which, you would have to plan, design, and develop the tests and move forward with the regular testing process of executing the tests and reviewing the results before starting the next cycle.
The Learning Curve
Completing a degree or a course is a great value add. But that alone is never enough. “Practice Makes Perfect” is an old saying, but it still holds up when it comes to automation. The key factor to remember is not to overwhelm yourself by starting out with extremely difficult tasks. Even in case of any misstep, simple test cases will make it easier to debug, maintain, and even reuse. Start small, but make sure you do it right. The more you keep automating test cases, the more equipped you get in handling any unforeseen scenarios that might arise as challenges in the process. The objective here is to develop your automation tester skills and not just getting certified. So make sure you continue the learning process by being updated with any new tool in the market, new tips, hacks, and so on.
Conclusion
We hope you found this blog to be insightful and helpful. Finally, we would like to say that you have to be rooted in the concept of delivering better software quality. As one of the best manual software testing companies, we understand the importance of manual testing and that it can’t be completely replaced with automation. So make sure to stay updated on both fronts as both are vital aspects in delivering quality software.
by admin | Sep 22, 2021 | Automation Testing, Blog, Latest Post |
During the early days, record and play was popular to create automation scripts. However, in the modern era, it goes without saying that you have to be highly skilled in test automation scripting. Some automation testing tools claim that it supports code-less automation. But in reality, there is no substantial fact to prove that code-less automation is a game-changer and that no coding knowledge is required to create test automation scripts. In this blog article, you will learn why coding skills are a key to kick start your test automation career and what are all the coding concepts you should know to begin with.
JavaScript & HTML Basics
Basic knowledge in JavaScript and HTML is a must-have skill for any automation tester. If you have sufficient knowledge about a web element’s HTML tag & attributes, and its associated JavaScript events, you can create a robust automation test script.
Let’s say you want to fill a date using the calendar field, there is no need for you to automate the date selection in the calendar field. Rather, you can fill the date directly using the Selenium JavaScriptExecutor instead of writing complex code snippets.
In addition to that, you should also know what the HTML DOM tree structure is, and how the page components are divided using DIV tags. So it is evident here that basic knowledge in JavaScript and HTML is very crucial when you are at the budding stages of your test automation career.
Object-Oriented Programming
We know for a fact that it is not possible to create an automation test script without a class. So it is mandatory for you to know the below-mentioned object-oriented programming concepts prior to starting your test automation career.
– Constructor
– Object Creation
– Method Overloading & Overriding
– Inheritance
– Getters & Setters
As a leading automation test company, we make sure we provide the best in class programming and tool level training to all our resources before they are inducted into any project. Make sure you pour your heart and soul into the process as it is vital for you to know the real purpose of each concept and how it is implemented in test automation while learning object-oriented programming. One of the best sources to learn OOPS concepts is the multiple GitHub projects which are public. You will be able to learn how OOPS concepts are used in test automation and fly high in your test automation career.
Coding Design Patterns
Page Object Pattern is a fundamental part of programming that every test automation engineer will know about. However, there are a lot of other coding design patterns which you can use in test automation to avoid boilerplate codes.
Singleton Pattern
When it comes to test automation, you can use the Singleton pattern for DB connections. Once a DB connection is established for query execution, there will be no need for you to open a new DB connection to execute another query if you use the Singleton pattern.
Factory Pattern
Factory Pattern allows you to create an object from one of the several possible classes that share a common superclass. By following this pattern, you can hide the instantiation logic and avoid writing complex logic inside the ‘if else’ blocks.
Strategy Pattern
Using the Strategy pattern, you will be able to implement the methods’ logic of multiple classes that share a common interface and objective and call the methods in one place instead of calling all the implemented methods of the classes for different logics in multiple places.
Dependency Injection
There will be a need to create multiple page object classes for test automation. If you want to create objects for the page object classes only once and serve the created objects in all the tests, then you need to know how to set up the Dependency Injection pattern in your Framework.
Though Test Automation Design patterns are advanced concepts, you should at least know the basics of them before starting your test automation career.
Exception Handling
You have to keep in mind the fact that you will never handle exceptions in your automated tests. The reason behind it is that if a script throws an exception, it will be marked as a failure and the exception details will be required for troubleshooting. However, if you get into the framework and other automation library development, you have to catch exceptions because libraries are not tests. So make sure to avoid unwanted exceptions. It would be better if you report them in log files that are related to test automation frameworks.
Assertion Libraries
Assertions are important to report whether an automated test case has passed or not. There are several assertion libraries available in the market and so you should learn how to use assertions in your tests. Apart from that, you should also know that assertion chaining allows you to write complex validations in a single readable line.
Conclusion
As an Automation Testing Services Company, we train our resources in all the aspects of coding in order to create robust test automation scripts and frameworks. As stated earlier, even with the introduction of tools that claim codeless automation, there is just no path to automation without coding. Simply put, you can’t ignore coding and do automation testing as coding will have a huge impact on your test automation career.
by admin | Sep 20, 2021 | Automation Testing, Blog, Latest Post |
Nowadays we cover all the functional tests in automation using Selenium and Appium tools. But the question here is, are we doing the Automated GUI Testing right? We would definitely check whether a button is clicked or not. But we might fail to check whether CSS has been applied as excepted and if the button is displayed to the end-user as per the design.
Let’s say an e-commerce website has an ‘Add to Cart’ button that is blue in color and the font is white in color. But what if the font color is also made blue by mistake? The result would be a button that seems to be empty despite having the text. The more serious underlying issue here is that the end-user will have difficulty in making a purchase as they will not be able to find the ‘Add to Cart’ button. In this case, the automation test script will pass even though the issue is a huge business concern that will lead to financial loss.
Another example is having a button that is too small and inconvenient for touch action on mobile devices. These type of issues can’t be spotted until it is tested manually. So, in this blog article, we will be taking a look at how to get automated GUI testing right.
Layout Testing
The above-discussed roadblocks and topics of concern can be overcome if we had the option to check the layout of the GUI elements.
Galen Framework is a great option that will fulfill this need of ours as it enables us to check both the size and alignment of GUI elements on multiple browsers and devices. .spec is the file format of the Galen script and you can write the scripts using the Galen spec language. Specs files can be triggered for execution from JavaScript and Java as well.
Galen is an open-source project. It even lets us perform Selenium actions in order to perform some functionalities on GUI and view certain page components. Parameterization is a critical feature for any test automation framework, and Galen supports parameterization in data tables. We will be able to tag the data table inside the spec file.
Grouping the tests and running a group test using its tag is a must-have feature. We know for a fact that we will not run all the tests in one go every time. Moreover, if you don’t group the tests, the test output (HTML Report) will list all the executed tests in one group instead of showing a segregated output. So it becomes a cumbersome task for an automation tester to analyze the report. Galen also supports mutation testing.
As an automation software testing company, we have used Galen in many of our automation testing projects and detected many responsive and GUI-related issues that would have been overlooked without Galen.
Visual Testing
Visual testing is another viable option we can opt for to detect many UI issues. But what is visual testing? Storing the baseline screenshots of web pages, and capturing the actual images again to compare them with the baseline images is called Visual Testing. As stated earlier, when a Selenium script is used to click a button, the script does not confirm whether the button is displayed as per the design. However, if you compare the web page screenshots, you will unearth many UI issues and have enough time to solve them.
Menu Touring
Menu touring is a type of visual testing and it is exactly what the name suggests it to be. We will write scripts to navigate all the pages from the main menu and all the other available links as well. Once the page is loaded, we can take a screenshot and compare the screenshot with the baseline image. As one of the leading software test automation companies, we set up a menu touring automated test suites as visual smoke tests for our clients. So with the feedback from both the Automated Function Regression testing and Visual regression testing, your team will be able to deploy the application confidently.
Tools for Visual Testing
It is very much possible to create Visual regression test suites without the aid or usage of any visual testing tool. All you would need to know is how to navigate to different web pages/mobile screens and compare the screenshots. However, there are some tools available in the market which are specifically developed for the purpose of visual testing alone and they can come in handy.
Applitools
One can say that Applitools is a quite sophisticated visual testing tool as it supports over 50+ frameworks and languages. Using it you will be able to write tests for web, mobile, desktop, IoT, AR, and even VR apps.
Percy
Once you have written the tests using the above tool, the other aspect is comparing the screenshots and that is where Percy comes into the picture. It can be used to compare the screenshot against the baseline image. You can even run the tests with different responsive widths and even across different browsers.
Functional testing alone is not sufficient. Visual testing is a must to identity GUI issues that could go overlooked during functional testing. So pick the right visual testing tool which fits well with your existing CI/CD pipeline. If a tool is a good fit for your requirement, go ahead and use it instead of reinventing the wheel. Implementing and managing custom frameworks for visual testing is an overhead that should be avoided. As a tester, you must focus on being able to provide quick and accurate feedback at regular intervals. So leave the visual testing to the tool as your job is to create the scripts.
Conclusion
Automated GUI testing is instrumental in deploying your website/apps with the utmost confidence. GUI issues have the potential to bring down your business’ reputation at first sight even before your product has a chance to win the customer over with its functionality. So make sure to catch the GUI issues before they are reported by end-users.
