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
Currently we are using different testing libraries across the project. Given that the circuits use mocha (circom_tester) and hardhat for the contracts test use mocha too, it seems wise to stop using jest across all other TS packages in favour of Mocha. The changes will be minimum.
Love it! I suspect this will solve some Jest <> Mocha interface clashing issues I've been facing in this branch: #755 (comment)
My (naive) preference would have been to use Jest over Mocha, given it seems to be overall more popular & better maintained, but if Mocha & Hardhat use Mocha, that sounds like a great reason to just roll with that!
Love it! I suspect this will solve some Jest <> Mocha interface clashing issues I've been facing in this branch: #755 (comment)
My (naive) preference would have been to use Jest over Mocha, given it seems to be overall more popular & better maintained, but if Mocha & Hardhat use Mocha, that sounds like a great reason to just roll with that!
Yea I see the point of using Jest, we can always switch back and solve the issues between mocha<>jest in case mocha is missing some features that we will need in the future. So far it seems like we can run everything as we did befre with ts-mocha 🙂
Currently we are using different testing libraries across the project. Given that the circuits use mocha (circom_tester) and hardhat for the contracts test use mocha too, it seems wise to stop using jest across all other TS packages in favour of Mocha. The changes will be minimum.
This would also help with some issues arising when running typedoc on the repo
The text was updated successfully, but these errors were encountered: