Compliance Testing

Compliance Testing

A non-functional testing technique whose sole purpose is to validate whether the product developed meets the organization’s benchmarks or not..

This is actually a type of audit which is done to make sure that all the standards are met. It’s the responsibility of process or compliance team to assess product at every phase for its design, content and development methodologies and make sure that they are as per company standard. This team is also responsible to improve the current standards which ultimately results in more quality product.

The standards normally used by the IT industry, are basically defined by the large organizations like IEEE (International institute of electrical and electronics engineers) or W3C (World Wide Web Consortium) etc. It can also be carried out by a independent / third party company which specializes in this type of testing and service.

Objectives

  • Evaluate the documentation of the project to check for completeness and reasonableness.
  • Ensures that the development and maintenance process meet the prescribed documentation.
  • Ensures that all deliverables of each milestone are as per the standards.

When to use compliance testing:

It’s totally product manager call to decide what should be the correct time for compliance testing. In common practice, this type of testing is done at the completion of every milestone. This gives an advantage to check compliance at every stage and any issue can be resolved there and then. If this is done at the completion of project and many discrepancies are found then it’s very difficult to resolve these type of issues. Situation becomes really difficult if development team or design team have not followed the prescribed standards and there is urgent need of rework to fix things up.

Sometimes, the standards, based on which this testing has to be performed, have issues in themselves. In that case, effort needs to be put in right direction to rectify or improve them so that they can be used.