You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is more of a mocha issue, but in this library's describe block if possibly any assertion or possibly code in a before block is failing it causes the next describe block (in the case of di-ed25519-test-suite this is the crypto specific describe block) to not execute. This results in tests not running. One option might be to explicity to set bail to false in mocha, another possibility is binding the prototype of this test to the parent test suite. This only occurs on failure and might be intermittent.
p.s. above issue suggests the issue might be with chai, if that is the case then using chai as a peerDep to ensure the same chai instance is being used in both tests might work, or passing chai into the function itself.
Potential Culprits:
errors in before blocks
assertions throwing
The text was updated successfully, but these errors were encountered:
This is more of a mocha issue, but in this library's describe block if possibly any assertion or possibly code in a before block is failing it causes the next describe block (in the case of di-ed25519-test-suite this is the crypto specific describe block) to not execute. This results in tests not running. One option might be to explicity to set
bail
to false in mocha, another possibility is binding the prototype of this test to the parent test suite. This only occurs on failure and might be intermittent.Related issue: mochajs/mocha#2781
p.s. above issue suggests the issue might be with chai, if that is the case then using chai as a peerDep to ensure the same
chai
instance is being used in both tests might work, or passing chai into the function itself.Potential Culprits:
before
blocksThe text was updated successfully, but these errors were encountered: