Sick of using time.sleep in integration/testnet tests? We are too!

[PatrickAlphaC]

time.sleep is really annoying to use when trying to run tests, because the Chainlink node could respond much earlier or much later than the time you give it.

In our chainlink-mix we've added a new function in helpful_scripts called listen_for_event, you can find the function here and an example of using it here.

Here is the docstring that defines what the function does:

def listen_for_event(brownie_contract, event, timeout=200, poll_interval=2):
    """Listen for an event to be fired from a contract.
    We are waiting for the event to return, so this function is blocking.
    Args:
        brownie_contract ([brownie.network.contract.ProjectContract]):
        A brownie contract of some kind.

        event ([string]): The event you'd like to listen for.

        timeout (int, optional): The max amount in seconds you'd like to
        wait for that event to fire. Defaults to 200 seconds.

        poll_interval ([int]): How often to call your node to check for events.
        Defaults to 2 seconds.
    """

Additionally, we've added some quality of life improvements to verification. Happy coding!