This is a interoperability report for implementers for the Verifiable Credentials Data Model v2.0 specification.

Conformance Testing Results

These tests were run on

Key

🚫
 Pending
✓
 Passed
❌
 Failed
⊘
 Access Denied
⏱
 Timeout
—
 Not Implemented

The results of the tests are shown below:

Basic Conformance

Implementer ⇒
⇓Test Name
apicatalog.com Aviary Tech Digital Bazaar Gen Digital Kataru Content VC MakoLab OpSecId Procivis One Core SpruceID Trential VC Issuer Mock
A conforming document MUST be secured by at least one securing mechanism as described in Section 4.12 Securing Mechanisms.
✓
✓
✓
❌
Expected Gen Digital to have issued a VC.: expected undefined to exist 
AssertionError: Expected Gen Digital to have issued a VC.: expected undefined to exist
                        at should.exist (node_modules/chai/lib/chai/interface/should.js:144:34)
                        at Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/1.03-conformance.js:47:16)
                        at process.processImmediate (node:internal/timers:483:21)
✓
✓
✓
✓
✓
✓
✓
A conforming issuer implementation MUST include all required properties in the conforming documents it produces.
✓
✓
✓
❌
Expected Gen Digital to have issued a VC.: expected undefined to exist 
AssertionError: Expected Gen Digital to have issued a VC.: expected undefined to exist
                        at should.exist (node_modules/chai/lib/chai/interface/should.js:144:34)
                        at Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/1.03-conformance.js:54:16)
                        at process.processImmediate (node:internal/timers:483:21)
✓
✓
✓
✓
✓
✓
✓
A conforming issuer implementation MUST secure the conforming documents it produces using a securing mechanismdescribed in Section 4.12 Securing Mechanisms.
✓
✓
✓
❌
Expected Gen Digital to have issued a VC.: expected undefined to exist 
AssertionError: Expected Gen Digital to have issued a VC.: expected undefined to exist
                        at should.exist (node_modules/chai/lib/chai/interface/should.js:144:34)
                        at Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/1.03-conformance.js:62:16)
                        at process.processImmediate (node:internal/timers:483:21)
✓
✓
✓
✓
✓
✓
✓
A conforming verifier implementation MUST perform verification on a conforming document as described inSection 4.12 Securing Mechanisms.
✓
✓
✓
❌
Got unwanted rejection: Failed to verify credential. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to verify credential.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/1.03-conformance.js:70:9)
✓
❌
Got unwanted rejection: Failed to verify credential. Actual message: "Request failed with status code 400 Bad Request: POST https://db.makolab.pro/verifiers/credentials/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to verify credential.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://db.makolab.pro/verifiers/credentials/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/1.03-conformance.js:70:9)
✓
✓
✓
✓
✓
A conforming verifier implementation MUST produce errors when non-conforming documents are detected.
✓
✓
✓
✓
✓
❌
Missing expected rejection: Failed to reject malformed VP. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject malformed VP.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/1.03-conformance.js:81:9)
✓
✓
✓
✓
✓

Contexts

Implementer ⇒
⇓Test Name
apicatalog.com Aviary Tech Digital Bazaar Gen Digital Kataru Content VC MakoLab OpSecId Procivis One Core SpruceID Trential VC Issuer Mock
Verifiable credentials MUST include a @context property.
✓
✓
✓
❌
fetch failed 
TypeError: fetch failed
                        at node:internal/deps/undici/undici:13510:13
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async function_ (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/node_modules/ky/distribution/core/Ky.js:21:28)
                        at async _handleResponse (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/node_modules/vc-test-suite-implementations/node_modules/@digitalbazaar/http-client/lib/httpClient.js:101:16)
                        at async makeHttpsRequest (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/node_modules/vc-test-suite-implementations/lib/requests.js:49:14)
                        at async post (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/TestEndpoints.js:71:27)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.03-contexts.js:42:22)
✓
✓
✓
✓
✓
✓
✓
Verifiable presentations MUST include a @context property.
❌
Got unwanted rejection: verifier apicatalog.com rejected VP with valid @context. Actual message: "MissingVerifiable" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: verifier apicatalog.com rejected VP with valid @context.
                    Actual message: "MissingVerifiable"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.03-contexts.js:57:11)
✓
✓
❌
Got unwanted rejection: verifier Gen Digital rejected VP with valid @context. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: verifier Gen Digital rejected VP with valid @context.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.03-contexts.js:57:11)
✓
❌
Missing expected rejection: Failed to reject a VP with a missing @context. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VP with a missing @context.
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.03-contexts.js:63:11)
❌
Got unwanted rejection: verifier OpSecId rejected VP with valid @context. Actual message: "Request failed with status code 400 Bad Request: POST https://vc.opsec.id/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: verifier OpSecId rejected VP with valid @context.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://vc.opsec.id/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.03-contexts.js:57:11)
❌
Got unwanted rejection: verifier Procivis One Core rejected VP with valid @context. Actual message: "Request failed with status code 400 Bad Request: POST https://canivc.core.dev.procivis-one.com/vc-api/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: verifier Procivis One Core rejected VP with valid @context.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://canivc.core.dev.procivis-one.com/vc-api/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.03-contexts.js:57:11)
✓
✓
❌
Got unwanted rejection: verifier VC Issuer Mock rejected VP with valid @context. Actual message: "Request failed with status code 400 Bad Request: POST https://vc-issuer-mock.onrender.com/didkit-http/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: verifier VC Issuer Mock rejected VP with valid @context.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://vc-issuer-mock.onrender.com/didkit-http/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.03-contexts.js:57:11)
Verifiable credentials: The value of the @context property MUST be an ordered set where the first item is a URL with the value https://www.w3.org/ns/credentials/v2.
✓
✓
✓
❌
fetch failed 
TypeError: fetch failed
                        at node:internal/deps/undici/undici:13510:13
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async function_ (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/node_modules/ky/distribution/core/Ky.js:21:28)
                        at async _handleResponse (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/node_modules/vc-test-suite-implementations/node_modules/@digitalbazaar/http-client/lib/httpClient.js:101:16)
                        at async makeHttpsRequest (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/node_modules/vc-test-suite-implementations/lib/requests.js:49:14)
                        at async post (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/TestEndpoints.js:71:27)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.03-contexts.js:71:20)
