January 26th, 2012 — Basics of Software testing, Manual Testing, Software Testing Books, Software Testing Templates, Testing Interview questions
I am glad to share “Manual Testing Help” eBook prepared by one of our readers. The content of this eBook is very useful to understand manual testing concepts, testing methodologies and preparing for software testing interviews.
Here are some of the topics covered in this book:
April 18th, 2010 — Basics of Software testing, Manual Testing, Quality assurance, Testing best practices
Note: If you missed the first part of this post please read it: Why Documentation is important in testing?
As I mention in my earlier post, in general, understanding about software testing documentation is “It can be done only by the person who has free time”. We need to change this mindset, and then only we can leverage documentation power on our projects.
It’s not that we don’t know how to do the documentation right. We just don’t think it’s important.
Everyone must have standard templates for all the kinds of documentation starting from Test strategy, test Plan, Test cases, and Test data to Bug report. These are just to follow some standards (CMMI, ISO etc.) but, when it comes to actual implementation how many of these documents are really used by us? We just need to synchronize our quality process with documentation standards and other process in an organization.
Continue reading →
March 7th, 2010 — Manual Testing, Testing best practices
This is a guest article by ‘Tejaswini patil’ – Associate QA Manager.
In my Software Testing career, I never heard people talking much about software testing documentation. The general opinion about testing documentation is that, anyone who has free time can do the documentation like Test case, Test plan, status report, Bug report, project proposal etc.
Even I did not stress more on the documentation, but I can say it’s my habit to place all the data in black and white and to update others about that as well.
Just want to share my experience with you:
We had delivered a project (with an unknown issue in that) to one of our client (angry client). And they found issue at Client side, which was very bad situation for us, and as usual all blame was on QA’s. The Continue reading →
