National Science and Technology Program Completion Testing: Scope, Standards, and Process

National Science and Technology Program completion testing provides independent, standards-based verification that research deliverables meet the technical indicators defined in project task statements before final acceptance. This technical guide explains the scope of completion testing, typical sample types, testing items, evaluation methods, and applicable standards for software, hardware, and material outputs. Discover how accredited third-party laboratories help research teams achieve smooth project acceptance with compliant testing reports.

Technical Overview

National Science and Technology Program completion testing refers to the independent verification and validation activities carried out when a research project funded under a national science and technology program reaches its conclusion phase. In China, publicly funded research projects—such as those under the National Key R&D Program and its predecessor initiatives—are formally closed through a structured acceptance process administered by the competent science and technology authorities. During this process, the undertaking entity must submit objective evidence demonstrating that all quantitative and qualitative technical indicators specified in the approved project task statement have been achieved.

A completion testing report issued by an accredited third-party laboratory serves as the core evidentiary document for this acceptance review. The testing laboratory independently examines the project deliverables—typically software systems, hardware prototypes, intelligent equipment, or new materials—against the acceptance criteria, the contractual technical indicators, and relevant national and international standards. The resulting report is presented to the expert review panel, which uses it to judge whether the project has fulfilled its scientific and technical objectives.

Because the testing conclusion directly influences the acceptance outcome, the report must be produced under a rigorous quality management framework. Reputable testing laboratories operate in accordance with ISO/IEC 17025 (general requirements for the competence of testing and calibration laboratories) and hold national laboratory accreditation and metrology accreditation qualifications, ensuring that the data and conclusions are legally defensible, traceable, and internationally recognized.

Testing Samples

Software Systems and Information Platforms

Application software, management information systems, big data platforms, cloud services, scientific computing software, databases, algorithm libraries, and artificial intelligence models developed as project deliverables. These are evaluated as complete software products covering functional completeness, performance, security, and documentation quality.

Embedded Systems and Intelligent Hardware

Embedded software running on dedicated controllers, industrial control units, robotics platforms, intelligent terminals, communication modules, and Internet of Things devices. Testing covers both the embedded software quality and the electrical, environmental, and electromagnetic compatibility behavior of the host hardware.

Scientific Instruments and Sensor Products

Prototype instruments, precision sensors, detection devices, measurement modules, and analytical apparatus developed through program funding. Testing verifies measurement accuracy, repeatability, stability, and environmental adaptability against the indicators declared in the task statement.

New Materials and Advanced Components

Advanced alloys, composites, functional coatings, electronic components, battery materials, and other material deliverables. Testing is performed using recognized methods from GB, ISO, IEC, ASTM, and EN standard systems to confirm composition, mechanical properties, and performance parameters.

Testing Items

For software and system deliverables, testing items are organized around the software product quality model defined in ISO/IEC 25010 and implemented for evaluation purposes under GB/T 25000.51. Typical testing items include:

• Functional suitability: functional completeness, functional correctness, and functional appropriateness measured against the requirements specification and the project task statement.
• Performance efficiency: response time, throughput, concurrency capacity, and resource utilization under defined load conditions.
• Compatibility: co-existence with other systems and interoperability with specified interfaces, protocols, and data formats.
• Usability: appropriateness of the user interface, learnability, operability, and accessibility of key workflows.
• Reliability: maturity, availability, fault tolerance, and recoverability under normal and abnormal operating conditions.
• Security: confidentiality, integrity, authenticity, non-repudiation, and accountability, evaluated with reference to baseline control sets such as GB/T 22239 where applicable.
• Maintainability: modularity, reusability, analysability, and modifiability, often assessed through static code quality analysis.
• Portability: adaptability, installability, and replaceability across the declared operating environments.
• User documentation: completeness, correctness, and consistency of user manuals and operational documentation.

For hardware, instrumentation, and material deliverables, testing items are determined by the technical indicators of the project and typically include:

• Electrical safety and performance verification of electronic equipment.
• Environmental adaptability testing, including high temperature, low temperature, temperature cycling, damp heat, vibration, and shock, conducted with reference to the GB/T 2423 series (aligned with IEC 60068).
• Electromagnetic compatibility testing, including emissions and immunity, conducted with reference to the GB/T 17626 series (aligned with IEC 61000-4).
• Mechanical, thermal, electrical, and chemical characterization of materials according to the relevant GB, ISO, IEC, ASTM, or EN test methods.
• Accuracy, linearity, repeatability, and long-term stability verification for instruments and sensors.

Testing Methods

Completion testing follows a defined life cycle aligned with ISO/IEC/IEEE 29119 software testing concepts and GB/T 15532 (specification for computer software testing), adapted to the acceptance context. The general workflow proceeds through the following stages:

• Requirements analysis: the laboratory reviews the project task statement, requirement specifications, and acceptance criteria to identify every testable technical indicator.
• Test planning: a test plan is prepared defining scope, test environment, methods, schedule, entry and exit criteria, and risk mitigation measures.
• Test case design: test cases and test procedures are derived from the requirements and indicators, with traceability maintained from each indicator to the corresponding cases.
• Environment construction: a controlled test environment replicating the declared operational configuration is established and verified.
• Test execution: black-box functional testing, performance and load testing, security testing, documentation review, and static analysis are executed, with all defects logged, classified, and tracked to closure.
• Regression testing: corrected defects are retested and impacted functions are re-verified to confirm resolution.
• Report issuance: the completion testing report is issued, stating the tested configuration, the methods applied, the observed results, and a clear conclusion on whether each technical indicator is satisfied.

Methodologically, the laboratory applies a combination of techniques selected according to the deliverable type: equivalence partitioning, boundary value analysis, and decision table methods for functional coverage; automated load generation and monitoring tools for performance measurement; static analyzers and code review for maintainability assessment; and vulnerability scanning combined with manual verification for security evaluation. All measurement results are traceable to calibrated instruments and reference standards, in conformity with ISO/IEC 17025 requirements.

Applications

Completion testing reports are used across a wide range of publicly funded research and development contexts, including:

• Final acceptance of projects under the National Key R&D Program and other national science and technology programs administered by national funding agencies.
• Concluding reviews for projects inherited from earlier national high-technology and basic research initiatives, where independent verification of achieved indicators is required.
• Acceptance of provincial and municipal science and technology projects, technology innovation funds, and major special projects that adopt national acceptance practices.
• Mid-term assessment and milestone verification of long-cycle research projects requiring staged confirmation of technical progress.
• Deliverable handover between undertaking entities, research institutes, universities, and industrial partners, where an independent quality statement supports technology transfer.
• Supporting documentation for achievement appraisal, science and technology awards applications, and intellectual property substantiation.

In each application, the value of the report lies in its independence: because the laboratory has no development interest in the deliverable, its conclusions provide the acceptance authority and the expert panel with impartial, reproducible evidence.

FAQ

Why is third-party testing required for project acceptance?

Acceptance authorities require objective evidence that technical indicators have been met. Self-declared results from the development team lack independence, whereas a report from an accredited third-party laboratory operating under ISO/IEC 17025 provides traceable, impartial verification that satisfies the expert review panel.

What materials must be prepared before testing?

The undertaking entity typically provides the project task statement or contract, requirement specifications, user and operational documentation, a deployable and stable version of the deliverable, access credentials and test data, and a declaration of the target test environment. For hardware and materials, sample units, design documentation, and declared performance parameters are required.

How long does completion testing take?

The duration depends on the number of technical indicators, the scale of the deliverable, and the test types involved. A focused software verification campaign may be completed within a few weeks, while projects combining software, hardware, environmental, and electromagnetic compatibility testing require additional scheduling for chamber time and sample conditioning.

Which standards govern the testing process?

Software evaluation is primarily based on GB/T 25000.51 together with the ISO/IEC 25010 quality model, supported by GB/T 15532 for test process specification and ISO/IEC/IEEE 29119 for testing concepts. Hardware testing references the GB/T 2423 and GB/T 17626 series, and material testing applies the relevant GB, ISO, IEC, ASTM, or EN methods. Laboratory competence is governed by ISO/IEC 17025.

What happens if an indicator fails during testing?

Failures are documented as defects with severity classifications. The development team corrects the issues, and the laboratory performs regression testing to confirm resolution. Only when all declared indicators are satisfied—or when documented deviations are explicitly accepted by the acceptance authority—is a conclusive report issued.

Is the report valid for both national and provincial acceptance?

Yes, provided the report is issued by a laboratory holding valid national accreditation and metrology accreditation qualifications covering the applied test methods. Such reports are recognized by national, provincial, and municipal science and technology acceptance authorities.