Skip to content

Conversation

vy
Copy link
Member

@vy vy commented Feb 6, 2024

This PR tries to repair, and if cannot, removes ineffective tests.

@vy vy added this to the 2.23.0 milestone Feb 6, 2024
@vy vy requested a review from ppkarwasz February 6, 2024 21:16
@vy vy self-assigned this Feb 6, 2024
Copy link
Contributor

@ppkarwasz ppkarwasz left a comment

Choose a reason for hiding this comment

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

I would keep the misnamed tests and just name them correctly.

@ppkarwasz
Copy link
Contributor

If I can be blunt most of our tests are "ineffective", since they cover a lot of common code, but don't always cover all the functionalities of the tested component.

@vy
Copy link
Member Author

vy commented Feb 8, 2024

@ppkarwasz, I have checked misnamed test classes. If they contain tests that are not covered by other (effective) test classes, I tried to fix them, otherwise, I removed them.

@vy vy merged commit fe6d7f2 into 2.x Feb 8, 2024
@vy vy deleted the 2.x-ineffective-tests branch February 8, 2024 12:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants