PACT Conformance Testing Checklist

1. Background: Definition of Conformance

Note: The following sections are copied from the tech specs. See the respective technical specification for the latest definition.

A conforming host system is any algorithm realized as software and/or hardware that complies with the relevant normative statements in §6 HTTP REST API.

A conforming requesting data recipient is any algorithm realized as software and/or hardware that complies with the relevant normative statements in §6 HTTP REST API.

This checklist is a recommendation from WBCSD to be used as a reference for the Bilateral Conformance Testing.

Click here to go back to the Conformance Testing guidelines.

2. Checklist of/for Functionality for V1 & V2

2.1. Mandatory Functionality

Action Authenticate

Action ListFootprints

Action GetFootprint
Host system offers its actions under https method only
Host System performs the Authentication Flow for PCF Data exchange as specified in the Pathfinder Technical Specification V2 for all Actions
Host System endpoint follows the Request/ Response syntax for all mandatory actions (Authenticate, ListFootPrints, GetFootPrints) and optional action (Action Events – not applicable for V 1) as specified in the Pathfinder Technical Specification V2
Host System has implemented the Error Responses as specified in the Pathfinder Technical Specification V2 Section 6.9

3. Additional Checklist of/for Functionality for V2

3.1. Mandatory Functionality

Implemented Action Events as specified in Pathfinder Technical Specification V2 and PCF data was exchanged successfully

Or

If not Implemented Action Events then it responded to authenticated Action Events calls with an error response with code NotImplemented

3.2. Optional (sic!) Functionality