✓
✓
✓
✓
✓
✓
✓
Verifiable presentations: The value of the @context property MUST be an ordered set where the first item is a URL with the value https://www.w3.org/ns/credentials/v2.
✓
✓
✓
✓
✓
❌
Missing expected rejection: Failed to reject a VP that has the wrong context order. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VP that has the wrong context order.
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.03-contexts.js:89:9)
✓
✓
✓
✓
✓
Verifiable Credential `@context`: "Subsequent items in the ordered set MUST be composed of any combination of URLs and/or objects where each is processable as a JSON-LD Context."
❌
Got unwanted rejection: Failed to support objects in the `@context` Array. Actual message: "Invalid context value type. Expected JsonString but got [{"ExampleVerifiableCredential":"https://example.org/#ExampleVerifiableCredential"}]." 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to support objects in the `@context` Array.
                    Actual message: "Invalid context value type. Expected JsonString but got [{"ExampleVerifiableCredential":"https://example.org/#ExampleVerifiableCredential"}]."
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.03-contexts.js:114:9)
✓
✓
❌
Got unwanted rejection: Failed to support multiple `@context` URLs. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to support multiple `@context` URLs.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.03-contexts.js:111:9)
✓
❌
Got unwanted rejection: Failed to support multiple `@context` URLs. Actual message: "Request failed with status code 400 Bad Request: POST https://db.makolab.pro/issuers/credentials/issue" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to support multiple `@context` URLs.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://db.makolab.pro/issuers/credentials/issue"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.03-contexts.js:111:9)
✓
✓
✓
✓
✓
Verifiable Presentation `@context`: "Subsequent items in the ordered set MUST be composed of any combination of URLs and/or objects where each is processable as a JSON-LD Context."
❌
Got unwanted rejection: Failed to support multiple `@context` URLs in a VP. Actual message: "InvalidDocument" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to support multiple `@context` URLs in a VP.
                    Actual message: "InvalidDocument"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.03-contexts.js:132:9)
✓
✓
❌
Got unwanted rejection: Failed to support multiple `@context` URLs in a VP. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to support multiple `@context` URLs in a VP.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.03-contexts.js:132:9)
✓
❌
Missing expected rejection: Failed to reject a VP with an invalid `@context` URL. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VP with an invalid `@context` URL.
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.03-contexts.js:150:9)
❌
Got unwanted rejection: Failed to support multiple `@context` URLs in a VP. Actual message: "Request failed with status code 400 Bad Request: POST https://vc.opsec.id/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to support multiple `@context` URLs in a VP.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://vc.opsec.id/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.03-contexts.js:132:9)
❌
Got unwanted rejection: Failed to support multiple `@context` URLs in a VP. Actual message: "Request failed with status code 400 Bad Request: POST https://canivc.core.dev.procivis-one.com/vc-api/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to support multiple `@context` URLs in a VP.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://canivc.core.dev.procivis-one.com/vc-api/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.03-contexts.js:132:9)
✓
✓
❌
Got unwanted rejection: Failed to support multiple `@context` URLs in a VP. Actual message: "Request failed with status code 400 Bad Request: POST https://vc-issuer-mock.onrender.com/didkit-http/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to support multiple `@context` URLs in a VP.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://vc-issuer-mock.onrender.com/didkit-http/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.03-contexts.js:132:9)

Identifiers

Implementer ⇒
⇓Test Name
apicatalog.com Aviary Tech Digital Bazaar Gen Digital Kataru Content VC MakoLab OpSecId Procivis One Core SpruceID Trential VC Issuer Mock
If present, the value of the id property MUST be a single URL, which MAY be dereferenceable.
✓
✓
✓
❌
Got unwanted rejection: Failed to accept a VC with a DID credentialSubject identifier. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with a DID credentialSubject identifier.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.04-identifiers.js:34:9)
✓
❌
Got unwanted rejection: Failed to accept a VC with a valid identifier. Actual message: "Request failed with status code 400 Bad Request: POST https://db.makolab.pro/issuers/credentials/issue" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with a valid identifier.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://db.makolab.pro/issuers/credentials/issue"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.04-identifiers.js:43:9)
✓
✓
✓
✓
✓

Types

Implementer ⇒
⇓Test Name
apicatalog.com Aviary Tech Digital Bazaar Gen Digital Kataru Content VC MakoLab OpSecId Procivis One Core SpruceID Trential VC Issuer Mock
Verifiable credentials MUST contain a type property with an associated value.
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
Verifiable presentations MUST contain a type property with an associated value.
✓
✓
✓
✓
✓
❌
Missing expected rejection: Failed to reject a VP without a type. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VP without a type.
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.05-types.js:43:9)
✓
✓
✓
✓
✓
The value of the type property MUST be one or more terms and/or absolute URL strings.
❌
Got unwanted rejection: Failed to accept a VC with an additional type defined in the `@context`. Actual message: "Invalid context value type. Expected JsonString but got [{"ExampleTestCredential":"https://example.org/#ExampleTestCredential"}]." 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with an additional type defined in the `@context`.
                    Actual message: "Invalid context value type. Expected JsonString but got [{"ExampleTestCredential":"https://example.org/#ExampleTestCredential"}]."
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.05-types.js:57:9)
✓
✓
❌
Got unwanted rejection: Failed to accept a VC with an additional type as a URL. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with an additional type as a URL.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.05-types.js:53:9)
✓
✓
✓
✓
✓
✓
✓
If more than one (type) value is provided, the order does not matter.
✓
✓
✓
❌
Got unwanted rejection: Failed to accept a VC with different type array ordering (VC type last). Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with different type array ordering (VC type last).
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.05-types.js:76:9)
✓
✓
✓
✓
✓
✓
✓
Verifiable Credential objects MUST have a type specified.
✓
✓
✓
❌
Got unwanted rejection: Failed to accept a VC with additional type. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with additional type.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.05-types.js:90:11)
✓
❌
Got unwanted rejection: Failed to accept a VC with additional type. Actual message: "Request failed with status code 400 Bad Request: POST https://db.makolab.pro/issuers/credentials/issue" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with additional type.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://db.makolab.pro/issuers/credentials/issue"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.05-types.js:90:11)
✓
✓
✓
✓
✓
Verifiable Presentation objects MUST have a type specified.
❌
Got unwanted rejection: Failed to accept VP with `@context` mapped type. Actual message: "MissingVerifiable" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept VP with `@context` mapped type.
                    Actual message: "MissingVerifiable"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.05-types.js:106:11)
