Skip to content

Conversation

@IlyaFaer
Copy link
Contributor

@IlyaFaer IlyaFaer commented May 5, 2021

No description provided.

@google-cla google-cla bot added the cla: yes This human has signed the Contributor License Agreement. label May 5, 2021
metadata,
Column("id", Integer, primary_key=True, nullable=True),
Column("text_data", Text),
)
Copy link
Contributor Author

@IlyaFaer IlyaFaer May 5, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The test is actually testing Text type, so I suppose we can make the id column (which is Integer and not directly considered by the test) nullable and without autoincrement (which is not supported anyway). The change makes three more tests passing (there are some cleanup/teardown errors, but the tests themselves are working fine - we'll take a look at cleanups little bit later).

Безымянный

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think #36 PR will cover all text type tests.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#36 does too many overrides. You only need to change several symbols to add manual primary key, but it requires to copy the whole test source code for every failing test.

Plus to this, #36 includes some unclear changes, like this one:

Безымянный

It looks pretty much like a meaningful diverge from the original test. Instead all of it just a single test data override can be done, keeping the original tests as they were.

@IlyaFaer IlyaFaer requested review from AVaksman and larkee May 11, 2021 09:30
Copy link
Contributor

@larkee larkee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please revert the changes to test class ordering. Additionally, could this logic be extended to other test classes or is it unique to TextTest?

@IlyaFaer
Copy link
Contributor Author

Please revert the changes to test class ordering. Additionally, could this logic be extended to other test classes or is it unique to TextTest?

Not sure what does it mean "to test class ordering".

Yeah, I suppose there is a couple of more test cases, which could use the similar data definition override instead of overriding every test - that's what I was talking about earlier. Still, all of the PRs now merged, so it's not very obvious on which tests this logic can be extended. Requires a local revert and closer look.

@larkee
Copy link
Contributor

larkee commented May 25, 2021

Not sure what does it mean "to test class ordering".

Ah, my wording was unclear. The test classes have been reordered e.g. QuotedNameArgumentTest and StringTest have both been moved to a different place. Please revert this reordering so the diff shows the changes more clearly unless there was a reason for the reordering.

Yeah, I suppose there is a couple of more test cases, which could use the similar data definition override instead of overriding every test - that's what I was talking about earlier. Still, all of the PRs now merged, so it's not very obvious on which tests this logic can be extended. Requires a local revert and closer look.

This looks to have been address in #75 so once the reordering has been addresses this LGTM 👍

@IlyaFaer
Copy link
Contributor Author

@larkee, oh, I got it. Reverted.

@IlyaFaer IlyaFaer merged commit 55a367f into main May 25, 2021
@IlyaFaer IlyaFaer deleted the text_nullable branch May 25, 2021 07:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla: yes This human has signed the Contributor License Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants