Posts

Showing posts from April, 2021

Top Challenges in Test Automation

  Challenges faced during Website Test Automation. Which tool to go for? –  Website Test Automation is highly tool dependent. There are plenty options available to choose from the market. It is relevant to evaluate and find a tool that fits your budget and business needs. How much to automate? –  You cannot automate everything! So you need to plan thoroughly regarding which process to automate and upto what level? This needs to be coordinated with DevOps. Parallel Execution –  of multiple test cases is usually not viable. Even when viable, then bug logging and debugging becomes a strenuous task. False Positives and False Negatives(Flakiness)-  A false positive is a scenario where the system is fundamentally working fine but the automation scripts shows otherwise. This could cost a tester a huge amount of his time and money for finding something which doesn’t even exist. Vice-versa, a false negative is a scenario where the automation script declares the system to...

How Do I Know I’m A Good Tester? Inspiring Thoughts From James Bach!

  James Bach.  What comes to your mind when you hear the name? Disruptive & Controversial Tester. Founding member of the Context-Driven School of Software Testing. Creator of Rapid Software Testing™, Session-Based Test Management, and one of the progenitors and advocates of skilled exploratory software testing. The original buccaneer Tester. His thoughts are revolutionary & an inspiration to both entry-level & experienced testers. He is straight-forward & fearless in advancing the Software Testing technology. James Bach is synonymous with testing, and has been disrupting the industry and influencing and mentoring testers since he got his start in testing over 30 years ago. A month ago I thought of starting a ‘Inspiring Thoughts of…’ series to get insights & advice from some of the expert testers around the world. It’s always great to read about the leaders and their views around Software Testing. Excited about the thought, I shot an e-mail to the top 10 Tes...

New Features in Selenium 4

Image
  The  Selenium 4 WebDriver will be completely W3C Standardized.  For example, it’s used heavily in  mobile testing through tools such as Appium and iOS Driver.  The W3C standard will encourage compatibility across different software implementations of the WebDriver API. Let’s take an example of how Selenium Grid communicates with Driver executables as of now – Adopting New Protocol A test in Selenium 3.x, on the local end (through JSON wire protocol) communicates with the browser at the End node. This requires encoding and decoding of the API. In Selenium 4, the test will directly communicate without any encoding and decoding of API requests (through the W3C Protocol), though Java bindings will be backward-compatible, but focusing more on the W3C Protocol. The JSON wire protocol will no longer be used. Selenium 4 IDE TNG Selenium IDE support for Chrome is in the bucket. As we all know, Selenium IDE is a record and playback tool. It will now be available with mu...

Agile QA

Image
  The agile testing lifecycle includes the following 5 phases: Impact assessment Agile Testing Planning Release Readiness Daily Scrums Test Agility Review As you understand now, these are the steps that one need to follow to perform testing. However every organization has its own way of following the process, this picture shows a cycle that should be performed throughout the sprint in a agile process. Now the question is what's the benefit of adopting this methodology. So the benefits of the agile testing approach are as follows: It saves time and money Agile testing reduces documentation It is flexible and highly adaptable to changes It provides a way for receiving regular feedback from the end user Better determination of issues through daily meetings Hope this somewhat helps you understand about agile QA process. For any further question or queries you can reach out to me at  abhiguptaqa@gmail.com

Common Selenium C# Exceptions and Fixes

Exception 1: The process cannot access the file ‘bin\Debug\chromedriver.exe’ because it is being used by another process.   The Problem   The problem here is that your ChromeDriver is being used by another process. So when it’s trying to be copied, it can’t because it’s being used.   The Solution   Option A 1.     Open Task Manager and kill all chromedriver.exe processes   Option B 1.     Open Powershell command line. 2.     Execute command: Get-Process chromedriver | Stop-Process 3.     This will kill all processes at once   Exception 2: System.InvalidOperationException : unknown error: Chrome version must be…   Error Message System.InvalidOperationException : unknown error: Chrome version must be >= 54.0.2840.0   The Problem Another issue with compatibility of ChromeDriver with Chrome Browser. In this case it was Chrome version 48.0 not workin...