In particular MatchSequencePattern tests for consistency between Enumerable and Queryable and so should be in the tests for each to catch any regressions in either. (Consider how dotnet/corefx#5947 changing the Enumerable API didn't trigger it in CI).
There are some further tests that are really testing Enumerable or Queryable and should be tested along with the relevant assembly, though most are already well covered by the existing tests. And exception is QueryableOfQueryable which hits features of both Queryable and of Expressions but those features of Expressions it touches on are already well covered in parameter an lambda tests.
In particular
MatchSequencePatterntests for consistency betweenEnumerableandQueryableand so should be in the tests for each to catch any regressions in either. (Consider how dotnet/corefx#5947 changing theEnumerableAPI didn't trigger it in CI).There are some further tests that are really testing
EnumerableorQueryableand should be tested along with the relevant assembly, though most are already well covered by the existing tests. And exception isQueryableOfQueryablewhich hits features of bothQueryableand ofExpressionsbut those features ofExpressionsit touches on are already well covered in parameter an lambda tests.