Please go through the rest of this test and provide some additional comments.

Clarify why we are using total_rows of 7.
Clarify why setting total_rows to 7 despite only have six rows of tabledata is ok/reasonable
Clarify what is at the indexed positions:

• tabledata_list_request_1[1]
• tabledata_list_request_2[1]

Clarify why we are using total_rows of 7.
Clarify why setting total_rows to 7 despite only have six rows of tabledata is ok/reasonable

Done.

Clarify what is at the indexed positions:
tabledata_list_request_1[1]
tabledata_list_request_2[1]

There are comments above the code block explaining that these are the first and the second requests that the client sends to the server.

Here we mention sending page_token, but nowhere in the test do we confirm that page_token is set or that it has been sent, etc.

In fact, while it is correct, with this language in place, it seems weird that in tabledata_resource_2, pagetoken is set to None. The above language implies that we might send something besides None.

Should we revise the language slightly?
Do we mean some other argument/attribute besides page_token?

In the last message, the page token will be empty because there is no following page.

Also, tabledata_resource_2 is what the server returns, not what we pass to the server. The process of sending the page token happens within result = job.result(page_size=page_size, start_index=start_index) and I don't think it's realistic to expose that in unit test.