Entries Tagged 'Quality assurance' ↓

Does Quality Assurance Remove Need for Quality Control?

This is a guest post by Meenal Balajiwale.

“If QA (Quality Assurance) is done then why do we need to perform QC (Quality Control)?”, This thought may come to our minds at times and it seems to be a valid point too.  This means, if we have followed all the pre-defined processes, policies & standards correctly and completely then why do we need to perform a round of QC?

Continue reading →

10 Tips to Help You Achieve Your Software Testing Documentation Goal

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 →

Fake God of Quality Versus True Humans – Who is Responsible for Software Quality?

Several thousands of Software Testers whom I came across had the notion that they are into testing and are solely responsible for quality. Some of them even think that being a tester also empowers them as a God of Quality for the product.

The questions I ask you is: Is this for good?

Here is what I think and would like to see you considering these ideas.  Continue reading →

Types of Risks in Software Projects

Are you developing any Test plan or test strategy for your project? Have you addressed all risks properly in your test plan or test strategy?

As testing is the last part of the project, it’s always under pressure and time constraint. To save time and money you should be able to prioritize your testing work. How will prioritize testing work? For this, you should be able to judge more important and less important testing work. How will you decide which work is more or less important? Here comes need of risk-based testing.

Continue reading →

What is Regression Testing? Regression Testing Tools and Best Practices

What is Regression Testing?

Regression means retesting the unchanged parts of the application. Regression Testing is the one in which test cases are re-executed in order to check whether the previous functionality of the application is working fine and the new changes have not introduced any new bugs. This test can be performed on a new build when there is a significant change in the original functionality that too even in a single bug fix.

This is the method of verification. Verifying that the bugs are fixed and the newly added features have not created any problem in the previous working version of the software.

Continue reading →