The utmost priority of Ultimate Consultancy is that of delivering a software product of maximum quality while complete care is being taken in the process of developing and testing a software product. In the field of software testing, audit may be defined as the action to evaluate a software product against the specified and established standards and specification, in order to ensure that the developed product adheres to these standards. The fundamental aim in carrying out the audit of a software testing phase is to ensure that the process being used and implemented in the testing process is of high and desired standard or if improvements are required. 

Benefits

Audit testing does not exhaustively test a product to uncover every possible issue and defect and so the cost in time and personnel that such a test would entail can be avoided. Instead, audit testing aims to examine a testing process that is already in place in order to establish the coverage and accuracy of the process.

An audit provides multiple benefits to a project. Common reasons for initiating an audit includes:

• Lack of experience with a particular project.
• Questionable history with a certain type of project.
• A new business partnership between companies.
• Getting peace of mind in regards to the testing team.
• Finding problems caused by the complexity of the project.
• Verifiable controls for quality assurance.
• Improvement of internal resources.
• Complex high level standards associated when working with organizations such as government agencies, medical devices, military projects and financial institutions.

Most commonly, audit testing is implemented towards the end of, or just after a testing cycle. Audit testing can, and in many cases should, be implemented before, during, and after, threfore covering all phases of a cycle: 

Process of Audit and Testing

In the initial stage, the elements to be examined maintain focus on the tools that are intended for use and the processes adhered to. When an audit is to be conducted prior to the start of a test cycle, the following process is likely:

1. Familiarization with the goals of the project, the particular standards the project must adhere to, and all relevant documentation.
2. Examination of the testing processes and tools the processes will utilize.
3. Review the communication protocols and test management plan.
4. Interview relevant personnel.
5. If practical, run simulated test case.
6. Submit the report.

Considerations for pre-cycle audit testing include:

• Especially helpful with little testing experience or new product directions.
• Does not interfere with the testing
• Helps prevent excessive waste of personnel/time resources on faulty methods/tools
• Familiarization for future audits
• Does not have results of the cycle to confirm

The most impactful time to run an audit is during the actual test cycle. It is now that the auditor has results they can confirm by asking the testers to show how they came to them. This allows the auditor to evaluate the tools and the process, as they are utilized, for the most comprehensive feedback potential. 

1. Familiarization with the goals of the project, standards the project must adhere to, and all relevant documentation.
2. Examination of the testing processes and tools the processes are utilizing.
3. Review the communication protocols and test management plan.
4. Interview relevant personnel.
5. Examine a representative sample of test case results and the processes used to obtain them.
6. Evaluate communication and test management in action.
7. Examine processes for potential defect evaluation and correction where applicable.
8. Submit report.

Considerations for during-cycle audit testing include:

• Results exist for comparison and evaluation
• Potential for positive impact on the test cycle in progress
• Simplifies scheduling with all relevant members present during times of testing.
• Can see conflicts between written plan/management and execution in action.
• Adds time and expense to a project

The time when the need of an audit is most noticeable is often after the completion of a test cycle. It is here that a mismatch between expectations and delivery is most visible and the utility of an audit is most easily justified. When an audit is to be conducted post-test cycle, the following process is likely:

1. Familiarization with the goals of the project, standards the project must adhere to, and all relevant documentation.
2. Examination of the testing processes and tools that were used for the test cycle.
3. Review the communication protocols and management plans that were used.
4. Interview relevant personnel.
5. Examine a representative sample of test case results and the processes that were utilized to get them.
6. Examine how many defects were found and corrected. Also, examine how many defects that were found remain.
7. Examine how many defects were not found by the test cycle that have been discovered post-test cycle and their severity.
8. Submit report.

Considerations for after-cycle auditing include:

• All results for comparison and consideration are identifiable.
• Mismatches between expectations and results are most visible and defined.
• Does not interfere with the timeframe of the test cycle.
• Can be used to confirm a positive result/expectation parameter.
• Has no impact on the results of the completed test cycle.