Skip to content

Should batch consistency be tested with a batch of non-identical items? #1294

@jcaw

Description

@jcaw

The batch_consistency_test.py files check that behaviour is consistent on batches vs. items, but the current infrastructure does this with batches of identical items. This approach may miss bugs related to data leakage between items within a batch, for example #994. I suggest items should be different to ensure those kinds of issues are flagged.

I have an alternate implementation here which uses batches with different items (where possible). Would you like me to open a PR?

(I've just implemented it for the functional tests for now, but I can also expand it to the root batch_consistency_check.py too.)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions