Unit, Regression, and Integration Testing

What has to be true about your code before it can be tested — and how do unit, regression, and integration tests build on each other?

Finger exercises

Short drills on what this video just taught. Write the code, run the checks, and reveal the answer only if you are stuck.

0 / 5 passed

Exercise 1 of 5

One place to change

Three different places in a program each tidy up a raw name the same way: remove the whitespace around it, fold it to lowercase, and drop every hyphen. One of the three copies has already drifted out of step with the other two. Pull the cleanup into a single function named clean_name so there is exactly one place to change, and give it a docstring answering the video's three questions — what input it expects, what it does, what it returns.

Hint: .strip(), .lower() and .replace() are the three string methods involved.

# The whole cleanup, written once, so every caller gets every future change.
def clean_name(raw):
    # your code here
    return ...

# The whole cleanup, written once, so every caller gets every future change.
def clean_name(raw):
    # your code here
    return ...

Python runs in your browser

⌘/Ctrl + Enter runs

is a function

strips, lowercases and drops hyphens, in one pass

carries a docstring saying what goes in, what happens, what comes out

←Previous Catching a Returned Function: Two Names, One Object Next Black Box vs Glass Box: Where Test Cases Come From →