When to STOP testing?

When to STOP testing?

This is a common question which hits every tester's mind. At the initial iterations of the development we are interested to find defects in the product but later on after two, three iterations on the same, testing the same stuff, a question arises on our mind, "When to STOP testing?".

Ideally, as we all know that although it's possible to find all the defects in the software but this will take a lifetime and the process of getting bugs and fixing will go on forever. So there are certain factors to be taken into considerations while testing to fulfil the intent of testing. Testing is a process which is involved so that the current and expected behaviour is matched. Here are some of the conditions when testing can be stopped:

• Allocated Budget for testing is consumed.
• When all the planned test cases are executed and passed
• When timelines for the released are reached.
• Major Areas are working as per expectations
• Test coverage is fulfilled as per plan.

 

There can be more such conditions when we testing can be stopped. Let me know your thoughts in comments on "by when do you think testing can be stopped?".

Requirement Traceability Matrix

Requirement Traceability Matrix

Traceability means the ability to trace something. RTM or Requirement Traceability Matrix is a matrix where mapping of the entire requirements provided by the client or a Product owner is done in a single document which can be taken as a proof that the requirements are incorporated in to the final feature / product to be delivered.

RTM is a list of requirements and a place to track them with test cases. The aim to having this matrix or document is to ensure a full test coverage with the requirement and there is a no miss of any functionality while testing process.

Why RTM?

As it is utmost important for a tester to understand the requirements completely, so to deliver a high quality output. As the further processes depends on how good is the understanding of requirements, hence it makes very important to involve testers in initial stages of SDLC.

Now, once the requirements are clear, further these requirements are broken down to test scenarios and next to detailed test cases.

Here comes the answer to question "Why RTM". Once the detailed test cases are in place, to verify that it aligns with the requirement, we use RTM to map requirements with test scenarios and test cases. In this way RTM will be helpful in gauging that we have complete test coverage and ensure a quality output.

RTM is typically a excel sheet where the mapping of requirements with test cases and scenarios is done.