✓
✓
❌
Got unwanted rejection: Failed to accept VP with `@context` mapped type. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept VP with `@context` mapped type.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.05-types.js:106:11)
✓
❌
Missing expected rejection: Failed to reject VP missing `VerifiableCredential` type. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject VP missing `VerifiableCredential` type.
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.05-types.js:109:11)
❌
Got unwanted rejection: Failed to accept VP with `@context` mapped type. Actual message: "Request failed with status code 400 Bad Request: POST https://vc.opsec.id/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept VP with `@context` mapped type.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://vc.opsec.id/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.05-types.js:106:11)
❌
Got unwanted rejection: Failed to accept VP with `@context` mapped type. Actual message: "Request failed with status code 400 Bad Request: POST https://canivc.core.dev.procivis-one.com/vc-api/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept VP with `@context` mapped type.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://canivc.core.dev.procivis-one.com/vc-api/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.05-types.js:106:11)
✓
✓
❌
Got unwanted rejection: Failed to accept VP with `@context` mapped type. Actual message: "Request failed with status code 400 Bad Request: POST https://vc-issuer-mock.onrender.com/didkit-http/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept VP with `@context` mapped type.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://vc-issuer-mock.onrender.com/didkit-http/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.05-types.js:106:11)
`credentialStatus` objects MUST have a type specified.
❌
Got unwanted rejection: Failed to accept a VC with `credentialStatus` with a `type`. Actual message: "Invalid context value type. Expected JsonString but got [{"CredentialStatusList2017":"https://example.org/examples#CredentialStatusList2017"}]." 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with `credentialStatus` with a `type`.
                    Actual message: "Invalid context value type. Expected JsonString but got [{"CredentialStatusList2017":"https://example.org/examples#CredentialStatusList2017"}]."
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.05-types.js:120:11)
✓
✓
❌
Got unwanted rejection: Failed to accept a VC with `credentialStatus` with a `type`. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with `credentialStatus` with a `type`.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.05-types.js:120:11)
✓
❌
Missing expected rejection: Failed to reject a VC with `credentialStatus` without a `type`. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with `credentialStatus` without a `type`.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.05-types.js:123:11)
✓
✓
✓
✓
✓
`termsOfUse` objects MUST have a type specified.
❌
Got unwanted rejection: Failed to accept a VC with `termsOfUse` with a `type`. Actual message: "Invalid context value type. Expected JsonString but got [{"OdrlPolicy2017":"https://example.org/examples#OdrlPolicy2017"}]." 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with `termsOfUse` with a `type`.
                    Actual message: "Invalid context value type. Expected JsonString but got [{"OdrlPolicy2017":"https://example.org/examples#OdrlPolicy2017"}]."
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.05-types.js:133:11)
✓
✓
❌
Got unwanted rejection: Failed to accept a VC with `termsOfUse` with a `type`. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with `termsOfUse` with a `type`.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.05-types.js:133:11)
✓
❌
Missing expected rejection: Failed to reject a VC with `termsOfUse` without a `type`. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with `termsOfUse` without a `type`.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.05-types.js:136:11)
✓
✓
✓
✓
✓
`evidence` objects MUST have a type specified.
❌
Got unwanted rejection: Failed to accept a VC with `evidence` with a `type`. Actual message: "Invalid context value type. Expected JsonString but got [{"DocumentVerification2018":"https://example.org/examples#DocumentVerification2018"}]." 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with `evidence` with a `type`.
                    Actual message: "Invalid context value type. Expected JsonString but got [{"DocumentVerification2018":"https://example.org/examples#DocumentVerification2018"}]."
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.05-types.js:146:11)
✓
✓
❌
Got unwanted rejection: Failed to accept a VC with `evidence` with a `type`. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with `evidence` with a `type`.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.05-types.js:146:11)
✓
❌
Missing expected rejection: Failed to reject a VC with `evidence` without a `type`. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with `evidence` without a `type`.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.05-types.js:149:11)
✓
✓
✓
✓
✓
`refreshService` objects MUST have a type specified.
❌
Got unwanted rejection: Failed to accept a VC with `refreshService` with a `type`. Actual message: "Invalid context value type. Expected JsonString but got [{"ExampleRefreshService":"https://example.org/examples#ExampleRefreshService"}]." 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with `refreshService` with a `type`.
                    Actual message: "Invalid context value type. Expected JsonString but got [{"ExampleRefreshService":"https://example.org/examples#ExampleRefreshService"}]."
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.05-types.js:158:11)
✓
✓
❌
Got unwanted rejection: Failed to accept a VC with `refreshService` with a `type`. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with `refreshService` with a `type`.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.05-types.js:158:11)
✓
❌
Missing expected rejection: Failed to reject a VC with `refreshService` without a `type`. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with `refreshService` without a `type`.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.05-types.js:161:11)
✓
✓
✓
✓
✓
`credentialSchema` objects MUST have a type specified.
❌
Got unwanted rejection: Failed to accept a VC with `credentialSchema` with a `type`. Actual message: "Invalid context value type. Expected JsonString but got [{"ExampleJsonSchema":"https://example.org/examples#ExampleJsonSchema"}]." 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with `credentialSchema` with a `type`.
                    Actual message: "Invalid context value type. Expected JsonString but got [{"ExampleJsonSchema":"https://example.org/examples#ExampleJsonSchema"}]."
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.05-types.js:170:11)
✓
✓
❌
Got unwanted rejection: Failed to accept a VC with `credentialSchema` with a `type`. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with `credentialSchema` with a `type`.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.05-types.js:170:11)
✓
❌
Missing expected rejection: Failed to reject `credentialSchema` without a `type`. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject `credentialSchema` without a `type`.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.05-types.js:173:11)
✓
✓
✓
✓
✓

Names and Descriptions

Implementer ⇒
⇓Test Name
apicatalog.com Aviary Tech Digital Bazaar Gen Digital Kataru Content VC MakoLab OpSecId Procivis One Core SpruceID Trential VC Issuer Mock
If present, the value of the name property MUST be a string or a language value object as described in 11.1 Language and Base Direction.
✓
✓
✓
❌
Got unwanted rejection: Failed to accept a VC with a `name` as a string. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with a `name` as a string.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.06-names-and-descriptions.js:48:9)
✓
✓
❌
Timeout of 15000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.06-names-and-descriptions.js) 
Error: Timeout of 15000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.06-names-and-descriptions.js)
                        at listOnTimeout (node:internal/timers:581:17)
                        at process.processTimers (node:internal/timers:519:7)
✓
✓
✓
✓
If present, the value of the description property MUST be a string or a language value object as described in 11.1 Language and Base Direction.
✓
✓
✓
❌
Got unwanted rejection: Failed to accept a VC with `description` as a string. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with `description` as a string.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.06-names-and-descriptions.js:73:9)
✓
✓
❌
Timeout of 15000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.06-names-and-descriptions.js) 
Error: Timeout of 15000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.06-names-and-descriptions.js)
                        at listOnTimeout (node:internal/timers:581:17)
                        at process.processTimers (node:internal/timers:519:7)
✓
✓
✓
✓
If present (on `issuer`), the value of the name property MUST be a string or a language value object as described in 11.1 Language and Base Direction.
✓
✓
✓
❌
Got unwanted rejection: Failed to accept a VC with `issuer.name` as a string. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with `issuer.name` as a string.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.06-names-and-descriptions.js:102:9)
✓
✓
❌
Timeout of 15000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.06-names-and-descriptions.js) 
Error: Timeout of 15000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.06-names-and-descriptions.js)
                        at listOnTimeout (node:internal/timers:581:17)
                        at process.processTimers (node:internal/timers:519:7)
✓
✓
✓
✓
If present (on `issuer`), the value of the description property MUST be a string or a language value object as described in 11.1 Language and Base Direction.
✓
✓
✓
❌
Got unwanted rejection: Failed to accept a VC with `issuer.description` as a string. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with `issuer.description` as a string.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.06-names-and-descriptions.js:128:9)
✓
✓
❌
Timeout of 15000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.06-names-and-descriptions.js) 
Error: Timeout of 15000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.06-names-and-descriptions.js)
                        at listOnTimeout (node:internal/timers:581:17)
                        at process.processTimers (node:internal/timers:519:7)
✓
✓
✓
✓

Issuer

Implementer ⇒
⇓Test Name
apicatalog.com Aviary Tech Digital Bazaar Gen Digital Kataru Content VC MakoLab OpSecId Procivis One Core SpruceID Trential VC Issuer Mock
A verifiable credential MUST have an issuer property.
✓
✓
✓
❌
fetch failed 
TypeError: fetch failed
                        at node:internal/deps/undici/undici:13510:13
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async function_ (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/node_modules/ky/distribution/core/Ky.js:21:28)
                        at async _handleResponse (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/node_modules/vc-test-suite-implementations/node_modules/@digitalbazaar/http-client/lib/httpClient.js:101:16)
                        at async makeHttpsRequest (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/node_modules/vc-test-suite-implementations/lib/requests.js:49:14)
                        at async post (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/TestEndpoints.js:71:27)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.07-issuer.js:34:22)
✓
✓
✓
✓
✓
✓
✓
The value of the issuer property MUST be either a URL or an object containing an id property whose value is a URL; in either case, the issuer selects this URL to identify itself in a globally unambiguous way.
❌
Missing expected rejection: Failed to reject an issuer identifier that was not a URL. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject an issuer identifier that was not a URL.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.07-issuer.js:46:9)
✓
❌
Missing expected rejection: Failed to reject an issuer identifier that was not a URL. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject an issuer identifier that was not a URL.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.07-issuer.js:46:9)
❌
Got unwanted rejection. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.07-issuer.js:44:9)
✓
❌
Missing expected rejection: Failed to reject a null issuer identifier. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a null issuer identifier.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.07-issuer.js:50:9)
✓
✓
✓
✓
✓

Credential Subject

Implementer ⇒
⇓Test Name
apicatalog.com Aviary Tech Digital Bazaar Gen Digital Kataru Content VC MakoLab OpSecId Procivis One Core SpruceID Trential VC Issuer Mock
A verifiable credential MUST contain a credentialSubject property.
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
The value of the credentialSubject property is a set of objects where each object MUST be the subject of one or more claims, which MUST be serialized inside the credentialSubject property.
✓
✓
✓
❌
Got unwanted rejection: Failed to accept a VC with multiple `credentialSubject`s. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with multiple `credentialSubject`s.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.08-credential-subject.js:49:9)
✓
❌
Missing expected rejection: Failed to reject a VC with an empty `credentialSubject`. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with an empty `credentialSubject`.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.08-credential-subject.js:45:9)
✓
✓
✓
✓
✓

Validity Period

Implementer ⇒
⇓Test Name
apicatalog.com Aviary Tech Digital Bazaar Gen Digital Kataru Content VC MakoLab OpSecId Procivis One Core SpruceID Trential VC Issuer Mock
If present, the value of the validFrom property MUST be an [XMLSCHEMA11-2] dateTimeStamp string value representing the date and time the credential becomes valid, which could be a date and time in the future or in the past.
✓
✓
✓
❌
Got unwanted rejection: Failed to accept a VC with a valid `validFrom` date-time. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with a valid `validFrom` date-time.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.09-validity-period.js:37:9)
✓
❌
Missing expected rejection: Failed to reject a VC using an incorrect `validFrom` date-time format. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC using an incorrect `validFrom` date-time format.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.09-validity-period.js:43:9)
✓
✓
✓
✓
✓
If present, the value of the validUntil property MUST be an [XMLSCHEMA11-2] dateTimeStamp string value representing the date and time the credential ceases to be valid, which could be a date and time in the past or in the future.
✓
✓
✓
❌
Got unwanted rejection: Failed to accept a VC with a valid `validUntil` date-time. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with a valid `validUntil` date-time.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.09-validity-period.js:57:9)
✓
❌
Missing expected rejection: Failed to reject a VC using an inccorect `validUntil` date-time format. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC using an inccorect `validUntil` date-time format.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.09-validity-period.js:66:9)
✓
✓
✓
✓
✓
If a validUntil value also exists, the validFrom value MUST express a datetime that is temporally the same or earlier than the datetime expressed by the validUntil value.
✓
✓
✓
❌
Got unwanted rejection: Failed to accept a VC with a `validUntil` after its `validFrom`. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with a `validUntil` after its `validFrom`.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async testTemporality (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/assertions.js:115:3)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.09-validity-period.js:76:9)
✓
✓
✓
✓
✓
✓
✓
If a validFrom value also exists, the validUntil value MUST express a datetime that is temporally the same or later than the datetime expressed by the validFrom value.
✓
✓
✓
❌
Got unwanted rejection: Failed to accept a VC with a `validUntil` after its `validFrom`. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with a `validUntil` after its `validFrom`.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async testTemporality (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/assertions.js:115:3)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.09-validity-period.js:82:9)
✓
✓
✓
✓
✓
✓
✓

Status

