Showing posts with the label Blogs

Test-aliens are here on Earth, Go slow developers!

 Why should a company have a team for Software Testing and Quality Assurance? What is the need to test a software? Why shouldn't developers test their own work? When I started my career around two years back I encountered above listed queries. At that time I had no reply to these queries. But after dwelling around two years in IT sector I come along with some firm replies. All above listed questions are inter-belonging and the highlighted one was recently posted in a programmer's Q&A post, it inevitably raised my curious eyebrow. This can be a big debate. Diving straight to the point, the simple, unmistakable and well known answer is : “Developers are not very good testers.” But according to my understanding correct answer is, - “They don't want to see bugs in their code and only look for happy paths and and happy endings.” Believe me I was a developer in the past and then I moved to QA to avoid QA on my code, now I'm coding Automated Selenium Scrip

How I learned Selenium WebDriver in just 4 weeks

You can learn Selenium WebDriver yourself in just 1 month, yes you read it right! If you want above statement to work for you, then you would have to come up with a proper study plan and follow it with discipline. Discipline is the key here. Let me help you to make that study plan and also will share very useful blog posts links for the same, later in this post. Table of Content 1. My Story of becoming Selenium Professional 2. My Experiments with Selenium 3. Future of Selenium Automation Testing 4. Which language has a better career prospect with Selenium - Java or Python? 5. The 4 Weeks Plan to Learn Selenium WebDriver 6. What next after being Selenium expert? 1. My Story of becoming a Selenium Automation Professional I started my career way back in 2011 as a Manual Software Tester. I had interest in Java but didn't have much practical knowledge of it. I started learning Java slowly. It took some time to get some good  knowledge on Java. Then in 2012 I switched my first c

Advance Level Screenshot capturing using Selenium WebDriver and TestNG Listners

In my opinion, you should avoid the following: using static drivers  (because using static variables is a bad practice) using static methods for taking screenshots  (because using static methods is a bad practice) taking screenshots in the test methods  (because you will duplicate code in lots of tests) taking screenshots in the @After methods  (because you dont need to do this) I prefer to take the screenshots using a TestNG listener as follows. create a class for taking the screenshots Every time you need to take a screenshot, create an object for this class and use the capture method. The capture method will take the screenshot and save it in the screenshots folder. package framework ; import java . io . File ; import java . io . FileOutputStream ; import org . openqa . selenium . OutputType ; import org . openqa . selenium . TakesScreenshot ; import org . openqa . selenium . WebDriver ;   public class Screenshot { private WebDriver driver ;