9. Fail Validation - odoo-ps/pshk-process GitHub Wiki

Reponsible: FC, TC
Responsibility: Informing TC on what went wrong with the development
Objective: Identify the issue reported and make analysis on what to do
Next Stage: Development

General

During testing (client or FC side), if an error occurs or the result does not conform to the requirement, this is the stage to record all the failures and inform the TC of what went wrong.

During testing (from the client or FC side), there may be things that do not go according to plan. For example:

• An error (bug) pops up.
• Development does not conform to the original requirements.
• Client requests for extra / change in requirement.

Reporting Error

• When an error/bug is encountered, it should be recorded. Report the flow you took that results in that error.
• Report also the flow that violates the requirement. If it is previously not in the requirement, it's not a fail validation but instead an extra requirement which means that extra analysis + dev is required.

Reporting Changes

If the client has requested extra requirements, FC needs to assess whether or not the requirements are very different from the original requirement. If yes, advise making a new task instead. If not, proceed with the analysis.

Resolving

For bug/error TC should try to understand the cause of failure and re-assess his own developments. Once the problem is found, move it to development.
If it is an extra requirement, FC and TC should post their own analysis and move it to development once settled.