Back in August of 2018 the whole testing automation community had been struck by the big news: Simon Stewart, the founding member of Selenium, had officially confirmed the release date and some of the major updates for Selenium 4 at the Selenium Conference in Bangalore. The 4.0 version of the worlds beloved framework for web testing automation was meant to be released by Christmas 2018. Selenium 4 release date Now, those who were familiar with the story behind the Selenium 3.0 release, which was also supposed to happen by Christmas, probably already knew back then, the new version would most likely indeed be finished by Christmas, but probably not in 2018. Just like it’s happened with the previous version which was released three years later than promised at the time of the original announcement. And they would have been right! As of today (and we are updating the information about Selenium 4.0 release in February 2019) the release of the new version still

Selenium or QTP? I come across this question every single time I face automation newbie. Before jumping into any solution, I would ask you to go through the following features of both automation tools : QTP: It is licensed tool. You have to pay to use it. It supports both Web and Desktop automation. It doesn't require much coding skills. It supports VB script only as automation language. It only supports Windows platform. It supports limited browsers and their versions. You can’t integrate other automation tools with it like Sikuli, AutoIT etc. Selenium (WebDriver): Selenium is free of cost. Selenium only supports Web automation. Selenium requires coding skills. Selenium supports many languages like Java, Python, PHP, C#, Ruby, Perl etc. Selenium supports all platforms, Windows, Linux, Mac. Selenium supports almost every browser like Chrome, FF, Safari, Opera, IE and their versions. It gives the flexibility to integrate Java or Python modules, other automatio

We all know the importance of humor in our life. And sometimes it comes our way when it's most unexpected and sometimes during stressful work hours and you just can't restrict yourself from sharing these funny moments with others.                                                   I am going to share some of the funniest experiences of the QA Engineers with developers. We IT professionals aware of the epic cold war between Developers and QA's. Developers never accept bug in their code and very often they give some illogical and funny excuses to back their buggy code. When some of the QA Engineers have been asked to share there funniest experiences /conversations with developers, see their responses: Suresh: In my recent project, every time I found a bug, Developer used to say, No user will use that feature so we don't care about that bug :) Next one is lol :D :D :D Ralph: After I reported a “very bad” bug, the developer came to find me and gav

Talk of the town! Automation is the latest trend. Many Managers are chasing good-quality automation guys to set up an automation suite for their project. But to pick the right match of language and automation tool is the biggest defiance for them. Have undergone circs when projects failed by choosing wrong tools and technology. Question arising, what factors should be pondered while making the choice for the automation tool? Some managers look towards clients for the answer, but to me this is not a handy approach at all. How can a person, who is not a techie can counsel you on this puzzle? Manager should be aware of his team's skillset and capabilities well. If team members are more into manual and they don't have a smashing command over technical language then Robot Framework can be a best-fit for his team. Being an Automation freak, I used to look-around for the several automation tools available in the tech-space. I am fond of learning new technologies and the new stuff. And