A test should fail if expected set contains elements that are not part of actual set.
The exclude/include/join_by should still be respected.
The order should not be relevant, so the behavior should be unordered by default.
The unordered should not be supported

The simplified SQL representation of that comparison would be something like:

--ut.expect(actual).to_include(expected).join_by(pk) 
--ut.expect(actual).to_contain(expected).join_by(pk) 
select *
  from expected
    left join actual 
   on expected.pk = actual.pk
 where actual.row is null;

--ut.expect(actual).to_include(expected)
--ut.expect(actual).to_contain(expected)
select *
  from expected
    left join actual 
   on expected.row_hash = actual.row_hash
 where actual.row_hash is null;

The not_to_inculde should behave differently. As it should fail if any of rows that are expected is included.

--ut.expect(actual).to_include(expected).join_by(pk) 
--ut.expect(actual).to_contain(expected).join_by(pk) 
select *
  from expected
    left join actual 
   on expected.pk = actual.pk
 where actual.pk is not null;

--ut.expect(actual).to_include(expected)
--ut.expect(actual).to_contain(expected)
select *
  from expected
    left join actual 
   on expected.row_hash = actual.row_hash
 where actual.row_hash is not null;

Do you think it's worth implementing?
@lwasylow - do you think it would it be difficult to add?

Add to_include matcher for collections and cursors #79

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions