code: def expect(post_state: Dict[str, Any]=None,
             networks: Any=None,
             transaction: TransactionDict=None) -> Callable[..., Dict[str, Any]]:
  
      
      return partial(_expect, post_state, networks, transaction)
docs: Specify the expected result for the test.
  
      For state tests, multiple expectations can be given, differing in the transaction data, gas
      limit, and value, in the applicable networks, and as a result also in the post state. VM tests
      support only a single expectation with no specified network and no transaction (here, its role
      is played by :func:`~eth.tools.fixtures.fillers.execution`).
  
      * ``post_state`` is a list of state definition in the same form as expected
        by :func:`~eth.tools.fixtures.fillers.pre_state`. State items that are
        not set explicitly default to their pre state.
  
      * ``networks`` defines the forks under which the expectation is applicable. It should be a
          sublist of the following identifiers (also available in `ALL_FORKS`):
  
        * ``"Frontier"``
        * ``"Homestead"``
        * ``"EIP150"``
        * ``"EIP158"``
        * ``"Byzantium"``
  
      * ``transaction`` is a dictionary coming in two variants. For the main shard:
  
        +----------------+-------------------------------+
        | key            | description                   |
        +================+===============================+
        | ``"data"``     | the transaction data,         |
        +----------------+-------------------------------+
        | ``"gasLimit"`` | the transaction gas limit,    |
        +----------------+-------------------------------+
        | ``"gasPrice"`` | the gas price,                |
        +----------------+-------------------------------+
        | ``"nonce"``    | the transaction nonce,        |
        +----------------+-------------------------------+
        | ``"value"``    | the transaction value         |
        +----------------+-------------------------------+
  
      In addition, one should specify either the signature itself (via keys ``"v"``, ``"r"``,
      and ``"s"``) or a private key used for signing (via ``"secretKey"``).