Skip to content

Commit

Permalink
update independent impl cli (#17)
Browse files Browse the repository at this point in the history
* update block impl cli

* updates

* updates

* working

* update test cases

* update

* updates

* update tests

* update test mappings and features

* simple reporting working

* update

* sd jwt working

* update

* update readme
  • Loading branch information
decentralgabe authored Dec 13, 2024
1 parent 8dc56c5 commit a3d7321
Show file tree
Hide file tree
Showing 95 changed files with 1,432 additions and 1,711 deletions.
3 changes: 2 additions & 1 deletion .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,8 @@
reports/*.html

# Output
tests/output/*/*/*.json
tests/output/*
!tests/output/.gitkeep

# Logs
logs
Expand Down
17 changes: 12 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ The suite makes use Digital Bazaar's [mocha-w3c-interop-reporter](https://github
```
.
├── implementations/
│ ├── docker-compose.yml
│ ├── compose.yml
│ ├── implementations.json
│ └── [implementation folders]
├── tests/
Expand All @@ -46,10 +46,17 @@ The suite makes use Digital Bazaar's [mocha-w3c-interop-reporter](https://github
This file defines the structure of the test suite. It exports two main objects:

1. `TestResult`: An enum of possible test outcomes (success, failure, indeterminate, error).
2. `GenericTestMapping`: A mapping of test names to their configurations. Each test configuration includes:
2. `TestMapping`: A mapping of test names to their configurations. Each test configuration includes:
- `number`: A unique identifier for the test
- `input_file`: The name of the input file to be used
- `config`: Configuration options for the test, including the `check` property which determines the feature being tested
- `input_file`: The name of the input file to be used, representing:
- For issuance, a JSON unsigned Verifiable Credential or Presentation
- For verification, a signed Verifiable Credential or Presentation, encoded as a JWT string (JOSE),
Base64 string (COSE), or SD-JWT string (Selective Disclosure JWT)
- `key_file`: The name of the key file to be used, representing a Verification Method
- `fn`: The function being tested either `issue` or `verify`
- `disclosure_paths`: An array of paths to be disclosed in a Selective Disclosure JWT (e.g. `["issuer", "validFrom", "credentialSubject.id"]`)
- `feature`: The function being tested, one of `credential_jose`, `credential_cose`, `credential_sdjwt`,
`presentation_jose`, `presentation_cose`, or `presentation_sdjwt`
- `expected_result`: The expected outcome of the test

### test-runner.js
Expand Down Expand Up @@ -92,7 +99,7 @@ To add a new implementation:
Note: if your implementation does not support a feature, set the value to `false`. This will cause the test runner to
skip tests for that feature.

4. Update `implementations/docker-compose.yml` to include your new service:
4. Update `implementations/compose.yml` to include your new service:

```yaml
services:
Expand Down
5 changes: 5 additions & 0 deletions implementations/compose.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
services:
independent:
build: ./independent
volumes:
- ../tests:/tests
9 changes: 0 additions & 9 deletions implementations/docker-compose.yml

This file was deleted.

39 changes: 0 additions & 39 deletions implementations/example-sdk/README.md

This file was deleted.

3 changes: 0 additions & 3 deletions implementations/example-sdk/go.mod

This file was deleted.

Empty file removed implementations/example-sdk/go.sum
Empty file.
79 changes: 0 additions & 79 deletions implementations/example-sdk/main.go

This file was deleted.

119 changes: 0 additions & 119 deletions implementations/example-sdk/validator.go

This file was deleted.

26 changes: 0 additions & 26 deletions implementations/example-server/Dockerfile

This file was deleted.

Loading

0 comments on commit a3d7321

Please sign in to comment.