Implementer ⇒
⇓Test Name
apicatalog.com Aviary Tech Digital Bazaar Gen Digital Kataru Content VC MakoLab OpSecId Procivis One Core SpruceID Trential VC Issuer Mock
The type property is REQUIRED.
✓
✓
✓
✓
✓
❌
Missing expected rejection: Failed to reject a VC with `credentialStatus` without a `type`. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with `credentialStatus` without a `type`.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.10-status.js:33:9)
✓
✓
✓
✓
✓
The related normative guidance in Section 4.5 Types MUST be followed.
❌
Got unwanted rejection: Failed to accept a VC with `credentialStatus` with a `type`. Actual message: "Invalid context value type. Expected JsonString but got [{"CredentialStatusList2017":"https://example.org/examples#CredentialStatusList2017"}]." 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with `credentialStatus` with a `type`.
                    Actual message: "Invalid context value type. Expected JsonString but got [{"CredentialStatusList2017":"https://example.org/examples#CredentialStatusList2017"}]."
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.10-status.js:42:9)
✓
✓
❌
Got unwanted rejection: Failed to accept a VC with `credentialStatus` with a `type`. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with `credentialStatus` with a `type`.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.10-status.js:42:9)
✓
❌
Missing expected rejection: Failed to reject a VC with `credentialStatus` without a `type`. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with `credentialStatus` without a `type`.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.10-status.js:45:9)
✓
✓
✓
✓
✓
If present (credentialStatus.id), the normative guidance in Section 4.4 Identifiers MUST be followed.
❌
Got unwanted rejection: Failed to accept a VC with `credentialStatus` without an `id`. Actual message: "Invalid context value type. Expected JsonString but got [{"CredentialStatusList2017":"https://example.org/examples#CredentialStatusList2017"}]." 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with `credentialStatus` without an `id`.
                    Actual message: "Invalid context value type. Expected JsonString but got [{"CredentialStatusList2017":"https://example.org/examples#CredentialStatusList2017"}]."
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.10-status.js:54:9)
✓
✓
❌
Got unwanted rejection: Failed to accept a VC with `credentialStatus` without an `id`. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with `credentialStatus` without an `id`.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.10-status.js:54:9)
✓
✓
✓
✓
✓
✓
✓
(If a credentialStatus property is present), The type property is REQUIRED. It is used to express the type of status information expressed by the object. The related normative guidance in Section 4.5 Types MUST be followed.
❌
Got unwanted rejection: Failed to accept a VC with a valid `credentialStatus`. Actual message: "Invalid context value type. Expected JsonString but got [{"CredentialStatusList2017":"https://example.org/examples#CredentialStatusList2017"}]." 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with a valid `credentialStatus`.
                    Actual message: "Invalid context value type. Expected JsonString but got [{"CredentialStatusList2017":"https://example.org/examples#CredentialStatusList2017"}]."
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.10-status.js:79:9)
✓
✓
❌
Got unwanted rejection: Failed to accept a VC with a valid `credentialStatus`. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with a valid `credentialStatus`.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.10-status.js:79:9)
✓
❌
Missing expected rejection: Failed to reject a VC missing `credentialStatus.type`. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC missing `credentialStatus.type`.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.10-status.js:71:9)
✓
✓
✓
✓
✓

Data Schemas

Implementer ⇒
⇓Test Name
apicatalog.com Aviary Tech Digital Bazaar Gen Digital Kataru Content VC MakoLab OpSecId Procivis One Core SpruceID Trential VC Issuer Mock
The value of the credentialSchema property MUST be one or more data schemas that provide verifiers with enough information to determine whether the provided data conforms to the provided schema(s).
✓
✓
✓
❌
Got unwanted rejection: Failed to accept a VC containing a valid `credentialSchema`. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC containing a valid `credentialSchema`.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.11-data-schemas.js:36:9)
✓
✓
✓
✓
✓
✓
✓
Each credentialSchema MUST specify its type (for example, JsonSchema), and an id property that MUST be a URL identifying the schema file.
✓
✓
❌
Missing expected rejection: Failed to reject `credentialSchema` without an `id`. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject `credentialSchema` without an `id`.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.11-data-schemas.js:52:9)
✓
✓
❌
Missing expected rejection: Failed to reject `credentialSchema` without a `type`. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject `credentialSchema` without a `type`.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.11-data-schemas.js:48:9)
✓
✓
✓
✓
✓
If multiple schemas are present, validity is determined according to the processing rules outlined by each associated type property
✓
✓
✓
❌
Got unwanted rejection: Failed to accept a VC containing multiple valid `credentialSchema`. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC containing multiple valid `credentialSchema`.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.11-data-schemas.js:67:9)
✓
✓
✓
✓
✓
✓
✓

Verifiable Presentations

Implementer ⇒
⇓Test Name
apicatalog.com Aviary Tech Digital Bazaar Gen Digital Kataru Content VC MakoLab OpSecId Procivis One Core SpruceID Trential VC Issuer Mock
If [the `id` field is] present, the normative guidance in Section 4.4 Identifiers MUST be followed.
❌
Got unwanted rejection: Expected verifier apicatalog.com to verify a VP with a valid id. Actual message: "InvalidDocument" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Expected verifier apicatalog.com to verify a VP with a valid id.
                    Actual message: "InvalidDocument"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.13-verifiable-presentations.js:39:9)
✓
✓
❌
Got unwanted rejection: Expected verifier Gen Digital to verify a VP with a valid id. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Expected verifier Gen Digital to verify a VP with a valid id.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.13-verifiable-presentations.js:39:9)
✓
✓
❌
Got unwanted rejection: Expected verifier OpSecId to verify a VP with a valid id. Actual message: "Request failed with status code 400 Bad Request: POST https://vc.opsec.id/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Expected verifier OpSecId to verify a VP with a valid id.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://vc.opsec.id/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.13-verifiable-presentations.js:39:9)
❌
Got unwanted rejection: Expected verifier Procivis One Core to verify a VP with a valid id. Actual message: "Request failed with status code 400 Bad Request: POST https://canivc.core.dev.procivis-one.com/vc-api/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Expected verifier Procivis One Core to verify a VP with a valid id.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://canivc.core.dev.procivis-one.com/vc-api/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.13-verifiable-presentations.js:39:9)
✓
✓
❌
Got unwanted rejection: Expected verifier VC Issuer Mock to verify a VP with a valid id. Actual message: "Request failed with status code 400 Bad Request: POST https://vc-issuer-mock.onrender.com/didkit-http/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Expected verifier VC Issuer Mock to verify a VP with a valid id.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://vc-issuer-mock.onrender.com/didkit-http/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.13-verifiable-presentations.js:39:9)
The type property MUST be present.
❌
Got unwanted rejection: Expected verifier apicatalog.com to verify a VP with initial type VerifiablePresentation. Actual message: "MissingVerifiable" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Expected verifier apicatalog.com to verify a VP with initial type VerifiablePresentation.
                    Actual message: "MissingVerifiable"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.13-verifiable-presentations.js:51:11)
