ECHA/2020/666  Annex 1 to Tender Specifications  Technical Specifications Restricted  64 (77) 6.3.2.1. Before the Acceptance Test Phase  6.3.2.2. Acceptance of the Deployment Package  6.3.2.3. Acceptance testing Activities  Closure  Test pass / fail criteria  Prior to entry into Acceptance Test phase, typically any code delivered by the contractor  shall be subject to several technical quality thresholds (ref. section 7.3).  Prior to acceptance testing of the Software, first of all ECHA shall judge whether or not the  delivery is acceptable. Deviations from delivery requirements shall be classified as critical,  major or minor issues, depending on the impact. Details of what the contractor shall deliver can be found in the relevant sections of the  Run, Grow and Transform Work Packages. The contractor shall deliver to ECHA the full  and complete Deployment Package ('deployment kit') containing all the necessary  artefacts, configurations and information that would be necessary to allow ECHA, to  amongst other things, setup the environment, deploy and operate the software. Note,  however, that ECHA shall typically only perform an assessment of the quality of this  Deployment Package, but not actually use it. It is by default the contractor that will always  be the party that performs the deployment of the software, using the Deployment Package.  Details concerning the contractor's responsibility regarding developing and testing the  Software can be found in the relevant sections of the Run, Grow and Transform Work  Packages. It is crucial that the contractor shall test and correct the software until it reaches  the requisite quality threshold / a level of quality that makes it acceptable for deployment  into production, where applicable. ECHA shall simply perform the final formal acceptance  / validation testing. The acceptance of the software is finishing with the successful  deployment in the production environment, unless otherwise agreed in the Specific  contract.  ECHA will specify and run necessary test cases for formal acceptance / validation testing.  If requested by ECHA, the contractor shall support and provide assistance to ECHA's  personnel for the execution of the tests. Typically, the timing, scope, and roles and  responsibilities of the testing will be documented in the Test Plan or Quality Plan.  The Acceptance Testing is under the responsibility of ECHA and may be repeated until the  software attains the acceptance criteria. Based on the outcome of the tests, ECHA will  decide whether the software under test can be 'accepted as is' or can be 'accepted with  reservations' (which will be implemented in future releases of the application) or 'cannot  be accepted'. In the latter case, the changes will need to be implemented and a new  Acceptance Testing cycle will be planned. Each test shall only have been deemed to be successful if the actual result matches the  expected result predicted by the functional and / or non-functional requirements  specifications. If this is not the case, the tester will raise an issue and report that the test  failed. It should be noted that the requirements may also include specific thresholds for  software performance (e.g. response times).  Unless specified otherwise in the specific contracts, the following number of defects that  can be accepted and their criticality shall apply:  • When one critical issue is raised during the Acceptance Testing, the Acceptance  Testing may be interrupted and the software may be rejected.  P.O. Box 400, FI-00121 Helsinki, Finland | Tel. +358 9 686180 | echa.europa.eu 