Entries Tagged 'Quality assurance' ↓

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 →

This article is by Pradeep Soundararajan, our guest author at SoftwareTestingHelp.

Many thousands of software testers 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.

Quality is everyone’s responsibility and not just a tester out there or thousands of them out there. If your family has to be happy, you can’t assign a person in your family as ensurer of happiness and catch the ensurer responsible if something goes wrong. If a family has to be happy forever, it has to happen with everyone participating and facilitating it.

Continue reading →

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 Software Testing?
Regression means retesting the unchanged parts of the application. Test cases are re-executed in order to check whether previous functionality of application is working fine and new changes have not introduced any new bugs.

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

Continue reading →

First in brief know what is Quality? Quality can be define in different manner. Quality definition may differ from person to person. But finally there should be some standards. So Quality can be defined as

• Degree of excellence – Oxford dictionary
• Fitness for purpose – Edward Deming
• Best for the customer’s use and selling price – Feigenbaum
• The totality of characteristics of an entity that bear on its ability to satisfy stated or implied needs – ISO

How a Product developer will define quality – The product which meets the customer requirements.
How Customer will define Quality – Required functionality is provided with user friendly manner.

Continue reading →