Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

DM-32682: Mock out metadata setting in test #142

Merged
merged 1 commit into from
Dec 6, 2021
Merged

DM-32682: Mock out metadata setting in test #142

merged 1 commit into from
Dec 6, 2021

Commits on Dec 3, 2021

  1. For some subtasks only mock out the run() method 

    With the task mocked out the metadata values calculated
by the task are no longer real values but are themselves
MagicMock objects. MagicMock objects can't be stored in
a TaskMetadata so instead the run methods for the
associator subtasks are explicitly mocked to return
usable data for the metadata.

This works with PropertySet since that seems to accept
the mock value and silently ignores it.
    @timj
    timj committed Dec 3, 2021
    Configuration menu
    Copy the full SHA
    e1e0571 View commit details
    Browse the repository at this point in the history