Release advice

The release advice is created at the end of the test execution. The purpose of the release advice is to provide the client and other stakeholders with a level of insight into the quality of the test object that will allow them to make informed decisions on whether the test object can go on the following stage with its present status. The following phase in this connection refers to a subsequent test level, or production. For that reason, the release advice is usually created under severe pressure of time, since immediately after execution of the last tests and before the test object is released to the next phase, there is usually very little time available. The test manager would do well to have a draft release advice largely prepared towards the end of the last tests, so that only the last test results need to be processed.

The information in the release advice should not actually come as a surprise to the client. He has been kept abreast of developments relevant to him by means of reliable progress reports and, where necessary, risk reports. In order to supply the client with the information necessary at this stage, the release advice should cover at least the following subjects: 

• Recommendation  
  A recommandation as to whether, from the point of view of the testing, it would be advisable to transfer the test object in its present state to the next phase The final decision on whether or not to go on to the next phase does not lie within the test process. Many more factors are at work here, other than those relating to the test process. For example, political or commercial interests that make it impossible to postpone transfer to a subsequent phase, despite a negative release advice. 
• Obtained and unobtained results  
  Which test goals have been achieved and which not, or only to a certain degree? On the basis of test results on characteristics and object parts, the test manager gives his opinion and advice on the test goals set by the client. It is also indicated whether the exit criteria have been met. The number and severity of the open defects play an important role here. Per defect, it is indicated what the consequences are for the organisation. If possible, riskreducing measures are also indicated, such as, for example, a workaround, allowing the test object to go on to the next phase without the defect being solved. 
• Risk estimate  
  During the planning phase at the beginning of the test process, an agreement is made with the client about the extent to which product risks will be covered, and with what degree of thoroughness. For various reasons, it may be decided to cover certain parts less thoroughly with testing than the risk estimate indicates. Moreover, during the test process, all kinds of changes are still usually being made to the original strategy; moreover, the original risk estimate has possibly been adjusted, perhaps resulting in additional or different risks. In this part of the release advice, the test manager points out which characteristics or object parts have not been tested, or have been less thoroughly tested than the risks justify and so present a higher risk. The associated consequences are also shown.