-
Notifications
You must be signed in to change notification settings - Fork 6
Open
Description
Currently the JCS suite still creates test data by calling on a remote endpoint:
vc-di-eddsa-test-suite/tests/50-jcs-verify.js
Lines 10 to 31 in 720e2b0
| import {issuerNameJCS} from './test-config.js'; | |
| const {tags} = config.suites['eddsa-jcs-2022']; | |
| // only use implementations with `eddsa-jcs-2022` verifiers. | |
| const {match: verifierMatches} = endpoints.filterByTag({ | |
| tags: [...tags], | |
| property: 'verifiers' | |
| }); | |
| describe('eddsa-jcs-2022 (verify)', function() { | |
| let issuedVc; | |
| let credentials; | |
| before(async function() { | |
| const {match: issuerMatches} = endpoints.filterByTag({ | |
| tags: [...tags], | |
| property: 'issuers' | |
| }); | |
| // FIXME: Currently uses 'bovine' as default issuer to issue a verifiable | |
| // credential for the `eddsa-jcs-2022` verifier tests. This needs to be | |
| // updated in future to use either Digital Bazaar or generate the vc using | |
| // `vc-generator` helper. | |
| const [issuer] = issuerMatches.get(issuerNameJCS).endpoints; |
This suite needs to remove all test data creation using endpoints (even outside of the JCS verify suite).
- expand the vc-generator to cover all suites involved with the test
- use that vc-gen to create both rdfc and jcs test fixtures
Metadata
Metadata
Assignees
Labels
No labels