Automation Stuff

There are many benefits to test automation. The reduced execution time alone is enough to turn heads. But if your organization has plans to implement DevOps, automating testing is no longer a question of if, but when. That’s not to say that all testing should be automated. If you’re still in the process of weighing the pros and cons of adding test automation to your everyday experience, you’ll benefit from reading our blog detailing the perks of test automation. To ensure that you and your organization are set up for success from the moment you launch your first test automation, keep reading this blog. Revolutionizing processes Testing automation has helped us revolutionize our delivery process while driving consistent, calculated releases to our customers. As you might’ve already learned, testing automation can benefit anyone implementing new cloud solutions in their organization. Specifically, large enterprises, complex infrastructures, developers, and testing teams w...

Making sure that your software performs well under expected (or anticipated) peak loads is critical.  Load and performance testing can provide valuable data to identify bottlenecks and problem areas in your software.  The main options available for load and performance testing of Web applications are: HTTP or Protocol based testing Selenium or browser based testing Hybrid option using a combination of protocol and browser based testing These options are very different in the way they work and the results they deliver. HTTP OR PROTOCOL BASED TESTING Protocol based testing solutions (like the ones built with JMeter, Gatling etc.) load the servers with traffic at the protocol (HTTP) level and assess the response of the server to that traffic.  So if you are looking to see how your servers perform under load conditions this works really well.  Additionally, since you are driving protocol (HTTP/S) level traffic, it is easy to generate really large volumes o...

We are seeing a great deal of interest amongst online merchants in using automation to increase the amount of testing on their digital commerce applications.  One question that keeps coming up – “ I believe automation can help me with my testing, but I am not sure what I should automate.  How do I get started? ” We will try to answer this question here. Automation can help improve the testing process for all types of software including digital commerce applications.  Automation works best for tests that must be run frequently, in a highly scalable manner where large numbers of tests have to be completed in a short period of time. Automation also has the advantage of ensuring consistency by eliminating ‘human error’ in testing.   Testing helps identify errors introduced when ‘something changes’ in an application. While code/feature change is the frequent driver of tests, digital commerce applications have ‘change’ introduced by many factors. ...

A few weeks ago I lectured about the importance of testing the test automation framework. At the beginning of the lecture, I asked the audience the following questions: “Who here writes automation?” – There was almost an entire show of raised hands. “Who here defines themselves as a developer?”- Only a few raised hands. “Who here writes tests for their automation framework?” – The audience was silent. Out of 60 people, not even a single raising hand appeared. This fact did not come as much surprise to me, since testing our automation is not so trivial (at least not currently).  I hope that by the end of this post you will agree with me the testing your automation framework is not something you should give up on. 3 main reasons for writing tests for our automation Reason #1 – We are developers! It is very important that we remember that every one of us who writes code is, first of all, a  developer . Even if your code does not go off to p...

Including unit tests in your web app projects leads to various benefits: Primarily, an effective and measurable way of proving code quality to developers and other project stakeholders. Browser  automation  takes these concepts even further, and applies the practice to running integration and regression tests live within the presentation layer user interface (UI). From there on, we can codify integration test scripts that do all the work for us – proving that the web app works as expected in the platform in which it will ultimately run. One of  the most known and implemented tools used for web browser automation  is  Selenium . It is not only intended to be used in automating web applications for testing purposes, but also for automation of web-based administration tasks. In fact, it is a set of different software tools, each with a different approach to supporting  test automation . Learning all of its tools will give you many different options for app...

In this post, we will review EventListeners – one of  Selenium WebDriver ‘s functionalities that enables us to create reports and logs while avoiding code duplication. Let’s assume that we’re running a test case with Selenium that includes a few steps, such as: navigation to a certain website, taping a button, entering text into a field, etc. We want all of these actions to be reported to some sort of log system. So, of course, we can add a line of code after each step that will take care of reporting, but that will be an overhead making the code less readable, as described in the example below (printing to console window): driver. get ( "https://www.ebay.com/" ) ; System.out. println ( "Go to Site: Ebay.com" ) ; driver. findElement ( By. id ( "gh-ac" ) ) . sendKeys ( "GoPro HERO6" ) ; System.out. println ( "Insert Text into field" ) ; driver. findElement ( By. id ( "gh-btn" ) ) . click ( ) ; System.out. println...