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