✓
✓
❌
Got unwanted rejection: Expected verifier Gen Digital to verify a VP with initial type VerifiablePresentation. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Expected verifier Gen Digital to verify a VP with initial type VerifiablePresentation.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.13-verifiable-presentations.js:51:11)
✓
✓
❌
Got unwanted rejection: Expected verifier OpSecId to verify a VP with initial type VerifiablePresentation. Actual message: "Request failed with status code 400 Bad Request: POST https://vc.opsec.id/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Expected verifier OpSecId to verify a VP with initial type VerifiablePresentation.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://vc.opsec.id/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.13-verifiable-presentations.js:51:11)
❌
Got unwanted rejection: Expected verifier Procivis One Core to verify a VP with initial type VerifiablePresentation. Actual message: "Request failed with status code 400 Bad Request: POST https://canivc.core.dev.procivis-one.com/vc-api/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Expected verifier Procivis One Core to verify a VP with initial type VerifiablePresentation.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://canivc.core.dev.procivis-one.com/vc-api/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.13-verifiable-presentations.js:51:11)
✓
✓
❌
Got unwanted rejection: Expected verifier VC Issuer Mock to verify a VP with initial type VerifiablePresentation. Actual message: "Request failed with status code 400 Bad Request: POST https://vc-issuer-mock.onrender.com/didkit-http/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Expected verifier VC Issuer Mock to verify a VP with initial type VerifiablePresentation.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://vc-issuer-mock.onrender.com/didkit-http/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.13-verifiable-presentations.js:51:11)
One value of this property MUST be VerifiablePresentation, but additional types MAY be included.The related normative guidance in Section 4.5 Types MUST be followed.
❌
Got unwanted rejection: Expected verifier apicatalog.com to verify a VP with initial type VerifiablePresentation. Actual message: "MissingVerifiable" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Expected verifier apicatalog.com to verify a VP with initial type VerifiablePresentation.
                    Actual message: "MissingVerifiable"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.13-verifiable-presentations.js:66:9)
✓
✓
❌
Got unwanted rejection: Expected verifier Gen Digital to verify a VP with initial type VerifiablePresentation. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Expected verifier Gen Digital to verify a VP with initial type VerifiablePresentation.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.13-verifiable-presentations.js:66:9)
✓
✓
❌
Got unwanted rejection: Expected verifier OpSecId to verify a VP with initial type VerifiablePresentation. Actual message: "Request failed with status code 400 Bad Request: POST https://vc.opsec.id/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Expected verifier OpSecId to verify a VP with initial type VerifiablePresentation.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://vc.opsec.id/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.13-verifiable-presentations.js:66:9)
❌
Got unwanted rejection: Expected verifier Procivis One Core to verify a VP with initial type VerifiablePresentation. Actual message: "Request failed with status code 400 Bad Request: POST https://canivc.core.dev.procivis-one.com/vc-api/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Expected verifier Procivis One Core to verify a VP with initial type VerifiablePresentation.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://canivc.core.dev.procivis-one.com/vc-api/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.13-verifiable-presentations.js:66:9)
✓
✓
❌
Got unwanted rejection: Expected verifier VC Issuer Mock to verify a VP with initial type VerifiablePresentation. Actual message: "Request failed with status code 400 Bad Request: POST https://vc-issuer-mock.onrender.com/didkit-http/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Expected verifier VC Issuer Mock to verify a VP with initial type VerifiablePresentation.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://vc-issuer-mock.onrender.com/didkit-http/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.13-verifiable-presentations.js:66:9)
The verifiableCredential property MAY be present. The value MUST beone or more verifiable credential and/or enveloped verifiable credential objects (the values MUST NOT be non-object values such as numbers, strings, or URLs).
❌
Got unwanted rejection: Failed to verify a valid VP. Actual message: "InvalidDocument" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to verify a valid VP.
                    Actual message: "InvalidDocument"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.13-verifiable-presentations.js:84:9)
✓
✓
❌
Got unwanted rejection: Failed to verify a valid VP. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to verify a valid VP.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.13-verifiable-presentations.js:84:9)
✓
✓
❌
Got unwanted rejection: Failed to verify a valid VP. Actual message: "Request failed with status code 400 Bad Request: POST https://vc.opsec.id/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to verify a valid VP.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://vc.opsec.id/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.13-verifiable-presentations.js:84:9)
❌
Got unwanted rejection: Failed to verify a valid VP. Actual message: "Request failed with status code 400 Bad Request: POST https://canivc.core.dev.procivis-one.com/vc-api/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to verify a valid VP.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://canivc.core.dev.procivis-one.com/vc-api/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.13-verifiable-presentations.js:84:9)
✓
✓
❌
Got unwanted rejection: Failed to verify a valid VP. Actual message: "Request failed with status code 400 Bad Request: POST https://vc-issuer-mock.onrender.com/didkit-http/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to verify a valid VP.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://vc-issuer-mock.onrender.com/didkit-http/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.13-verifiable-presentations.js:84:9)
If present (holder), the value MUST be either a URL or an object containing an id property.
❌
Got unwanted rejection: Failed to verify a valid VP with holder. Actual message: "InvalidDocument" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to verify a valid VP with holder.
                    Actual message: "InvalidDocument"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.13-verifiable-presentations.js:99:9)
❌
Got unwanted rejection: Failed to verify a valid VP with holder object. Actual message: "Request failed with status code 400 Bad Request: POST https://demo.av1.sh/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to verify a valid VP with holder object.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://demo.av1.sh/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.13-verifiable-presentations.js:106:9)
✓
❌
Got unwanted rejection: Failed to verify a valid VP with holder. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to verify a valid VP with holder.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.13-verifiable-presentations.js:99:9)
✓
✓
❌
Got unwanted rejection: Failed to verify a valid VP with holder. Actual message: "Request failed with status code 400 Bad Request: POST https://vc.opsec.id/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to verify a valid VP with holder.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://vc.opsec.id/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.13-verifiable-presentations.js:99:9)
❌
Got unwanted rejection: Failed to verify a valid VP with holder. Actual message: "Request failed with status code 400 Bad Request: POST https://canivc.core.dev.procivis-one.com/vc-api/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to verify a valid VP with holder.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://canivc.core.dev.procivis-one.com/vc-api/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.13-verifiable-presentations.js:99:9)
✓
✓
❌
Got unwanted rejection: Failed to verify a valid VP with holder. Actual message: "Request failed with status code 400 Bad Request: POST https://vc-issuer-mock.onrender.com/didkit-http/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to verify a valid VP with holder.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://vc-issuer-mock.onrender.com/didkit-http/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4.13-verifiable-presentations.js:99:9)

