Test Criteria who should create them?

Over the years many software projects have failed due to insufficient testing being carried out by both the developers and the client. Why is this happening? In most cases it’s because the client has no knowledge of load testing, compliance issues around usability or more worryingly are moved way from retrospective testing by the developer.

Is this really the clients fault? Many developers and project managers believe that it is solely the client responsibility to set the acceptance criteria. Although I believe in the long run that this view has to change.

The most common excuse I have heard is that the client will not pay for the testing, have you really explained to them they risk they may be putting on their business if the project fails or the application collapses at a critical moment. After working with business cases and risk analysis my experience is that testing becomes a real driver for the project and the budget is found or an arrangement is made to allow this within the client’s organisation.

When we take on a project there is a great deal of faith put in us by in most cases a client that has no technical experience or limited knowledge and believes that detailed testing will be carried out. As developers and project managers we should explain to them the areas that we need to test in the project and strive to understand the exposure their business might face if this goes wrong.

This approach has several benefits: (Most of the points have been aimed at the developer but the main advantage for the client is that they have a working, tested and stable application.)

• The client begins to trust and become more open with the team through increased interaction.
• Making testing a priority can elevate pressure when software is not 100% correct as the client understands the risk.
• It also helps to close of products and can be used as a tool to support change control.
• Less support and bug fixing at the end of a project.
• More clients are satisfied and happy to refer and act as a reference for you.

I know that this is something that is undertaken by most developers and project managers it is  something that has cropped up allot in conversation and in work over the last few weeks and is fresh in my mind.

Popularity: 1% [?]

Related posts:

1. Agile Development in a Commercial Organisation
2. Communication in Web Projects
3. Dave Astels – Beyond Test Driven Development: Behaviour Driven Development
4. Using Excel to create Gantt Chart