Get a Free Test Automation Assessment

Fellow dev & QA's willing to improvise their test automation effectiveness, take up our quick 5 minutes survey and get a custom report with pointers to improvise your test automation strategy.  Link here: http://bit.ly/2nns4PV


Popular posts from this blog

Defect Tracking System – Wastage of Money & Time ???

Image
As a QA I have been logging bugs since 5 years. But what do we do with that ? A typical flow: If this is the only thing we need to do then why taking so much of pain to have a defect tracking system . To log a standard bug (Standard Bug= Broken Functionality), we need to write steps to reproduce, pre-requisites (if any), expected result, actual result, priority, severity, snapshot (if any), Test environment details and finally save it. This takes around roughly 3-5 minutes to log a bug. To say truth, I have never seen any report coming out of defect tracking system which is of use in analyzing the pattern of bug or finding out any trend in them. All I have seen apart from tracking usage, is the summary of bugs with count based on Priority and Severity. Is that the only purpose of Defect Tracking System? If that is the case then why not use a Google spreadsheet rather then investing money of the company and time of QA in a bug logging system. I am sure if we mine the data which i
Read More »

Test Case Paths : Happy, Sad & Bad

Image
I came back from the background of writing test cases which were categorized in either Positive or Negative test cases. Positive test cases were business flows which may or may not give any result but they will certainly not give any exception or error. Negative test cases are those test cases which were bound to result into some exception or better expressed as error causing scenarios.  Then those positive test cases were prioritized as High/Medium/Low . Finally it used to result in quite a comprehensive test case document. Then it will go through the process of review and few more updates or change of priority etc. Certainly it is a tedious process. Here in ThoughtWorks I got introduced to different way of categorizing test cases called “ Happy/Sad/Bad ”. A test case which results you in a positive result is a Happy path , for e.g. entering proper username and password on login page. A test case which yields no result like entering invalid username and invalid password on a logi
Read More »

What a QA role in TestVagrant looks like?

Image
Disclaimer : Not a post to promote my Org. Read it if you want to understand what we do at  TestVagrant  and what you can expect from your career as a QA here. Almost 4 years back we created the company called  TestVagrant  and the prime intention was to make testing very intelligent and innovative. We want to make testing lean, more efficient, foster intelligence in solution which we owned and built. We wanted to challenge the assumptions of the testing and create something which is more intuitive and value addition to the software development process. And this happens when you own the design when you can influence it and change it based on the knowledge and skill you have acquired over a period of time. End of the day we wanted everyone to believe in the work they are doing, enjoy the work, experiment with what they are learning and have the courage to question the status quo and above all feel free to implement their ideas. We code to test and make testing faster and accurate. G
Read More »