Enveloped Verifiable Credentials

Implementer ⇒
⇓Test Name
Digital Bazaar OpSecId
The @context property of the object MUST be present and include a context, such as the base context for this specification, that defines at least the id, type, and EnvelopedVerifiableCredential terms as defined by the base context provided by this specification.
✓
✓
The id value of the object MUST be a data: URL [RFC2397] that expresses a secured verifiable credential using an enveloping security scheme, such as Securing Verifiable Credentials using JOSE and COSE [VC-JOSE-COSE].
✓
✓
The type value of the object MUST be EnvelopedVerifiableCredential.
✓
✓

Enveloped Verifiable Presentations

Implementer ⇒
⇓Test Name
Digital Bazaar OpSecId
The @context property of the object MUST be present and include a context, such as the base context for this specification, that defines at least the id, type, and EnvelopedVerifiablePresentation terms as defined by the base context provided by this specification.
✓
✓
The id value of the object MUST be a data: URL [RFC2397] that expresses a secured verifiable presentation using an enveloping securing mechanism, such as Securing Verifiable Credentials using JOSE and COSE [VC-JOSE-COSE].
✓
✓
The type value of the object MUST be EnvelopedVerifiablePresentation.
✓
✓

Advanced Concepts

Implementer ⇒
⇓Test Name
apicatalog.com Aviary Tech Digital Bazaar Gen Digital Kataru Content VC MakoLab OpSecId Procivis One Core SpruceID Trential VC Issuer Mock
When processing the active context defined by the base JSON-LD Context document defined in this specification, compliant JSON-LD-based processors produce an error when a JSON-LD context redefines any term.
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
The value of the relatedResource property MUST be one or more objects of the following form:
❌
Missing expected rejection: Failed to reject a VC with a relatedResource as array of strings. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource as array of strings.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:95:9)
✓
✓
❌
Got unwanted rejection: Failed to accept a VC with valid relatedResource objects. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with valid relatedResource objects.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:69:9)
❌
Got unwanted rejection: Failed to accept a VC with valid relatedResource objects. Actual message: "Invalid credential: missing credentialSubject" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with valid relatedResource objects.
                    Actual message: "Invalid credential: missing credentialSubject"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:69:9)
❌
Missing expected rejection: Failed to reject a VC with a relatedResource as array of strings. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource as array of strings.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:95:9)
✓
✓
❌
Missing expected rejection: Failed to reject a VC with a relatedResource as array of strings. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource as array of strings.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:95:9)
✓
❌
Missing expected rejection: Failed to reject a VC with a relatedResource as array of strings. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource as array of strings.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:95:9)
The identifier for the resource is REQUIRED and conforms to the format defined in Section 4.4 Identifiers.
❌
Missing expected rejection: Failed to reject a VC with a relatedResource with no `id` field. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource with no `id` field.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:108:9)
✓
❌
Missing expected rejection: Failed to reject a VC with a relatedResource with no `id` field. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource with no `id` field.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:108:9)
✓
✓
❌
Missing expected rejection: Failed to reject a VC with a relatedResource with no `id` field. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource with no `id` field.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:108:9)
✓
✓
❌
Missing expected rejection: Failed to reject a VC with a relatedResource with no `id` field. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource with no `id` field.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:108:9)
✓
❌
Missing expected rejection: Failed to reject a VC with a relatedResource with no `id` field. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource with no `id` field.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:108:9)
The value MUST be unique among the list of related resource objects.
❌
Missing expected rejection: Failed to reject a VC with a relatedResource with a duplicate `id` field. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource with a duplicate `id` field.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:125:9)
❌
Missing expected rejection: Failed to reject a VC with a relatedResource with a duplicate `id` field. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource with a duplicate `id` field.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:125:9)
❌
Missing expected rejection: Failed to reject a VC with a relatedResource with a duplicate `id` field. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource with a duplicate `id` field.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:125:9)
✓
✓
❌
Missing expected rejection: Failed to reject a VC with a relatedResource with a duplicate `id` field. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource with a duplicate `id` field.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:125:9)
❌
Missing expected rejection: Failed to reject a VC with a relatedResource with a duplicate `id` field. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource with a duplicate `id` field.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:125:9)
❌
Missing expected rejection: Failed to reject a VC with a relatedResource with a duplicate `id` field. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource with a duplicate `id` field.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:125:9)
❌
Missing expected rejection: Failed to reject a VC with a relatedResource with a duplicate `id` field. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource with a duplicate `id` field.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:125:9)
❌
Missing expected rejection: Failed to reject a VC with a relatedResource with a duplicate `id` field. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource with a duplicate `id` field.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:125:9)
❌
Missing expected rejection: Failed to reject a VC with a relatedResource with a duplicate `id` field. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource with a duplicate `id` field.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:125:9)
Each object associated with relatedResource MUST contain at least a digestSRI or a digestMultibase value.
❌
Missing expected rejection: Failed to reject a VC with a relatedResource with no digest info. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource with no digest info.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:139:9)
✓
❌
Missing expected rejection: Failed to reject a VC with a relatedResource with no digest info. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource with no digest info.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:139:9)
✓
✓
❌
Missing expected rejection: Failed to reject a VC with a relatedResource with no digest info. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource with no digest info.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:139:9)
✓
✓
❌
Missing expected rejection: Failed to reject a VC with a relatedResource with no digest info. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource with no digest info.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:139:9)
✓
❌
Missing expected rejection: Failed to reject a VC with a relatedResource with no digest info. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource with no digest info.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:139:9)
If the digest provided by the issuer does not match the digest computed for the retrieved resource, the conforming verifier implementation MUST produce an error.
❌
Missing expected rejection: Failed to reject a VC with a relatedResource with wrong digest. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource with wrong digest.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:154:9)
❌
Missing expected rejection: Failed to reject a VC with a relatedResource with wrong digest. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource with wrong digest.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:154:9)
❌
Missing expected rejection: Failed to reject a VC with a relatedResource with wrong digest. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource with wrong digest.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:154:9)
✓
✓
❌
Missing expected rejection: Failed to reject a VC with a relatedResource with wrong digest. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource with wrong digest.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:154:9)
❌
Missing expected rejection: Failed to reject a VC with a relatedResource with wrong digest. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource with wrong digest.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:154:9)
❌
Missing expected rejection: Failed to reject a VC with a relatedResource with wrong digest. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource with wrong digest.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:154:9)
❌
Missing expected rejection: Failed to reject a VC with a relatedResource with wrong digest. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource with wrong digest.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:154:9)
❌
Missing expected rejection: Failed to reject a VC with a relatedResource with wrong digest. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource with wrong digest.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:154:9)
❌
Missing expected rejection: Failed to reject a VC with a relatedResource with wrong digest. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with a relatedResource with wrong digest.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:154:9)
The value of the refreshService property MUST be one or more refresh services that provides enough information to the recipient's software such that the recipient can refresh the verifiable credential.
✓
✓
✓
❌
Got unwanted rejection. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:178:9)
✓
✓
✓
✓
✓
✓
✓
Each refreshService value MUST specify its type.
✓
✓
✓
✓
✓
❌
Missing expected rejection: Failed to reject a VC with `refreshService` without a `type`. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject a VC with `refreshService` without a `type`.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:189:11)
✓
✓
✓
✓
✓
The value of the termsOfUse property MUST specify one or more terms of use policies under which the creator issued the credential or presentation.
❌
Got unwanted rejection. Actual message: "Invalid context value type. Expected JsonString but got [{"OdrlPolicy2017":"https://example.org/examples#OdrlPolicy2017"}]." 
AssertionError [ERR_ASSERTION]: Got unwanted rejection.
                    Actual message: "Invalid context value type. Expected JsonString but got [{"OdrlPolicy2017":"https://example.org/examples#OdrlPolicy2017"}]."
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:202:9)
✓
✓
❌
Got unwanted rejection. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:202:9)
✓
✓
✓
✓
✓
✓
✓
Each termsOfUse value MUST specify its type, for example, IssuerPolicy, and MAY specify its instance id.
❌
Got unwanted rejection. Actual message: "Invalid context value type. Expected JsonString but got [{"OdrlPolicy2017":"https://example.org/examples#OdrlPolicy2017"}]." 
AssertionError [ERR_ASSERTION]: Got unwanted rejection.
                    Actual message: "Invalid context value type. Expected JsonString but got [{"OdrlPolicy2017":"https://example.org/examples#OdrlPolicy2017"}]."
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:210:9)
✓
✓
❌
Got unwanted rejection. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:210:9)
✓
❌
Missing expected rejection. 
AssertionError [ERR_ASSERTION]: Missing expected rejection.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:208:9)
✓
✓
✓
✓
✓
If present, the value associated with the evidence property is a single object or a set of one or more objects.
❌
Got unwanted rejection. Actual message: "Invalid context value type. Expected JsonString but got [{"DocumentVerification2018":"https://example.org/examples#DocumentVerification2018"}]." 
AssertionError [ERR_ASSERTION]: Got unwanted rejection.
                    Actual message: "Invalid context value type. Expected JsonString but got [{"DocumentVerification2018":"https://example.org/examples#DocumentVerification2018"}]."
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:221:9)
✓
✓
❌
Got unwanted rejection. Actual message: "fetch failed" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection.
                    Actual message: "fetch failed"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/5-advanced-concepts.js:221:9)
✓
✓
✓
✓
✓
✓
✓

Algorithms

Implementer ⇒
⇓Test Name
apicatalog.com Aviary Tech Digital Bazaar Gen Digital Kataru Content VC MakoLab OpSecId Procivis One Core SpruceID Trential VC Issuer Mock
This section contains an algorithm that conforming verifier implementations MUST run when verifying a verifiable credential or a verifiable presentation.
❌
Got unwanted rejection: Failed to verify a valid VP. Actual message: "MissingVerifiable" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to verify a valid VP.
                    Actual message: "MissingVerifiable"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/7-algorithms.js:46:9)
✓
❌
Got unwanted rejection: Failed to verify a valid VP. Actual message: "Request failed with status code 400 Bad Request: POST https://vc2.veresverifier.dev/verifiers/z19w7KofwvE2nkJeRVLp8NDxz/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to verify a valid VP.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://vc2.veresverifier.dev/verifiers/z19w7KofwvE2nkJeRVLp8NDxz/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/7-algorithms.js:46:9)
❌
fetch failed 
TypeError: fetch failed
                        at node:internal/deps/undici/undici:13510:13
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async function_ (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/node_modules/ky/distribution/core/Ky.js:21:28)
                        at async _handleResponse (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/node_modules/vc-test-suite-implementations/node_modules/@digitalbazaar/http-client/lib/httpClient.js:101:16)
                        at async makeHttpsRequest (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/node_modules/vc-test-suite-implementations/lib/requests.js:49:14)
                        at async post (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/TestEndpoints.js:71:27)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/7-algorithms.js:38:20)
❌
Missing expected rejection: Failed to reject an invalid VP. 
AssertionError [ERR_ASSERTION]: Missing expected rejection: Failed to reject an invalid VP.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/7-algorithms.js:50:9)
❌
Got unwanted rejection: Failed to verify a valid VC. Actual message: "Request failed with status code 400 Bad Request: POST https://db.makolab.pro/verifiers/credentials/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to verify a valid VC.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://db.makolab.pro/verifiers/credentials/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/7-algorithms.js:40:9)
❌
Got unwanted rejection: Failed to verify a valid VP. Actual message: "Request failed with status code 400 Bad Request: POST https://vc.opsec.id/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to verify a valid VP.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://vc.opsec.id/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/7-algorithms.js:46:9)
❌
Got unwanted rejection: Failed to verify a valid VP. Actual message: "Request failed with status code 400 Bad Request: POST https://canivc.core.dev.procivis-one.com/vc-api/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to verify a valid VP.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://canivc.core.dev.procivis-one.com/vc-api/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/7-algorithms.js:46:9)
✓
✓
❌
Got unwanted rejection: Failed to verify a valid VP. Actual message: "Request failed with status code 400 Bad Request: POST https://vc-issuer-mock.onrender.com/didkit-http/presentations/verify" 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to verify a valid VP.
                    Actual message: "Request failed with status code 400 Bad Request: POST https://vc-issuer-mock.onrender.com/didkit-http/presentations/verify"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/7-algorithms.js:46:9)