Skip to content

Mock relationship between request and messages #10

@xd009642

Description

@xd009642

Currently, we look at each matcher in a mock independently. However, they should be linked therefore when we have a mock with:

  1. Matching on a path (/stream/json)
  2. Matching on message contents (all messages valid json)

And another mock with:

  1. Matching on a path (/stream/binary)
  2. Matching on message contents (not json messages!)

We should be able to connect to /stream/binary and /stream/json with two different connect_async calls and then after we've picked which request it matches only check those mocks not the others.

This might just be as simple as when we run the request level mocks any that have a false instead of a true we don't retain and we pass in the passing ones to handle_socket and only check them (or pass a list of indexes 🤷 )

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions