- From: Ken Ebert <ken@sovrin.org>
- Date: Tue, 2 Jul 2019 14:23:28 -0600
- To: Dmitri Zagidulin <dzagidulin@gmail.com>
- Cc: public-vc-wg@w3.org
- Message-ID: <CA+Tjgofp1M7uNo4mfePtbE_DHc4_0Z8QAA=k8+KfL-K0ZVwY-w@mail.gmail.com>
This looks awesome. I found one bug that caused the status tests to be skipped if refresh is marked as not implemented. I reported this in issue #73 and created PR #74 to fix it. On Tue, Jul 2, 2019 at 7:28 AM Dmitri Zagidulin <dzagidulin@gmail.com> wrote: > Hi all, > > The VC Test Suite has been updated (the various advanced features have > been broken out into their own separate sections), and you can view the > current implementation results here: > > > https://w3c.github.io/vc-test-suite/implementations/#conformance-testing-results > > Aside from the changed UI (different sections), a new config option has > been added: > > *Marking Features as Not Supported (explicitly)* > > You can now mark a feature section as skipped in your config file by > adding it to the *sectionsNotSupported *parameter, to explicitly denote > that this feature will not be supported in your implementations. > > For example, if you wanted to skip all features except for the Basic > section, you would add the following to your config.json: > > "sectionsNotSupported": ["schema", "refresh", "evidence", "status", "tou", > "ldp", "jwt", "zkp"] > > (obviously, you should edit that to fit the sections that your > implementation is skipping, if any). > > Implementors are very much encouraged to re-run their test suites and > submit new report PRs to the vc-test-suite repo. > > Dmitri >
Received on Tuesday, 2 July 2019 20:24:02 UTC