Entries Tagged 'Testing Concepts' ↓
June 30th, 2014 — Basics of Software testing, Testing Concepts, Types of testing
So…do you really think it will take that huge amount of time to test, what you call system testing, even after spending lot of efforts on integration testing?
The client we recently approached for the project was not convinced about the estimation we provided for each testing effort.
I had to chime in with an example -
Mike, I would like to elaborate our efforts and importance of system testing with an example.
Shoot, he replied. Continue reading →
June 12th, 2014 — Questions & answers, Testing Concepts, Testing Interview questions
Our popular software testing questions and answers series is back again! Just to remind – in this series we answer questions asked by the readers. You can check some earlier posts in this series here and here. Got a question? Submit it in the comment section below or use the contact form.
In today’s article in this series, we are going to answer (with examples) some most commonly asked (and confusing) questions about the difference between test plan, test strategy, test case, test script, test scenario and test condition.
These questions are asked by “sasi C“.
Continue reading →
December 5th, 2013 — Testing Concepts, Testing Methodologies
In our last article, we saw ‘Cause and effect graph’ test case writing technique. Today let’s move to next dynamic test case writing method – State transition technique.
Note – The test design techniques mentioned here may seem difficult but once you get hold of it, it becomes very easy to implement and reuse, increasing productivity and test coverage.
What is State transition testing technique?
State transition technique is a dynamic testing technique, which is used when the system is defined in terms of a finite number of states and the Continue reading →
December 2nd, 2013 — Quality assurance, Testing Concepts, Testing Methodologies
Dynamic Testing Techniques – Cause and Effect Graph.
Test case writing forms an integral part in testing, whether it is manual or automation. Every project is exclusive and has <n> number of test conditions that needs to be covered.
We should focus on two points whenever we write test cases. These are:
Mitigating the risk
This paper revolves around the second point which is “Coverage”. To be precise – Requirements Coverage.
October 23rd, 2013 — Software Testing Templates, Testing Concepts, Testing Methodologies
Traceability Matrix – How to Create and Use It
Today’s session is about an important QC tool, that is either over-simplified (read overlooked) or over-emphasized – Traceability Matrix(TM).
Most often, the making, reviewing or sharing of a Traceability Matrix is not one of the primary QA process deliverables – so it is not majorly concentrated on, thus causing the under-emphasis. On the contrary, some clients expect a TM to reveal earth-shattering facets about their product (under test) and are disappointed.
“When used right, a Traceability Matrix can be your GPS for your QA journey”.
Continue reading →
September 19th, 2011 — Quality assurance, Questions & answers, Testing Concepts
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 mind some times and looks a valid point too. This means if we have followed all the pre-defined processes, policies and standards correctly and completely then why do we need to perform a round of QC?
In my opinion QC is required after QA is done. While in ‘QA’ we define the processes, policies, strategies, establish standards, developing checklists etc. to be used and followed through out the life cycle of a project. And while in QC we follow all those defined processes, standards and policies to make sure Continue reading →