8. Iteration or looping around

If an issue is found it may actually be a problem with the user requirement itself. It is quite common for the user requirement to not consider an unexpected situation.

For instance, the document might state that the system is to be used by 10 people at the same time. But by the time testing is underway something changes in the company and now the system needs to deal with 20 people instead.

In which case the client has to agree to change the user requirement document.

Then testing continues with the modified user requirement document.

Changing user requirements part way through a project causes delays and extra cost. It is often the most common reason a project fails especially on large projects.

Testing is usually an 'iterative' process.