...
The following documentation MUST be received by the Ed-Fi Alliance prior to certification. Ed-Fi may ask for clarifications or changes in order to ensure clarity and uniformity.
1. Product
...
Availability Information
See Requirements - Product Availability Information
2. Initial
...
Implementation Verification Information
See Requirements - Implementation Verification
3. Data
...
Mapping
See Requirements - Data Mapping
4. Usage
...
Narrative:
| Expand | ||
|---|---|---|
| ||
A short narrative The usage narrative is a short narrative text account of how the data exchange features to be tested are exposed to product users or otherwise functionality is made available to product users in their product. This information will be part of the certification registry entry. This SHOULD be fewer than 1000 words and can be provided in any common text format (MS Word, .txt file, etc.). |
...
| Expand | ||
|---|---|---|
| ||
The provider will show evidence, via a live, synchronous meeting and screen sharing, the ability to perform the transactional tests listed in Student Information Systems API v3 Certification - Test Scenarios#TestScenarios-TransactionalTestCases This includes exercising the individual API resources. Note that there are often some questions as to what outcome qualifies as "passing" a test, when there are significant data model differences, slight differences in data semantics between systems, use of default values, or other situations. In such cases, the Requirements - Testing Requirements document is used to determine the outcome. Please be aware that actual student data – data — including anonymized or obfuscated data derived from real data – data — MUST NOT be used in certification testing. |
...
| Expand | ||
|---|---|---|
| ||
The provider will show evidence, via a live, synchronous meeting and screen sharing, the ability to perform batch updates. See Student Information Systems API v3 Certification - Test Scenarios#TestScenarios-BatchTestCases for details. |
7. Error
...
Handling Verification Test
| Expand | ||
|---|---|---|
| ||
The provider / API client MUST be able to perform the following actions:
Field work within the Ed-Fi community has revealed that this application behavior is a necessary condition of system interoperability. Accordingly, the test scenarios may include situations in which an API resource (or resources) will be made unavailable to the client, or in which the API reports other errors due to resource availability (e.g., HTTP 500 error). The client is expected to be able to successfully handle such situations. |
...