tf.compat.v1.test.StubOutForTesting

View source on GitHub

Support class for stubbing methods out for unit testing.

tf.compat.v1.test.StubOutForTesting()

Sample Usage:

You want os.path.exists() to always return true during testing.

stubs = StubOutForTesting() stubs.Set(os.path, 'exists', lambda x: 1) ... stubs.CleanUp()

The above changes os.path.exists into a lambda that returns 1. Once the ... part of the code finishes, the CleanUp() looks up the old value of os.path.exists and restores it.

Methods

CleanUp

View source

CleanUp()

Undoes all SmartSet() & Set() calls, restoring original definitions.

Set

View source

Set(
    parent, child_name, new_child
)

In parent, replace child_name's old definition with new_child.

The parent could be a module when the child is a function at module scope. Or the parent could be a class when a class' method is being replaced. The named child is set to new_child, while the prior definition is saved away for later, when UnsetAll() is called.

This method supports the case where child_name is a staticmethod or a classmethod of parent.

Args:

SmartSet

View source

SmartSet(
    obj, attr_name, new_attr
)

Replace obj.attr_name with new_attr.

This method is smart and works at the module, class, and instance level while preserving proper inheritance. It will not stub out C types however unless that has been explicitly allowed by the type.

This method supports the case where attr_name is a staticmethod or a classmethod of obj.

Notes:

Args:

Raises:

SmartUnsetAll

View source

SmartUnsetAll()

Reverses SmartSet() calls, restoring things to original definitions.

This method is automatically called when the StubOutForTesting() object is deleted; there is no need to call it explicitly.

It is okay to call SmartUnsetAll() repeatedly, as later calls have no effect if no SmartSet() calls have been made.

UnsetAll

View source

UnsetAll()

Reverses Set() calls, restoring things to their original definitions.

This method is automatically called when the StubOutForTesting() object is deleted; there is no need to call it explicitly.

It is okay to call UnsetAll() repeatedly, as later calls have no effect if no Set() calls have been made.

__enter__

View source

__enter__()

__exit__

View source

__exit__(
    unused_exc_type, unused_exc_value, unused_tb
)