Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Describe nested compose matchers and mismatches with indentation #8

Open
markhobson opened this issue Jul 24, 2015 · 0 comments
Open

Comments

@markhobson
Copy link
Owner

Nested uses of ComposeMatchers.compose lose their hierarchical context. For example:

Expected: a person with title "a" and first name "b" and last name "c" and home address is an address with street "d" and city "e"
     but: title was "x" and home address street was "y" and city was "z"

This should be improved once #7 writes matchers on separate lines:

Expected: a person with title "a"
          and first name "b"
          and last name "c"
          and home address is an address with street "d"
          and city "e"
     but: title was "x"
          and home address street was "y"
          and city was "z"

We should then try to indicate hierarchy with deep indentation:

Expected: a person with title "a"
          and first name "b"
          and last name "c"
          and home address is an address with street "d"
              and city "e"
     but: title was "x"
          and home address street was "y"
              and city was "z"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant