dennisdoomen / fluentassertions.mockly / 35120030801

90%

push

github

Add ordering, count and timing assertions on RequestCollection (#97)

* Add ordering, count and timing assertions on RequestCollection

Implements the API proposal from #80:
- ContainRequestsInOrder(params string[]) / (params (HttpMethod, string)[]) asserts
  requests matching URL patterns occurred in the given order (subsequence match).
- ContainRequestsFor(urlPattern, OccurrenceConstraint) / (method, urlPattern, OccurrenceConstraint)
  asserts the number of matching requests using FluentAssertions' Exactly/AtLeast/AtMost/etc.
- AllHaveBeenSentWithin(TimeSpan) asserts all captured requests fall within a given time span
  of each other.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

* Simplify a redundant index computation and exercise all overloads in tests

The failure message for the first missing request in ContainRequestsInOrder
computed the request number as a variable addition even though the branch
only ever runs when the index is zero, tripping a 'useless addition of 0'
code-scanning alert. Replace it with the literal request number.

Also add specs that call the array-plus-because overloads directly and
chain off the returned AndConstraint, so static analysis can see that the
overloads and their return values are genuinely used by consumers, matching
the existing HaveCalledInOrder pattern in this file.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

548 of 648 branches covered (84.57%)

Branch coverage included in aggregate %.

126 of 130 new or added lines in 1 file covered. (96.92%)

963 of 1060 relevant lines covered (90.85%)

24.79 hits per line