The respond_to matcher doesn't seem possible

Might be possible if a matcher was dynamically generated by a macro, 
but... ¯\_(ツ)_/¯
This commit is contained in:
Michael Miller 2019-02-01 19:21:31 -07:00
parent 5389a39231
commit 7c8239e55b

View file

@ -113,7 +113,7 @@ In no particular order, features that have been implemented and are planned:
- [ ] Matchers
- [X] Equality matchers - `eq`, `ne`, `be ==`, `be !=`
- [X] Comparison matchers - `lt`, `le`, `gt`, `ge`, `be <`, `be <=`, `be >`, `be >=`, `be_within[.of]`, `be_close`
- [ ] Type matchers - `be_a`, `respond_to`
- [X] Type matchers - `be_a`
- [ ] Collection matchers - `contain`, `have`, `contain_exactly[.in_order|.in_any_order]`, `match_array[.in_order|.in_any_order]`, `start_with`, `end_with`, `be_empty`, `has_key`, `has_value`, `all`, `all_satisfy`
- [X] Truthy matchers - `be`, `be_true`, `be_truthy`, `be_false`, `be_falsey`, `be_nil`
- [ ] Error matchers - `raise_error`