openzeppelin-test-helpers icon indicating copy to clipboard operation
openzeppelin-test-helpers copied to clipboard

Assertion library for Ethereum smart contract testing

Results 42 openzeppelin-test-helpers issues
Sort by recently updated
recently updated
newest added

Uusing expectRevert in my hardhat tests. It all was fine until upgrading to the latest version of hardhat, now I get: @openzeppelin/test-helpers WARN expectRevert: Assertions may yield false negatives! Revert...

…th the same name (Multiple ABI entries for event error) Solution: remove the resitrcition, modify the filtering function so it can handle multiple events with the same name

Solution: fix event signature calculation routine so that event topic[0] matches

…lved (5 of 12 low, 9 of 34 moderate, 45 of 54 high, 17 of 21 critical) vulnerabilities

I am using openzeppelin-test-helpers to test my project, expectEvent etc is working as I expected but when I call expectRevert, this error is being raised: ``` 1) Contract: Flipa Bets...

I asked about this issue at stackoverflow, but didn't get an answer. As I am not sure, if there is a problem from my side or a real issue, I...

`expectEvent()` is not capturing an expected event (SmartContract is correct and tested in other ways) in [expectEvent()](https://github.com/OpenZeppelin/openzeppelin-test-helpers/blob/6e54db1e1f64a80c7632799776672297bbe543b3/src/expectEvent.js#L23) I has to put: return ({ event: receipt.events[name].event, args: receipt.events[name].args }); instead of:...

Requested in https://github.com/OpenZeppelin/openzeppelin-test-environment/issues/73#issuecomment-629425128. Some prior conversation in https://github.com/OpenZeppelin/openzeppelin-test-helpers/pull/116#issuecomment-611281410.

Since 0.8.4 we have use of new and cheap custom errors https://blog.soliditylang.org/2021/04/21/custom-errors/ Using them in contract code, but in test I need to use expectRevert.uspecified to handle them in any...

The bug caused tests using `expectRevert` to pass despite the revertReason not fully being correct because of the use of `String.prototype.indexOf` to verify if the correct revert reason was contained...