-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jest CLI test is failing -- possibly resolver test code issue #111
Comments
Sorry for breaking the imports by referencing a not existing file. Actually the There are also some changes to the Universal Resolver which will fix test failures but we won't be able to have a 100% green testsuite atm. By the end of the week, I will create a PR will all the changes. |
I've opened #114 which should fix most issues. |
After disabling |
This has now been fixed, we put broken implementations in their own grouping (but do run these when generating the final report). |
Running jest (
npm run test
) on the current head of themain
branch produces a lot of errors.While there is at least a minor issue in PR #96 (one file is missing), currently,
There might be some issue with the resolver testing code.
@peacekeeper Since you're the implementer of the test code, would you please kindly check the reason why they're failing?
since
universal-resolver-did-factom.json
is missing, you need to remove the following line indid-resolution/default.js
.I created PR #110 for a temporary workaround.
The text was updated successfully, but these errors were encountered: