A tester's ride through a function's life cycle

In the video lesson, you met the preprocessing function row_to_list(row). The row comes from a data file and is supposed to contain tab separated housing area and prices. If that's the case, the function returns a list containing housing area and price. But some rows are dirty, containing missing data or separators, and then the function returns None.

The following series of events happens during the function's life cycle.

You add the first implementation of the function.
You add a new feature: the function should work for data separated by a single space (" ") as well as a single tab ("\t").
A bug is reported: the function does not return None for the invalid row " \t293,410\n". You fix it.
You refactor to make the code more compact.

Question

The table illustrates the requirements of the first implementation of the row_to_list() function (Event 1).

Argument	Type	Return value
`"2,081\t314,942\n"`	Valid	`["2,081", "314,942"]`
`"\t293,410\n"`	Invalid	`None`
`"1,463238,765\n"`	Invalid	`None`

row_to_list() is available in the console. Call the function on the listed arguments and check the return values. Does the implementation have any bugs? If yes, which one?

Possible Answers

The function returns None for the argument "2,081\t314,942\n" instead of the correct return value ["2,081", "314,942"].
The function returns ["", "293,410"] for the argument "\t293,410\n" instead of the correct return value None.
The function returns False for the argument "1,463238,765\n" instead of the correct return value None.
The implementation returns the correct value in each case. It is correctly implemented and without bugs.

Take Hint (-7 XP)

Exercise

A tester's ride through a function's life cycle

Instructions 1/4

Question

Possible Answers