Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move TestDocstringCheckerYield to functional tests #5435

Merged
merged 30 commits into from
Nov 29, 2021

Conversation

DanielNoord
Copy link
Collaborator

  • Add yourself to CONTRIBUTORS if you are a new contributor.
  • Write a good description on what the PR does.

Type of Changes

Type
βœ“ πŸ”¨ Refactoring

Description

@Pierre-Sassoulas I've tried to keep a somewhat sane commit history..
This was quite a lot of work and there are 4/5 files like this 😒

@DanielNoord DanielNoord added the Maintenance Discussion or action around maintaining pylint or the dev workflow label Nov 29, 2021
@coveralls
Copy link

coveralls commented Nov 29, 2021

Pull Request Test Coverage Report for Build 1517451127

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 2 unchanged lines in 1 file lost coverage.
  • Overall coverage decreased (-0.01%) to 93.512%

Files with Coverage Reduction New Missed Lines %
pylint/testutils/decorator.py 2 93.94%
Totals Coverage Status
Change from base Build 1516433435: -0.01%
Covered Lines: 13994
Relevant Lines: 14965

πŸ’› - Coveralls

Copy link
Member

@Pierre-Sassoulas Pierre-Sassoulas left a comment

Choose a reason for hiding this comment

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

I've tried to keep a somewhat sane commit history. This was quite a lot of work

Yeah, I can see that, my bad, I'll trust you for the next one πŸ˜„ It's really easy to check with a commit for each thank you. On the other hand copy pasting code is not something with a high probability of mistake either (the 'touchy' part is the config and if it's important and forgotten the test will fail without it).

I just have a remark regarding the place where the functional test were added. Right now extension's functional tests are in tests/functional/ext/extension_name, could you move it in docparams ? I know it's not really organized right now. In particular it's not intuitive that extension should be in ext and not their first letter dir right now. This is something we'll likely discuss in #5396

@Pierre-Sassoulas Pierre-Sassoulas added this to the 2.13.0 milestone Nov 29, 2021
@DanielNoord
Copy link
Collaborator Author

I've tried to keep a somewhat sane commit history. This was quite a lot of work

Yeah, I can see that, my bad, I'll trust you for the next one πŸ˜„ It's really easy to check with a commit for each thank you. On the other hand copy pasting code is not something with a high probability of mistake either (the 'touchy' part is the config and if it's important and forgotten the test will fail without it).

No I think it was actually a fair comment. I just should have split the test into the different styles from the beginning and not at the end. That would have made the history a lot clearer. I will keep that in mind for the other docparams files πŸ˜„

I just have a remark regarding the place where the functional test were added. Right now extension's functional tests are in tests/functional/ext/extension_name, could you move it in docparams ? I know it's not really organized right now. In particular it's not intuitive that extension should be in ext and not their first letter dir right now. This is something we'll likely discuss in #5396

Will do! I guess you approve of the rest? I'll merge after the move then!

@Pierre-Sassoulas
Copy link
Member

I guess you approve of the rest?

Yeap :) !

@DanielNoord DanielNoord modified the milestones: 2.13.0, 2.12.2 Nov 29, 2021
@DanielNoord DanielNoord merged commit f761b32 into pylint-dev:main Nov 29, 2021
@DanielNoord DanielNoord deleted the move-unittests-11 branch November 29, 2021 19:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Maintenance Discussion or action around maintaining pylint or the dev workflow
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants