Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Testing: Assert on dev revert strings (ape test)
See original GitHub issueOverview
be able to assert using ape.reverts on the dev revert message (it’s like a special comment in the contract source file).
this feature requires #347 transaction tracing in order to see what line of code the failure occurred on. could also just show the failed line of code directly with the assert, but the dev revert string is useful for coverage testing
Specification
with ape.reverts(dev_message="This is a dev message"):
...
The dev_message should be a mutually exclusive parameter from the existing expected_message.
Dependencies
#347
Look at how brownie did it as an example!
https://eth-brownie.readthedocs.io/en/stable/api-test.html#brownie.test.plugin.RevertContextManager
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Completed via https://github.com/ApeWorX/ape/pull/1125
Status update: once https://github.com/ApeWorX/ape/issues/937 is completed this will be able to be finished as well