Rosco Kalis

I would like to remove the dependency on web3 (used in `createTransactionResult()`). Instead I could perhaps support passing in transaction receipts, along with a contract instance/abi, so the logs in...

In the light of #6 and #9, it could be possible to change the API of the library to be more fluent, allowing additional assertions to be added more easily....

Thanks @zanawar, I agree with the things you said. I think I will get started on implementing some first test version of the basic truffle-assertions functionality (eventEmitted, eventNotEmitted) to see...

I added tests for all methods (except `createTransactionResult()`) to the v1.0 branch. I should still add some tests using fixtures generated with truffle v5 to be sure. With these tests...

Hi @kivanov82 Thank you for opening this bug report. Do you have some example code where this happens so that I can look at what is happening?

Good to hear that you found a workaround for now. I will look at what the best way is to handle this in a more straightforward way in the future.

@PaulRBerg this is definitely one of the more important issues open right now. I've discussed some ways to improve this flow in #1. One thing I'm wondering if the new...

Are these events emitted by the contract that you called a function on or was it emitted in a different contract that was called somewhere in the call stack? Could...

Thanks @TripleSpeeder! This should definitely be supported if it currently isn't. I will look into it.

Hi @StefH This is currently not possible using the library, but it is something that could be implemented. I'll think about how this could be done.