-
Notifications
You must be signed in to change notification settings - Fork 11.8k
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
Add BigNumber support to expectEvent/inLogs #1026
Comments
nventuro
changed the title
expectEvent/inLogs doesn't work for BigNumbers
expectEvent/inLogs could be improved
Jun 18, 2018
frangio
added
feature
New contracts, functions, or helpers.
tests
Test suite and helpers.
labels
Aug 15, 2018
Reopening because we have no issue to track supporting BigNumber equality in |
nventuro
changed the title
expectEvent/inLogs could be improved
Add BigNumber support to expectEvent/inLogs
Aug 16, 2018
6 tasks
jbogacz
added a commit
to jbogacz/openzeppelin-solidity
that referenced
this issue
Sep 20, 2018
* switched direct logs array check to expectEvent method in AllowanceCrowdsale.test.js
jbogacz
added a commit
to jbogacz/openzeppelin-solidity
that referenced
this issue
Sep 20, 2018
* switched direct logs array check to expectEvent method in AllowanceCrowdsale.test.js
jbogacz
added a commit
to jbogacz/openzeppelin-solidity
that referenced
this issue
Sep 20, 2018
* switched direct logs array check to expectEvent method in AllowanceCrowdsale.test.js
jbogacz
added a commit
to jbogacz/openzeppelin-solidity
that referenced
this issue
Sep 21, 2018
* switched direct logs array check to expectEvent method in AllowanceCrowdsale.test.js
nventuro
pushed a commit
that referenced
this issue
Sep 26, 2018
* Add BigNumber support to expectEvent/inLogs (#1026) * switched direct logs array check to expectEvent method in AllowanceCrowdsale.test.js * Refactor expectEvent.inLogs function to use simple value number check * Introduced should.be.bignumber method to compare BigNumber values * Destructure transaction object to extract logs field
nventuro
pushed a commit
that referenced
this issue
Sep 27, 2018
* Add BigNumber support to expectEvent/inLogs (#1026) * switched direct logs array check to expectEvent method in AllowanceCrowdsale.test.js * Refactor expectEvent.inLogs function to use simple value number check * Introduced should.be.bignumber method to compare BigNumber values * Use expectEvent to test logs (#1232) * Removed trailing space
come-maiz
pushed a commit
that referenced
this issue
Oct 21, 2018
* Add BigNumber support to expectEvent/inLogs (#1026) * switched direct logs array check to expectEvent method in AllowanceCrowdsale.test.js * Refactor expectEvent.inLogs function to use simple value number check * Introduced should.be.bignumber method to compare BigNumber values * Destructure transaction object to extract logs field (cherry picked from commit 947de54)
come-maiz
pushed a commit
that referenced
this issue
Oct 21, 2018
* Add BigNumber support to expectEvent/inLogs (#1026) * switched direct logs array check to expectEvent method in AllowanceCrowdsale.test.js * Refactor expectEvent.inLogs function to use simple value number check * Introduced should.be.bignumber method to compare BigNumber values * Use expectEvent to test logs (#1232) * Removed trailing space (cherry picked from commit 536262f)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current equality test fails for BigNumber objects (which have an
equal
method).chai-bignumber
supports these assertions with the chainnumber.should.be.bignumber.equal(otherNumber
).The text was updated successfully, but these errors were encountered: