The specification says:
In practice, implementers validate their resolver against the
<a href="https://github.com/w3c-ccg/did-resolution-mocha-test-suite">DID Resolution Test Suite</a> which exercises
normative MUSTs and error conditions (such as invalid DIDs, deactivated DIDs, unsupported methods,
relative URL expansion, etc.) to ensure that client applications can reliably depend on correct resolution behavior
across different DID methods.
However, that is not the purpose of the test suite--which is to test the features of the specification. The implication creates a misunderstanding of the purpose of the suite, suggesting that it is a compliance mechanism for evaluating the quality of the software. It isn't and shouldn't be interpreted that way, as doing so creates security-impacting misconceptions.
This was fixed in PR#311 and #315, but those are being deconstructed.
The specification says:
However, that is not the purpose of the test suite--which is to test the features of the specification. The implication creates a misunderstanding of the purpose of the suite, suggesting that it is a compliance mechanism for evaluating the quality of the software. It isn't and shouldn't be interpreted that way, as doing so creates security-impacting misconceptions.
This was fixed in PR#311 and #315, but those are being deconstructed.