This is Markdown file setup_doctest.md

This will be the setup code.

The setup logic makes the names assigned here global to the test module. The code assigns the names math, mylist, a, b, and the function doubler(). Use phmdoctest –setup FIRST to select it. Setup code does not have an output block.

import math

mylist = [1, 2, 3]
a, b = 10, 11

def doubler(x):
    return x * 2

This test case shows the setup names are visible

print("math.pi=", round(math.pi, 3))
print(mylist)
print(a, b)
print("doubler(16)=", doubler(16))

expected output:

math.pi= 3.142
[1, 2, 3]
10 11
doubler(16)= 32

This test case modifies mylist.

The objects created by the –setup code can be modified and blocks run afterward will see the changes.

mylist.append(4)
print(mylist)

expected output:

[1, 2, 3, 4]

The next test case sees the modified mylist.

print(mylist == [1, 2, 3, 4])

expected output:

True

The names created by the setup code are optionally visible to sessions.

When running phmdoctest setup names become visible to sessions by using these options:

• –setup specifies a code block that initializes variables.
• –setup-doctest injects the setup variables into the doctest namespace.

Run the generated test file with pytest.

• Specify –doctest-modules to run the sessions.
• Sessions run in a separate context from the Python code/output block pairs. The setup and teardown get repeated.

The value 55 is appended to mylist. Note that the 4 appended by the test case above is not there. This is because the sessions run in a separate context.

>>> mylist.append(55)
>>> mylist
[1, 2, 3, 55]

The change to mylist made in the session above is visible.

>>> mylist
[1, 2, 3, 55]
>>> round(math.pi, 3)
3.142

This will be specified as the teardown code.

Use phmdoctest –teardown LAST to select it. Teardown code does not have an output block.

mylist.clear()
assert not mylist, "mylist was not emptied"