Entries Tagged 'Quality Assurance' ↓

Significant Changes in the QA World: Our 2013 Recap & Happy New Year!

We want to wish a Happy and Healthy New Year 2014 to all our readers!

2013 has been a wonderful year for STH – why wouldn’t it be? We had the best of the readers and followers behind us.

Back in December 2006, I started this blog with an intention to help software testers and today – after 7 years – it is helping thousands of software testing and quality assurance professionals worldwide!

Continue reading →

Cause and Effect Graph – Dynamic Test Case Writing Technique For Maximum Coverage with Fewer Test Cases

Dynamic Testing Techniques – Cause and Effect Graph.

Test case writing forms an integral part of testing, whether it is manual or automation. Every project is exclusive and has a <n> number of test conditions that need to be covered.

We should focus on two points whenever we write test cases. These are:
Mitigating the risk
Coverage.


This paper revolves around the second point which is “Coverage”. To be precise – Requirements Coverage.

Continue reading →

How to Perform Test Documentation Reviews in 6 Simple Steps – QA Process

By now, we all know that for a tester, documentation is an integral part of his daily life. There is an overload of testing artifacts that are created, reviewed, approved, used, maintained and distributed.  We always have clear-cut processes laid out for how to create a document, how to use it, who should it go to, etc.

Through this article, we are going to shed some light on the small but important topic – Reviews.

Reviewing is a form of testing too – the verification part of the V&V also called static testing.

Software Testing Document Reviews

Types of Reviews:

  1. Reviewing your own work – Self Checking
  2. Peer- review
  3. Supervisory

Continue reading →

How to Use Poka-Yoke (Mistake Proofing) Technique to Improve Software Quality

Software Process Engineering
Software Engineering is a discipline that aims at producing high-quality software through systematic, well-planned approach to software development. It contains many good practices, following the standards to achieve the quality product. The three main phases of Software Development are Analysis – Design – Implementation. To accomplish high-quality software is essential to produce the defect-free product.

The defect is the unexpected or undesired behaviour that occurs in the product. Anything related to defect is a continual process, not a particular state.

Defect Management
Finding and fixing the defect in the early stage of the software development reduces time, rework and money. Finding the defect in later stages always costs multiple times than early stages. It enhances the quality by adding reliability, portability, maintainability etc. Hence it is advisable every company should go with defect management system and defect management team at every stage of the development to attain the good quality in products and to gain the customer confidence.

One of such mistake proofing technique is POKA-YOKE, Continue reading →

How to Achieve Level 5 Maturity for QA and Testing Process

This article explains what are CMM levels and how to achieve these CMM levels for QA processes – explained with best examples.

For any process, whether it is a QA process, development process or any non-technical process, there are levels of its maturity. By levels of maturity, we mean that the level of formality and processes improvement, like ad-hoc processes – to formally defined steps – to managed result metrics – to optimization of the processes.

CMM (Capability Maturity Model) is a process-based model which is used to assess the maturity of an organization for different domains. The concept of CMM was introduced by Software Engineering Institute (SEI) in the USA.

Continue reading →